Re: work product review

[Mary McRae <mary.mcrae@oasis-open.org>]

On Jan 25, 2010, at 6:44 AM, Hanssens Bart wrote:

> Hello Mary,
> 
> 
> thanks for reviewing the State of Interop Report v1.0. I do have a few questions here:
> 
> - regarding the mandatory Conformance clause: since this is only report, not a specification,
> would it be OK to include a section Conformance that would only contain this:  (last sentence
> of section 1 - Introduction)
> 
> "Note: This report is informative and contains no normative clauses or references."

Yes, this is perfectly acceptable.
> 
> 
> - do we have to create a new revision of it, or can the current cd03 be corrected "in place" ?

New revision
> 
> - when the changes are made, does the TC has to vote again in order to (re-)approve it ?

Yes. The TC Process only allows a set of items on the cover page and the running footers to be changed without requiring a new version.

> 
> 
> 
> Best regards,
> 
> Bart
> 
> ________________________________________
> From: Mary McRae [mary.mcrae@oasis-open.org]
> Sent: Monday, January 25, 2010 12:15 AM
> To: Hanssens Bart
> Cc: oic@lists.oasis-open.org
> Subject: 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 a public review announced (the checklist can be found here: http://docs.oasis-open.org/templates/QAChecklistV3.html) :
> 
> 1. Specification URIs
> a. These need to specify the full path to the document; currently you have a file name followed by 'at' followed by a kavi directory rather than a docs.oasis-open.org location
> The URI generator can help you create properly formatted URIs: http://www.oasis-open.org/committees/uri-block-generator.php
> 
> b. Note that one of the 'this version' URIs must be designated as 'authoritative' by the TC
> 
> c. Note that previous version URIs should say N/A if not available at docs.oasis-open.org
> 
> d. Note that latest version should not contain any stage-specific information in the URI/filename
> 
> 2. Technical Committee
> Must be the full name of the TC and hypertext-linked to the TC public home page
> 
> 3. Related Work:
> should contain the URL and/or hypertext link to the related specification
> 
> 4. Running footer
> should not contain the document type extension
> 
> 5. Status:
> The hypertext links do not match the actual URI text (3x)
> 
> 6. Notices Section:
> Please note last paragraph and insert any trademarked terms (ODF, OIC, etc.)
> 
> 6. Conformance Section
> This must be included and must be the last numbered section immediately preceding any appendices.
> 
> 
> The TC must make the appropriate changes and resubmit the Committee Draft.
> 
> 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.
> 
> 
> 
> 
> 
> 
> 
>