ebXML Forum News

Tuesday, February 07, 2012

ebXML Registries Core of New U.S. Aviation Weather Platform

The US Congress last week authorized funding over the next four years for a major upgrade of the US air traffic control system called NextGen that will be based on advanced GPS technology, rather than the current radar-based approach, with a key element of that system covering weather data, organized using ebXML registry and repository standards.


You can read more about this whole development effort in this article from SoftXML magazine.

Thursday, January 26, 2012

OASIS ebXML RegRep V4.0 approved as an OASIS Standard

OASIS ebXML RegRep Version 4.0 has been approved by the membership as an OASIS Standard [1].



The OASIS ebXML RegRep V4.0 [3] standard specification defines the service interfaces, protocols and information model for an integrated registry and repository. The repository stores digital content while the registry stores metadata that describes the content in the repository. RegRep is an open specification for software that manages diverse content such as documents, images, services, devices, assets, schemas, WSDL, ontologies, records. Statements of Use for RegRep V4.0 were received from MIT's Lincoln Laboratory, Wellfleet Software and NOAA. More information on OASIS ebXML RegRep v4.0 and the TC generally can be found on the TCs web page at http://www.oasis-open.org/committees/regrep/.

Monday, June 13, 2011

B2B Web Services: ebXML Messaging version 3.0 and AS4 Interoperability Demonstration

Announcement:  Webinar on June 29

http://img.gotomeeting.com/g2mimages/webinar/themes/basic/button_registerNow.gif

Space is limited.
Reserve your Webinar seat now at:
https://www1.gotomeeting.com/register/665092680

Within OASIS, the ebXML Messaging Services Technical Committee designs Web Services-based messaging protocols for B2B data exchange. In 2002 the TC developed the version 2.0 of ebMS. Since then it has continued to respond to emerging requirements and newer technologies and standards which in 2007 resulted in the OASIS standard approved version 3.0 Core Specification. And most recently, the TC has produced two significant new deliverables:

·         The AS4 profile : a light-weight profile of the ebMS 3.0 Core Specification. AS4 is designed with input from GS1 and is a Web Services-based functional superset of both ebMS 2.0 and of the EDIINT AS2 standard.
·         The ebMS 3.0 Advanced Features Specification : extends the ebMS 3.0 Core Specification with support for ebMS intermediaries (multi-hop), efficient high-volume messaging (bundling) and exchange of very large messages (splitting and compression).

OASIS invites you to attend a free webinar that will provide:

§  A recap of ebMS 3.0, its main features and advantages over the earlier version 2.0.
§  A brief overview of AS4 and the new Advanced Features specification.
§  An interoperability demonstration showing use of AS4 in support of the OAG Order to Invoice process for use in the midmarket. This demonstration will involve multiple independent AS4 implementations.

Who should attend: 

Standards experts from other OASIS TCs and from other standards groups working on B2B data exchange or Web Services.  Software architects, product managers and product marketeers in B2B and data exchange areas. End users and specialists with an interest in new trends in data exchange.

Reference links:
ebMS TC public home page: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-msg

Time:

17:00 PM - 19:00 PM CEST (Central Europe)
11:00 AM - 12:00 PM EDT (US East Coast)
08:00 AM - 09:00 AM PDT (US West Coast)
Title:
B2B Web Services: ebXML Messaging version 3.0 and AS4 Interoperability Demonstration
Date:
Wednesday, June 29, 2011
Time:
11:00 AM - 12:00 PM EDT
After registering you will receive a confirmation email containing information about joining the Webinar.
System Requirements
PC-based attendees
Required: Windows® 7, Vista, XP or 2003 Server

Macintosh®-based attendees
Required: Mac OS® X 10.4.11 (Tiger®) or newer

Wednesday, February 02, 2011

Latest CAMeditor v1.9 now available from Sourceforge

The latest CAMeditor release is now available from Sourceforge:
 
 
Highlights include:
 
1) Complete external code lists support for code values via files and import of code lists
 
