@dockmd and I have run the package against our validator.
A CSIP104 is triggered. I think it is a flaw in the validator.
CSIP101-CSIP104 + CSIP119 states requirements for when there are no representations present (and those reqs uses fptr).
CSIP105-CSIP112 states requirements when representations are present (and those req uses mptr).
The package has a representation where all the files are described in the representation METS, so there is mptr in the Package METS and no fptr.
I have updated/created a new valid IP located at: https://github.com/DILCISBoard/eark-ip-test-corpus/tree/integration/corpus/template-ip/Valid_IP_example
@dockmd and I have run the package against our validator.
A CSIP104 is triggered. I think it is a flaw in the validator.
CSIP101-CSIP104 + CSIP119 states requirements for when there are no representations present (and those reqs uses fptr). CSIP105-CSIP112 states requirements when representations are present (and those req uses mptr).
The package has a representation where all the files are described in the representation METS, so there is mptr in the Package METS and no fptr.