W3C home > Mailing lists > Public > www-xkms@w3.org > November 2002

New XKMS Requirements Editors draft

From: <Frederick.Hirsch@nokia.com>
Date: Mon, 25 Nov 2002 09:42:33 -0500
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF90106752D@bsebe001.americas.nokia.com>
To: <www-xkms@w3.org>

There is a new Editors version of the XKMS requirements draft [1], one that I believe addresses all
open issues against the requirements. Please look at it and post to the list if any corrections are needed.
Thanks Joseph for posting it to the web site and fixing some html issues.

Please note that the following requirements have changed in the last month (this edit and the last):
2.1.3, 2.1.14 (new),2.2.2,  2.4.5, 2.5.4, and 4.1 (new). 
Affiliations of the editors have also changed, and references have been updated.

Implications include potential addition of text to the XKMS specification for justification of optional  
features (2.1.3/SHOULD), and for unbounded schema maxOccurs elements (2.1.14/SHOULD).

Please send mail to the list if there are any outstanding issues with the requirements.

regards, Frederick

Changes from previous version:

1. Updated date to November.

2. Fixed Ds: prefix typo, replacing it with ds: in a few places

3. Edited requirement 2.1.14 that was added in the last pass (teleconference discussion, issue 72, closed)
 - removed "Tentative" 
 - eliminated "are discouraged and"

4. Added phrase to end of requirement 2.2.2 (to close issue 87 on issues list)
 + "Exclusive Canonicalization SHOULD be used as the XML Digital Signature
 canonicalization method."

5. Added new requirement to section 4 on coordination, [2]

"The Working Group may satisfy the {Payload, Transaction, and
  Authentication} requirements via its own specification or via normative
  reference to other specifications. The Working Group SHOULD avoid
  redundant  specification of those features where possible but SHOULD also
  consider the  timely completion of its own deliverable, this choice is at
  the Working  Group's discretion."

6. Updated references for consistent format and updated those that have advanced status:
Exclusive Canonicalization -  Rec
DOM - date update
P3P - rec
XML - second edition
XML Enc - proposed rec
XML Enc rqmts - Note

7. ran through tidy with configuration file Shivaram provided.

[1] http://www.w3.org/2001/XKMS/Drafts/xkms-req.html

Unnumbered issue item:
"Before getting into the issues list in detail: After we get next rev of requirements document first get W3C-wide last call for (need to update requirements document wrt message level security) and then ask OASIS WSS to review our requirements ACTION Joseph R. to provide requirements text."

Frederick Hirsch
Technology Architect
Nokia Mobile Phones
5 Wayside Rd., Burlington, MA 01803 USA
Received on Monday, 25 November 2002 09:42:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:40 UTC