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] Syntax + object model

[ Lists Home | Date Index | Thread Index ]

Having said that, I think the interchange usages of XML will for the
foreseeable future outnumber and outweigh the processing uses.
 
These two use cases aren't competing with one another, BTW.  Nobody is keeping score to see which one is "winning".  
 
Not that Tim is suggesting otherwise, but it seems people lately are way to quick to read "versus" into things which are actually complimentary.  If XML was "just another interchange syntax" or instead "just another data model", it wouldn't be very interesting.  It is interesting in large part because it has affordances for both.

 
________________________________

From: Tim Bray [mailto:tbray@textuality.com]
Sent: Sun 5/25/2003 10:20 AM
To: Mike Champion
Cc: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Syntax + object model



Mike Champion wrote:
>
>
>>  Object models are
>> *local*. Syntax is *global*.
>
> The success of XSLT, XPath, and the (probable) success of at least the
> hard core of XQuery is a strong counter-example to this assertion.

It's much simpler than this, I think.  There are two kinds of things you
do with XML.  First, you use it to interchange data among disparate
systems. Second, you use it as a basis for processing once you've
received it.

The first (interchange) scenario has no requirement whatsoever for a
shared data model: there are a million existence proofs on the ground of
interoperating applications who defined the syntax, got on with the job,
and are now in production.

The second (processing) scenario obviously presupposes a data model,
ranging from the moronically-simple SAX event stream to a detailed
object model with fully worked out thread-safety and concurrency and so
on.  The degree to which object models can be shared from one
programming language to another, or from one OS to another, varies
wildly.  People are claiming thath XPath model works well for a wide
variety of processing scenarios.  I'm inclined to believe this based on
what I've seen so far.

Having said that, I think the interchange usages of XML will for the
foreseeable future outnumber and outweigh the processing uses.

--
Cheers, Tim Bray
         (ongoing fragmented essay: http://www.tbray.org/ongoing/)



-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>







 

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

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