Logical file paths - directory separators

[bcail]

In the Version objects, should the logical file path values in the state block allow windows or unix directory separators (eg. "dir/file.txt" vs "dir\file.txt")? Should a file name in a logical path be allowed to contain any directory separator characters (eg. "dir/file_with_/_char.txt)? Or should OCFL even care what's in that logical file path?

[awoods]

As a point of reference, BagIt takes the following approach:

• https://tools.ietf.org/html/draft-kunze-bagit-08#section-7.2.2

As specified above, only the Unix-based path separator ('/') may be
used inside filenames listed in BagIt manifests and "fetch.txt"
files. When bags are exchanged between Windows and Unix platforms,
care should be taken to translate the path separator as needed.

[ahankinson]

Related to #243

[zimeon]

I think we should follow Bagit here and make a normative statement in the introduction to Inventory that

The forward slash (/) path separator MUST be used in existing and logical file paths in the manifest, fixity and state blocks within the inventory. Implementations that target systems using other separators will need to translate paths appropriately.