Altova Mailing List Archives

RE: [xml-dev] How to handle "newline" characters in an XML parser.

From: "Len Bullard" <cbullard@------.--->
To: "'Michael Kay'" <mike@--------.--->, "'Redefined Horizons'" <redefined.horizons@-----.--->, "'Klotz, Leigh'" <Leigh.Klotz@-----.--->
Date: 12/10/2006 2:51:00 AM
He would definitely want to control the distribution and contracts, squeeze
down the network a bit, yes.  I can't quarrel with the effort if it is
useful with some subset of the web community, but in effect, that is what he
is subsetting:  the definition of his user base.  Even then, it isn't
correct to say he does no one a service, just that such a service cannot by
definition have the reach of XML so it does no one a service to make the
claim that it is XML.  

Given that XML does not have a means to express a subset of itself and some
subset of the web user community might find such a thing useful, it is a
weakness of XML declaratively although nothing stops him from making an
instance conformant unless he actually breaks the syntax in so doing.  So
the best and only advice one can give for such a requirement is to return to
SGML and write their own SGML Declaration, in effect, go to the parent and
create a different subset of SGML.  

Lots of luck selling that one. :-)


From: Michael Kay [mailto:mike@s...] 

> I'm so looking forward to the messages from users saying "how 
> do I get [tool x] to serialize my data in a form that the 
> Redefined.Horizons parser will accept?"
> Subsetting XML does no-one a service.
> That's what SGML said about XML.  Kettle is black.

Alright, I'll qualify my statement. Subsetting XML does no one a service
unless the subset is likely to achieve widespread agreement and support.

Michael Kay


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.