The basics on our Edifact syntax
Go to the "Syntax dependent components", and read both the texts available on the "introduction" page.
These texts are not that long, and it is necessary to have at least gone over them.

Important parts of the website
In Dutch and in French, we explain how different parts of the website are related/connected with one another.

A message to the "digital natives"
What can be said; these are muddy waters...
This is not a "green field" (a blanc sheet of paper on which you can start drawing whatever, "out of the blue").
This is a "brown field" environment; an existing ecosystem with chained IT systems up and running.
You, boys and girls, have to put aside your shiny sneakers and bleached jeans; you must wear some serious chinos and rubber boots, you must dive into this pool of mud, get your hands dirty and dig out the information needed.
Here, you will find no glory without some pain and suffering.
Please, please, do read the manuals.
Michel Bormans, april 15th 2016.

A video about our Telebib2/Edifact Validation Tool
This is a first for us; we want to start using video material to help and instruct our audience.
In this first trial we talk about the tool which validates a message.
This is done in two stages, somewhat alike what is done when validating XML content. There too one first validates the content against the XML-syntax and when and if OK, only then the content is validated against the XML-schema which the XML-content refers to.
We fully separated these two stages in two separate utilities...

Context of this validation tool
The norm we develop, maintain and promote is an essential element within the roadmap leading to maximised efficiency for our stakeholders.
The annual figures published about the messages implemented and exchanged do show the difference in between what is dictated by our annual releases versus what is attained by those who must implement and maintain, which for sure is no easy task.
We, the Telebib centre, have more than once been positionned in between parties somewhat annoyed by unclear implementations and hence unclear reciprocal expectations.
In these matters we sincerely believe that the offering of such a validation tool, coming from the same source as the norm in itself, allows for all to accept the mutual agreement as the common standard to be gained.
These are the arguments which triggered the development of such validation tool, the ultimate goal being, as mentionned before, the maximised efficiency of/for our stakeholders.
And no, this is not about policing the playing field; this is all about facilitating and assisting the development teams in their daily work, by delivering them some means of quality-control.

...

To be continued...