Re: [xml-dev] [ANNOUNCE] New MicroXML draft available

["Pete Cordell" <petexmldev@codalogic.com>]

Thanks John.  I don't interpret the current draft in this way, but I'll have 
a better look and see what I missed.  Maybe the problem is my brain is just 
saying "Yeah, it's namespaces" and not looking at all the details!

Maybe what's needs is an extra sentence along the lines of:

    "A MicroXML parser presents xmlns* attributes to an application as 
regular attributes and does not perform any special processing of these 
attributes.  Nor does a MicroXML parser perform any special processing of 
attributes whose name's include a prefix declared by xmlns* attributes. 
When using an attribute with a namespace prefix, an application SHOULD use 
the namespace name associated with the prefix, rather than the prefix, but 
this is not required."

Feel free to re-write that in English!

Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using C++ XML
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
for more info
----- Original Message ----- 
From: "John Cowan" <cowan@mercury.ccil.org>
To: "Pete Cordell" <petexmldev@codalogic.com>
Cc: "Stephen D Green" <stephengreenubl@gmail.com>; "Peter Flynn" 
<peter@silmaril.ie>; <xml-dev@lists.xml.org>
Sent: Thursday, July 14, 2011 6:50 PM
Subject: Re: [xml-dev] [ANNOUNCE] New MicroXML draft available


>
> Pete Cordell scripsit:
>
>> So, if you had the two documents:
>>
>> <book foo:author="John" xmlns:foo="http://example.com/book"/>
>>
>> and:
>>
>> <book bar:author="John" xmlns:bar="http://example.com/book"/>
>>
>> are they considered the same?
>
> In the MicroXML data model they are different.
>
>> What part does the MicroXML parser play in this interpretation, and
>> what part the application?
>
> An application MAY choose to consider them the same.  If it uses
> Element.getAttributeNamespace or some analogue, it's easy to do so.
>
> -- 
> John Cowan  cowan@ccil.org   http://ccil.org/~cowan
> Assent may be registered by a signature, a handshake, or a click of a 
> computer
> mouse transmitted across the invisible ether of the Internet. Formality
> is not a requisite; any sign, symbol or action, or even willful inaction,
> as long as it is unequivocally referable to the promise, may create a 
> contract.
>       --Specht v. Netscape
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>