spec
spec copied to clipboard
OCFL
The Oxford Common File Layout (OCFL) specifications
One issue with OCFL v1.x is that the `inventory.json` can get quite large-- especially when there are many versions, version files, and you add fixity to the mix. A more...
Hi, I'm reading through 1.1 and it's wonderful! Am I correct in thinking that a Storage Root is optional but highly recommended if you want to achieve the goal of...
If there are no version inventories then one can only tell that the spec version of a prior object version is the same or any prior spec version compared to...
I was thinking about unicode normalization again. I know last time this was discussed, perhaps it was on Slack, that normalization was considered outside of the scope of the spec....
Fixture https://github.com/OCFL/fixtures/pull/79 / `E010_missing_versions` brings up an interesting question for me. Is it really necessary to have a version directory for every version? There will be a version directory if...
Review all the MAY declarations inthe specification to establish whether it might be tightened up (convert to MUSTs) for V2.0
Cross references encourage people to read the implementation notes since they clarify points and answer many questions.
See, for example, https://iiif.io/api/presentation/3.0/
We have a section on digest migratiion https://ocfl.io/draft/implementation-notes/#digest-migration but do not cover the case of going to new version of the spec. This should cover the mutability of the conformance...
Looking toward the release of 1.1 and the possibility of 2.0 on the horizon, it may be helpful to include a non-normative statement describing expectations for compatibility between 1.0 and...