Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fixed: Logical paths clarification #423

Merged
merged 4 commits into from
Mar 4, 2020
Merged

Fixed: Logical paths clarification #423

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f023675
Fixed: Logical paths clarification
ahankinson Feb 18, 2020
324ebd0
Another kick at the logical path can
ahankinson Feb 18, 2020
8791e63
Fixed: Change SHOULD to MUST
ahankinson Mar 3, 2020
84f63d0
Fixed: Improved wording based on review
ahankinson Mar 4, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion draft/spec/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -296,7 +296,8 @@ <h2>Terminology</h2>
</dt>
<dd>
A path that represents a file's location in the <a>logical state</a> of an object. Logical paths are
used in conjunction with a digest to represent the file name for a given bitstream at a given version.
used in conjunction with a digest to represent the file name and path for a given bitstream at a given
version.
</dd>
<dt>
<dfn>Logical State</dfn>:
Expand Down Expand Up @@ -698,6 +699,15 @@ <h2>Version</h2>
containing <a>logical path</a> names of files in the OCFL Object state that have
content with the given digest.
</p>
<p>
<a href="#logical-path">Logical paths</a> present the structure of an OCFL Object at a
given version. This is given as an array of values, with the following restrictions to
provide for path safety in the common case of the logical path value representing a file
path. The logical path MUST be interpreted as a set of one or more path elements joined by
a <code>/</code> path separator. Path elements MUST NOT be <code>.</code>, <code>..</code>,
or empty (<code>//</code>). Additionally, a logical path MUST NOT begin with a leading
<code>/</code>.
</p>
<blockquote class="informative">
<p>
Non-normative note: The <a>logical state</a> of the object uses content-addressing
Expand Down