Format name: PDF file format File extension: pdf MIME type label: application/pdf Format specification: ISO 32000-1:2008 (Appendix 18 Item 16 of the Specification) Format implementation: Adobe Acrobat version 8, OpenOffice.org version 2, Microsoft Office 2007 and software of other manufacturers, Adobe Reader (for preview) Raster graphics formats Format name: Tagged Image File Format (TIFF) File extension: tif, tiff MIME type label: image/tif, image/tiff, image/tiff-fx Format specification: LST ISO 12234-2:2008 (Appendix 18 Item 12 of the Specification) Format implementation: Scanners, software of various manufacturers Format name: Joint Photographic Experts Group (JPEG) format File extension: jpg, jpeg, jfif MIME type label: image/jpeg Format specification: LST ISO/IEC 10918-1:2009 (Appendix 18 Item 11 of the Specification) Format implementation: Digital cameras, software of various manufacturers, internet browsers (for preview) Format name: Portable Network Graphics (PNG) format File extension: png MIME type label: image/png Format specification: LST ISO/IEC 15948:2009 (Appendix 18 Item 13 of the Specification) Format implementation: Software of various manufacturers, internet browsers (for preview) __________________
Electronic document specification ADOC-V2.0 Appendix 6 FORMATS FOR THE ATTACHED ELECTRONIC DOCUMENTS No. Requirement Description Format: Electronic document in conformity with this Specification, stored in the package File extension: adoc, asice, sce MIME type label: application/vnd.etsi.asic-e+zip Format: Electronic document in conformity with the ADOC-V1.0 specification File extension: adoc application/vnd.lt.archyvai.adoc-2008 MIME type label: 3. Format: Electronic document, stored in ASiC-S type container file in conformity with the requirements of the ASiC standard and the ASiC Baseline Profile. File extension: asics, scs MIME type label: application/vnd.etsi.asic-s+zip 4. Format: Electronic document, stored in ASiC-E type container file in conformity with the requirements of the ASiC standard and the ASiC Baseline Profile. File extension: asice, sce MIME type label: application/vnd.etsi.asic-e+zip 5. Format: Electronic document in conformity with the MDOC-V1.0 specification. File extension: mdoc MIME type label: application/vnd.lt.archyvai.mdoc-2010 6. Format: Electronic document in conformity with the EGAS V1.0 specification. File extension: adoc MIME type label: application/vnd.lt.sodra.egas-2009 7. Format: Electronic document in conformity with the PDF-LT-V1.0 specification File extension: pdf MIME type label: application/pdf __________________
Employee who registered the document registrar Employee8 Not in element No No ID code of the natural person (legal entity) who registered the document code Text Not in element Yes, in element, for legal entity No Metadata of the received document registration Received document registrations: receptions Element Not in element Yes, in the document if registered Yes Received document registration: reception Element Yes Yes, in the document if registered Yes Reception date date Date6 Not in element Yes, in element No Registration No. of the received document number Text Not in element Yes, in element No Employee who registered the document registrar Employee8 Not in element No No Receiver: receiver Element Not in element Yes, in element No Receiver’s name or first name and surname name Text Not in element Yes, in element No Receiver’s code code Text Not in element Yes, in element if legal entity No Receiver’s supplemental code additionalCode Text4 Yes N; No Receiver’s e-mail address email Text Not in element No No Receiver’s address address Text Not in element No No Receiver is: natural person (true) or legal entity (false). individual Logical Not in element Yes, in element No Metadata of electronic signatures (stored in the XAdES signature file) Claimed signing time SigningTime Date6 Not in XAdES signature Yes, in XAdES signature - Purpose of electronic signature CommitmentTypeIndication Text (optional)9 Not in XAdES signature Yes, in XAdES signature -
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.
CertifiedRoles Prohibited 0 SignedDataObjectProperties Yes 1 DataObjectFormat Yes 1-N One DataObjectFormat element shall be generated for each ds:Reference element pointing to the file. This element shall not be created for the ds:Reference element pointing to the ds:SignedProperties element. Description No 0-1 ObjectIdentifier No 0-1 MimeType Yes 1 MIME type for the file indicated in this element shall match the MIME type for that file specified in manifest file (META-INF/manifest.xml). Encoding No 0-1 CommitmentTypeIndication Yes 1 For all data objects covered by this signature single signature purpose (commitment type) shall be indicated. AllDataObjectsTimeStamp Prohibited 0 IndividualDataObjectsTimeStamp Prohibited 0 UnsignedProperties No 0-1 UnsignedSignatureProperties No 0-1 SignatureTimeStamp Yes 1 Only one SignatureTimeStamp/EncapsulatedTimeStamp element may be generated to store time-stamp; xadesv141:ArchiveTimeStamp/XMLTimeStamp element use is prohibited. CompleteCertificateRefs Prohibited 0 Item 63 of the Specification. CompleteRevocationRefs Prohibited 0 Item 63 of the Specification. AttributeCertificateRefs Prohibited 0 Item 63 of the Specification. AttributeRevocationRefs Prohibited 0 Item 63 of the Specification. SigAndRefsTimeStamp Prohibited 0 Item 63 of the Specification. RefsOnlyTimeStamp Prohibited 0 Item 63 of the Specification. CertificateValues No 0-1 For certificates storage the EncapsulatedX509Certificate element shall be used; OtherCertificate element use is prohibted. RevocationValues No 0-1 CRLValues and/or OCSPValues elements shall be used to store certificate validation data; OtherValues element use is prohibited. AttrAuthoritiesCertValues Prohibited 0
LST ISO/IEC 29500-2:2009 “Information technology - Document description and processing languages - Office Open XML File Formats - Part 2: Open Packaging Conventions (ISO/IEC 29500-2:2008, identical)”; TECHNICAL CORRIGENDUM 1: LST ISO/IEC 29500-2:2009/AC1:2010. LST ISO/IEC 29500-3:2009 “Information technology - Document description and processing languages - Office Open XML File Formats - Part 3: Markup Compatibility and Extensibility (ISO/IEC 29500-3:2008, identical)”; TECHNICAL CORRIGENDUM 1: LST ISO/IEC 29500-3:2009/AC1:2010. LST ISO/IEC 29500-4:2009 “Information technology - Document description and processing languages - Office Open XML File Formats - Part 4: Transitional Migration Features (ISO/IEC 29500-4:2008, identical)”; TECHNICAL CORRIGENDUM 1: LST ISO/IEC 29500-4:2009/AC1:2010. 16. LST ISO 32000-1:2009 “Document management - Portable document format - Part 1: PDF 1.7 (ISO 32000-1:2008, identical)”. 17. OASIS: “Open Document Format for Office Applications (OpenDocument) Version 1.2”, http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html, 2011. 18. PKWARE “.ZIP File Format Specification”, . 19. RFC 6960 “X.509 Internet Public Key Infrastructure: Online Certificate Status Protocol – OCSP”, , 2013. 20. RFC 3161 “Internet X.509 Public Key Infrastructure: Time-Stamp Protocol (TSP)”, , 2001. 21. RFC 3986 “Uniform Resource Identifier (URI): Generic Syntax”, , 2005. 22. RFC 3987 “Internationalized Resource Identifiers (IRIs)”, , 2005. 23. RFC 4288 “Media Type Specifications and Registration Procedures”, , 2005. 24. RFC 5280 “Internet X.509 Public Key Infrastructure: Certificate and Certificate Revocation List (CRL) Profile”, , 2008. 25. W3C Recommendation “XML Signature Syntax and Processing (Second Edition)”, , 2008.