From CAM Editor
Jump to: navigation, search

Content Assembly Mechanism

The OASIS Content Assembly Technical Committee (CAM TC), which met for the first time in January 2003, was chartered "to produce 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." CAM charter[1]

The original work predating CAM was begun in the later days of the ebXML initiative as an off-shoot of the ebXML Registry work. This working group was dubbed "BRIM" – Business Registry Interface Model and the focus was Registry content assembly services and content syntax storage specifications link to BRIM reference at CEFACT. The work was moved into OASIS at the end of 2002 to better facilitate the necessary XML development.

The formal public OASIS CAM standard specification was approved in June of 2005.

The development of the jCAM processor validation engine was first done in Java by Martin Roberts, and that was followed by work on the jCAM editor in Eclipse. The sponsor for this was British Telecomm - BTplc - in the UK. This work formed the foundation for the camprocessor project on Sourceforge.net and the original open source release. Work then continued with development of supporting xslt scripts that leverage the base CAM template format. These supporting tools perform a range of functions and generate and consume various XML artifacts.

More Pages

Additional information on CAM at Wikipedia.org