[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Submission requests for 30-day public review of Portable MediaService and Web Services SIPs
I have inspected the documents proposed as candidates for 30-day public review [1] and have discussed the specifications with TC Chair James Cabral. These specifications are vintage 2008/2009, and are not surprisingly out of sync with the new TC Process rules, for example, in lacking the required Conformance Clause sections. Furthermore, the specs have other errors of citation, and omission of required standalone machine-readable files (Computer Language Definition Files) [3], and so forth. Therefore, an updated CSD will need to be created for the two specifications before we can send them out for public review. I have explained to James that creating the new CSDs will actually be faster and a lot less effort because it will allow, if the TC so elects, avoidance of a second (15-day) review if everything gets fixed in CSD02. That is, your TC can in theory follow path "B" to a Final Deliverable rather than path "A": A. CSD01 -> CSPRD01 (30) -> CSD02 -> CSPRD02 (15) -> CS B. CSD01 -> CSD02 -> CSPRD01 -> CS The additional time in "A" is substantially more than fifteen (15) days because - a public review requires that the TC "acknowledge the receipt of each comment, track the comments received, and post to its primary e-mail list its disposition of each comment at the end of the review period." - a second public review requires a published diff record against the 30-day review draft "Changes made to a committee draft after a review must be clearly identified in any subsequent review, and the subsequent review shall be limited in scope to changes made in the previous review. I have also sent Jim a couple correction sheets documenting link errors, mis-named files, and other bugs/infelicities that I know the TC would want to eliminate, or must eliminate, in order to proceed to Final Deliverable. TC Admin will endeavor to assist in any ways needed to help advance the two profiles. Best wishes, Robin -- Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/who/staff.php#cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 ============== References: [1] 30-day Committee Specification Draft Review Request for ElectronicCourt Filing 4.0 Portable Media Service Interaction Profile Version 2.0 http://lists.oasis-open.org/archives/legalxml-courtfiling/201103/msg00011.html 30-day Committee Specification Draft Review Request for ElectronicCourt Filing 4.0 Web Services Service Interaction Profile Version 2.01 http://lists.oasis-open.org/archives/legalxml-courtfiling/201103/msg00012.html [2] http://www.oasis-open.org/committees/process-2010-07-28.php#quality-conformanceClauses (8) Conformance Clauses. (8a) For Standards Track Work Products: "A specification that is approved by the TC at the Committee Specification Public Review Draft, Committee Specification or OASIS Standard level *must* include *a separate section*, listing *a set of numbered conformance clauses*, to which any implementation of the specification must adhere in order to claim conformance to the specification (or any optional portion thereof)." Note also: when you advance the specification to become a CS final deliverable, the spec will need to be qualified by "Statements of Use" which must reference the conformance clauses which are not yet instantiated in the document: "Statement of Use", with respect to a Committee Specification, is a written statement by an OASIS Organizational Member stating that it is successfully using or implementing that specification in accordance with the conformance clauses specified in Section 2.18, and stating whether its use included the interoperation of multiple independent implementations. http://www.oasis-open.org/committees/process-2010-07-28.php#dStatementUse New Process: http://www.oasis-open.org/committees/process-faq.php 1. When does this new TC Process go into effect, and how does it apply to existing projects? The new TC Process goes into effect on 15 October 2010 (simultaneous with the new IPR Policy). Specifications that are either out for Public Review or have completed a 60-day Public Review as of 15 October 2010 AND are submitted for OASIS Standard Ballot on or before 15 January 2011 will be subject to the requirements in Section 3.4 in effect on 1 September 2009. Any specifications that have not been submitted for Public Review or have been submitted but the review has not yet been announced on 15 October 2010; or have completed the Public Review process but are not submitted for OASI S Standard Ballot by 13 January 2011, will be subject to the requirements in Section 3.4 in effect on 15 October 2010. [3] TC Process rule on standalone machine-readable files (Computer Language Definition Files) http://docs.oasis-open.org/TChandbook/Reference/WPQualityChecklist.html#machine-readable-files http://www.oasis-open.org/committees/process-2010-07-28.php#quality-formalLangDefns ca line 132 "This file MUST be XML valid against the ECF-4.0-PortableMediaMessagingProfile.xsd schema included in this specification. that identifies" I don't find any standalone XSD schema file with the identifier "ECF-4.0-PortableMediaMessagingProfile.xsd" in the CD01 release. TC Process requires, for Standards Track Work Products, that all normative computer language definitions must be provided in separate plain text files, and each text file must be referenced [by URI] from the Work Product [prose document]. ls -1R ecf-v4.0-portablemedia-spec | grep -i PortableMediaMessagingProfile (null) I only see these files in the cd01 release: ecf-v4.0-portablemedia-spec-cd01.doc ecf-v4.0-portablemedia-spec-cd01.html ecf-v4.0-portablemedia-spec-cd01.pdf ecf-v4.0-portablemedia-spec-cd01.zip ecf-v4.0-portablemedia-spec.doc ecf-v4.0-portablemedia-spec.html ecf-v4.0-portablemedia-spec.pdf image001.jpg Connected-Document.pdf ECF-4.0-CoreFilingMessage.xml ECF-4.0-Operation.xml ECF-4.0-PaymentMessage.xml LeadDocument.pdf ECF-4.0-MessageReceiptMessage.xml ECF-4.0-PortableMediaProfile.xsd [ *ECF-4.0-PortableMediaMessagingProfile.xsd <- lacking** ]
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]