From 5c78ddef24370b95e733e3966a945c41cc9930a3 Mon Sep 17 00:00:00 2001
From: Simeon Warner <simeon.warner@cornell.edu>
Date: Wed, 11 Jul 2018 16:21:12 -0400
Subject: [PATCH 1/2] Version directory naming

---
 index.html | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/index.html b/index.html
index e6ba1373..444ebccf 100644
--- a/index.html
+++ b/index.html
@@ -187,6 +187,29 @@ <h2>Top-level Inventory Checksum</h2>
     <section id='versions-directories'>
       <h2>Versions Directories</h2>
 
+      <p>
+	OCFL object content is stored as a sequence of one or more versions. Each object version is stored in a version
+	directory under the object root. The sequence of version numbers is the sequence of positive integers: 1, 2, 3, etc.,
+	and the version directory name is constructed by adding the prefix <code>v</code>.
+      </p>
+      <p>
+	It is RECOMMENDED that implementations use version directory names constructed without zero-padding the version
+	number, ie. <code>v1</code>, <code>v2</code>, <code>v3</code>, etc..
+      </p>
+      <p>
+	For compatibility with existing filesystem conventions, implementations MAY use zero-padded version numbers,
+	with the following restriction: If zero-padded version numbers are used then they MUST start with a zero. For example,
+	in an implementation that uses five digits the version directory names <code>v00001</code> to <code>v09999</code> are
+	allowed, <code>v10000</code> is not allowed.
+      </p>
+      <p>
+	The first version of an object defines the naming convention for all versions of the object. All versions MUST use the
+	same naming convention: either a non-padded version number, or a zero-padded version number of consistent length.
+	Operations that	add a new version to an object MUST follow the directory naming convention established by earlier
+	versions. In all cases, references to files inside version directories from inventory files MUST use the actual version
+	directory names.
+      </p>
+
       <section id='version-declaration'>
           <h2>Version declaration</h2>
           <p>

From c6e32919193f5169199db415753c570cac96d97b Mon Sep 17 00:00:00 2001
From: Simeon Warner <simeon.warner@cornell.edu>
Date: Wed, 18 Jul 2018 09:38:17 -0400
Subject: [PATCH 2/2] Clarify that all versions of a specific object must use
 same naming convention

---
 index.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index 444ebccf..ec95382a 100644
--- a/index.html
+++ b/index.html
@@ -203,9 +203,9 @@ <h2>Versions Directories</h2>
 	allowed, <code>v10000</code> is not allowed.
       </p>
       <p>
-	The first version of an object defines the naming convention for all versions of the object. All versions MUST use the
-	same naming convention: either a non-padded version number, or a zero-padded version number of consistent length.
-	Operations that	add a new version to an object MUST follow the directory naming convention established by earlier
+	The first version of an object defines the naming convention for all versions of the object. All versions of an object
+	MUST use the same naming convention: either a non-padded version number, or a zero-padded version number of consistent
+	length. Operations that add a new version to an object MUST follow the directory naming convention established by earlier
 	versions. In all cases, references to files inside version directories from inventory files MUST use the actual version
 	directory names.
       </p>