OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cam message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Content Assembly Mechanism (CAM) v1.1 Submitted for OASIS Standard


OASIS Members:

The OASIS Content Assembly Mechanism (CAM) Technical Committee has submitted the following specification, which is an
approved Committee Specification, to be considered as an OASIS Standard:

Content Assembly Mechanism Specification Version 1.1

The text of the TC submission is appended.

You now have until 15 May to familiarize yourself with the submission and provide input to your organization's voting
representative.

On 16 May, a Call For Vote will be issued to all Voting Representatives of OASIS member organizations. They will have
until the last day of May, inclusive, to cast their ballots on whether this Committee Specification should be approved
as an OASIS Standard or not.

Members who wish to discuss this ballot may do so through member-discuss@lists.oasis-open.org.

In accordance with the OASIS Technical Committee Process, this Committee Specification has already completed the
necessary 60-day public review period as noted in the submission below.

The normative TC Process for approval of Committee Specifications as OASIS Standards is found at
http://www.oasis-open.org/committees/process.php#3.4

Any statements related to the IPR of this specification are posted at:
http://www.oasis-open.org/committees/cam/ipr.php

Your participation in the review and balloting process is greatly appreciated.

Mary

Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org
phone: 603.232.9090

-----------------------

a) Links to the approved Committee Specification in the TC's document repository, and any appropriate supplemental
documentation for the specification, both of which must be written using the OASIS templates. The specification may not
have been changed between its approval as a Committee Specification and its submission to OASIS for consideration as an
OASIS Standard, except for the changes on the title page and running footer noting the approval status and date. 
 
http://docs.oasis-open.org/cam/v1.1/cs01/OASIS-CAM-Specification-1_1-015-041007.html
http://docs.oasis-open.org/cam/v1.1/cs01/OASIS-CAM-Specification-1_1-015-041007.doc
http://docs.oasis-open.org/cam/v1.1/cs01/OASIS-CAM-Specification-1_1-015-041007.pdf
 
(b) The editable version of all files that are part of the Committee Specification;
 
http://docs.oasis-open.org/cam/v1.1/cs01/OASIS-CAM-Specification-1_1-015-041007.doc
http://docs.oasis-open.org/cam/v1.1/cs01/CAM-v1_1.xsd 
 
(c) Certification by the TC that all schema and XML instances included in the specification, whether by inclusion or
reference, including fragments of such, are well formed, and that all expressions are valid;
 
Specification verified as ready for OASIS member ballot -
http://www.oasis-open.org/apps/org/workgroup/cam/ballot.php?id=1226
 
(d) A clear English-language summary of the specification; 
 
The Content Assembly Mechanism (CAM) provides an open XML based system for using business
rules to define, validate and compose specific business documents from generalized schema
elements and structures.
 
A CAM rule set and document assembly template defines the specific business context, content
requirement, and transactional function of a document. A CAM template must be capable of
consistently reproducing documents that can successfully carry out the specific transactional function that they were
designed for. CAM also provides the foundation for creating industry libraries and dictionaries of schema elements and
business document structures to support business process needs.
 
(e) A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards
developing organizations; 
 
There is no similar specification work being performed by other OASIS TCs.  The CAM work can be used in conjunction with
and by other OASIS TCs to formalize use patterns and templates for their own schemas or to generate / validate policies
such as SAML and XACML assertions. CAM implementations can provide validation web services for registry or general
transaction exchanges for industry standards groups use. Related external work includes ISO/IEC 19757-3:2006 schematron
and the W3C XSD work and the W3C SML submission, along with work by UN/CEFACT on UCM and CCMA.
 
(f) The Statements of Use presented above; 
 
BTplc: http://lists.oasis-open.org/archives/cam/200703/msg00005.html
Metlife: http://lists.oasis-open.org/archives/cam/200702/msg00012.html
Nortel: http://lists.oasis-open.org/archives/cam/200703/msg00006.html
 
(g) The beginning and ending dates of the public review(s), a pointer to the announcement of the public review(s), and a
pointer to an account of each of the comments/issues raised during the public review period(s), along with its
resolution; 
 
Public review: http://lists.oasis-open.org/archives/tc-announce/200611/msg00015.html
 
Started 01 December 2006, and ended 30 January 2007 
 
Comments and resolutions:
http://www.oasis-open.org/committees/download.php/22742/CAM%20V1-1%20Member%20Comment%20Review.pdf
 
(h) An account of and results of the voting to approve the specification as a Committee Specification, including the
date of the ballot and a pointer to the ballot; 
Opening:   Tuesday, 3 April 2007 @ 17:00 ET 
Closing:   Tuesday, 10 April 2007 @ 23:45 ET 

Passed with eligible members who have voted:  6 of 8 75% 

http://www.oasis-open.org/apps/org/workgroup/cam/ballot.php?id=1265
 
(i) An account of or pointer to votes and comments received in any earlier attempts to standardize substantially the
same specification, together with the originating TC's response to each comment;
 
N/A - first specification member ballot
 
(j) A pointer to the publicly visible comments archive for the originating TC; 
 
http://lists.oasis-open.org/archives/cam-comment/
 
(k) A pointer to any minority reports submitted by one or more Members who did not vote in favor of approving the
Committee Specification, which report may include statements regarding why the member voted against the specification or
that the member believes that Substantive Changes were made which have not gone through public review; or certification
by the Chair that no minority reports exist. 
 
N/A - no minority reports
 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]