Resources IDs must conform to a number of constraints. Resources IDs are made up of parts separated by '/' characters. For example, the resource ID "foo/bar
" is made up of two parts "foo
" and "bar
". The following restrictions apply to resource ID parts:
Resource IDs are translated to paths on disk when they are persisted in OCFL. The goal is for these paths to be as transparent as possible, however a minimal translation is applied to ensure that the paths are safe on filesystem. The specifics of the translation depend on the operating system.
The following characters are percent-encoded:
The following characters are percent-encoded: