This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: xslt and edi question
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: Re: [xsl] xslt and edi question
- From: "cutlass" <cutlass at secure0 dot com>
- Date: Wed, 1 Aug 2001 18:21:38 +0100
- References: <DB4D0D451426D11190EA0060B03CCC790185BF4E@VANCOUVER_NT>
- Reply-To: xsl-list at lists dot mulberrytech dot com
and thats because EDI represents ( at least to me ) the antithesis of what
xml is as a pure file format, though i can use & in EDI without any
*grumble*<![CDATA[]]> *grumble*................
cheers, jim fuller
----- Original Message -----
From: "Clapham, Paul" <pclapham@core-mark.com>
To: <xsl-list@lists.mulberrytech.com>
Sent: Wednesday, August 01, 2001 6:14 PM
Subject: RE: [xsl] xslt and edi question
> I can't speak for Allen, and I know this is off-topic for XSLT, but in my
> experience with EDI the short answer is "Damn right they expect us to do
> that translation."
>
> PC2
>
> -----Original Message-----
> From: Richard Draucker [mailto:richard@draucker.com]
> Sent: August 1, 2001 10:03
> To: xsl-list@lists.mulberrytech.com
> Subject: Re: [xsl] xslt and edi question
>
>
> I thought the whole value in XML for EDI was the deployment of a
schema/dtd
> to which each client would adhere. Are you saying the clients expect you
to
>
> do the translation from their inhouse format to your XML schema/dtd for
> them?
> Just curious.
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list