Attached please find a proposed mapping of RosettaNet Implementation
Framework (RNIF) 2.0 message header elements to ebXML message header
elements that Pete Wenzel, Brad Lund, Prasad Yendluri and I have put
together. This currently makes direct use of the SOAP-ENV:Header
extensibility feature to add RosettaNet namespace qualified elements, in
order to make it easy for solution providers to simultaneously support RNIF
2.0 and RNIF 3.0. (RNIF 3.0 is expected to be layered on top of the ebXML
Messaging Service.)
The purpose of this post is to solicit feedback on the naturaless of the
mapping, and to stimulate discussions on the completeness of the ebXML SOAP
Extension Elements schema. For example, should this mapping directly make
use of SOAP-ENV:Header extensions? Should the ebXML MessageHeader itself
allow for namespace qualified elements? Should additional elements be
provided in the ebXML header to avoid the need to encode multiple RNIF
header elements into a single ebXML header element?
For readers who are not familiar with the RNIF 2.0 header structures, I am
also attaching RosettaNet message guidelines for the RNIF DeliveryHeader adn
RNIF ServiceHeader. Further information on RNIF 2.0 can be found at:
http://www.rosettanet.org/rosettanet/Rooms/DisplayPages/LayoutInitial?Contai
ner=com.webridge.entity.Entity%5BOID%5BAE9C86B8022CD411841F00C04F689339%5D%5
D
-Arvola