315-ga-2: Double definition of "ResponseId" attribute

Hi,
 
In response to your issue [1], all the changes as suggested have been made in the draft available [2].  We will consider this issue resolved and closed pending any other comments.
 
- There is a part of the Schema defining "RequestSignatureValue" 
element in the Compound Request Section (par[127]) which I think it 
should appear before the beginning of this section, in par[126].

- FIXED

- In the definition of the "StatusRequest" element (par[132]) it is 
said that it inherits the element attributes of "PendingRequestType", 
and the same can be understood from the Schema. However, 
the "ResponseId" attribute -which is already part 
of "PendingRequestType"- is defined there. To make it more confusing 
it is said to be Optional whereas in "PendingRequestType" it was 
Required. Should this reference be removed from there?

- FIXED duplicate reference removed.

- Maybe this is not so important, but in the Data Encryption Example 
(par[146]) a key is bound to bob @ "example.com" but then in par[147] 
the name used is bob @ "bobcorp.test". Of course the example is 
perfectly understandable but maybe both paragraphs should be 
consistent.

- IN PROGRESS a separate issue [3] exists for this.
 
[1]  http://www.w3.org/2001/XKMS/Drafts/cr-issues/issues.html#315-ga-2
[2]  http://www.w3.org/2001/XKMS/Drafts/XKMS-PR-DRAFT/PR-DRAFT-xkms-part-1.html
[3]  http://www.w3.org/2001/XKMS/Drafts/cr-issues/issues.html#315-ga-3
 
Thanks and Regards
 
/Shivaram

		
---------------------------------
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.