RE: ebXML and RosettaNet

[Krishna Sankar <ksankar@cisco.com>]

Hi all,

	Let me add my thoughts to the mix.

	1.	RN and ebXML can be interchangeable (i.e. you can execute a Business
process via RN or ebXML, if one has defined the BPs) but *not* interoperable
without a bridge. (Jim's first paragraph explains this) i.e. semantically
Yes, syntactically NO. (Of course, I am a little liberal with the words
"syntax" and "semantics")

	2.	We all (could) agree that the payloads might be the same, but the
difference is in the transport and most probably transformations would be
required at the header, envelope and other similar structures.

	3.	If we envision a bridge between "compatible" standards (i.e. standards
in the same space) how do we fill the missing elements ? Most probably
default values specific to the particular Business Process and organization.

	3.	A related issue is the security. One can transport an encrypted payload
across the different standards, but if the whole message is signed, the
bridge would not be able to sign the envelopes for the sender ;-0

	4.	A mapping between the standards definitely is useful, but I do not think
an interoperability specification *between* standards is ebXML's
responsibility. As the standards are evolving at a fast rate, no standard
can publish an interoperability "bridge" with others in it's own space. Of
course, the standards need to say how they will operate with the ones they
depend on - like the XML DSIG, XMLEncryption et al.

		With due respect to all other standards, I also cannot see ebXML as a (or
THE) super "B2B" standard

	5.	Organizations would need to support multiple standards (hopefully a few)
between their customers, partners and suppliers. i.e. if someone talks ebXML
to an organization, the organization will need an ebXML engine and similarly
would need a RosettaNet engine to talk to partners who talk only RosettaNet.
Most probably the architecture would include an abstraction layer (like a
middleware) to mask this difference from the backend services.

		I am for a light weight XML infrastructure which can support DTDs,
choreographies and Business Processes from various vertical and horizontal
standards. May be that is where Erik's convergence can be achieved. Till now
we had the firmware/hardware transport (TCP et al) and may be it is time for
an upper layer software transport. BTW, there are more initiatives in this
space including BizTalk (to some extent) and the XMLP. SOAP, of course, is a
candidate here (at a lower level in the stack) as ebXML and XMLP are based
on SOAP

		But like Erik pointed out, talking ebXML to a partner who has only
RosettaNet infrastructure, wouldn't be possible. My question here is, do we
need interoperability at this level ? Do ebXML and RosettaNet and BizTalk
and XMLP need to talk to each other ? And is it a reality to expect them to
do so ?

cheers

|-----Original Message-----
|From: Erik.J.Leckner@seagate.com [mailto:Erik.J.Leckner@seagate.com]
|Sent: Saturday, March 24, 2001 2:42 PM
|To: jdc-icot@lcc.net
|Cc: JohnY@Edifecs.com; Erik.J.Leckner@seagate.com;
|ebxml-bp@lists.ebxml.org
|Subject: Re: ebXML and RosettaNet
|Importance: High
|
|
|
|
|
|
|All,
|
|For clarification purposes, I would like to summarise the
|conclusion from this discussion:
|
|   An ebXML-based service cannot deliver RNet PIPs without
|transformation from RNIF or UMM to BP.
|   This makes defining interworking ('interoperability') between
|the two services/architectures somewhat of a daunting task.
|
|   Question: Is it in ebXML's scope to interwork with all or a
|select set of existing electronic business exchange industry
|           standards, such as RosettaNet? If it is all, then
|obviously ebXML can not focus on one set of standards to interwork.
|             ebXML would then act as the convergence point for all
|B2B standards .
|
|   John stated that 'Only a RosettaNet offical will be able to
|express their policy with regard to use of their formats outside of the
|   RN group.' This sounds like ebXML might need to address this
|topic with the possibility of defining interworking gateways or 'bridges'
|   between various industry standards, such as RosettaNet.
|Otherwise, this topic might always come up in the future when an
|organization
|   must define their own mapping/bridge between the two standards,
|if they choose to support multiple standards, such as ebXML and
|   RosettaNet.
|
|   Question: Should ebXML define the specification of
|interoperability mechanisms to enable multi-standard communication
|to take place,
|             If so, the work would have to be based on a set of
|scenarios, such as this:
|
|          1. ebXML to RosettNet
|          2. RosettaNet to ebXML
|          3. ebXML to 'standard x'
|          4. 'standard x' to ebXML
|               ...
|
|Best Regards,
|Erik J Leckner
|Director, Technical Architecture & Standards
|Seagate Technology, LLC
|
|
|
|
|
|Jim Clark <jdc-icot@lcc.net> on 03/24/2001 09:28:25 AM
|
|To:   John Yunker <JohnY@Edifecs.com>
|cc:   Erik.J.Leckner@seagate.com, ebxml-bp@lists.ebxml.org
|
|Subject:  Re: ebXML and RosettaNet
|
|
|Gentlemen,
|
|I would like to add my 2 cents worth. Like John I have been involved in
|both
|efforts.
|
|First, I fully concur with John's assessment, however, I would like to
|expand on
|a few issues.
|
|In that there are some structural differences between a ebXML document and
|a
|RNet document, I do not believe that they are interexchangeable as is.
|ebXML has
|added some elements and moved some others. If a process requires some of
|these
|new elements, one will not be able to use a RNet Doc without adding this
|info.
|If one were to use a ebXML compliant document in an RNet implementation, it
|may
|require some restructuring. (not a difficult problem). Conclusion: use RNet
|in
|ebXML - maybe; use ebXML in RNet - most likely; so it may be best to model
|or
|define documents in ebXML so that the effort to use in both places is
|minimal.
|
|RNet PIPs- Along with the divergence in goals has been a divergence in
|perspectives. This shows up in divergence in the BP Specification Schema
|from
|the UMM MetaModel. Any process definition that is built on the UMM
|Metamodel or
|the RNIF1.0 or RNIF2.0 will be directly interchangeable. RNIF was built on
|the
|UMM Architecture and is a subset of the UMM.  Any process definition built
|on
|the BP Specification Schema will need transformation or production rules to
|map
|from the BP Schema to RNIF or UMM. It is too early to determine, but I do
|not
|believe that this transformation can be done without lose of semantics
|between
|the two representations.
|
|We may be close to interoperability but not interchangeability.
|
|Jim Clark
|Dir of Industry Solutions
|E2open
|936.264.3366
|
|John Yunker wrote:
|
|> Erik,
|>
|> I have participated in groups defining both the RosettaNet and ebXML
|> architecture. These comments are my own opinion and are not binding on
|> anyone in either organization.
|>
|> ebXML messaging infrastructure meets the requirements for executing
|> RosettaNet PIPs. Several key members of the RNIF 2.0 team are also
|members
|> of ebXML TRP, TPA, and BP.
|>
|> Also, the meta-metamodel upon which the specifications are based is
|common
|> between RosettaNet and ebXML, and has become part of the UN/CEFACT TMWG
|UMM.
|>
|> That said, there is no formal alignment at a specification level between
|the
|> two groups... In fact there is a divergence of primary goal between the
|two
|> groups. ebXML goal is to be horizontal enabler, and is currently
|embracing
|> many busines message groups, with wide latitude for individual members
|use
|> of formats. RosettaNet goal is interoperability between members, and
|> strongly constrains the element level content in their messages.
|>
|> It is very likely that RosettaNet messages will be executable within the
|> ebXML context, although there will probably not be strong restrictions on
|> message use, which begs the question "is it really RosettaNet, or just a
|> borrowing of their layouts". Only a RosettaNet offical will be able to
|> express their policy with regard to use of their formats outside of the
|RN
|> group.
|> Your question includes the phrase "ebXML defines similar specifications
|for
|> industries such as disk-drive designers/manufacturers". This is as far as
|I
|> can tell a non-issue, since ebXML will not be developing specifications
|for
|> specific industries. It is highly likely that the task of creating
|> specifications (when existing ones are not simply "adopted for use") will
|> fall to a group such as X12, OAG, or UN/CEFACT. This is a current area of
|> discussion that you should become involved in through BP/CC.
|> My observations only,
|> John
|>
|> -----Original Message-----
|> From: Erik.J.Leckner@seagate.com [mailto:Erik.J.Leckner@seagate.com]
|> Sent: Friday, March 23, 2001 1:55 PM
|> To: ebxml-bp@lists.ebxml.org
|> Subject: ebXML and RosettaNet
|> Importance: High
|>
|> Hi,
|>
|> Could anyone please answer the following question?
|>
|> Will ebXML's components be a replacement for RosettaNet PIP documents
|> transferred in b2b
|> exchanges or will ebxml support RosettaNet PIPs, as is? I would like to
|> know whether or not
|> this will change as ebXML defines similar specifications for industries
|> such as disk-drive designers/manufacturers (computer hardware, etc.).
|>
|> Best Regards,
|> Erik J Leckner
|> Seagate Technology, LLC
|> San Jose, CA
|> Director, Technical Architecture & Standards
|>
|> ------------------------------------------------------------------
|> To unsubscribe from this elist send a message with the single word
|> "unsubscribe" in the body to: ebxml-bp-request@lists.ebxml.org
|>
|> ------------------------------------------------------------------
|> To unsubscribe from this elist send a message with the single word
|> "unsubscribe" in the body to: ebxml-bp-request@lists.ebxml.org
|
|(See attached file: jdc-icot.vcf)
|
|
|