Not in element Yes, in element for Position of responsible person positionName Text No legal entity Structural subdivision structuralSubdivision Text Not in element No No Legal entity name organizationName Text Not in element No No Legal entity code code Text Not in element No No Supplemental code of legal Yes additionalCode Text4 No No entity Street address address Text Not in element No No E-mail address email Text Not in element No No Person represents himself (true) Not in element individual Logical Yes, in element No or legal entity (false). Notes: 1 Description of recurrent values: Value Description Yes Metadata may recur within enclosing element. Not in element Metadata shall not recur within enclosing parent element, but may recur if enclosing element recurs within document. Not in document Metadata shall not recur in any metadata file. Not in XAdES signature Metadata shall not recur in XAdES signature, but may recur in other XAdES signatures if they are present within 2 Description of mandatory values: Description Value Yes, in document Metadata shall be present within e-document (within any metadata file). Yes, in element Metadata shall be present within enclosing present element if that element is present. No Metadata is optional Yes, in XAdES signature Metadata shall be present in any XAdES signature. 3 XAdES signature may secure only logically related metadata groups; it may not cover isolated elements of relevant group (Items 65 and 83 of the Specification). All metadata group elements, which may be secured by a separate XAdES signature, shall contain the attribute. ID 4 Element shall have the attribute and its value should indicate the type of supplemental code (e.g., VAT payer code, social codeType security ID code, etc.). 5 If not set, the document is considered as composed when (if applicable) registered in the institution, where the document has originated (the date of edocument registration shall be used). Otherwise the claimed time of the last signature (stored in element) with indicated SigningTime – signature purpose of or shall be used. signature confirmation 6 Date, or date and time, as defined in the W3C recommendations for the XML format (xsd:dateTime or type with designated time xsd:date zone).
Position of responsible person positionName Text Not in element Yes, in element for legal entity No Structural subdivision structuralSubdivision Text Not in element No No Legal entity name organizationName Text Not in element No No Legal entity code code Text Not in element No No Supplemental code of legal entity additionalCode Text4 Yes No No Street address address Text Not in element No No E-mail address email Text Not in element No No Person represents himself (true) or legal entity (false). individual Logical Not in element Yes, in element No Notes: 1 Description of recurrent values: Value Description Yes Metadata may recur within enclosing element. Not in element Metadata shall not recur within enclosing parent element, but may recur if enclosing element recurs within Not in document Metadata shall not recur in any metadata file. Not in XAdES signature Metadata shall not recur in XAdES signature, but may recur in other XAdES signatures if they are present within 2 Description of mandatory values: Value Description Yes, in document Metadata shall be present within e-document (within any metadata file). Yes, in element Metadata shall be present within enclosing present element if that element is present. No Metadata is optional Yes, in XAdES signature Metadata shall be present in any XAdES signature. 3 XAdES signature may secure only logically related metadata groups; it may not cover isolated elements of relevant group (Items 65 and 83 of the Specification). All metadata group elements, which may be secured by a separate XAdES signature, shall contain the ID attribute. 4 Element shall have the attribute codeType and its value should indicate the type of supplemental code (e.g., VAT payer code, social security ID code, etc.). 5 If not set, the document is considered as composed when (if applicable) registered in the institution, where the document has originated (the date of edocument registration shall be used). Otherwise – the claimed time of the last signature (stored in SigningTime element) with indicated signature purpose of signature or confirmation shall be used. 6 Date, or date and time, as defined in the W3C recommendations for the XML format (xsd:dateTime or xsd:date type with designated time zone). document.
adoc_v2_amend.docx