• To: xml-dev@l...
• Subject: RE: [ANN] "Future of Software and Databases" NetSeminar(December 3)
• From: Mike Champion <mc@x...>
• Date: Sun, 27 Oct 2002 09:00:33 -0500
• In-reply-to: <004201c27db6$ec917230$6401a8c0@pcukmka>

10/27/2002 7:46:52 AM, "Michael Kay" <michael.h.kay@n...> wrote:


>I think that many of the design decisions in XML (and SGML) can only be
>justified by considering it primarily as an interchange format.
>
>No-one designing a storage format, for example, would have designed it
>so that you can't locate an element by ID except by reading the file
>serially from the beginning. That's why XML databases, even native XML
>databases, don't actually store XML: they store a representation of the
>XML InfoSet optimized for storage and retrieval.

OK, I see your point and more or less agree. SGML or document-oriented XML
may be the "native" storage format for lots of industrial-strength 
applications (aircraft maintenance manuals being the canonical 
example) but the requirement for interchange, interoperability, and usability
by future generations of software totally dominates the design.

I guess I wouldn't want to distinguish "XML" from "a representation of
the XML Infoset" however, but that's another perma-thread.

• References:
  • RE: [ANN] "Future of Software and Databases" NetSeminar (December 3)
    • From: "Michael Kay" <michael.h.kay@n...>

• Prev by Date: RE: ANN: xpath1() scheme for XPointer
• Next by Date: XML cf XML Infoset
• Previous by thread: Re: [ANN] "Future of Software and Databases" NetSeminar (December 3)
• Next by thread: Re: [ANN] "Future of Software and Databases" NetSeminar(December 3)
• Index(es):
  • Date
  • Thread