RE: Message Header Info

["Rik Drummond" <drummond@onramp.net>]

that should be appropriate in the final draft of this effort. at this time
we are going to make it simple and just list stuff in groups as john said in
the last conf. call. you might wish to take a header item and show it in iso
9735 so that everyone on the list understands what you are suggesting...
best regards, rik

-----Original Message-----
From: owner-ebxml-transport@lists.oasis-open.org
[mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of DDOBBING
Sent: Tuesday, February 15, 2000 6:02 PM
To: ebXML-Transport@lists.oasis-open.org
Subject: RE: Message Header Info


Tim,

As I understand it, the task for which John Ibbotson was seeking input,
related to the extract and analysis of the data item specifications
contained in the various message based enveloping techniques.  Therefore, I
believe it to be  important that the latest approved version of ISO 9735
(EDIFACT application level syntax rules) is used, albeit at this juncture V4
may not have widespread implementation.

I must point out that the basic syntax rules specified in Version 4 remain
unchanged from Version 3, with the exception that the coverage of character
repertoires has been extended, and two new techniques have been introduced
(the provision for 'dependency notes' and the introduction of a service
repetition character).  The 'dependency notes' correspond to 'syntax notes'
in X12.  The repetition character is a syntax issue and not really related
to the task at hand.

In effect, Version 4 of ISO 9735 is an extension Version 3 (e.g. the UNB
(Interchange header segment has been enhanced between V3 and V4 to permit
the identification of the service code list directory version number;
identification of the character encoding scheme; and internal
sub-identification of the sender and recipient. In addition, to conform to
year 2000 requirements, the date format in this segment has been extended).
By using V4, I do not think this would present any problem in building a
bridge to V3 (at an appropriate point during the project). However, if we
use V3 as the basis, then building a bridge to V4 could well be problematic.

Having said the above, the other key feature in V4 is the specification of
the envelopes for Interactive EDI (used by the US travel industry, etc) and
for security.  Nether of these features appear in V3.

Finally, the new features in V4 were added at the instigation of user
requests and as such represent specific requirements of the business
community. I do not think it to be wise to exclude the supporting data items
from the analysis.

Regards
David


--- David Dobbing, Data Logistics, ddobbing@attmail.com

> -----Original Message-----
> From: Tim McGrath
> Sent: Tuesday, February 15, 2000 12:16 AM
> To: DDOBBING
> Cc: internet!lists.oasis-open.org!ebXML-Transport
> Subject: Re: Message Header Info
>
>
> Dave's response raises an interesting issue about EDIFACT Headers.
>
> He has provided Version 4. specifications.  This latest
> standard provides several functional extensions such as
> repeating elements, formal dependency notes and enhanced security.
>
> However in a practical sense many existing EDIFACT
> users/systems/value added networks are not in a hurry to
> migrate from  Syntax Version 3 (or Version 2).   Furthermore,
> Version 4 is not fully upwardly compatible with previous
> syntax versions potentially making such migration costly.  On
> this basis it appears that much of the EDIFACT community are
> now stable at version 3.
>
> My suspicion is that to provide a more appropriate bridge
> between EDIFACT and  XML we must address the systems that are
> currently in use (ie Version 3 Headers).
>
> Should this be undertaken in parallel to the analysis of
> EDIFACT Version 4 ??
>
>
> DDOBBING wrote:
>
> > Hello John,
> >
> > Recently joined the group. If you have not already received
> same, please find attached the specification of the
> UN/EDIFACT Headers  This specification (Part 1 of 9) is the
> most recent version, Version 4 of the syntax (ISO 9735) as
> published October 1998.  You can also find the directory of
> the components at the JSWG (Joint Syntax Working Group) at
> http://pc1.gefeg.com/jswg, including the associated code
> lists. By all means if you have any further queries, an
> e-mail. I am a member of the JSWG and editor of the aforementioned.
> >
> > Regards
> > David
> >
> > David DOBBING
> > Data Logistics Pty Ltd
> > 505 Darling Street
> > Balmain
> > Sydney   NSW 2041
> > AUSTRALIA
> >
> > Ph: +61 2 9555-9914
> > Fx: +61 2 9555-1589
> > E-mail: ddobbing@attmail.com
> >
> > ------------------------------------------------------------------
> >
> > > -----Original Message-----
> > > From: internet!uk.ibm.com!john_ibbotson
> > > Sent: Thursday, February 10, 2000 9:28 PM
> > > To: internet!lists.oasis-open.org!ebXML-Transport
> > > Subject: Message Header Info
> > >
> > > From the call yesterday we decided to analyse the
> following headers:
> > >      UCC Net
> > >      OAG
> > >      e5
> > >      XML Messaging
> > >      BizTalk
> > >      EDI INT AS1 & AS2
> > >      EDI Header
> > >      RosettaNet
> > >      FIX
> > > I've also added ICE to the list.
> > >
> > > So far I've received pointers to:
> > >      EDI INT AS1 & AS2
> > >      FIX
> > >      ICE
> > >      RosettaNet
> > > So we're missing several. Can you get them to me asap so we
> > > can complete the
> > > initial analysis on time ?
> > >
> > > After the call yesterday, I contacted the guys in IBM
> > > Research who put together
> > > the document I circulated at Orlando on header structures.
> > > They have volunteered
> > > to do the leg work on analysing the different headers since
> > > they already have
> > > experience with those listed in the document. I will keep
> > > them in line with the
> > > WG's requirements and timescales.
> > >
> > > Cheers,
> > > John
> > >
> > > MQSeries Technical Strategy & Planning,
> > > IBM UK Ltd, Hursley Park,
> > > Winchester, SO21 2JN
> > >
> > > Tel: +44 (0)1962 815188
> > > Fax: +44 (0)1962 816898
> > > Notes Id: John Ibbotson/UK/IBM
> > > email: john_ibbotson@uk.ibm.com
> > >
> >
> >
> --------------------------------------------------------------
> ----------
> >                          Name: Part1_Jswg_n95.pdf
> >    Part1_Jswg_n95.pdf    Type: Acrobat (application/pdf)
> >                      Encoding: base64
> >
> >                            Name: Part1TC_Jswg_n96.pdf
> >    Part1TC_Jswg_n96.pdf    Type: Acrobat (application/pdf)
> >                        Encoding: base64
>
> --
> regards
> tim mcgrath
> TEDIS   fremantle  western australia 6160
> phone: +618 93352228  fax: +618 93352142
>
>