Revised CAM charter text

["David RR Webber \(XML\)" <david@drrw.info>]

Team,

 

Since we need to bring our charter back up to date with our current work and OASIS procedures - I've taken the existing text and just revised the text from "List of Deliverables" onwards.  The main statement of purpose text is identical to what we have already - the new revised details is on the deliverables themselves and other items we did not have before.   I've borrowed from what other TCs have now in their Charters to put together this revised charter - hopefully this then confirms more closely to what OASIS expects as a norm.

 

I'm anticipating we can have a discussion here on wording and details - refine this - and then we will need to propose this new charter text, second it, and then move to open a Kavi ballot vote to approve it.  

 

Thanks, DW

================ DRAFT CHARTER TEXT ===============================

 

The charter for this TC is as follows.

 

Name

Content Assembly Mechanism (CAM) TC

 

Statement of Purpose

The purpose of this TC is to provide a specification of a generalized mechanism in XML whereby implementers can deliver the means to bring together business process context and the localized implementation business rules needed to take a raw industry standard schema instance and combine that with actual business information content, context and roles and produce a valid consistent XML document instance.

 

OASIS is developing specifications for business process mechanisms, industry standard schemas, registry systems, and schema mechanisms. The CAM specification will allow these four components to be brought together in a consistent and standard way and publish assembly implementation instructions based on these OASIS specifications. This will facilitate the work of industry groups and allow development of software tools that work consistently with all these specifications.

 

OASIS CAM project will contribute to the horizontal and e-business framework specifications of OASIS and will also provide interoperability for other XML and non-XML standards working together.

 

The CAM TC will include derived business context mechanism support within the assembly process and thus harmonize with existing OASIS work where business context is used.

 

List of Deliverables

OASIS CAM specification and associated schema definitions

OASIS CAM specification extensions to cover particular domain solution requirements

Library of non-normative examples of CAM templates for other OASIS specifications

OASIS CAM non-normative guides to using CAM with other OASIS specifications

OASIS CAM specification updates particularly to incorporate new developments from the W3C of related XML specifications and changes.

 

Deliverable Items

• OASIS specification documents.
• Revised requirements document  following major specification release and prior to follow-on work commencing
• Reference schema(s) for CAM template structures and applicable example templates.
• Industry or domain specific examples or implementation guides may be developed. The due dates will be determined after the initial set of deliverables is complete.

Anticipated Audience

The primary audience for the final output of this TC is business process transaction data analysts and software transaction interface implementers. In addition these groups and communities:

·     Any organization (private/public) that needs to exchange business data in a standard way

·     Any tools that process transactional data, particularly XML

·     Any solution providers that provide solutions around transactions of data

·     Any standard group that needs to represent transaction exchanges in a standard way as part of its overall standards work

·     e-Government initiatives

·     Industry consortiums

·     Registry implementations of ebusiness terms and transaction formats and rules

Language

All business will be conducted in English.

 

Contributions

The specifications produced and any contributions will be free from encumbered IPR licensing requirements and compatible with use for public open source implementations and associated licensing.

 

Scope of Work

The OASIS CAM TC's effort will address and align with vertical industry needs for content assembly and validation and focus on ease of use. The specification can be integrated into and bind with existing or emerging technologies.

 

The TC's work should build upon similar, existing standards wherever possible and align with other relevant standards for XML content handling and storage methods particularly.

Support the ebXML framework and Web services to provide a loosely coupled, highly aligned specification set, while enabling support for other emerging technologies. Promote the utility of this principle, through, for example, actively working with other OASIS technical committees, industry and standards organizations.