This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
People that don't read the parsing rules do not understand what possibilities the file format has for adding things such as metadata headers. That needs to be clarified. Also add a notice at syntax specification that implementers need to read the parsing section.
I'm not sure we should highlight that. It could encourage people to use it, which we don't want (we don't want people sticking their own headers in there and creating backwards-compatibility headaches when the spec itself wants to use it). It doesn't seem important to know about these things in order to implement the spec or use the file format. Agreed on the latter, of course.
I'm with zewt on this. This is something we shouldn't mention. (e.g. we don't mention it for HTML — the closest we get to it is mentioning one case, in passing, in an example under "Errors that could interfere with new syntax in the future" in an introduction section.)
I don't think we should point out in the syntax where the parser will skip things, if people want to know that they should read the parser section. Telling implementors to read the parser and not the syntax also seems like a rather extreme precaution, one I would like to see implementors complain about before taking. Silvia, I think we should close this bug.
Yes, fair enough.