RE: EDIINT and the EDI XML movement ...

[Brain <thebrain@xxxxxxxxxxxxxxxxx>]

It certainly makes sense to me to support XML.

-----Original Message-----
From:	RIK drummond [SMTP:drummond@xxxxxxxxxx]
Sent:	Wednesday, December 09, 1998 2:13 PM
To:	Gunther Schadow; chuck.egerter@xxxxxxxx; clueder@xxxxxxxxxxxxxxxx; ietf-ediint@xxxxxxx; John.Mani@xxxxxxxxxxx
Cc:	gannon@xxxxxxxxxxxx
Subject:	RE: EDIINT and the EDI XML movement ...

So are you'all feeling that we should support xml as part of the ediint
standards?

regards, rik

> -----Original Message-----
> From: owner-ietf-ediint@xxxxxxx [mailto:owner-ietf-ediint@xxxxxxx]On
> Behalf Of Gunther Schadow
> Sent: Monday, December 07, 1998 9:55 AM
> To: chuck.egerter@xxxxxxxx; clueder@xxxxxxxxxxxxxxxx;
> gunther@xxxxxxxxxxxxxxxxxxx; ietf-ediint@xxxxxxx; John.Mani@xxxxxxxxxxx
> Cc: gannon@xxxxxxxxxxxx
> Subject: RE: EDIINT and the EDI XML movement ...
>
>
> That's exactly what I meant: everyone is looking at XML and is planning
> to use it. So is HL7, so is X12, so is EDIFACT (?), everyone may be
> at a slightly different stage in the process (e.g. HL7 is almost
> committed to using XML for its version 3 and is planning on a demo
> for Spring 1999. But the bottomline for now is: noone is really done,
> and if someone where done with the specs, the broad user base is still
> not there. Give it some more time.
>
> But anyway, the part that was removed from my original message was that
> I don't believe XML presentation syntax puts a lot of new requirements
> to EDIINT protocols. The only thing that I conceive necessary is to
> introduce a parameter "syntax" for the MIME-EDI container so that the
> message processor can select the appropriate parser:
>
> Content-type: application/edi-hl7; syntax="xml"
>
> <HL7MSG ...>
> ...
> </HL7MSG>
>
>
>
> or
>
> Content-type: application/edi-hl7; syntax="traditional"
>
> MSH|...|||||
> BLA|||||
> BLA|||||
>
>
> This parameter "syntax" is already part of the current HL7 EDIINT
> draft. At last, we might want to think about revising RFC 1767
> (MIME-EDI).
>
> regards
> -Gunther
>
> Gunther Schadow -----------------------------------
> http://aurora.rg.iupui.edu
> Regenstrief Institute for Health Care
>
> 1001 W 10th Street RG5, Indianapolis IN 46202, Phone: (317) 630 7960
> schadow@xxxxxxxxxxxxxxxxxxx ---------------------- #include
> <usual/disclaimer>
>
> From: "Egerter, Chuck" <chuck.egerter@xxxxxxxx>
> Date: Sun, 06 Dec 1998 22:06:01 -0500
> > OBI has not yet released a version of their spec that uses XML.
>  The team is
> > just in the beginning phases of discussing how and when to
> incorporate it.
> > But... everyone is very optimistic about the benefits that we will gain
> >
> > Patrick - you may have more to add.
> >
> > > From:	clueder@xxxxxxxxxxxxxxxx [SMTP:clueder@xxxxxxxxxxxxxxxx]
> > > Sent:	Wednesday, November 25, 1998 4:04 PM
> > > To:	gunther@xxxxxxxxxxxxxxxxxxx; ietf-ediint@xxxxxxx;
> > > John.Mani@xxxxxxxxxxx
> > > Subject:	Re: EDIINT and the EDI XML movement ...
> > >
> > > >XML EDI may be relevant in the future. However, currently it seems to
> > > >be a moving target. As far as I know, neither X12 nor EDIFACT nor HL7
> > > >have been "converted" significant amounts of their users to XML, ...
> > >
> > > With one big exception: OBI (Open buying on the internet) use
> of XML for
> > > X12 850 purchase order.
> > >
>