On 02/08/12 19:40, Philip TAYLOR wrote:
Exactly as you meant it in your earlier message :
I meant it as defined in the HTML5 specification. You're apparently
disallowing that, so I wanted to know what your definition was.
The specification for the parsing process for HTML 4.01 is directly
derivable for the specification for the parsing process for SGML,
taking into account any notes in the DTD where the exact behaviour
could not be specified in SGML or differed therefrom.
And since, as we've already discussed, browsers aren't using the DTDs,
then we know they're all parsing everything pre-HTML5 incorrectly.
To base a specification on what
a particular subset of browsers do at some arbitrary point in time
is to completely fail to understand the reason for a specification
in the first place.
A specification that no-one ever implements is no use to anyone either.
I am unaware of any facility for augmenting the HTML 5
non-DTD in a similar way to get around future failures to conform.
Use the XML serialisation of HTML5 and define your own schema. I know
someone did this for HTML5 + RDFa, there may be some other examples but
I've not followed that sort of thing in detail.
Rob
______________________________________________________________________
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
