- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 29 Aug 2008 11:41:49 +0200
- To: "Michael(tm) Smith" <mike@w3.org>
- CC: Jirka Kosek <jirka@kosek.cz>, Henri Sivonen <hsivonen@iki.fi>, HTML WG <public-html@w3.org>
Michael(tm) Smith wrote: > Jirka Kosek <jirka@kosek.cz>, 2008-08-29 10:17 +0200: > >> Henri Sivonen wrote: >>> I'd be OK with <!DOCTYPE html PUBLIC "XSLT-compat">, since it reflects >>> the problem it is solving--making the string resistant to bogus >>> rationalizations about its purpose. >> That's indeed way to go. As HTML5 is not an SGML application there is no >> reason to stick to FPI syntax inside "public identifier". I think that >> this proposal will accommodate all parties. > > A couple of questions/comments - > > - Instead of "XSLT-compat" or some other arbitrary string, why > not just require (if we do decide we want to allow it > there at all) that it just be the empty string? XSLT engines > can output an empty value for it, and it seems to me that if > we have it all, we would want the value to be empty, not some > standard value that would become a de facto public ID and that > apps would lead to the same very real "bogus rationalizations > about its purpose" problem that Henri describes. > ... Good idea. BR, Julian
Received on Friday, 29 August 2008 09:43:01 UTC