This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Feedback by Addison Phillips from W3C I18N group: http://lists.w3.org/Archives/Public/public-tt/2015Mar/0057.html I18N comment: http://www.w3.org/International/track/issues/424 http://www.w3.org/TR/webvtt1/#webvtt-file-structure The document structure is described as a sequence of prose. Wouldn't it be better to describe it as a grammar using an established syntax such as ABNF, EBNF, or railroad diagrams? Our WG found the document much harder to comprehend that it might otherwise have been.
Are you asking for an ABNF for creation of just the file structure or for anything in a WebVTT file?
It's almost impossible to write a conformant ABNF for this. I'd regard this as a nice-to-have. I'd be happy to look at a patch for this, though, if you have one.
I can have a look at creating non-normative railroad diagrams.
Can we either provide the diagrams, or close as wontfix (as we do not intend to change the way that VTT is specified at this time)?
Note that if it's helping authors that is desired, we have the guide material at the (admittedly frozen) webplatform docs site. https://docs.webplatform.org/wiki/concepts/VTT_Captioning We need a new place to host this content.
I moved the page wholesale into the Wiki https://www.w3.org/wiki/VTT_Concepts
(In reply to David Singer from comment #6) > I moved the page wholesale into the Wiki > > https://www.w3.org/wiki/VTT_Concepts That's not a formal grammar - that's just an authoring guide.
(In reply to Silvia Pfeiffer from comment #7) > (In reply to David Singer from comment #6) > > I moved the page wholesale into the Wiki > > > > https://www.w3.org/wiki/VTT_Concepts > > That's not a formal grammar - that's just an authoring guide. Yes, agreed. But railroad diagrams would also be only informative, I hope. I don't think we can have both a formal grammar and formal parsing rules without severe risk that they don't match, so I took the previous discussion as saying that No, we won't have a formal grammar, but we'll try to make life easier for authors by supplying railroad diagrams or an authoring guide. In the lack of diagrams, I suggest we at least point towards the guide.
Given the existence of an authoring guide, and our desire not to have normative syntax in addition to normative parsing rules, can we close this issue?
Closing.
Addison, would you mind indicating if you're ok with the resolution of this bug? Thanks