There is no published version of the gXML 1.0 spec, which is what
SpecBuilder uses (the only document publicly available is for something
like version .7 or .8 both of which are very different than 1.0). I
have implemented it, but had to reverse engineer it. As far as I can
tell, gXML is not very widely used. SEF seems to be used more (you can
purchase EDI specifications in SEF). There is a current document that
describes the current version of the SEF spec.
Ironically, both X12 and EDIFACT have messages which describe messages
(DIRDEF and I forget what the X12 is), however I have not heard of any
implementations of that technology.
As Brian says, I think people are (sadly) more committed to Word and
paper formats.
Francis
akshay_sap wrote:
>
> Hi ALL,
>
> I want to convert EDI to XML with compliance checking. For
> that, I need to parse or read an SEF file and validate the EDI file. I
> tried to read SEF file programmatically, but didnt get success. Can
> anyone help me out in parsing or reading an SEF file.
>
> I would like to ask one more thing. Which formats of implementation
> guideline for EDI are commonly used? Is it SEF or gXML?
>
> Thanks n Regards,
> Akshay
>
>
--
Francis Upton IV
[EMAIL PROTECTED]
Tel 510 835 3123
Fax 501 648 1464 (yes, it's 501)
Cell 510 432 1589
[Non-text portions of this message have been removed]
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
