atom feed6 messages in org.oasis-open.lists.ebxml-bpRE: [ebxml-bp] "ediPath" support?
FromSent OnAttachments
Dale MobergOct 15, 2004 8:55 am 
Monica J. MartinOct 15, 2004 9:38 am 
Yunker, JohnOct 15, 2004 9:53 am 
David RR WebberOct 15, 2004 9:55 am 
Dale MobergOct 15, 2004 12:35 pm 
Monica J. MartinOct 15, 2004 12:45 pm 
Subject:RE: [ebxml-bp] "ediPath" support?
From:Dale Moberg (dmob@cyclonecommerce.com)
Date:Oct 15, 2004 12:35:56 pm
List:org.oasis-open.lists.ebxml-bp

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:yun@amazon.com] Sent: Friday, October 15, 2004 9:54 AM To: Monica J. Martin; Dale Moberg Cc: ebxm@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:Moni@Sun.COM] Sent: Friday, October 15, 2004 9:39 AM To: Dale Moberg Cc: ebxm@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.