1

Specification of Electronic document PDF-LT-V1.0

Appendix 1

metadATA

sectioni

CREATION OF THE DOCUMENT METADATA

The metadata of the document creation are stored in the metadata stream of PDF document catalog. These metadata are optional for the Level BDocument. The example of such metadata is presentedin Appendix 4 SectionI.

Metadata / XMP property1 / Type2 / Mandatory in
Level A Document / Description
ID of the specification of the electronic document / LTUd:standardVersion / Closed Choice of Text / Yes / The value “PDF-LT-V1.0”shall be indicated for the edocumentcompliant tothis Specification.
Indication of edocument conformity with the Specification requirements level. / xmp:Identifier / Unordered array of Text / Yes / The conformity shall be indicated as an array item qualified with scheme, as defined in the Note 7 of this Appendix.
Author of the document / LTUd:authors / Ordered array of Person / Yes / The array of items describing one or more legal entities or natural persons who created the document. The array shall contain at least one item.
The names of the authors (LTUdEnt:nameproperty) shall be repeated in the dc:creatorproperty.
Addressees / LTUd:recipients / Ordered array of Person / Yes,
depending on the document nature / If addressees are indicated, they shall be specified as array of items describing one or more legal bodies or natural persons as addressees. The specified array shall contain at least one item. If addressees are not indicated, this metadata property shall not be present.
Document title / dc:title / Language
Alternative / Yes / The array of this property shall contain a default item (an item with xml:langqualifier value of “x-default”).
Titles of legal entities or names and surnames of natural persons – document creators / dc:creator / Ordered
array of
ProperName / Yes / The document producing application shall set the property value with the names of authorsspecified in LTUdEnt:nameitems ofthe documentmetadata propertyLTUd:authors. The document processing applicationshall use the values specified in the LTUd:authors metadata property.
Document languages / dc:language / Unordered
array of
Locale / No / The list of languages used in the document. For documents in Lithuanian languagethe value “lt-LT” should be specified.
ID of the document copy / LTUd:documentCopyIdentifier / Text / No / The metadata property is used to distinguish nonidentical copies of the document, e.g., different copies of the contract for Lithuanian and Latvian parts.
Document registration data in the copy / LTUd:originalRegistrations / Ordered array of Registration / No / Document registration (LTUd:registration) metadata transferred from the original document into its electronic copy.
Registration data of the received document in the copy / LTUd:originalReceptions / Ordered array of Registration / No / Received document registration metadata (LTUd:reception) transferred from the original document into its electronic copy.
Document receivers in the copy / LTUd:originalReceivers / Ordered array of Person / No / Document receivers’ metadata (LTUd:receiver) transferred from the original document into its electronic copy.
Name and version of application, which produced the document / xmp:CreatorTool / AgentName / No / The recommended format of the propertytext value is specified below in the table of XMP value types.

sectionii

doCument registraTION metadATA

Document registration metadata are storedin the metadata stream of PDF signature dictionary. These metadata are optional for Level BDocument. Examples of metadata are presented in Sections II and III of Appendix 4.

Metadata / XMP property1 / Type2 / Mandatory for the Level A Document
/ Description
Registration data of the document created / LTUd:registration / Registration / Yes, if registration is mandatedby legal acts. / Filled in by the author of e-document.
Document may contain zero or more instances of this metadata property, but no more than one metadata propertyshall be specified in a single metadata stream of PDF signature dictionary.
Registration data of the document received / LTUd:reception / Registration / Yes, if registration is mandated by legal acts. / Filled in by the receiver of e-document.
Document may contain zero or more instances of this metadata property, but no more than one metadata property shall be specified in a single metadata stream of PDF signature dictionary. When the registration metadata of the received document are specified, the document receiver’s data (LTUd:receiver) shall be specified in the same metadata stream.
Receiver of the document / LTUd:receiver / Person / Yes, if registration is mandated by legal acts. / Filled in by the receiver of the e-document.
Document may contain zero or more instances of this metadata property, but no more than one metadata property shall be specified in a single metadata stream of PDF signature dictionary.

section Iii

ElECtroniC SIGNATURE metadATA

Electronic signature metadata are stored in the dictionary entries of each PDF electronic signature.

