Add profanity/offensive words filter attribute

[wicg]

Add profanity/offensive words filter attribute

[marcoscaceres]

That seems like a bug in Chrome (or Google's speech service). The recognition engine should be profanity agnostic. The consuming application should then do its own filtering.

[Ninajoy]

Thank you for your answer.

I can see a bug was registered for this in chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=804812&q=speech%20censored&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified

In the HTML Speech Incubator document in chapter 7.1.2.3 Builtin Default Grammars on https://www.w3.org/2005/Incubator/htmlspeech/XGR-htmlspeech-20111206/ the following was included: It is recommended that speech services support a filter parameter that can be set to the value noOffensiveWords to represent a desire to not recognize offensive words.

Would it therefore be handy, to prevent further misunderstandings about this subject, to change my request to include in the speech-api documentation that the engine should be profanity agnostic?