dilcisboard / e-ark-dip Goto Github PK

With the demise of the free Travis service the publication of the E-ARK specifications needs to be handled by GitHub actions.

Ch. 4.3.1: Extra ">" characters in the text.

As it is now - the Content Information Type specifications for different Content Information Types are within the specification.

Find placeholders and responsible people for Content Information Type specifications

Change CS IP to CSIP.

DILCISBoard/E-ARK-CSIP#424
DILCISBoard/E-ARK-CSIP#229 (comment)
DILCISBoard/GroupDocumentation#16

Update following DILCISBoard/E-ARK-CSIP#709 needed

@andersbonielsen

The DIP METS table has to be the same requirements and wordings as the new CSIP.

Given in profile:
Namespace: xmlns:csip=https://dilcis.eu/XML/METS/CSIPExtensionMETS
xmlns:sip=https://dilcis.eu/XML/METS/SIPExtensionMETS
Path: http://earksip.dilcis.eu/schema/DILCISExtensionSIPMETS.xsd

metsRootElementExample1:
xmlns:csip="https://dilcis.eu/XML/METS/CSIPExtensionMETS"
https://dilcis.eu/XML/METS/CSIPExtensionMETS https://dilcis.eu/XML/METS/CSIPExtensionMETS/DILCISExtensionMETS.xsd">

metsRootElementExample2:
xmlns:csip="https://dilcis.eu/XML/METS/CSIPExtensionMETS"
https://dilcis.eu/XML/METS/CSIPExtensionMETS https://dilcis.eu/XML/METS/CSIPExtensionMETS/DILCISExtensionMETS.xsd

Appendix1:
xmlns:csip="https://dilcis.eu/XML/METS/CSIPExtensionMETS"
https://dilcis.eu/XML/METS/CSIPExtensionMETS https://dilcis.eu/XML/METS/CSIPExtensionMETS/DILCISExtensionMETS.xsd https://dilcis.eu/XML/METS/SIPExtensionMETS https://dilcis.eu/XML/METS/SIPExtensionMETS/DILCISExtensionSIPMETS.xsd

Result: Path to schema work in examples and appendix.
Needed: In metsRootElementExample1 and metsRootElementExample2 namespace for SIP is needed as well as the pointer to the schema. In Appendix 1 the namespace needs to be given (xmlns:sip). In element <related_profile) it’s the wrong path to the CSIP profile.

This is stated in the DIP specification:
"The DIP specification is limited to include one and only one representation from an AIP (for which many may exist)."

I don't understand why this is so.

The documents for the different IPs should be standardized so that they are structured in a similar way and the references should keep the same ID for the same element (CSIP7 should always be the same element in all documents).

There are some repetition of schema locations and one might be wrong.

In structMap there are now new requirements.
In index.md the DIP requirements for these new requirements need to be handled. New requirements are marked with a ? in the pull request 16

Example:

Should access metadata be stored in EAD?
DIP access restristions

Should the other cases than "one and only one representation in a DIP" be somehow shortly discussed further, to leave clear room for other options? Maybe one page discussion for the possibilities?

The whole CS IP table is unnecessary. It would be clearer to just list the elements and attributes where the DIP differs from CS IP or AIP.

The appendix in the METS Profile needs to be unique.

DILCISBoard/E-ARK-CSIP#591

All extra elements for SIP, AIP and DIP should be included in CSIP, but as optional information.
Then, documents are needed that describe how to create a SIP, AIP, DIP and how to use the elements at EU level and that it is possible to adapt for local use in different countries.

Similiar to in the SIP the linking with an anchor in the description doesnt work.
DILCISBoard/E-ARK-SIP#72

This page is an insert after the cover that acknowledges the EU funding and project partners.

Update follwing DILCISBoard/E-ARK-CSIP#710 needed

Remove/redefine purpose in regard to reference implementation
https://github.com/DILCISBoard/E-ARK-DIP/blob/master/specification/01-introduction/index.md

"To recommend a set of metadata related to the structural and the access aspects of the DIP as implemented by the reference implementation."