Editor’s Draft
SIP content profiles
SIP content profiles define specific configurations of the meemoo SIP specification that are supported by the meemoo ingest pipeline. They group different types of content that share a similar structure (e.g., there is only one representation or one file) and/or have the same metadata demands (e.g. all of the supplied metadata fits in the DCTERMS vocabulary).
A profile adds extra restrictions or extensions on top of the SIP specification. Hence, the SIP validation process depends on both. A delivered SIP MUST indicate which profile it adheres to in the package METS.xml through the mets/@csip:OTHERCONTENTINFORMATIONTYPE attribute. Note that the csip:CONTENTINFORMATIONTYPE attribute must always be set to OTHER.
Continue to Basic profile.