SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EDOCxxx - Echange contextuel, document et ses meta-data - (Données document et Document / Document en zijn meta-data)
- Approved
, and is part of release 202301 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Any
Receiver : Any
Status : 2 - Version : 2
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Document
|
No
|
-
|
-
|
Mand.
|
Document...
|
||
| 20 |
Document - Présence de fichier multimedia
|
Yes
|
1
|
Mand.
|
MultimediaFileIsPresentProcesscode
|
|||
| 30 | u |
Document - Document à (faire) signer
|
Yes
|
3
|
Option.
|
DocumentToBeSignedProcesscode
|
||
| 40 | u |
Document - Signature digitale présente
|
Yes
|
3
|
Option.
|
DigitalSignaturePresentProcesscode
|
||
| 50 |
Document - Pérennité du URL
|
No
|
-
|
-
|
Cond.
|
FTX+063 présent et limité dans le temps
|
UrlDurabilityDate
|
|
| 60 |
Document - Numéro du document
|
No
|
-
|
-
|
Option.
|
DocumentReference
|
||
| 70 |
Document - URL document
|
No
|
-
|
-
|
Cond.
|
GIS+EW12 = 2 Non
|
UrlDocumentText
|
|
| 80 |
Document - Media représentant le document
|
No
|
-
|
-
|
Cond.
|
GIS+EW12 = 1 Oui
|
...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.