OASIS Key Management Interoperability Protocol (KMIP) TC

Hi,   In our TC call today, I had mentioned about the Appendix D. Operations and Object Cross-Reference where the table is overflowing the page width. I propose to remove this, if no one uses this. If there are folks who rely on this, I would like suggestions on how to format this table so that this can be fitted into the document. Appendix D. Operations and Object Cross-Reference The following table indicates the types of Managed Object(s) that each Operation accepts as input or provides as output. This table is not normative. Operation                                                               Managed Objects Certificate Symmetric Key Public Key Private Key Split Key Template Secret Data Opaque Object PGP Key Create N/A Y N/A N/A N/A Y N/A N/A N/A Create Key Pair N/A N/A Y Y N/A Y N/A N/A N/A Register Y Y Y Y Y Y Y Y Y Re-key N/A Y N/A N/A N/A Y N/A N/A N/A Re-key Key Pair N/A N/A Y Y N/A Y N/A N/A N/A Derive Key N/A Y N/A N/A N/A Y Y N/A N/A Certify Y N/A Y N/A N/A Y N/A N/A Y Re-certify Y N/A N/A N/A N/A Y N/A N/A Y Locate Y Y Y Y Y Y Y Y Y Check Y Y Y Y Y N/A Y Y Y Get Y Y Y Y Y Y Y Y Y Get Attributes Y Y Y Y Y Y Y Y Y Get Attribute List Y Y Y Y Y Y Y Y Y Add Attribute Y Y Y Y Y Y Y Y Y Modify Attribute Y Y Y Y Y Y Y Y Y Delete Attribute Y Y Y Y Y Y Y Y Y Obtain Lease Y Y Y Y Y N/A Y N/A Y Get Usage Allocation N/A Y Y Y N/A N/A N/A N/A N/A Activate Y Y Y Y Y N/A Y N/A Y Revoke Y Y N/A Y Y N/A Y Y Y Destroy Y Y Y Y Y Y Y Y Y Archive Y Y Y Y Y Y Y Y Y Recover Y Y Y Y Y Y Y Y Y Validate Y N/A N/A N/A N/A N/A N/A N/A Y Query N/A N/A N/A N/A N/A N/A N/A N/A N/A Cancel N/A N/A N/A N/A N/A N/A N/A N/A N/A Poll N/A N/A N/A N/A N/A N/A N/A N/A N/A Notify N/A N/A N/A N/A N/A N/A N/A N/A N/A Put Y Y Y Y Y Y Y Y Y Discover Versions N/A N/A N/A N/A N/A N/A N/A N/A N/A Table 321: Operation and Object Cross-reference Thanks, Kiran

On 26/07/2013 8:03 AM, Kiran Kumar Thota wrote: Hi,   In our TC call today, I had mentioned about the Appendix D. Operations and Object Cross-Reference where the table is overflowing the page width. I propose to remove this, if no one uses this. If there are folks who rely on this, I would like suggestions on how to format this table so that this can be fitted into the document. On reflection,  I think all those appendices (B through C) actually should be moved out of the specification into the usage guide (they are all non-normative) or removed entirely. Or alternatively they need to be carefully reviewed and made normative. Tim.