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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: Common XML (was Re: Document Feature Requirements)

[ Lists Home | Date Index | Thread Index ]
  • From: David Megginson <david@megginson.com>
  • To: <xml-dev@xml.org>
  • Date: 10 Apr 2000 20:23:30 -0400

"Don Park" <donpark@docuverse.com> writes:

> I would agree with you if it was just the parser and the application
> with nothing in between.  Unfortunately, most e-commerce systems is
> based on N-tier designs with lots of middleware and mediums between
> the data source and the application.  You have to worry, not just
> about the size of the your toilet hole, but all the pipes between
> your home and the sewer plant.  Sorry about my rather yucky
> analogy. <g>

Most e-commerce players are going to use XML only for interchange;
despite the best efforts of self-proclaimed XML vendors, few real
players would be foolish enough to redesign all of their internal
around XML.

That means that you're going to get XML => proprietary internal
storage => XML, where the XML that comes out may or may not bear any
resemblance to the XML that goes in -- elements, attributes, PIs, and
even character data may come out completely transformed (or not at
all), because equivalence will be defined by something other than the
XML markup model.


All the best,


David

-- 
David Megginson                 david@megginson.com
           http://www.megginson.com/

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************




 

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

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