This issue is split between here and the EMREX Standard issue 2. Points marked with "EMREX issue" are covered in the other issue ticket but they are left here to keep the issue numbering consistent.
1) Additional (XML) 3rd signature field in ELMO, concerning ELMO XML diploma data only (without attachements) – for better machine-machine operations on ELMO container. Currently ELMO supports only signing the XML as a whole, including any attachments. The attachments can also be signed individually depending on the format. This request is to enable signing the XML file independent of any attachments so that the signature is valid even if the attachments are removed for example, for storage space reasons.
Current supported signing: XML+PDF and PDF
Required supported signing: XML+PDF and PDF and XML
2) EMREX issue.
3) If necessary: check Alignment/Interoperability of ELMO signatures according to EU/ETSI Signature standards (XAdes….). This issue affects both ELMO and EMREX and is present here and in the EMREX standard repository. The requirement on the ELMO side is to make ELMO schema description mention possibility of different file types and detached signatures.
4) If necessary: additional XML Elements for explicit Signatures Types/Attributes: advanced / qualified … (in ELMO + EMREX). This issue affects both ELMO and EMREX and is present here and in the EMREX standard repository. Same as issue number 3 and cover there.
5) EMREX issue.
6) Integrations of transfer/access restrictions or receiver restrictions attributes (privacy, GDPR). This issue affects both ELMO and EMREX and is present here and in the EMREX standard repository.
7) Integration of explicit time-depending validity attributes (expires on ….; because practical crypotography generates only temporary valid crypto data (e.g. for hashes, signatures ), adding links to eIDAS preservation services options. Add support for displaying signature date on the document. This concerns the presentation layer of ELMO as the signature date can be pulled from the signature. Also add support for linking to eIDAS preservation services. These services are currently part of the upcoming eIDAS 2 regulation and cannot be specified in detail but they would include a link to a preservation service endpoint where the validity of the document can be extended. This would apply only to XML or XML+PDF signing.
8) EMREX/EWP issue.
9) Linkage / relations ELMO-EMREX: additional encapsulations/headering levels (see e.g. OSI or SOAP, IPv6-sub-headering/next-header), e.g. for trustworthy NCP features lookups. Implement new standards for data linking in order to support external data linked by URLs. To add support for these feature in the v2 of ELMO. Further documentation will be provided by HS Harz.
This issue is split between here and the EMREX Standard issue 2. Points marked with "EMREX issue" are covered in the other issue ticket but they are left here to keep the issue numbering consistent.
1) Additional (XML) 3rd signature field in ELMO, concerning ELMO XML diploma data only (without attachements) – for better machine-machine operations on ELMO container. Currently ELMO supports only signing the XML as a whole, including any attachments. The attachments can also be signed individually depending on the format. This request is to enable signing the XML file independent of any attachments so that the signature is valid even if the attachments are removed for example, for storage space reasons.
Current supported signing: XML+PDF and PDF Required supported signing: XML+PDF and PDF and XML
2) EMREX issue.
3) If necessary: check Alignment/Interoperability of ELMO signatures according to EU/ETSI Signature standards (XAdes….). This issue affects both ELMO and EMREX and is present here and in the EMREX standard repository. The requirement on the ELMO side is to make ELMO schema description mention possibility of different file types and detached signatures.
4) If necessary: additional XML Elements for explicit Signatures Types/Attributes: advanced / qualified … (in ELMO + EMREX). This issue affects both ELMO and EMREX and is present here and in the EMREX standard repository. Same as issue number 3 and cover there.
5) EMREX issue.
6) Integrations of transfer/access restrictions or receiver restrictions attributes (privacy, GDPR). This issue affects both ELMO and EMREX and is present here and in the EMREX standard repository.
7) Integration of explicit time-depending validity attributes (expires on ….; because practical crypotography generates only temporary valid crypto data (e.g. for hashes, signatures ), adding links to eIDAS preservation services options. Add support for displaying signature date on the document. This concerns the presentation layer of ELMO as the signature date can be pulled from the signature. Also add support for linking to eIDAS preservation services. These services are currently part of the upcoming eIDAS 2 regulation and cannot be specified in detail but they would include a link to a preservation service endpoint where the validity of the document can be extended. This would apply only to XML or XML+PDF signing.
8) EMREX/EWP issue.
9) Linkage / relations ELMO-EMREX: additional encapsulations/headering levels (see e.g. OSI or SOAP, IPv6-sub-headering/next-header), e.g. for trustworthy NCP features lookups. Implement new standards for data linking in order to support external data linked by URLs. To add support for these feature in the v2 of ELMO. Further documentation will be provided by HS Harz.