| || |
Elements of EC-Design
Business process data model
This data model describes all information that is exchanged between actors in order to
support the business process between those actors.
Transaction data model
A transaction data model specifies the information requirements of one transaction. It is a
view on the business process data model.
Each individual message function in a transaction, specified by a user group, is called a
functional message. A functional message is defined as a view on the transaction data
An EDIFACT message defines the structure for the exchange of information in a transaction
and is part of a Trade Data Interchange Directory (TDID). Each TDID consists of a message
directory, segment directory, (composite) data element directory, and codelists.
A mapping of a transaction data model to an EDIFACT message describes the conversion of
information in the transaction data model into the syntax of the EDIFACT message. A
transaction data model can be mapped to multiple EDIFACT messages.
The functional message XML Schema technical documentation from EC-Design is an exact specification of the
functional message in terms of the international W3C XML Schema standard. This output
format is intended for machines more so than for humans to read. The functional message XML
Schema can be fed straight into any conventional XML, XML Schema parser, such that the
operational environment is configured automatically with the functional message modeled in EC-Design.
Actors and Actor group
An actor is a user which implements one or more functional messages. An actor group is a
number of users which have agreed to introduce EDI by means of one or more functional