Next in thread →
Next in month →
Re: [cmis] CMIS work product review
*********************** Warning: Your file, CMIS-cd04.zip, contains more than 32 files after decompression and cannot be scanned. *********************** I'm familiar with rules limiting behavior. :) Here's the zip (See attached file: CMIS-cd04.zip) -Al Al Brown Emerging Standards and Industry Frameworks CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home Office 714 327 3453 Mobile 714 263 6441 Email CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation. Mary McRae ---10/19/2009 11:30:28 AM---Hi Al, I can't take anything out of SVN (not that I'm not capable, but our From: Mary McRae <> To: Al Brown/Costa Mesa/IBM@IBMUS Cc: <>, , Date: 10/19/2009 11:30 AM Subject: Re: [cmis] CMIS work product review Hi Al, I can't take anything out of SVN (not that I'm not capable, but our rules prevent it). Please export the fixed version of the specification and either attach to email or upload to Kavi. Thanks! Mary On Oct 19, 2009, at 2:22 PM, Al Brown wrote: Mary, The changes are reflected in the specification - http://tools.oasis-open.org/version-control/browse/wsvn/cmis/trunk/Specification/CMIS%20Specification.doc. I was not able to find sample namespace documents under the link you provided. What is necessary for them? -Al Al Brown Emerging Standards and Industry Frameworks CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home Office 714 327 3453 Mobile 714 263 6441 Email CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation. <graycol.gif>---10/15/2009 01:45:56 AM---Mary, thank you for your detailed comments/instructions. To our Editors: Please update the spec per From: <> To: <>, <> Cc: <> Date: 10/15/2009 01:45 AM Subject: RE: [cmis] CMIS work product review Mary, thank you for your detailed comments/instructions. To our Editors: Please update the spec per Mary's instructions at your earliest convenience. Thanks. Since this is primarily a format change to conform to OASIS requirements, TC voting on these changes is not needed.. To all: Once we revised the spec, we will conduct another formal ballot to approve it as a Committee Draft, and approve its submission for Public Review. Thank you for your patience. BTW, my network connectivity in the next several days is a bit uncertain. I'll check email whenever I can. Regards, david -----Original Message----- From: Mary McRae [mailto:] Sent: Wednesday, October 14, 2009 6:25 PM To: Eric S. Chan; Al Brown Cc: Sabine Ocker; CMIS List Subject: [cmis] CMIS work product review The following issues have been idientified in the submitted work products and must be corrected before they can be uploaded to docs.oasis-open.org : 1. Creation of a master document (Content Management Interoperability Services Version 1.0) that contains all common information and references the 3 separate components. Note all changes in all documents should be accepted before publishing. ---- Domain Model: 1. Title should be as follows: Content Management Interoperability Services Version 1.0 Part 1 - Domain Model 2. Status: Committee Draft 01 (or whatever number is appropriate; should be consecutive) 3. Specification URIs This Version: Please see URI Generator for assistance in determining (http://www.oasis-open.org/committees/uri-block-generator.php ) Also, one of the 3 formats must be declared as authoritative (noted by the word 'Authoritative' in parens following the specific URL) Previous Version: Should be 'N/A' Latest Version: Should be version-agnostic URIs 4. OASIS Technical Committee Please spell out the full name of the committee; also hypertext link should point to TC public home page 5. Related work: This is meant for related OASIS work only 6. Namespaces: This should be a hypertext link; also need namespace document (see templates at http://docs.oasis-open.org/templates) 7. Abstract: Remove references to files in svn. Any/all references must be to fixed/ static versions either in docs.oasis-open.org or Kavi. 8. Status: Hypertext links behind physical URLs do not match the named locations. 9. Notices: Copyright should be 2009 "CMIS" should be added after "OASIS" where it's noted [insert specific trademarked names and abbreviations here] No other modifications are allowed to the Notices section. (You might want to place CMIS logo usage information in an appendix) 10. Footer: document identifier should match filename without extension Date is improperly formatted Page # of # should be right-justified 11. References Still contains OASIS boilerplate templates 12. Section 4 Schema Says placeholder. Recommend moving schema to appendix; note separate schema file will take precedence over any schema incorporated into the specification file. 13. Conformance Section Needs to actually be numbered. 14. Acknowledgements: Only TC Members can be listed in the specification. Note that Associate members are not entitled to have their company name listed. Associate members can most easily be identified by looking at the roster and seeing whether their company is a hyperlink or just plain text. Associates will not be hyperlinked (Ektron, EsoCE- NET, Greenbytes, FatWire) ----- Restful AtomPub Binding 1. Title should be as follows: Content Management Interoperability Services Version 1.0 Part 3 - Restful AtomPub Binding 2. Status: Committee Draft 01 (or whatever number is appropriate; should be consecutive) 3. Specification URIs This Version: Please see URI Generator for assistance in determining (http://www.oasis-open.org/committees/uri-block-generator.php ) Also, one of the 3 formats must be declared as authoritative (noted by the word 'Authoritative' in parens following the specific URL) Previous Version: Should be 'N/A' Latest Version: Should be version-agnostic URIs 4. OASIS Technical Committee Hypertext link should point to TC public home page 5. Namespaces: This should be a hypertext link; also need namespace document (see templates at http://docs.oasis-open.org/templates) 6. Status: Hypertext links behind physical URLs do not match the named locations. 7. Notices: Copyright should be 2009 "CMIS" should be added after "OASIS" where it's noted [insert specific trademarked names and abbreviations here] 8. Footer: document identifier should match filename without extension Date is improperly formatted 9. References Need URL for CMISDM 10. Conformance Section Needs to actually be numbered. 11. Acknowledgements: Only TC Members can be listed in the specification. Note that Associate members are not entitled to have their company name listed. Associate members can most easily be identified by looking at the roster and seeing whether their company is a hyperlink or just plain text. Associates will not be hyperlinked (Ektron, EsoCE- NET, Greenbytes, FatWire) ---- Web Services Binding 1. Title should be as follows: Content Management Interoperability Services Version 1.0 Part 2 - Web Services Binding 2. Status: Committee Draft 01 (or whatever number is appropriate; should be consecutive) 3. Specification URIs This Version: Please see URI Generator for assistance in determining (http://www.oasis-open.org/committees/uri-block-generator.php ) Also, one of the 3 formats must be declared as authoritative (noted by the word 'Authoritative' in parens following the specific URL) Previous Version: Should be 'N/A' Latest Version: Should be version-agnostic URIs 4. OASIS Technical Committee Hypertext link should point to TC public home page 5. Namespaces: This should be a hypertext link; also need namespace document (see templates at http://docs.oasis-open.org/templates) 6. Status: Hypertext links behind physical URLs do not match the named locations. 7. Notices: Copyright should be 2009 "CMIS" should be added after "OASIS" where it's noted [insert specific trademarked names and abbreviations here] 8. Footer: document identifier should match filename without extension 9. References Need URL for CMISSCHEMA Remove boilerplate citation notice 10. Conformance Section Needs to actually be numbered. 11. Acknowledgements: Only TC Members can be listed in the specification. Note that Associate members are not entitled to have their company name listed. Associate members can most easily be identified by looking at the roster and seeing whether their company is a hyperlink or just plain text. Associates will not be hyperlinked (Ektron, EsoCE- NET, Greenbytes, FatWire) Regards, Mary Mary P McRae Director, Standards Development Technical Committee Administrator OASIS: Advancing open standards for the information society email: web: www.oasis-open.org twitter: fiberartisan #oasisopen phone: 1.603.232.9090 Standards are like parachutes: they work best when they're open. --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php CMIS-cd04.zip
Next in thread →
Next in month →