Metadata / PDF signature dictionary key / Type5 / Mandatory for Level A Document / Mandatory for Level BDocument / Description
Purpose of electronic signature / Reason / text string / Yes / Yes / Valid values to indicate the purpose of electronic signature:
  • signing – “signature”;
  • “confirmation”;
  • “conciliation”;
  • “visa”,
  • registration of the created document – “registration”;
  • registration of the received document – “registration-of-incoming-documents”;
  • “acknowledgement”;
  • addition of resolutionon assigned task – “resolution”;
  • indication of executed task – “end-of-execution”;
  • archival notarization– “notarisation”;
  • “copy-certification”;
  • confirmation of authenticity (integrity)– “authenticity”.
The value of this key shall be indicated without commas in lowercase letters. If other value, than listed here, is indicated, the purpose of the signature shouldbe interpreted assigning (i.e. as if “signature” value is set).
First name and surname of the signer / Name / text string / Yes, if not present in the signing certificate / Yes, if not present in the signing certificate / If the first name and surname of signer are indicated both in the signing certificate and in this PDF signature dictionary entry, they should match. Otherwise the information from the certificate shall be used.
Position of the signer / LTUd_Role / text string / Yes (for the head of Institution or person authorised by him) / No
Claimed signing time / M / date / Yes / Yes
Note of the signer / LTUd_SignerNotes / text string / Yes, depending on thedocument nature / No / Visa note, resolution text, additional note on executed task, etc.

Notes:

1. XMP propertiesare specified with prefix associating property namewith thenamespace URI (prefix:local), as defined in Chapter 2 of XMP specification “Schemas and Namespaces”. The description of XMP property prefixes, used to define the metadata schemas,isprovided in the table below.

Prefix / URI / Description
LTUd / / The metadata extension XMP schema,defined in Appendix 2 of the Specification; XMP properties are described in the metadata table.
dc / / Dublin CoremetadataXMP schema, defined inthe XMP specificationChapter 4“Dublin Core Schema”.
xmp / / AnXMP schema, defined in the XMP specificationChapter 4 “XMP Basic Schema”.
rdf / / XML schema, defined in the W3C Recommendations “RDF/XML Syntax SpecificationRevised)” (Appendix 11Item26).
xmpidq / / Namespace URI to qualify an item inxmp:Identifierarray, defined in the XMP specificationChapter 4“XMP Basic Schema”.

2.Valuetypes of metadata XMP properties are provided in the table below:

XMP data type / Description
Person / The metadata extension structure,defined in Item 3 of these Notes.
Registration / The metadata extension structure,defined in Item 4 of these Notes.
Boolean / The logicaldata type having two values: “True”or“False”.
Date / Date data type for date-time values isdefined in XMP specification Section4 “Basic Value Types”. Date formats without the day parameter (like “YYYY”or“YYYY-MM”) are prohibited. If time information is present, the time zone designator shall be used.
Text / A Unicode string, which may be empty (contain 0 symbols).
AgentName / Text type value, which is recommended to be filled in the following format:
“OrganizationSoftware_name Version (token; token;...)”,
where:
Organization – the name of the company or organization providing the software;
Software_name – the full name of the software;
Version – the version of the software;
token– additional information, indicating the version of operating system,softwarecomponents, etc.
Closed Choice of Text / String from the defined list of values.
Language Alternative / An alternative array of text value items. Each item in thearray(rdf:Altelement) shall have a language qualifier(xml:lang)associating with it. The value of qualifier is alanguage code that conforms to IETF RFC 3066 notation, or value of “xdefault” to denote a default item.
Locale / A simple text value denoting a language code following IETF RFC 3066.
ProperName / A name of a person or organization, represented as a Unicode text string.
Ordered array / A list of values whose order is significant, indicated usingrdf:Seqelement.
Unordered array / A list of values whose order does not have significance, indicated usingrdf:Bagelement.

