RE: AS2 XML requirements (was Re: HL7 Standards Process)

["Dick Brooks" <dick@xxxxxxxx>]

Wes,

I expect that HL7 will define "Transaction-set" identifiers when
constructing the Interoperability Profile. That's how it happened with GISB.
Perhaps a "namespace" qualified Transaction-Set identifier would be useful,
e.g. HL7:XXXyyyy


Dick Brooks
Group 8760
110 12th Street North
Birmingham, AL 35203
dick@xxxxxxxx
205-250-8053
Fax: 205-250-8057
http://www.8760.com/

InsideAgent - Empowering e-commerce solutions

> -----Original Message-----
> From: Rishel,Wes [mailto:wes.rishel@xxxxxxxxxxx]
> Sent: Wednesday, November 22, 2000 3:15 PM
> To: 'dick@xxxxxxxx'; 'Kit (Christopher) Lueder'
> Cc: 'Kepa Zubeldia'; Gunther Schadow; Rik Drummond; CLEM; Gary Crough;
> Beth Morrow; David@Drummondgroup. Com; GISB1@xxxxxxx;
> ietf-ediint@xxxxxxx
> Subject: RE: AS2 XML requirements (was Re: HL7 Standards Process)
>
>
> Is the transaction identifier qualified by another field or is
> there a need
> to set up a registry of transaction set identifiers? I suspect that HL7
> would prefer to maintain its own identifiers without worrying about
> collision with another standard or having to sit through length debates
> about whether to use a hyphen or an underbar.
>
>
> > -----Original Message-----
> > From: Dick Brooks [mailto:dick@xxxxxxxx]
> > Sent: Wednesday, November 22, 2000 9:57 AM
> > To: Rishel,Wes; 'Kit (Christopher) Lueder'
> > Cc: 'Kepa Zubeldia'; Gunther Schadow; Rik Drummond; CLEM; Gary Crough;
> > Beth Morrow; David@Drummondgroup. Com; GISB1@xxxxxxx;
> > ietf-ediint@xxxxxxx
> > Subject: RE: AS2 XML requirements (was Re: HL7 Standards Process)
> >
> >
> > Wes,
> >
> > > Furthermore, if all you know about a message is that it is
> > encoded in the
> > > XML syntax you really don't know enough to do an EDI function on the
> > > message. The EDI standards specify a lot more than syntax and these
> > > specifications are very much a part of the interface
> > contract. [snip]
> >
> > You are right on, that's why AS2 has a header field called
> > "Transaction-Set". The sender uses this header to identify
> > exactly what type of data is contained in the payload
> > (regardless of the
> > encoding syntax X12, XML. et al). For example, GISB uses the
> > same ANSI X12
> > 850 transaction set for different purposes so they created
> > transaction set
> > identifiers (e.g. G850NMST or G850RQCF) to provide more precision when
> > identifying a payload.  A sender would insert either "G850NMST" or
> > "G850RQCF" in the "transaction-set" header, this way the
> > receiving party can
> > "dispatch" processing to different "process flows" based on
> > the "transaction
> > set" identifier.
> >
> >
> > Dick Brooks
> > Group 8760
> > 110 12th Street North
> > Birmingham, AL 35203
> > dick@xxxxxxxx
> > 205-250-8053
> > Fax: 205-250-8057
> > http://www.8760.com/
> >
> > InsideAgent - Empowering e-commerce solutions
> >
> >