[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: The privilege of XML parsing - Data types, binary XML and

  • To: 'Sean McGrath' <sean.mcgrath@p...>, xml-dev@l...
  • Subject: RE: The privilege of XML parsing - Data types, binary XML and XMLpipelines (LONG)
  • From: "Bullard, Claude L (Len)" <clbullar@i...>
  • Date: Mon, 9 Dec 2002 13:15:50 -0600

soap binary
David Fallside just posted the rationale for the SOAP decisions 
to subset XML.   Note that SOAP is an infoset specification.

"XMLP WG Response on "SOAP and the Internal Subset""

Well worth reading for insights into the issues of attempting 
to subset XML for the purpose of creating a special purpose 
XML processor.   The comments:

"SOAP messages are specified as XML Infosets -- see [1] (Note, references
are to a snapshot of the latest editors' copies of the SOAP specs,
reflecting some resolutions to last call issues.  I believe the version I
am referencing is the latest that is stable in W3C URI "date space".  It is
later than our last official WD.)  The initial sender prepares a SOAP
message in the form of what the Infoset Recommendation calls a "synthetic
infoset" [2].  In other words, the initial sender typically does not have a
document to parse to produce the infoset;  rather, the initial sender
establishes, using programming structures of its choosing (could be
something like DOM or SAX) the elements, attributes and other content of
the outgoing message."

and

"Of course, the counter argument to all this is:  XML allows internal
subsets and external subsets, lots of off the shelf parsers would implement
them for you, and indeed some might not report the presence of the DTD at
all.  First of all, SOAP is not the only application of XML that requires
parsers to report the presence of DTDs.  Surely an XML editor would as
well.  Indeed, there is no W3C specification for what a general purpose
processor must be, just for what XML is."

are illuminating.   As I said earlier, what is at stake in the syntax 
vs threads and the subsets/profiles threads is the standard definition 
of the semantics of an XML processor.

len


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

[Roger Costello]
I passed your message along to a colleague.  Here are her comments:

 >XML is a syntax.  It has no data model.  So how would one "bury a data
 >model" in it even if one wanted to?

No problem.  Just invent something like XML Schema and the PSVI. Express
processing in terms of infoset items (a data structure) with associated
strong typing information and your done!

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.