OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Principles of XML design

[ Lists Home | Date Index | Thread Index ]

On Thu, May 05, 2005 at 04:13:44PM -0700, Joe English wrote:
> Not so weird.  As far as I can tell, other than well-formedness
> and validity errors the XML Rec places no constraints at all on
> what data a processor must report.  That's what the Infoset Rec
> is for.

This is a widely held view of the Infoset.  Officially, however,
the XML Information Set specification only defines a vocabulary:
that is, "if an XML processer returns the name of an element,
this is what you should call the thing that's returned", and so
on for many other items.  The XML Information Set is not exhaustive:
there are XML processors that return things to which the spec has
not assigned a name.  Neither is it mandatory: many XML processors
return a subset of the items listed there.

The informal term "an infoset" meaning "the result of parsing an
XML document and building some sort of different representation,
such as an in-memory graph" is not explicitly licensed by the
Infoset specification, but has led to some people imagining that
the Infoset is intended to define some sort of data model or API.

This is not the case.



Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS