About the XML Key Management Specification (XKMS 2.0) documents
The XML Key Management Specification (XKMS 2.0)
Specifications were produced by the XKMS Working Group.
This document lists known errata to the Recommendation. Each entry has the
following information:
- A unique identifier
- The date it was added to the errata page
- A classification of the error (e.g., editorial, clarification, bug,
known problem with the document itself)
- A short description of the problem and what part of the Recommendation
is affected.
- Any proposed corrections and whether those corrections would affect
conformance of documents or software
- Any normative corrections; see the section on Errata
Management in the W3C Process Document ([PROCESS] section
7.6.1) for more information about normative corrections
- A unique entry number
- The date it was added to the errata page.
- Whether the entry is considered an important error, a minor
typographical error, a clarification, or a known problem with the
document itself.
- The section referred to.
- A description of the problem and correction if applicable.
Please send general coments about this document tot www-xkms@w3.org, a mailing
list with a public archive.
- 1. MajorResult typo in [XKMS
2.0]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Specification, pp. [43],
[49],
[51],
[52],
[54],
[57],
[58],
[61],
[63],
[64],
[67],
[68]
(twice), [100]
(twice), [111]
(twice), [115]
and [130]
- Description: The text in those paragraphs rejects to a "MajorResult"
code..
- Correction: According to the XKMS Schema, it should read:
"ResultMajor" code.
- 2. MinorResult typo in [XKMS
2.0]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Specification, p. [52]
- Description: The text in those paragraphs rejects to a "MinorResult"
code..
- Correction: According to the XKMS Schema, it should read:
"ResultMinor" code.
- 3. Elements vs. Element typo [XKMS
2.0]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Specification, pp. [86],
[97],
[111],
[114],
[128],
[130],
[132],
[134a]
- Description: In Section 3.1.1 Type MessageAbstractType, last sentence
of [86] reads "... The MessageAbstractType abstract type contains the
following *element* and attributes". Obviously, "element" is lacking a
final "s", as MessageAbstractType type contains more than one element.
This typo appears in the other paragraphs mentioned here above.
- Correction: The corrected text should refer to "elements" rather than
element in the above cited paragraphs.
- 4. typo [XKMS 2.0]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Specification, p. [115]
- Description: The first sentence reads: "If the ResultMajor *value*
has the value Represent...".
- Correction: It should read: "If the ResultMajor *attribute* has the
value Represent...".
- 5. Two Figure 5 [XKMS 2.0]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Specification, p. [164],
[166]
- Description: There are two Figure 5: one in Section 4.3.1 and one in
Section 6.1.
- Correction: In Section 4.3.1, all occurrences of "Figure 5" should be
replaced by "Figure 4", ie. in productions [164] and [166].
- 6. typo [XKMS 2.0]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Specification, p. [352]
- Description: In section 9 Conformance, p. [352] reads: "For example
an XKMS service that supports the use of a transport *encoding* other
than HTTP SHOULD advertise that fact."
- Correction: It should read "For example an XKMS service that supports
the use of a transport *protocol* other than HTTP SHOULD advertise that
fact.".
- 7. Invalid SRV record [XKMS 2.0]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Specification, p. [376]
- Description: In section Appendix B.1 Domain Name Service, p. [376]
reads:
"_Service._Protocol.NameTTLClassSRVPriorityWeightPortTarget".
- Correction: SRV record components should be space-separated
(RFC2782). The correct record should read: "_Service._Protocol.Name TTL
Class SRV Priority Weight Port Target"
- 8. Incorrect name expansion for TLS
[XKMS 2.0 Bindings]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Bindings, [Table
of Contents], [Section
4.2], p. [71]
- Description: In Table of Contents, entry 4.2 reads: "4.2 Secure
Socket Layer and *Transaction* Layer (SSL/TLS) Security Binding".
- Correction: It should read "4.2 Secure Socket Layer and *Transport*
Layer (SSL/TLS) Security Binding". Same typo in table [71] (third
column header) and in Section 4.2 heading.
- 9. Incorrect "Structure of this
document" section [XKMS 2.0 Bindings]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Bindings, [Section
1.3]
- Description: Section 1.3, Structure of this document doesn't
correspond with actual Table of Contents respective items.
- Correction: The structure should read "Section 3: Soap Binding: How
to transport XKMS messages using the SOAP message protocol.". Section
5: should be deleted in this structure.
- 10. Response Authentication [XKMS
2.0 Bindings]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Bindings, p. [28]
- Description: In section 2.3, Response Authentication, p. [28] reads:
"[28]An XKMS service SHOULD support *Request* Authentication."
- Correction: It should read: "[28]An XKMS service SHOULD support
*Message Response* Authentication.".
- 11. Payload Authentication Binding
[XKMS 2.0 Bindings]
- Added: 7 October 2005
- Type: Editorial
- Refers to: XKMS 2.0
Bindings, p. [71b]
- Description: In Section 4.1 Payload Authentication Binding, paragraph
[71b] reads:
In the following table, Request/Signature means that a XKMS
Request element includes a <dsig:Signature> element in
enveloped mode. This signature is calculated using a digital
signature method.Request/MAC has similar meaning, except that the
signature is calculated using a Message Authentication Code (MAC).
However, there are no such references as Request/MAC in the table
following.
- Correction: The last sentence of this paragraph should read "In the
table shown in p. [72],
Request.Signature with MAC has similar meaning, except that the
signature is calculated using a Message Authentication Code (MAC).
- 12. Obsolette AssertionType attribute
[XKMS 2.0]
- Added: 15 December 2005
- Type: Editorial
- Refers to: XKMS 2.0,
p. [207]
- Description: p. [207] still contains a reference to
AssertionType, although
this type was obsoleted.
- Correction: It should read "[207]The following schema defines the
<Status> element and StatusType type:".
Copyright
© 2002-2005 W3C® (MIT, INRIA,
Keio), All Rights Reserved. W3C liability,
trademark,
document
use and software
licensing rules apply.
This document last modified: $Date:
Wednesday 14 December 2005 - 17:11:49$