RE: [ebxml-bp] "ediPath" support?

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

http://isotc.iso.org/livelink/livelink?func=ll&objId=3473365&objAction=b
rowse&sort=name

You should see a page with a lot of docs, including

Document 		154n372_dis20625_xml.pdf Functions

Document 		154n372a_dis20625_din16557-5.pdf Functions 

The 2nd has the sections mentioned.	

-----Original Message-----
From: Yunker, John [mailto:yunker@amazon.com] 
Sent: Friday, October 15, 2004 9:54 AM
To: Monica J. Martin; Dale Moberg
Cc: ebxml-bp@lists.oasis-open.org
Subject: RE: [ebxml-bp] "ediPath" support?

Could you please point me to a source for ISO/DIS20625?

I would agree that Xpath applied to EDI structure (delimited structure
with standard tag construction converted to XML) is the cleanest way to
approach this problem.

Thanks!
John

-----Original Message-----
From: Monica J. Martin [mailto:Monica.Martin@Sun.COM] 
Sent: Friday, October 15, 2004 9:39 AM
To: Dale Moberg
Cc: ebxml-bp@lists.oasis-open.org
Subject: Re: [ebxml-bp] "ediPath" support?


Dale Moberg wrote:

> Just as Xpath is used in combination with the document envelope
> notation, I propose that we consider whether ISO/DIS20625 be mentioned

> as a supported notation for EDI or at least EDIFACT syntax.
>
> We could adopt Tag Naming rule 6.1.1 (Variant 1) and then use the
> XPath syntax over these element tags to specify the segment group, 
> segment, composite data element, and data element...
>
This is definitely in support of the DocumentEnvelopeNotation. +1. Can 
you provide more specifics Dale to discuss Monday or the following week?

Thanks.