Wednesday, August 29, 2012

Golang project update: edigo

After some reflection, what I want to have is in fact to be able to auto-generate a Go package or packages, which can be imported into any Go code later, given an XML EDIFACT grammar file that is generated by some tool, such as (my current employer) Amadeus' Visual Services tool.

The format of this XML EDIFACT grammar file is

    Visual Services 5 - XML Generator
    ...list of transactions...
    ...list of messages...
    ...list of groups...
    ...list of segments...
    ...list of composites...

The resulting package codes could then be stored in a folder named after the interface name (in the above example "skd") as composites.go, segments.go, groups.go, etc. Every time there's a new version of the grammar XML file, edigo must be used to regenerate the said files.

That's all for now. I will write more on this later. Oh, and by the way, I've created a new repository on GitHub for this.


  1. I really enjoyed reading your blog. It was very well written and easy to understand. Unlike other blogs that I have read which are actually not very good. Thank you so much!
    Hire Golang Developer

  2. Good Article with new information, it left me a deep impression, thank you for sharing

    Casino Game Development