W3C home > Mailing lists > Public > public-xmlsec@w3.org > February 2009

ISSUE-63 Need to understand plans and impact of namespace undeclarations

From: Konrad Lanz <Konrad.Lanz@iaik.tugraz.at>
Date: Tue, 24 Feb 2009 21:46:35 +0100
Message-ID: <49A45CAB.8070202@iaik.tugraz.at>
To: Frederick Hirsch <frederick.hirsch@nokia.com>
CC: XMLSec WG Public List <public-xmlsec@w3.org>
Re: Need to understand plans and impact of namespace undeclarations

* In short:

Is http://www.w3.org/1999/11/REC-xpath-19991116-errata/ in force?

* Some Detail:

http://lists.w3.org/Archives/Public/public-xmlsec/2008Sep/0065.html :
> MichaelKay: XPath 1.0 data model can deal with namespace  
> undeclarations, even though not expressed in terms of XML 1.1
>   
> [...]
> klanz2: Should an C14n Vnext render namespace undeclaration on the  
> removal of a namespace node from an element, and is it forced to use  
> XML 1.1? Does the situation change when this namespace is actually  
> used by the element in question?
http://www.w3.org/1999/11/REC-xpath-19991116-errata/ :


> This means that an element will have a namespace node:
>   
>
>    *
>
>       for every attribute on the element or the nearest ancestor
>       element whose name starts with |xmlns:| and whose value is
>       non-empty unless the element itself or a nearer ancestor
>       redeclares the prefix with an empty value;
>

Which means from my reading that there are nodes in the XPath 1.0 data
model for undeclarations.


BR
Konrad

The long version for review:

http://www.w3.org/2007/xmlsec/20070502-klanz-c14n.pdf#page=14
http://tinyurl.com/MT-Konrad-Lanz-OASIS-DSS#page=21&view=FitBH,680 :

http://www.w3.org/2007/xmlsec/20070502-klanz-c14n.pdf#page=16 :
> fixup is necessary in C14n
>  prevent the creation of output

violating the namespace constraint: "Prefix Declared"
Relation to http://www.w3.org/2008/xmlsec/track/issues/26 "Require well
formed XML between transforms"

http://www.w3.org/2007/xmlsec/20070502-klanz-c14n.pdf#page=17
> maintain "undeclarations" ?

This means that an element will have a namespace node:
http://www.w3.org/1999/11/REC-xpath-19991116-errata/ :
>
>    *
>
>       for every attribute on the element or the nearest ancestor
>       element whose name starts with |xmlns:| and whose value is
>       non-empty unless the element itself or a nearer ancestor
>       redeclares the prefix with an empty value;
>

Which means from my reading that there are nodes in the data model for
undeclarations.

This however in conflict with Richard Tobin's reading
http://lists.w3.org/Archives/Public/public-xml-core-wg/2007Mar/0021.html,
who might have overlooked the errata.

http://lists.w3.org/Archives/Public/public-xml-core-wg/2007Mar/0021.html

Discussions in our WG on namespace undeclarations:

http://lists.w3.org/Archives/Public/public-xmlsec/2008Aug/0011.html
http://lists.w3.org/Archives/Public/public-xmlsec/2008Sep/0065.html
> 2) Joint discussion with XSL WG


BR
Konrad

-- 
Konrad Lanz, IAIK/SIC - Graz University of Technology
Inffeldgasse 16a, 8010 Graz, Austria
Tel: +43 316 873 5547
Fax: +43 316 873 5520
http://www.iaik.tugraz.at/content/about_iaik/people/lanz_konrad/
http://jce.iaik.tugraz.at/sic/products/xml_security/

Downlaod certificate chain (including the EuroPKI root certificate):
http://ca.iaik.tugraz.at/capso/certs.jsp



Received on Tuesday, 24 February 2009 20:47:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:43:57 GMT