Altova Mailing List Archives

Re: [xml-dev] heritage (was Re: [xml-dev] SGML on the Web)

From: Jeni Tennison <jeni@------------.--->
To: Tim Bray <tbray@----------.--->
Date: 10/8/2002 5:57:00 PM
Hi Tim,

> As for the decision, it was all over in about 45 seconds on one
> teleconference, I remember it clearly. Fairly early on in the XML
> design process. Someone (maybe me? I forget) said "er, should we do
> an API as well?" and James Clark said "isn't the idea that there's
> going to be one API that's going to work for all the different
> things you want to do kind of silly?" and everyone said "oh, right"
> and that was that.

But there's a big difference between a data model and an API onto a
data model. The Infoset, for example, isn't an API; you could imagine
many APIs onto the Infoset, which might reveal different parts of the
structure in different ways.

I guess that when I've been talking about a "data model" in this
thread, I've been talking about the Infoset-level data model rather
than the API-level data model. I fully agree that trying to define an
API-level data model would be a complete nightmare, even when you're
in a committee of 3. But agreeing on an Infoset-level data model is
"only" about as burdensome as agreeing on a syntax, at least if my
experience with LMNL is anything to go by.



Jeni Tennison


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.