W3C home > Mailing lists > Public > www-xkms@w3.org > August 2005

[XKMS2] Errata: MajorResult and MinorResult?

From: J.J.SOLARI <jjsolari@pobox.com>
Date: Wed, 17 Aug 2005 17:14:25 +0200
To: www-xkms@w3.org
Message-ID: <r02010500-1042-99315ADC0F3111DAA9C3000D93ADFDA4@[10.0.1.2]>

Hello,

In the process of translating the REC, I stumbled on what seems a
contradiction between the text of the REC and the XKMS Schema, that
is:

In Section 2 Protocol Exchanges, first sentence of production [43]
reads:
    
    [...]
    
Each XKMS response message contains a *MajorResult* code that
determines whether the response is final or further processing is
required. [...]

According to the XKMS Schema, it should read:

Each XKMS response message contains a *ResultMajor* code that
determines whether the response is final or further processing is
required.

NOTE: This typo appears also in productions [49], [51], [52], [54],
[57], [58], [61], [63], [64], [67], [68] (twice), [100] (twice),
[111] (twice), [115] and [130]


=================

As well, in Section 2.4 Synchronous and Asynchronous Processing,
second sentence of production [52] reads:

    [...]
    
If an XKMS service receives a request that cannot be processed
synchronously and the ResponseMechanism value Pending is not
specified the MajorResult code Receiver and *MinorResult* code
NotSynchronous are returned.

According to the XKMS Schema, it should read:

If an XKMS service receives a request that cannot be processed
synchronously and the ResponseMechanism value Pending is not
specified the {ResultMajor} code Receiver and *ResultMinor* code
NotSynchronous are returned.

NOTE: This typo appears also in production [64].


Should these typos have not already been reported...

That's all for now,

JJS.
Received on Wednesday, 17 August 2005 15:14:33 UTC

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