> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related 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 202101 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
Version : 1
Status : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2-UN/EDIFACT representation (including comments)
Indicator
Identifier
Version
10  
Document
No
-
-
Mand.
 
DOC+xxx 
20  
Document - Présence de fichier multimedia
Yes
1
Mand.
 
DOC+xxx - GIS+EW12+x--x' 
30  
Document - Document à (faire) signer
Yes
2
Option.
 
DOC+xxx - GIS+EW23+x--x' 
40  
Document - Signature digitale présente
Yes
2
Option.
 
DOC+xxx - GIS+EW24+x--x' 
50  
Document - Pérennité du URL
No
-
-
Cond.
FTX+063 présent et limité dans le temps 
DOC+xxx - DTM+161:ddmmyyyy:001' 
60  
Document - Numéro du document
No
-
-
Option.
 
DOC+xxx - RFF+009:x--x' 
70  
Document - URL document
No
-
-
Cond.
GIS+EW12 = 2 Non 
DOC+xxx - FTX+063+x--x:x--x:x--x:x--x:x--x' 
80  
Document - Media représentant le document
No
-
-
Cond.
GIS+EW12 = 1 Oui 
DOC+xxx - MMD+x--x+x--x:001:x--x:x--x' 

(*) n u d : new / updated / deleted since previous version.

(*bis) u : updated : this can be a codelist-version incrementing.
  Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
  The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
  Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...

(**) 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.