Public review of ebCORE Party Id Type committee specification

The OASIS ebCore TC has released the OASIS ebCore Party Id Type
Technical Specification Version 1.0 for public review.

Abstract:

"A mechanism for the identification of business partners in XML business documents and XML message headers using URN-based identifier types is required in many electronic business exchanges.

This specification specifies a formal URN-based mechanism for referencing party types from the ISO
6523, ISO 9735 and ISO 20022 identification scheme catalogs using the oasis URN namespace.

Sample applications include (but are not limited to): ebXML message headers; ebXML
collaboration protocol profiles and agreements; UBL, UN/CEFACT and OAGIS XML business documents;

and the UN/CEFACT SBDH."

PDF:
http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/CD02/PartyIdType-1.0.pdf
HTML:
http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/CD02/PartyIdType-1.0.html

For information on how to submit comments to the TC, see:

http://lists.oasis-open.org/archives/members/201004/msg00008.html

New .NET ebXML adaptor for H2O message server

CECID has jointly developed the .NET Development Tool for H2O with Apacus Software Corporation. The .NET tool developed allows applications written in C# to invoke the web services provided by H2O, without needing to know any details regarding the ebXML SOAP message format or in particular the SOAP with attachments details for sending and receiving messages.

Apacus is a Microsoft solution provider and the low cost H2O adapter provides .NET developers a robust proven message system at a fraction of the cost of other solutions.

The .NET library provided by Apacus bridges the gap between the H2O and .NET environment, extending H2O usage to MS platform.

For more details see the download web site (http://www.apacus.com) to obtain either the free trial version with payload size limited or to purchase the full product solution.

CAM v1.8 release - IEPD Tool and Canonical Dictionary support

The CAM Tool provides developers with a comprehensive solution set for building NIEM IEPD packages. This release consolidates 4 months of development work on both CAMeditor and CAMV for the OASIS CAM (Content Assembly Mechanism), and is the first for the 2010 “Alyeska” series.

Highlights

Significant enhancements are the new XSD Schema generation configured for NIEM 2.0 and NIEM 2.1 folder structures and the ability to use canonical XML dictionary components for top down schema designing. Developers build their information exchange definitions as sets of concise blueprints referencing the canonical XML dictionary of the exchange components. The CAM expander tool then generates the full IEPD exchange template from these. This allows developers to rapidly create tailored XSD schema and XML transaction instances along with their documentation directly by using the CAM tools. Example blueprints are provided for LEXS 3.1.4 and Emergency EDXL Hospital Availability exchanges.

The ability to generate XSD schema includes using folder structures by namespace extension and type (subset, extension, exchange, and external) along with customized header and footer documentation text. Built-in mappings are provided for NIEM 2.0, NIEM 2.1, LEXS and OASIS schemas. Custom mappings can be locally configured to match developer tooling needs.

For IEPD development the enhanced Interoperability and NDR checker provides more consistency rule checks now including spelling assistance. This tool significantly improves the quality of the resulting exchange by detecting common oversights, omissions and schema issues during the design process that are otherwise difficult to detect manually. All IEPD required artifacts can be generated using the CAM tools menu options. The “Compare to NIEM dictionary” tool produces NIEM component percentage reuse report analysis along with generating the NIEM cross-reference spreadsheet and SSGT Wantlist.xml file automatically.

The CAM canonical XML dictionary format is compatible with Microsoft Excel™ and utilizes the Core Components Technical Specification (CCTS) definitions thus making it accessible to business analysts to review the available data definitions for blueprint construction and extension. Included are tools to generate XML canonical dictionaries from existing exchange XSD schema, NIEM SSGT components or ERwin SQL model export XSD schema.

The project vision is to provide the leading open source toolset for implementing standards based information exchanges with XML. Simplifying and speeding the development process and enhancing the quality of your resulting schema for superior XML exchanges. To date the open source project has had over seventeen thousand file downloads from the Sourceforge.net resource site (http://www.sourceforge.net/projects/camprocessor).

The CAM Tool is built using Eclipse, Java, and Saxon xslt and is cross-platform deployable. The included CAMV validation engine can be deployed standalone with IBM MQ™ Application Server or equivalent exchange routing servers and systems.

Additional information on how the CAM methodology can accelerate your information exchange development through the application of XML component dictionaries and blueprints can be found at the OASIS web site:

http://www.oasis-open.org/committees/document.php?document_id=36146