• To: Sean McGrath <sean.mcgrath@p...>, xml-dev@l...
• Subject: RE: Interoperability [long]
• From: "Bullard, Claude L (Len)" <clbullar@i...>
• Date: Thu, 15 Nov 2001 11:14:56 -0600

To repeat an old mantra:

"Data is portable.   Systems interoperate."

It isn't as obvious as we would like 
it to be.  That is why having too much 
system information in the content gives 
me the willies.  A long long long time 
ago, islands of automation and seamless 
access to content were discussed as if they 
were the same problem, and for too long, 
people really believed that.

Syntax buys us a lot, though.  It just 
doesn't go the whole way when one can't decide 
if one needs getElementByID() or getElementByAtt(attName, value)
and those are the easy ones.  Tim is amazed at 
the volubility of the original thread.  I'm 
amazed it took this long to get to this thread.

One pass systems are unrealistic.

len

From: Sean McGrath [mailto:sean.mcgrath@p...]

Gosh, where to start! I run into problems flowing XML from
content creation, through editing, through processing, through
content management, through delivery processing.

I would identify these are the most irksome:

<good stuff snipped>

• Prev by Date: Re: Parsing Streaming XML Incrementally
• Next by Date: Re: Regarding XML support for Netscape
• Previous by thread: RE: IDs considered harmful or why keys might be betterthanIDs...
• Next by thread: RE: Interoperability [long]
• Index(es):
  • Date
  • Thread