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

Re: [good] Question about NS 1.1


Re:  [good] Question about NS 1.1
>I _think_ it's because of QNames in attribute/element values

Yes.  If QNames were only used for element and attribute names, they
could be (as indeed they are) resolved at parse-time and there would be
no need to keep the prefix -> namespace-name map around afterwards.

But many systems build on top of XML+namespaces - notably XPath - want
to interpret QNames in element content and attribute values, so the
map has to be available in some form or other.  (There is of course
no need to use the Infoset's description of [in-scope namespaces] as
an implementation specification!)

To get around this, you would have to either

 - not use QNames in content, but use some more direct form such as
   {http://example.org}foo, or

 - be able to reliably recognise QNames in content (e.g. a hypothetical
   version of XML might have a syntax for it).

-- Richard

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.