RE: [kmip] Groups - Proposal for Renaming the Application SpecificIdentification attribute v2 (Proposal for Renaming AppSpecID-2.doc)uploaded

[Scott Kipp <skipp@Brocade.COM>]

Rene,

This looks good and we're getting close.  I have a few editorial suggestions:

1)
If the server is unable to generate the Application Data an Application Name Space Not Supported error is returned to the client. 

Application is misspelled and a , is needed.  Should be:

If the server is unable to generate the Application Data an Application Name Space, a Not Supported error is returned to the client.

2) the "Application Data" table cell says:
No, if omitted and if the server can handle the Application Name Space then the server will set Application Data.  

I don't think you need to say the error case again since there can be so many errors.  I suggest to change it to:
No. If the Application Date is omitted, the server will set the Application Data.  

3) the "Initially set by" table cell says:

Client or Server only if requested by Client

I find the grammar confusing.  How about:

Client. If the Application Data is omitted, the server sets it.

Thanks,
Scott

-----Original Message-----
From: rpa@zurich.ibm.com [mailto:rpa@zurich.ibm.com] 
Sent: Thursday, June 11, 2009 9:41 AM
To: kmip@lists.oasis-open.org
Subject: [kmip] Groups - Proposal for Renaming the Application Specific Identification attribute v2 (Proposal for Renaming AppSpecID-2.doc) uploaded

The document revision named Proposal for Renaming the Application Specific Identification attribute v2 (Proposal for Renaming AppSpecID-2.doc) has been submitted by Rene Pawlitzek to the OASIS Key Management Interoperability Protocol (KMIP) TC document repository.  This document is revision #2 of Proposal for Renaming AppSpecID.doc.

Document Description:
Purpose: Rename the Application Specific Identification attribute because the current name does describe the purpose of this attribute accurately. It can be used for a variety of different purposes and not only for storing the intended use of a managed object. Thus, the attribute would benefit from a more generic name.

View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=32893

Download Document:  
http://www.oasis-open.org/committees/download.php/32893/Proposal%20for%20Renaming%20AppSpecID-2.doc

Revision:
This document is revision #2 of Proposal for Renaming AppSpecID.doc.  The document details page referenced above will show the complete revision history.


PLEASE NOTE:  If the above links do not work for you, your email application may be breaking the link into two pieces.  You may be able to copy and paste the entire link address into the address field of your web browser.

-OASIS Open Administration