3.Description of XMP value typePerson(prefix: LTUdEnt; namespace URI: is provided in the table below:

Metadata / XMP property / Type / Mandatory (if natural person indicated) for / Notes
Author / Addressee / Receiver
Natural person (True) or legal entity (False) / LTUdEnt:individual / Boolean / Yes / No / Yes
Title of legal entity or the first name and surname of natural person. / LTUdEnt:name / Text / Yes / Yes / Yes / The names of authors(specified in LTUdEnt:nameitems) shall be repeated in the document creation metadata property dc:creator.
ID code of legal entity or natural person / LTUdEnt:code / Text / Yes, iflegal entity indicated / No / Yes, iflegal entity indicated / The presence of the property valueshall be verified depending on LTUdEnt:individual value.
Address / LTUdEnt:address / Text / No / No / No
E-mail address / LTUdEnt:eMail / Text / No / No / No

4.Description of XMP value typeRegistration(prefix: LTUdReg; namespace URI: provided in the table below:

Metadata / XMP property / Type / Mandatory (when the registration data are set) / Notes
Registration date / LTUdReg:date / Date / Yes / Time information, if present, shall be specified with time zone designator, as defined in the XMP Specification.
Registration number / LTUdReg:number / Text / Yes
ID code of legal entity / LTUdReg:code / Text / No / If there are several authors of the document, the code of the legal entity, which registered the document, shall be indicated.For the received document, it is recommended to indicate the receiver’s code.

5.Text and date data types for PDF dictionary values are defined in the PDF-1.7 StandardSections 7.9.2 and 7.9.4.

6.The value of PDF file creation date (xmp:CreateDate) metadata should not be consideredas the time electronic documentwas created. Anelectronic document creation date is considered the date of the document registration (if the document is registered) or the date of the latest signature (when the document is not registered) of signing or confirmation purpose, stored in PDF signature dictionary “M”entry.

7.The following table provides the description of data structure to be used to specifythe conformance level of electronic document, stored in the xmp:Identifierproperty.

Metadata / XMP property / Type / Notes
Document conformance level / rdf:value / Text / Valid values:
“A”–indicateconformancetoLevel A;
“B”–indicateconformance toLevel B.
Qualifier / xmpidq:Scheme / Text / Shall be value“

______

1

Electronic document specification PDF-LT-V1.0

Appendix 2

metadataextensionXMP schema

rdf:RDFxmlns:rdf="

rdf:Descriptionrdf:about=""

xmlns:pdfaExtension="

xmlns:pdfaSchema="

xmlns:pdfaProperty="

xmlns:pdfaType="

xmlns:pdfaField="

<!-- PDF/A specific description of XMP metadata extension schema -->

pdfaExtension:schemas

rdf:Bag

rdf:lirdf:parseType="Resource"

pdfaSchema:schemaExtensionschema of PDF-LT-V1.0 electronicdocument metadata</pdfaSchema:schema

pdfaSchema:namespaceURI

pdfaSchema:prefixLTUd</pdfaSchema:prefix

pdfaSchema:property

rdf:Seq

<!-- Document creation metadata (stored in metadata stream of PDF document catalog) -->

rdf:lirdf:parseType="Resource"

pdfaProperty:namestandardVersion</pdfaProperty:name

pdfaProperty:valueTypeclosed Choice of Text</pdfaProperty:valueType

pdfaProperty:categoryinternal</pdfaProperty:category

pdfaProperty:descriptionID of the specification of the electronic document (ex. PDF-LT-V1.0)</pdfaProperty:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaProperty:nameauthors</pdfaProperty:name

pdfaProperty:valueTypeseq Entity</pdfaProperty:valueType

pdfaProperty:categoryexternal</pdfaProperty:category

pdfaProperty:descriptionAuthor(-s) of the document</pdfaProperty:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaProperty:namerecipients</pdfaProperty:name

pdfaProperty:valueTypeseq Entity</pdfaProperty:valueType

pdfaProperty:categoryexternal</pdfaProperty:category

pdfaProperty:descriptionAddressees</pdfaProperty:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaProperty:namedocumentCopyIdentifier</pdfaProperty:name

pdfaProperty:valueTypeText</pdfaProperty:valueType

pdfaProperty:categoryexternal</pdfaProperty:category

pdfaProperty:descriptionID of the document copy</pdfaProperty:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaProperty:nameoriginalRegistrations</pdfaProperty:name

pdfaProperty:valueTypeseq Registration</pdfaProperty:valueType

pdfaProperty:categoryexternal</pdfaProperty:category

pdfaProperty:descriptionDocument registration data in the copy </pdfaProperty:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaProperty:nameoriginalReceptions</pdfaProperty:name

pdfaProperty:valueTypeseq Registration</pdfaProperty:valueType

pdfaProperty:categoryexternal</pdfaProperty:category

pdfaProperty:descriptionRegistration data of the received document in the copy</pdfaProperty:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaProperty:nameoriginalReceivers</pdfaProperty:name

pdfaProperty:valueTypeseq Entity</pdfaProperty:valueType

pdfaProperty:categoryexternal</pdfaProperty:category

pdfaProperty:descriptionDocument receivers in the copy </pdfaProperty:description

</rdf:li

<!-- Documentregistration metadata (stored inmetadata streamof PDF signature dictionary) -->

rdf:lirdf:parseType="Resource"

pdfaProperty:nameregistration</pdfaProperty:name

pdfaProperty:valueTypeRegistration</pdfaProperty:valueType

pdfaProperty:categoryexternal</pdfaProperty:category

pdfaProperty:descriptionRegistration data of the document created</pdfaProperty:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaProperty:namereception</pdfaProperty:name

pdfaProperty:valueTypeRegistration</pdfaProperty:valueType

pdfaProperty:categoryexternal</pdfaProperty:category

pdfaProperty:descriptionRegistration data of the document received</pdfaProperty:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaProperty:namereceiver</pdfaProperty:name

pdfaProperty:valueTypeEntity</pdfaProperty:valueType

pdfaProperty:categoryexternal</pdfaProperty:category

pdfaProperty:descriptionReceiver of the document</pdfaProperty:description

</rdf:li

</rdf:Seq

</pdfaSchema:property

<!-- Metadatavalue types -->

pdfaSchema:valueType

rdf:Seq

<!-- Persontype -->

rdf:lirdf:parseType="Resource"

pdfaType:descriptionPerson(author, addressee, receiver) </pdfaType:description

pdfaType:namespaceURI

</pdfaType:namespaceURI

pdfaType:prefixLTUdEnt</pdfaType:prefix

pdfaType:typeEntity</pdfaType:type

pdfaType:field

rdf:Seq

rdf:lirdf:parseType="Resource"

pdfaField:nameindividual</pdfaField:name

pdfaField:valueTypeBoolean</pdfaField:valueType

pdfaField:descriptionNatural person (true) or legal entity (false)</pdfaField:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaField:namename</pdfaField:name

pdfaField:valueTypeText</pdfaField:valueType

pdfaField:descriptionTitle of the legal entity or the first name and surname of natural person.</pdfaField:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaField:namecode</pdfaField:name

pdfaField:valueTypeText</pdfaField:valueType

pdfaField:descriptionID code of legal entity or natural person</pdfaField:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaField:nameaddress</pdfaField:name

pdfaField:valueTypeText</pdfaField:valueType

pdfaField:descriptionAddress</pdfaField:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaField:nameeMail</pdfaField:name

pdfaField:valueTypeText</pdfaField:valueType

pdfaField:descriptionE-mail address</pdfaField:description

</rdf:li

</rdf:Seq

</pdfaType:field

</rdf:li

<!-- Registrationtype -->

rdf:lirdf:parseType="Resource"

pdfaType:descriptionCreated or received document registration</pdfaType:description

pdfaType:namespaceURI

</pdfaType:namespaceURI

pdfaType:prefixLTUdReg</pdfaType:prefix

pdfaType:typeRegistration</pdfaType:type

pdfaType:field

rdf:Seq

rdf:lirdf:parseType="Resource"

pdfaField:namedate</pdfaField:name

pdfaField:valueTypeDate</pdfaField:valueType

pdfaField:descriptionRegistration date</pdfaField:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaField:namenumber</pdfaField:name

pdfaField:valueTypeText</pdfaField:valueType

pdfaField:descriptionRegistration number</pdfaField:description

</rdf:li

rdf:lirdf:parseType="Resource"

pdfaField:namecode</pdfaField:name

pdfaField:valueTypeText</pdfaField:valueType

pdfaField:descriptionID code of legal entity</pdfaField:description

</rdf:li

</rdf:Seq

</pdfaType:field

</rdf:li

</rdf:Seq

</pdfaSchema:valueType

</rdf:li

</rdf:Bag

</pdfaExtension:schemas

</rdf:Description

</rdf:RDF

______

1

Electronic document specification PDF-LT-V1.0

Appendix 3

entries in the document catalog extensions dictionary identifying extensions defined in Specification

%PDF–1.7

</Type /Catalog

/Extensions

</LTUd

</BaseVersion /1.7

/ExtensionLevel 1

______

1

Electronic document specification PDF-LT-V1.0

Appendix 4

examples of metadata

Section i

document creation metadata
(storedin the metadata stream of PDF document catalog)

<?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>

x:xmpmetaxmlns:x="adobe:ns:meta/"

rdf:RDFxmlns:rdf="

<!-- PDF/A version (2) and conformance level (A, B or U)identification -->

rdf:Descriptionrdf:about=""

xmlns:pdfaid="

pdfaid:part2</pdfaid:part

pdfaid:conformanceB</pdfaid:conformance

</rdf:Description

<!-- LTUd XMP metadataextension schema -->

rdf:Descriptionrdf:about=""

xmlns:pdfaExtension="

xmlns:pdfaSchema="

xmlns:pdfaProperty="

xmlns:pdfaType="

xmlns:pdfaField="

<!-- (embedded schema from Appendix 2) -->

</rdf:Description

<!--Document conformance to Specification requirements level (A orB) -->

rdf:Descriptionrdf:about=""

xmlns:xmp="

xmlns:xmpidq="

xmp:Identifier

rdf:Bag

rdf:li

rdf:Description

rdf:valueA</rdf:value

xmpidq:Scheme

</rdf:Description

</rdf:li

</rdf:Bag

</xmp:Identifier

</rdf:Description

<!-- PDF-LT-V1.0 document creation metadata -->

rdf:Descriptionrdf:about=""

xmlns:LTUd="

xmlns:LTUdEnt="

LTUd:standardVersionPDF-LT-V1.0</LTUd:standardVersion

LTUd:authors

rdf:Seq

rdf:lirdf:parseType="Resource"

LTUdEnt:individualFalse</LTUdEnt:individual

LTUdEnt:nameAcme Ltd.</LTUdEnt:name

LTUdEnt:code1234568</LTUdEnt:code

LTUdEnt:addressMainstr. 115, City</LTUdEnt:address

LTUdEnt:</LTUdEnt:eMail

</rdf:li

rdf:lirdf:parseType="Resource"

LTUdEnt:individualTrue</LTUdEnt:individual

LTUdEnt:nameJohn Doe</LTUdEnt:name

LTUdEnt:addressHighstr. 2, Village</LTUdEnt:address

</rdf:li

</rdf:Seq

</LTUd:authors

LTUd:recipients

rdf:Seq

rdf:lirdf:parseType="Resource"

LTUdEnt:nameAdvent Corporation</LTUdEnt:name

LTUdEnt:code123456878</LTUdEnt:code

</rdf:li

rdf:lirdf:parseType="Resource"

LTUdEnt:nameJane Roe</LTUdEnt:name

</rdf:li

</rdf:Seq

</LTUd:recipients

LTUd:documentCopyIdentifier1/5</LTUd:documentCopyIdentifier

</rdf:Description

rdf:Descriptionrdf:about=""

xmlns:dc="

dc:language

rdf:Bag

rdf:lilt-LT</rdf:li

</rdf:Bag

</dc:language

dc:title

rdf:Alt

rdf:lixml:lang="x-default"Dėl darbo grupės sudarymo</rdf:li

rdf:lixml:lang="lt-LT"Dėl darbo grupės sudarymo</rdf:li

rdf:lixml:lang="en-GB"On working group establishing</rdf:li

</rdf:Alt

</dc:title

dc:creator

rdf:Seq

rdf:liAcme Ltd.</rdf:li

rdf:liJohn Doe</rdf:li

</rdf:Seq

</dc:creator

</rdf:Description

rdf:Descriptionrdf:about=""

xmlns:xmp="

xmp:CreatorToolSoftware Application 2.44.1 (Win XP)</xmp:CreatorTool

</rdf:Description

</rdf:RDF