SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 200901 : Identifier : M9730 - Objet technique, document annexé / Technisch object, bijgevoegd document - (Messages with added documents - Multimedia JPEG, TIF, PDF) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Any
Receiver : Any
Status : 3 - Version : 1
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
||
| 11 | n |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
|
| 12 | n |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 20 |
GUID (Globally Unique IDentifier) du message référencé
|
No
|
-
|
-
|
Mand.
|
ReferencedMessageGuidReference
|
||
| 30 |
Document annexé
|
No
|
-
|
-
|
Mand.
|
Document...
|
||
| 40 |
Indication présence Multimédia
|
Yes
|
1
|
Mand.
|
MultimediaFileIsPresentProcesscode
|
|||
| 50 |
MultiMediaData fichier : Composite element : Filetype, Filename, Stringbase, Stringlength, String
|
No
|
-
|
-
|
Mand.
|
...Datafile MultimediaDetail MultimediafileName MIMElikeContentTransferEncoding DatastringLength Datastring
|
||
(*) n u d : new / updated / deleted since previous version.
(**) Usage: The indications Mandatory / Conditional / Optional are to be understood in respect of the actual level of the Data element:
example given; some party data-set as a whole can be optional, while, if present, the party's name within that party data-set can be mandatory.
Remark: in UN/Edifact, "Mandatory / Conditional" are notions used within the standard. And within edi-guides (a refinement of a standard) the "Conditional" can become "Required / Optional / Dependent / Advised / Not used". Ideally we should implement the same ideas.
(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.