questions about X.509 Certificate Token Profile (CSD)

[Robin Cover <robin@oasis-open.org>]

The following questions arose in the process of creating
an appropriate cover page for the X.509 Certificate Token Profile (CSD).

1. Which URI should be used for the "Previous Version"
    specification?  Options:

    a) N/A [consider 1.1.1 CSD01 the first, with no "Previous"]
    b) http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-pr-RELTokenProfile.htm
       [the v1.1 OS]
    c) http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-errata-os-x509TokenProfile.doc
       [the Errata spec]

2. Who should be listed on the cover page as Editors?

The Work Product Registration for this spec lists five names:

Anthony Nadalin, IBM
Chris Kaler, Microsoft
Ronald Monzillo, Sun
Phillip Hallam-Baker, Verisign
Michael McIntosh
  See:
http://tools.oasis-open.org/issues/browse/TCADMIN-295
http://lists.oasis-open.org/archives/wss-m/201011/msg00008.html

But the WD02 document (.doc) Custom Properties lists only two:
Anthony Nadalin, IBM
Michael McIntosh

And the Version 1.1 OS listed as Editors these four:
Anthony Nadalin, IBM
Chris Kaler, Microsoft
Ronald Monzillo, Sun
Phillip Hallam-Baker, Verisign


3. Which URIs should be listed on the cover page for the
    Declared XML Namespace(s)?

The Work Product Registration for this spec lists five, with
one apparent duplication:

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#PKCS7
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier
  See:
http://tools.oasis-open.org/issues/browse/TCADMIN-295
http://lists.oasis-open.org/archives/wss-m/201011/msg00008.html

But the WD02 document (.doc) Custom Properties lists only:
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0

Inspection of the WD02 document "Section 2.2 Namespaces" reveals
nine URIs that might be candidates for identifying XML namespace names, and
of those, at least two ending in ".xsd" seem to be used in the
XML schemas as XML namespace names:

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#PKCS7
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3
http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd

4. For clarification on spec development: is the TC planning to release
    at least CSD02 and CSPRD02 (after the CSPRD01 public review)?  I ask
    because the WD02 document balloted for approval as CSD01 has a number
    of link errors which I imagine would be candidates for correction in
    CSD02.

5. In answers to any of the above, if principled grounds for the decision
can be explained, it may obviate the need to ask similar questions for
the other six WD02 specs, should those questions arise in my work.

The method of communication specification metadata to TC Admin (in the
design of October 2010) was that TCs would religiously edit the
Custom Property values. I'm not sure if that works in all cases, so
I'm testing the theory.  Feedback would be welcome on that point.
In theory: the Work Product Registration (template) sets out the
initial values, and the TC Editors use the Custom Property values in
successive Working Drafts to make any metadata updates.

For "Related work:" in connection with this spec, I would plan to say
it supersedes the OS and OS Errata, while being a part of the multi-part
"Web Services Security" spec which includes six other parts.

Thanks -rcc

Robin Cover
Interim TC Administrator
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/who/staff.php#cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783