- From: J.J.SOLARI <jjsolari@pobox.com>
- Date: Mon, 29 Aug 2005 19:00:58 +0200
- To: www-xkms@w3.org
Hello all,
Some more food for the errata of XKMS2 part 1, at
<http://www.w3.org/TR/2005/REC-xkms2-20050628/>:
=== 1
In Section 3.1.1 Type MessageAbstractType, last sentence of
production [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.
NOTE: Similar issue in productions [97], [111], [114], [128], [130],
[132] et [134]
=== 2
In production [115], first sentence reads:
If the ResultMajor *value* has the value Represent[...]
It should read:
If the ResultMajor *attribute* has the value Represent...
=== 3
Figure numbering is having the hiccups.
There are two Figure 5: one in Section 4.3.1 and one in Section 6.1.
Obviously, in Section 4.3.1, all occurrences of "Figure 5" should be
replaced by "Figure 4", ie. in productions [164] and [166].
=== 4
In section 9 Conformance, production [352] reads:
For example an XKMS service that supports the use of a transport
*encoding* other than HTTP SHOULD advertise that fact.
Should, IMHO, read:
For example an XKMS service that supports the use of a transport
*protocol* other than HTTP SHOULD advertise that fact.
=== 5
In section Appendix B.1 Domain Name Service, production [376] reads:
_Service._Protocol.NameTTLClassSRVPriorityWeightPortTarget
SRV record components should be space-separated (RFC2782) as:
_Service._Protocol.Name TTL Class SRV Priority Weight Port Target
That's all for XKMS2 part 1,
Regards,
JJS.
Received on Monday, 29 August 2005 17:01:14 UTC