jCAM: B2B Content Validation and Assembly toolset for ebXML

The  OASIS CAM specification provides an XML-scripting system for validating B2B transaction structures and content (http://www.oasis-open.org/committees/cam).

The jCAM open source implementation (http://www.jcam.org.uk) provides a Java-based component for use with your ebXML messaging systems.  The focus is on delivering a quick and easy way for your partners to ensure that their business transactions comform to the correct business rules needed.

You can generate CAM templates conveniently using the CAM editor tool that accepts your XML samples and produces the structure rules directly from those.

CAM templates are unique in also supporting context mechanisms and parameters.  This is allows use of partner roles and context models from the BPSS (http://www.oasis-open.org/committees/ebxml-bp ) ebBP business process definitions) and ebXML CPA partner agreements to flow through to the ebXML runtime environment.

This provides the coupling between your business process collaboration definitions and the ebXML messaging systems.

Also example UBL templates are available for CAM - showing how you can take advantage of core component based (CCTS) transactions and schemas - while giving your partners pre-built templates that guides their transaction integration work (see the freeb-UBL resource site http://sourceforge.net/projects/freeb-ubl/ ).

More information and online screen-cast tutorials are available at the jCAM website.

Are there any guidelines I need to follow in order to use jCam as a component to make things easier? Also, can we handcraft custom xml templates to fit our business transactions requirements?



"Perfection takes pratice, pratice takes discipline." -Fernando Cavendish

XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I