Skip to content

Revert "Fix a few typos and one consistency issue in the implementation notes" #674

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

Closed
rosy1280 wants to merge 1 commit into from
Closed

Revert "Fix a few typos and one consistency issue in the implementation notes" #674

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions draft/implementation-notes/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -321,7 +321,7 @@ Object, obviously, inherits no content and is populated by file additions.
* Addition: Adds a new file path and corresponding content to an OCFL Object. The path cannot exist in the previous
version of the object, and the content cannot have existed in any earlier versions of the object.

* Updating: Changes the content pointed to by a content path. The path must exist in the previous version of the OCFL
* Updating: Changes the content pointed to by an content path. The path must exist in the previous version of the OCFL
Object, and the content cannot have existed in any earlier versions of the object.

* Renaming: Changes the file path of existing content. The path cannot exist in the previous version of the OCFL Object,
Expand Down Expand Up @@ -510,9 +510,9 @@ and the corresponding `v2` inventory is:
{: #log-information}

There may be the need to record some actions on objects that do not result in changes to the object content. For
example, copying the object to new storage or validating fixity and finding nothing amiss. The `logs` directory is the
example, copying the object to new storage or validating fixity and finding nothing amiss. The `log` directory is the
location in an OCFL object where such events can be recorded. The OCFL does not make any assumptions about the contents
of this directory but, if it exists, then its contents will not be subject to any validation processes.
of this directory but, if it exists, then its contents will not be subject any validation processes.

### 3.6 Forward Delta
{: #forward-delta}
Expand Down Expand Up @@ -586,7 +586,7 @@ layout to an OCFL Storage Root.
the Workspace that is the same as its eventual storage path in the OCFL Storage Root. This means that it is easy for
clients to determine if an object is being updated and also provides a mechanism to implement objects with mutable
current versions without violating OCFL assumptions. When updating an OCFL Object, it is useful to make a copy of the
inventory of the most recent stable version of the object in this directory when it is created at the start of the update
inventory of most recent stable version of the object in this directory when it is created at the start of the update
operation.

* Version Assembly Directory: In this case, one version assembly directory should exist per OCFL Object at any time and
Expand Down