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

RE: Stupid Question (was RE: XML doesn't deserve its

  • To: "'Mike Champion'" <mc@x...>, xml-dev@l...
  • Subject: RE: Stupid Question (was RE: XML doesn't deserve its "X".)
  • From: Michael Brennan <Michael_Brennan@A...>
  • Date: Tue, 5 Mar 2002 13:58:30 -0800

xml is stupid
I prefer out-of-band mechanisms for this sort of thing. For one, why presume
that XML Schema types are the only metadata that will be useful for an
application? The practice of annotating the instance itself is limiting, and
inhibits generalized processing of information content (since a generalized
processor cannot distinguish between the information content and annotations
on it without explicit knowledge of the types of annotations allowed).

Microsoft's XML SDK has decent APIs for exposing the XML Schema type of
nodes. I don't know why more tools don't do so. That seems to me a weakness
of the tools. But there are tools out there that let you get at that info.

Beyond that, I'm in favor of generalized approaches such as Schematron,
Schematron-like languages, and the Schema Adjunct Framework as foundations
for attaching metadata to nodes to facilitate processing. That seems to me
to afford a great deal of extensibility to support varying use cases,
without forcing any particular use cases to change to accomodate other
unrelated use cases (which any infrastructural feature runs the risk of
doing).

Annotating instances with the necessary metadata seems to me to be a
slippery slope, and can introduce tighter couplings between processing
applications (since they now have to deal with the annotations as well as
the information content).

> -----Original Message-----
> From: Mike Champion [mailto:mc@x...]
> Sent: Tuesday, March 05, 2002 1:45 PM
> To: xml-dev@l...
> Subject: RE:  Stupid Question (was RE:  XML doesn't
> deserve its "X".)
> 
> 
> 3/5/2002 4:31:40 PM, "Dare Obasanjo" <dareo@m...> wrote:
> 
> >What exactly was your original concern and how is it not solved by
> >xsi:type? 
> 
> I was basically wondering why xsi:type isn't more widely used,
> in the context of Nicolas Lehunen's lament that the PSVI isn't
> widely supported.  Putting the type information in the instance
> would, in my "stupid" thinking, hit the 80:20 point by giving
> applications access to the type of an element without all sorts
> of currently unsupported voodoo.  As with most things, it
> comes down to best practices -- you CAN do lots of good things
> in XML if you carefully choose bits and pieces from the specs
> and roll your own code rather than expecting the parser/validator/
> wizard/whatever to do them for you.
> 
> Or is my basic assumption stupid, and people DO frequently 
> use xsi:type 
> rather than out-of-band schemas for this sort of thing?

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.