Altova Mailing List Archives

Re: [xml-dev] MicroXML and &

From: Uche Ogbuji <uche@------.--->
To: liam@--.---
Date: 6/1/2012 9:58:00 PM
On Fri, Jun 1, 2012 at 3:41 PM, Liam R E Quin <liam@w...> wrote:

> On Fri, 2012-06-01 at 15:00 -0600, Uche Ogbuji wrote:
> [...]
> > I couldn't even support such an idea in principle. For me, one of the
> > cornerstones of XML's value is in completely determining the lexical
> space.
> > I think leaving entity interpretation to applications would kick a huge
> > hole in that.
> Since an application can substitute an alternate DTD by mapping the
> public or system identifier, this is the status quo today.

So perhaps this is a matter of degree. For one thing, if an app does that,
each entity will at least be consistently (mis)interpreted throughout the
parse of the document, and this (mis)interpretation is still technically in
the lexical domain.

If each entity were reported to the application for interpretation, you
could have the app assign the same entity a completely different value at
different points in the document, which is to me what makes it feel like a
crossing of the line.

Uche Ogbuji             
Poetry ed @TNB:
Founding Partner, Zepheira


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.