In OASIS, there has historically been a division
of labour between the
various ebXML Technical Committees, with the ebXML Messaging Services
specification being responsible for the protocol and message format,
and the ebXML Collaboration Protocols and Agreement TC responsible for
the CPPA (Collaboration Protocol Profile/Agreement) configuration
formats. The version 2.0 of CPPA supported ebMS 2.0 since 2004.
The CPPA TC merged with another ebXML TC to become the ebCore Technical
Need to handle JSON exchanges? The CAM editor and designer, the CAMV validation and the Open-XDX open data toolset now all support JSON. A quick video available on this is here: http://www.youtube.com/watch?v=K7-JlYGsjEcNeed extended rule handling - see the COBie Smart Building Corp of Engineers example:
I have been trying to find commerical products which support ebXML 3 and AS4. Also I have been searching for training courses. Does anyone here have any ideas?
The latest CAM editor release showcases the ability to build XML exchanges from XML canonical dictionary components using ebXML CCTS-based techniques.
The online video tutorial walks through the steps using an OASIS HAVE Hospital Management example exchange schema and the NIEM core dictionary. Illustrating adding additional Aircraft components from the NIEM domain to the OASIS HAVE exchange.
The video takes 8 minutes to review and requires any email address to access.
The new CAM editor v2.0 features drag and drop component selection for designing XML exchange structures from dictionary components. The dictionary component format is consistent with the ebXML CCTS business entity objects approach. The dictionaries can be configured into domain collections to suite particular industry needs. A NIEM collection of dictionaries is available by default with the CAM editor download.
For more information see the CAM editor Sourceforge resource site.