2) Enhancements to the evaluator, NDR checks and NIEM re-use scoring tools
 
3) Performance enhancements to XSD schema importing tool
 
4) Generation of NIEM EIEC / BIEC dictionary schema from ERwin enterprise model components
 
5) Support for KeyRef notations in structure editor
 
6) Enhanced XML example generation
 
Then there's a raft of fixin's and improvements from over 4 months of development since the last release.  Full details are in the release notes PDF documentation and the online tracker system.

Please feel free to provide feedback via Sourceforge project discussion area, OASIS CAM dev list, or contacting the team directly.

ebXML framework and cloud services interoperability?

According to a new blog post on AS4 it has the potential to become the standard for cloud based integration services.  For more information on the concepts and ideas - see:

http://blogs.gxs.eu/2010/11/30/will-as4-become-the-communications-standard-for-cloud-based-integration-services/

February, 2011

Wednesday, December 01, 2010

Call for participation - OASIS Business Document Exchange TC

The purpose of the TC is to define specifications for a lightweight and federated messaging infrastructure supporting a 4-corner model(1) for the secure and reliable exchange of electronic documents.
The specific objectives will be to:

1. Establish specifications for a lightweight and federated document transport infrastructure supporting the secure and reliable exchange of electronic business documents.

2. Profile and maintain a robust, secure and lightweight addressing mechanism (SMLP) capable of exposing metadata about endpoints (including supported business processes, content standards, transport protocols, and security requirements) and capable of being operated in a highly distributed environment.

3. Support the dynamic creation of connections based on look-up of services at runtime.

4. a) Profile and maintain the START (Secure Trusted Asynchronous Reliable Transport) protocol. START is intended to be used as a transport profile between Service Providers in the 4-corner model.

4. b) Profile and maintain the LIME (Lightweight Message Exchange) protocol, a secure and reliable lightweight messaging protocol. LIME is intended to be used as a transport profile between senders or receivers and their Service Providers in a 4-corner model.

5. Profile and maintain the ebMS 3.0 protocol for use in the 4-corner model with SMLP.

6. Give guidance on using other transports in a 4-corner model.

7. Develop specifications that support service levels appropriate for large scale deployment.
First meeting:

The first meeting will be held on 19 January 2011 (at 17:00 CET) as a one-hour conference call. The meeting facility will be available at

https://connect.forskningsnettet.dk/bdexchange/. Sign in as guest.

(1) The 4-Corner Model

A document exchange process set-up whereby each Participant has contracted with one or several separate Service Providers, whereby the Service Providers ensure the correct interchange of documents between the Participants.
When senders and receivers of documents are supported by their own consolidator service provider (for the sender) and aggregator service provider (for the receiver), it is referred to as a 4-Corner model. A network usually based on open standards provides connectivity and the facilities for the secure trusted exchange of business documents. In the 4-Corner models, the consolidator and aggregator roles are often two different service providers.

Definition inspired from http://www.e-invoice-gateway.net/helpandsupport/glossary/

For more information see:

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=bdx

Sunday, August 15, 2010

Public review of OASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features

The OASIS ebXML Messaging Services Technical Committee has recently approved the following specification as a Committee Draft and approved the package for public review.

This specification complements the ebMS 3.0 Core Specification by specifying advanced messaging functionality for message service configuration, message bundling, messaging across intermediaries (multi-hop) and transfer of (compressed) messages as series of smaller message fragments. 

The public review starts today, 13 August 2010, and ends 12 October 2010. This is an open invitation to comment. We strongly encourage feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of OASIS work. We also welcome interested parties to join the TC as it continues to further development of its specifications. Please feel free to distribute this announcement within your organization and to other appropriate mail lists.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility:


http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ebxml-msg
The specification document and related files are available here:

Editable Source:
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/ebms-v3-part2-cd-01.odt
PDF:
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/ebms-v3-part2-cd-01.pdf
HTML:
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/ebms-v3-part2-cd-01.html


 

- visitors: