GithubHelp home page GithubHelp logo

Comments (4)

jmaferreira avatar jmaferreira commented on August 22, 2024

Hi @karinbredenberg,

I have a practical question about the implementation of this enhancement. When working out the dependecies of some SIP requirements I realise that there are dependencies that only exist on the CSIP.

For example, the following SIP requirement:

<requirement ID="SIP32" REQLEVEL="MAY" EXAMPLES="fileSecExample1">
    <description>
        <head>File format name</head>
        <p xmlns="http://www.w3.org/1999/xhtml">An optional attribute may be used if the MIMETYPE is not sufficient for the purposes of
            processing the information package.</p>
        <p xmlns="http://www.w3.org/1999/xhtml">Example: "Extensible Markup Language"</p>
        <p xmlns="http://www.w3.org/1999/xhtml">Example: "PDF/A"</p>
        <p xmlns="http://www.w3.org/1999/xhtml">Example: "ISO/IEC 26300:2006"</p>
        <dl xmlns="http://www.w3.org/1999/xhtml">
            <dt>METS XPath</dt>
            <dd>fileSec/fileGrp/file/@sip:FILEFORMATNAME</dd>
            <dt>Cardinality</dt>
            <dd>0..1</dd>
        </dl>
    </description>
</requirement>

Depedents of a requirement that lives outside the SIP METS profile. Namely, the dependecy is the following requirement of the CSIP:

<requirement ID="CSIP58" REQLEVEL="SHOULD" EXAMPLES="fileSecExample1 fileSecExample2">
    <description>
        <head>File section</head>
        <p xmlns="http://www.w3.org/1999/xhtml">References to all transferred content SHOULD be placed in the file section in the different file group
            elements, described in other requirements.</p>
        <p xmlns="http://www.w3.org/1999/xhtml">Only a single file section (`&lt;fileSec&gt;`) element should be present.</p>
        <p xmlns="http://www.w3.org/1999/xhtml">In the case that a package only contains metadata updates, i.e. exclusively metadata files, then no
            file references need to be added to this section.</p>
        <dl xmlns="http://www.w3.org/1999/xhtml">
            <dt>METS XPath</dt>
            <dd>mets/fileSec</dd>
            <dt>Cardinality</dt>
            <dd>0..1</dd>
        </dl>
    </description>
</requirement>

My question is, should I reference the inherited dependency that comes from the CSIP or should I solely add the dependecies that are within the same METS profile?

from e-ark-sip.

karinbredenberg avatar karinbredenberg commented on August 22, 2024

You can only reference ID's which is what you do in the RELATEDMAT attribute that are in the current profile.

Dependencies in the CSIP is described in the CSIP's RELATEDMAT attributes.

Remember that the SIP profile extends the CSIP profile, that means that first the requirements in CSIP needs to be fulfilled and then the ones in the SIP. So yes only add dependencies within the same profile.

from e-ark-sip.

jmaferreira avatar jmaferreira commented on August 22, 2024

Thanks Karin.

from e-ark-sip.

jmaferreira avatar jmaferreira commented on August 22, 2024

Issue resolved on commit baa2c99

from e-ark-sip.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.