Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SpeakableSpecification markup is seeing adoption, we should progress it into Core #2053

danbri opened this issue Sep 4, 2018 · 5 comments
Labels vocab General top level tag for issues on the vocabulary


Copy link

danbri commented Sep 4, 2018

The "speakable" construct (see #1389) is doing well. I propose we move it into core.

As broader context, we have been parking terms in until they get actually used for something, to get us past the chicken/egg situation of having perfectly usable proposals stuck in obscure corners of Github. Speakable seems a pretty solid example of something that has taken that path and got adopted, I'd like to show that things don't sit forever in Pending. And as before we can of course continue to refine things within the Core.


  • At Google (/cc @vholland ) we have been using this for the 'Google Assistant' to read out bits of news sites. I will find a few example URLs from sites who are publishing to illustrate adoption.
  • I am not aware of any serious technical issues.
  • The documentation for Google's use of this vocabulary is at
@danbri danbri added vocab General top level tag for issues on the vocabulary For Steering Group Attention labels Sep 4, 2018
@danbri danbri self-assigned this Sep 4, 2018
Copy link

@danbri I'm sure you have seen this already, but the UK Government (GDS) is exploring use of the speakable specification for HowTo content, among other things. They have a goal of providing cross-platform speakable content.

Certainly adds to rationale for transitioning it to core vocabulary.

Copy link

I would support moving this to core. After spending the past year building voice assistants for both Alexa and Google platforms, there's a need to support more voice-friendly content markup. A couple of use cases include:

  • Voice-friendly product names
  • HowTo instructions (tech support, instructional content) that would differ slightly depending on user channel

Copy link

chaals commented Sep 10, 2018

@jaymyers does the stuff there now do what you need?

Copy link

@chaals for the most part, yes. The real challenge for us is an internal define and create the actual strings that would get published

@danbri danbri closed this as completed in 135382d Feb 19, 2019
Copy link

Implemented in release 3.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels vocab General top level tag for issues on the vocabulary
None yet

No branches or pull requests

5 participants