The trailing " does nothing, though, just as the trailing ] did nothing.
> > This gives a concise and regular notation, it seems.
>
> Yes, and is very much in line with CSS thinking. A few questions
> remain:
>
> - should one also allow the more verbose versions (CLASS=foo,
> ID=x67y) in CSS1?
I think so. This encourages people to build in parsing which is trivially
extended to cope with arbitrary attributes used in selectors when CSS2
arrives.
> - what do people prefer,
> -- #x65y or "x56y" ?
> -- @CLASS=foo or [CLASS=foo] ?
I guess I have already voted ;-) but should point out that the particular
representations of the delimiter tokens were just examples, albeit ones I
would be happy to live with. The important point was that each token should
mean something and that meaning should be explained in human-readable terms
somewhere near the beginning of the CSS 1 document. I was also aiming for
a situation where the parser need not backtrack or buffer; the meaning of
a string should be known before it is read, and everything should be
properly delimited and umambiguous.
-- Chris Lilley, Technical Author and JISC representative to W3C +-------------------------------------------------------------------+ | Manchester and North Training & Education Centre ( MAN T&EC ) | +-------------------------------------------------------------------+ | Computer Graphics Unit, Email: Chris.Lilley@mcc.ac.uk | | Manchester Computing Centre, Voice: +44 161 275 6045 | | Oxford Road, Manchester, UK. Fax: +44 161 275 6040 | | M13 9PL BioMOO: ChrisL | | Timezone: UTC URI: http://info.mcc.ac.uk/CGU/staff/lilley/ | +-------------------------------------------------------------------+