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

Re: Re: determining ID-ness in XML

  • From: David Brownell <david-b@p...>
  • To: veillard@r...
  • Date: Thu, 01 Nov 2001 12:19:11 -0800

Re:  Re: determining ID-ness in XML
>       If the IDness
> of attributes is defined in a DTD then having the instance define this
> property too open wide the door to an array of problems due to the
> conflicts between the DTD and the instance:

Hence my initial enthusiasm for an xml:id-ish solution, if one could
be found that didn't mandate only one ID per element.  (There can be
many reasons to label a node; one-label-per-node restrictions are
trouble when labels get very much use.)  Maybe "xml:ids".


>   It may take quite a bit of time before finding and making decisions
> for all the corner cases associated to an indirect IDness mechanism.

Where the indirection was the "list the ID attributes in the instance"
(the xml:idatts approach) ... a related issue is that such mechanisms
are error prone.  They can work, if everyone agrees.


> If people don't want to do validation, then xml:id should be used, but
> if the document was authored with a DTD in mind, using an indirection
> mechanism to try to bypass the author intent doesn't seems to me to be
> an improvement, quite the opposite. 

I think that's mixing several things up.  "Wanting to do validation" is a
policy issue, unrelated to author intent, just like "wanting to avoid
reading the external subset".  Having a DTD is orthogonal to those,
and is more akin to author intent -- but isn't the same as wanting
to identify particular nodes by name/role (rather than the less stable
notion of "position" or, as Len said, "address").

I think the problem is needing stable node identifiers (by name/role)
that don't force document authors to declare them in internal subsets
(or use Schema-du-jour) to ensure that minimally conformant XML
parsers will see the decls.  So the question becomes where they get
identified.  A "global" definition, like an "xml:ids" attribute, seems to
be the least invasive/error-prone solution yet proposed.

- Dave



PURCHASE STYLUS STUDIO ONLINE TODAY!

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

Buy Stylus Studio Now

Cast Your Vote

We need your help – Vote for DataDirect XML Products!

  • Best SOA or XML site

Winners and finalists announced at SOA World Conference in November.

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-2007 All Rights Reserved.