[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: addressing issues raised in [kmip] work product review
Hi Mary - In addition to having the OASIS staff go ahead and make corrections to "KMIP Profiles" and "KMIP Specification", we would appreciate having the OASIS staff also make the corrections you noted to the "KMIP Usage Guide" and "KMIP Use Cases", including incorporating the following text to address the omitted conformance statements in those documents: Insert in "KMIP Usage Guide" as new Section 5 (immediately preceding appendix A): 5 Implementation Conformance This document is intended to be informational only and as such has no conformance clauses. The conformance requirements for the KMIP specification can be found in the "KMIP Specification" document itself, at the URL noted on the cover page of this document. Similarly, insert in "KMIP Use Cases" as new Section 11 (immediately preceding appendix A): 11 Implementation Conformance This document is intended to be informational only and as such has no conformance clauses. The conformance requirements for the KMIP specification can be found in the "KMIP Specification" document itself, at the URL noted on the cover page of this document. If there is any issue in terms of incorporating this text or otherwise addressing the corrections you noted, please let me know? Again, many thanks for your support in moving our KMIP work forward! Regards, Bob -----Original Message----- From: Mary McRae [mailto:mary.mcrae@oasis-open.org] Sent: Thursday, November 19, 2009 10:03 AM To: Griffin, Robert Cc: Sabine Ocker; kmip@lists.oasis-open.org Subject: [kmip] work product review The following issues have been identified in the submitted work products and must be corrected before they can be uploaded to docs.oasis-open.org and the public review announced: Key Management Interoperability Protocol Profiles version 1.0 1. Date: The date must be date the specification was approved as a Committee Draft and for Public Review. I believe this should be 5 November [Please make sure you put the date of the meeting in your meeting minutes, as well as the list of attendees and whether or not the meeting was quorate] 2. Specification URIs: a. This Version: The html link must be to an html page, not a zip file b. Previous Version: Please insert 'N/A' c. Latest Version: Please ensure that these are actual hypertext links and link to the proper location The html link must be to an html page, not a zip file 3. Related Work: URL need not be displayed; title of related work must hypertext link to current version and not latest one. 4. Document footer: a. change point size of filename to 8pt b. date must match that of the CD approval date c. remove "OASIS trademarks ... apply" from footer 5. Notices page Add KMIP to the list of trademarked names in last paragraph 6. Table of Contents This is very messed up; listing cover page items? Not sure how this happened 7. Normative References KMIP-Spec Include Draft number and hypertext-linked URL to the named version of the specification 8. Non-normative References KMIP-UG Include Draft number and hypertext-linked URL to the named version of the specification KMIP-UC Include Draft number and hypertext-linked URL to the named version of the specification [NOTE: As you go forward you will want to use use the designated cross reference form of motions so that these references can be updated post-approval] 9. Conformance The Conformance section must be the last numbered section immediately preceding any appendices 10. Acknowlegements: The following two members must be listed as Associate rather than displaying their company name (not organizational members) Peter Zelechoski Don McAlister ----- Key Management Interoperability Protocol Specification Version 1.0 1. Date: The date must be date the specification was approved as a Committee Draft and for Public Review. I believe this should be 5 November 2. Specification URIs: a. This Version: Please ensure that actual hypertext links are to the proper location b. Previous Version: Please insert 'N/A' 3. Related Work: URL need not be displayed; title of related work must hypertext link to current version and not latest one. 4. Document footer: a. date must match that of the CD approval date b. remove "OASIS trademarks ... apply" from footer 5. Notices page Add KMIP to the list of trademarked names in last paragraph 6. Normative References KMIP-Prof Include Draft number and hypertext-linked URL to the named version of the specification 8. Non-normative References KMIP-UG Include Draft number and hypertext-linked URL to the named version of the specification KMIP-UC Include Draft number and hypertext-linked URL to the named version of the specification 9. Acknowlegements: The following two members must be listed as Associate rather than displaying their company name (not organizational members) Peter Zelechoski Don McAlister ----- Key Management Interoperability Protocol Usage Guide version 1.0 1. Date: The date must be date the specification was approved as a Committee Draft and for Public Review. I believe this should be 5 November 2. Specification URIs: a. This Version: Please ensure that these are actual hypertext links and link to the proper location b. Previous Version: Please insert 'N/A' 3. Related Work: URL need not be displayed; title of related work must hypertext link to current version and not latest one. 4. Document footer: a. date must match that of the CD approval date b. remove "OASIS trademarks ... apply" from footer 5. Notices page Add KMIP to the list of trademarked names in last paragraph 7. Normative References KMIP-Spec Include Draft number and hypertext-linked URL to the named version of the specification KMIP-Prof Include Draft number and hypertext-linked URL to the named version of the specification 8. Non-normative References KMIP-UC Include Draft number and hypertext-linked URL to the named version of the specification [NOTE: As you go forward you will want to use use the designated cross reference form of motions so that these references can be updated post-approval] 9. Level 2+ Headings somehow were changed from Bold to Roman. Please ensure template styles are used. Major Headings (Level 1) should start a new page. Rule is missing at major headings. 10. Conformance The Conformance section is required, must be the last numbered section immediately preceding any appendices 11. Acknowlegements: The following two members must be listed as Associate rather than displaying their company name (not organizational members) Peter Zelechoski Don McAlister ----- Key Management Interoperability Protocol Use Cases Version 1.0 1. Date: The date must be date the specification was approved as a Committee Draft and for Public Review. I believe this should be 5 November 2. Specification URIs: a. This Version: Please ensure that these are actual hypertext links and link to the proper location b. Previous Version: Please insert 'N/A' c. Latest Version: Please ensure that these are actual hypertext links and link to the proper location 3. Technical Committee: Please ensure that hypertext link points to the TC's public home page http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=kmip 3. Related Work: URL need not be displayed; title of related work must hypertext link to current version and not latest one. 4. Document footer: a. date must match that of the CD approval date b. remove "OASIS trademarks ... apply" from footer 5. Notices page Add KMIP to the list of trademarked names in last paragraph 7. Normative References KMIP-Spec Include Draft number and hypertext-linked URL to the named version of the specification KMIP-Prof Include Draft number and hypertext-linked URL to the named version of the specification 9. Level 2+ Headings somehow were changed from Bold to Roman. Please ensure template styles are used. Major Headings (Level 1) should start a new page. Rule is missing at major headings. Line numbers are missing 10. Conformance The Conformance section is required, must be the last numbered section immediately preceding any appendices 11. Acknowlegements: The following two members must be listed as Associate rather than displaying their company name (not organizational members) Peter Zelechoski Don McAlister For the first two specifications, the TC can make the appropriate changes and resubmit the Committee Draft, or, as an alternative, OASIS Staff will make the necessary changes upon request. The last two are missing conformance sections and will therefore need to be updated by the TC. Regards, Mary Mary P McRae Director, Standards Development Technical Committee Administrator OASIS: Advancing open standards for the information society email: mary.mcrae@oasis-open.org web: www.oasis-open.org twitter: @fiberartisan #oasisopen phone: 1.603.232.9090 Standards are like parachutes: they work best when they're open.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]