Re: [wss] Revised xml:id proposal

[Anthony Nadalin <drsecure@us.ibm.com>]

Modification

All receivers MAY optionally be able to identify XML elements with a xml:id attribute as  
representing an id attribute and process it accordingly. Senders SHOULD use  
wsu:Id and MAY use xml:id. Note that use of xml:id in conjunction with  
inclusive canonicalization may be inappropriate, as noted in [XMLID]and thus
SHOULD be avoided.


Alternatively, in some cases a xml:id attribute may be used. Both a wsu:ID and xml:id
attribute on a single element MUST not be specified.  
It is an XML requirement that only one id attribute be specified on a  
single element.

Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
Frederick Hirsch <frederick.hirsch@nokia.com>

Frederick Hirsch <frederick.hirsch@nokia.com>

09/19/2005 12:45 PM

To	WSS Oasis <wss@lists.oasis-open.org>
cc	Hirsch Frederick <frederick.hirsch@nokia.com>
Subject	[wss] Revised xml:id proposal

This is a revised proposal to add xml:id to WSS 1.1 core, in response  
to public review comment and discussion on WSS list.

Line numbers below refer to latest draft which is public review with  
subsequent committee changes [1]

This revised proposal incorporates revisions by Paul Cotton [2] and  
changes to address concerns raised by Tony Nadalin [3] and to clarify  
MAYs and SHOULDS [4].

Add to section 4, ID References,

(1) Replace "attribute" at line 494 with

"attribute and the xml:id attribute [XMLID]."

XMLID is a reference to the W3C XML ID Recommendation, to be added to  
the references section of the document.

(2) Replace "are considered" with "are considered (in no particular  
order):" at line

(3) Add additional bullet after line 500:
* Global xml:id attributes on elements

(4) Add following paragraph right before 4.1, after line 504

Tokens and elements that are defined in this specification and  
related profiles to use wsu:Id attributes SHOULD use wsu:Id. Elements  
to be signed MAY use xml:id or wsu:Id, and use of xml:id MAY be  
specified in profiles. All receivers MUST be able to identify XML  
elements carrying a wsu:Id attribute as representing an attribute of  
schema type ID and process it accordingly. All receivers SHOULD be  
able to identify XML elements carrying a xml:id attribute as  
representing an id attribute and process it accordingly. Senders MAY  
use xml:id or wsu:Id. Note that use of xml:id in conjunction with  
inclusive canonicalization may be inappropriate, as noted in [XMLID].

(4) Add following to end of last paragraph in 4.1, at line 521

Alternatively, the xml:id attribute may be used. Applications MUST  
NOT specify both a wsu:ID and xml:id attribute on a single element.  
It is an XML requirement that only one id attribute be specified on a  
single element.

(5) Add reference to xml:id recommendation, section 16,  after XMLENC

[XMLID]             W3C Recommmendation, “xml:id Version 1.0”, 9  
September 2005.


regards, Frederick

Frederick Hirsch
Nokia

[1] http://www.oasis-open.org/apps/org/workgroup/wss/download.php/ 
13961/wss-v1.1-spec-draft-SOAPMessageSecurity-01.pdf

[2] http://www.oasis-open.org/apps/org/workgroup/wss/email/archives/ 
200509/msg00005.html

[3] http://www.oasis-open.org/apps/org/workgroup/wss/email/archives/ 
200509/msg00028.html

[4] http://www.oasis-open.org/apps/org/workgroup/wss/email/archives/ 
200509/msg00007.html


(See attached file: wss-v1.1-spec-pr-SOAPMessageSecurity-01-xmlid03p1.pdf)
(See attached file: wss-v1.1-spec-pr-SOAPMessageSecurity-01-xmlid03p2.pdf)---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 

=?UTF-8?B?d3NzLXYxLjEtc3BlYy1wci1TT0FQTWVzc2FnZVNlY3VyaXR5LTAxLXhtbGlkMDNwMS5wZGY=?=

=?UTF-8?B?d3NzLXYxLjEtc3BlYy1wci1TT0FQTWVzc2FnZVNlY3VyaXR5LTAxLXhtbGlkMDNwMi5wZGY=?=