OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: prototype proposal update

Nick, good job on the demo doc.
Here are some quick points:


-> add the "v1." in front of CustProfileUpdate in the intent.

-> remove the OTA <OTA_v1 ..........> and <v1.Content.........> tags from
the ebXML payload and paste in:
   <OTA_v1 Target="Production" GeoCode="+4256-1482">
        <v1.CustProfile ShareAllMarketInd="No" ShareAllSynchInd="Yes">
            <v1.Cust.PersonName NameType="Default">
            <v1.Cust.Telephone PhoneTech="Voice" PhoneUse="Work">
            <v1.Cust.Telephone PhoneTech="Voice" PhoneUse="Work">

Industry (verticals, but a better term) Migration points to an ebXML
Transport Infrastructure:

1) Industries would drop any industry-defined message type, such as that
by the "RQ" at the end of the original OTA <v1.CustProfileUpdateRQ> tag,
express this in the ebXML MessageType element. Note that OTA maintains
using it's industry-specific approach to versioning the OTA intention.
2) Industries would load the ebXML payload with the remaining industry
content. This
would mean dropping any industry-defined 'method or intention' and message
type, such as the
OTA <v1.CustProfileUpdateRQ> tag since this is to be defined in the ebXML
3) Other infrastructure information accomodated by the ebXML Transport
level defined
by an industry such as the TimeStamp attribute
from the original OTA top document element.........
<OTA_v1 Timestamp="2000-04-25 12:54:55.0" EchoToken="228722"
Target="Production" GeoCode="+4256-1482">
should be removed (given the same semantic as the ebXML Transport) and
into the ebXML Transport headers. The OTA EchoToken is in the same
because we can accomodate this in ebXML with the MID field that expresses
associated message Note we are not showing these in the demo.
4) An Industry may need to maintain information important to the industry
defined in perhaps a top industry root element with in ebXML payload. The
in the case of OTA are the the GeoCode and Target attributes on the
original OTA_v1 top tag.
These are now expressed within *what has now become the OTA payload top
tag* :
<OTA_v1 Target="Production" GeoCode="+4256-1482">.
Note that the TimeStamp and EchoToken are removed since the ebXML Transport
the same semantics.

A prime selling point that is evident in the demo of the ebXML Transport
(not complete for all of ebXML):

+ The ebXML Transport level provides a cross-industry approach for defining
constructs commonly defined by, or being defined by, industry-specific
efforts. The ebXML
Transport can free industry-level efforts from addressing
infrastructure-level constructs for
needed for commercial-level messaging.

Nick, I can speek to the detail in Brussels if needed.

Scott R. Hinkelman
Senior Software Engineer
XML/Java Solutions/Standards
Architecture and Development
IBM Austin
Office: 512-823-8097 TieLine: 793-8097
Home: 512-930-5675, Cell: 512-940-0519
Fax: 512-838-1074

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC