-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content directory path separators #530
Comments
I think when reading these things one has to be careful to distinguish between rules for the inventory and how that might be mapped onto a filesystem or store that perhaps does not use unix conventions. We've made it so that the mapping to unix conventions or to URIs is easy, but other things may be more tricky (like Windows) Per https://ocfl.io/1.0/spec/#inventory:
Reading the comment above I'm not quite sure what the question is. |
From my perspective this is the problem.
By my reading of the spec, this is unintended but valid. |
My understanding of the following text is that the "contentDirectory" must be direct child directory of the version directory in which it is found. I believe the intent of allowing configurable "contentDirectory" was to be able to use a directory name other than
Maybe the following language to 3.3.1 Content Directory would help clarify.
To:
|
https://ocfl.io/1.0/spec/#content-directory
I believe the intent of that sentence is that the content directory must be a direct child of the version directory. The problem is that it only forbids the
/
path separator, so on Windows you could legally havenested\content\dir
or even..\..\..\..\..\..\
.This is complicated by:
https://ocfl.io/1.0/spec/#inventory
However, that statement does not mandate a
/
separator incontentDirectory
, presumably because it's not supposed to able to have any path separator.The text was updated successfully, but these errors were encountered: