Alignment with Web Services Security

[Farrukh Najmi <Farrukh.Najmi@Sun.COM>]

Team,

The Web Services Security 1.0 specs are in OASIS member review for 
becoming an OASIS standard
(see announcement below from earlier this month).

I would like to propose that we consider the issue of whether we should 
align V3 with the WSS
specs.

I have read the specs and have found one small but significant issue for 
its use by us.

Section 4 of the The " Web Services Security: SOAP Message Security 1.0" 
spec
specifies wsu:Id as an xsd:ID type. This prevents the possibility of 
using URI or UUID as an id.
This is an unfortunate restriction because many systems (including ebXML 
Registry) use urn:uuid based ids and also other
URNs as ids.

Recall that we ran into this exact situation in ebXML Registry specs and 
decided to change the type of our id attribute
to string from xsd:ID.

This issue need to be addressed IMO by the WSS TC in order for us to use 
the WSS specs.
If it were addressed then I would be in favour of aliging with this spec 
for ebXML Registry version 3.

Thoughts.

-- 
Regards,
Farrukh

-------- Original Message --------

Subject: 	[OASIS members] WSS specification submitted for OASIS Standard
Date: 	Mon, 01 Mar 2004 08:31:59 -0500
From: 	Karl F. Best <karl.best@oasis-open.org>
Reply-To: 	karl.best@oasis-open.org
Organization: 	OASIS
To: 	members@lists.oasis-open.org, tc-announce@lists.oasis-open.org



OASIS members:

The OASIS Web Services Security TC (WSS TC) has submitted the Web
Services Security v1.0 specification, which is an approved Committee
Draft, for review and consideration for approval by OASIS members to
become an OASIS Standard. The TC's submission is attached below.

In accordance with the OASIS Technical Process, the specification has
already gone through a 30 day public review period. OASIS members now
have 15 days to familiarize themselves with the submission. By the 16th
of the month I will send out a Call For Vote to the voting
representative of each OASIS member organization, who will have until
the end of the month to cast their ballots on whether this Committee
Draft should be approved as an OASIS Standard. OASIS members should give
their input on this question to the voting reps of their respective
organizations.

The normative TC Process for approval of Committee Drafts as OASIS
Standards is found at
http://www.oasis-open.org/committees/process.php#standard

Please note that statements related to the IPR of this specification are
posted at http://www.oasis-open.org/committees/wss/ipr.php

-Karl

=================================================================
Karl F. Best
Vice President, OASIS
office +1 978.667.5115 x206 mobile +1 978.761.1648
karl.best@oasis-open.org http://www.oasis-open.org