Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Re^2: EDIFACT - edi - Validator

by Cow1337killr (Monk)
on Aug 13, 2016 at 12:59 UTC ( #1169708=note: print w/replies, xml ) Need Help??

in reply to Re: EDIFACT - edi - Validator
in thread EDIFACT - edi - Validator

When you said "sell it", it excited the reptile part of my brain.

That said, I read Why is EDI still used, and how to deal with it? Yikes.

I looked at About Bots edi translator software. Quote: Programming language: Python.

Conceivably, one could use Inline::Python to interface Perl to the Bots open source edi translator.

(Fortunately, it seems that the authors of both pieces of software are active.)

GotToBTru, you mentioned a grammar approach. The Marpa::R2 folks are always looking for niches where Marpa can demonstrate its prowess.

Replies are listed 'Best First'.
Re^3: EDIFACT - edi - Validator
by GotToBTru (Prior) on Aug 14, 2016 at 04:25 UTC

    EDI is one of the illustrations of the maxim "the nice thing about standards is there are so many to choose from." Well, almost. There are not that many to choose from. The most popular, ANSI X12 and EDIFACT, were developed by multi-industry committees and it shows it. The standards allow so many options that they might as well not be a standard. But it's kept food on my table since 1991.

    Because very frequently trading partners supply each other with written specifications, I have often thought an automated method to read those files (maybe based on a grammar) would help with developing a practical system to validate a particular document for a particular trading partner, without having to put together the full standard for the hundred of document types, each composed of some subset of thousands of segment types, each of which is composed of a subset of thousands of element types. Because even if the standard says, for instance, a G62 segment is required in a 204 document, a particular trading partner can say it isn't required for them, and the same personalization can happen at the element level. Ranting aside, I should actually try this sometime. The potential time savings could be significant.

    You want to hear something funny? Some people think XML would be preferable.

    But God demonstrates His own love toward us, in that while we were yet sinners, Christ died for us. Romans 5:8 (NASB)

      I have been researching EDI on the web.

      What would constitute a proof of concept? That is, without investing a whole bunch of resources to a test, what would the input and the output look like? When I say input, I also mean the reference files or tables that the validator would read as it encountered each data segment and data element in the EDI input file.

      I propose validating a simple purchase order. I further propose that we stick to X12 initially.

      I have seen a validator on the web, so I have an idea what kind of error messages a validator would generate.

      If the proof of concept works, then we can complicate it further.

        The concept I have has two inputs: the written specification and the EDI file to be validated. No attempt is made to check the EDI file against any other external standard.

        I should also note I have no time at present to explore this concept. I am very willing to act as an adviser on somebody else's.

        But God demonstrates His own love toward us, in that while we were yet sinners, Christ died for us. Romans 5:8 (NASB)

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1169708]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (3)
As of 2023-06-02 01:29 GMT
Find Nodes?
    Voting Booth?

    No recent polls found