From 4d5b788a8437d3387002d54551c5750f2e30e841 Mon Sep 17 00:00:00 2001 From: Rosalyn Metz Date: Thu, 14 Aug 2025 13:12:36 -0400 Subject: [PATCH 1/2] clarify what metadata and content means MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit We’ve found that institutions often assume OCFL is opinionated about the internal structure of an object, despite the introduction stating explicitly that OCFL does not define an object’s structure (i.e., what makes an object an object). One reason for this misunderstanding may be our loose use of the terms’ metadata’ and ‘content’ in the introduction (I’ll take the blame for that). In practice, when people see “metadata,” they often think only of descriptive metadata. However, metadata can also refer to other types, such as METS, which encompasses both structural and administrative metadata, or MIX, which captures technical metadata about an image. The changes here aim to clarify that we mean all forms of metadata, not just descriptive, so that users better understand OCFL’s scope. --- draft/spec/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/draft/spec/index.md b/draft/spec/index.md index 4f89783..8105dfa 100644 --- a/draft/spec/index.md +++ b/draft/spec/index.md @@ -69,7 +69,8 @@ versioning, robustness, and storage diversity. #### Completeness {:.no_toc #completeness} -The OCFL recommends storing metadata and the content it describes together so the OCFL object can be fully understood in +The OCFL recommends storing metadata (this includes all types of metadata; e.g., technical, structural, descriptive, etc.) +and the content (e.g., images, text files, etc.) it describes together so the OCFL object can be fully understood in the absence of original software. The OCFL does not make recommendations about what constitutes an object, nor does it assume what type of metadata is needed to fully understand the object, recognizing those decisions may differ from one repository to another. However, it is recommended that when making this decision, implementers consider what is From 9ad4f452d4d935aea3619f02e0cc9c765d9e5e38 Mon Sep 17 00:00:00 2001 From: Rosalyn Metz Date: Thu, 14 Aug 2025 13:14:59 -0400 Subject: [PATCH 2/2] line length changes oops...... --- draft/spec/index.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/draft/spec/index.md b/draft/spec/index.md index 8105dfa..79fb894 100644 --- a/draft/spec/index.md +++ b/draft/spec/index.md @@ -69,12 +69,12 @@ versioning, robustness, and storage diversity. #### Completeness {:.no_toc #completeness} -The OCFL recommends storing metadata (this includes all types of metadata; e.g., technical, structural, descriptive, etc.) -and the content (e.g., images, text files, etc.) it describes together so the OCFL object can be fully understood in -the absence of original software. The OCFL does not make recommendations about what constitutes an object, nor does it -assume what type of metadata is needed to fully understand the object, recognizing those decisions may differ from one -repository to another. However, it is recommended that when making this decision, implementers consider what is -necessary to rebuild the objects from the files stored. +The OCFL recommends storing metadata (this includes all types of metadata; e.g., technical, structural, descriptive, +etc.) and the content (e.g., images, text files, etc.) it describes together so the OCFL object can be fully +understood in the absence of original software. The OCFL does not make recommendations about what constitutes an +object, nor does it assume what type of metadata is needed to fully understand the object, recognizing those +decisions may differ from one repository to another. However, it is recommended that when making this decision, +implementers consider what is necessary to rebuild the objects from the files stored. #### Parsability {:.no_toc #parsability}