W3C home > Mailing lists > Public > www-tag@w3.org > November 2002

Re: Let's get some principles nailed down

From: Simon St.Laurent <simonstl@simonstl.com>
Date: Fri, 22 Nov 2002 13:35:04 -0500
To: www-tag@w3.org
Message-ID: <r01050400-1022-1E669D26FE4911D696190003937A08C2@[192.168.124.21]>

Noah Mendelsohn writes:
>CP3Revised:  Designers of applications SHOULD when practical define 
>semantics for XML applications in terms of the infoset, as opposed to 
>depending on serial forms.  When using serial forms, any two documents 
>that have the same infoset SHOULD be treated as semantically
equivalent. 

Ouch.  That opens up whole new cans of worms.

Personally, I don't see the Infoset as having much if anything to do
with XML, and definitions based on the Infoset rather than serial forms
sound like a wonderful excuse for organizations to define specs based on
"open" XML and then turn around and use proprietary binary
serializations.

If the TAG really wants to go that route, maybe it's time to just chuck
the misfortune of XML serialization and any notion of "marking up" as a
foundation of markup.

To come back to the original CP3:
>> CP3. When using XML, designers SHOULD NOT introduce 
>> syntax constraints beyond those involved in the 
>> definition of XML.

I've heard fairly regularly of cases where the internal subset is
banned, if not the entire DOCTYPE declaration.  Processing instructions
also seem like a popular bugaboo in some parts, notably the W3C.

Subsets of XML do seem to be proposed (and even used) on a regular
basis.  See, for example:
http://www.simonstl.com/articles/cxmlspec.txt


-- 
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com -- http://monasticxml.org
Received on Friday, 22 November 2002 13:34:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:12 GMT