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

Link to and fixup date for ipres news item #655

Merged
merged 1 commit into from
Oct 24, 2024
Merged

Link to and fixup date for ipres news item #655

Show file tree
Hide file tree
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
1 change: 1 addition & 0 deletions index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ Specifically, the benefits of the OCFL include:
* __Storage diversity__, to ensure content can be stored on diverse storage infrastructures including conventional filesystems and cloud object stores

## News
* 2024-10-24: [OCFL Editors Workshop at iPres](/news/#ocfl-editors-workshop-at-ipres)
* 2023-08-01: [Community Listening Sessions for Version 2 Announcement](/news/#community-listening-sessions-for-version-2-of-the-oxford-common-file-layout)
* 2022-10-07: [Version 1.1 Release Announcement](/news/#version-11-of-the-oxford-common-file-layout-ocfl-released)
* 2020-07-07: [Version 1.0 Release Announcement](/news/#version-10-of-the-oxford-common-file-layout-ocfl-released)
Expand Down
20 changes: 10 additions & 10 deletions news/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@

## OCFL Editors Workshop at iPres

**16-20 September 2024**
The OCFL Editors met during the iPres conference to review the use cases to be addressed in version 2.0 of the specification and come up with initial thoughts on how to proceed with each one. These thoughts have now been added to the [Confirmed: In-scope Issues](https://github.com/OCFL/Use-Cases/issues?q=is%3Aissue+is%3Aopen+label%3A%22Confirmed%3A+In-scope%22). The OCFL Editors now welcome further comments and feedback from the community before proceeding.
**24 October 2024**
The OCFL Editors met during the iPres conference 16-20 September 2024 to review the use cases to be addressed in version 2.0 of the specification and come up with initial thoughts on how to proceed with each one. These thoughts have now been added to the [Confirmed: In-scope Issues](https://github.com/OCFL/Use-Cases/issues?q=is%3Aissue+is%3Aopen+label%3A%22Confirmed%3A+In-scope%22). The OCFL Editors now welcome further comments and feedback from the community before proceeding.

### The OCFL Editors

Expand All @@ -22,7 +22,7 @@ The OCFL Editors haved reviewed the community feedback on use cases related to t
- Issue #48 [Large Inventory.json files](https://github.com/OCFL/Use-Cases/issues/48)
- Issue #50 [Application Profiles](https://github.com/OCFL/Use-Cases/issues/50)

Tallying up the community votes and responses, the following use cases will be addressed in version 2.0 of the specification.
Tallying up the community votes and responses, the following use cases will be addressed in version 2.0 of the specification.

- Issue #33 [Package per version storage](https://github.com/OCFL/Use-Cases/issues/33)
- Issue #42 [Support physical file-level deletion](https://github.com/OCFL/Use-Cases/issues/42)
Expand Down Expand Up @@ -71,11 +71,11 @@ Andrew Woods (Harvard University)

**1 August 2023**

In July of 2020, version 1.0 of the OCFL specification was released followed by version 1.1 in October of 2022.
In July of 2020, version 1.0 of the OCFL specification was released followed by version 1.1 in October of 2022.
We are now beginning to consider additional use cases and revisions that will lead to version 2.0 of the specification.

In addition to gathering feedback via issues and use cases, we would also like to gather feedback and new use cases from
the community through conversation. To that end we will hold a series of listening sessions, we invite all individuals who
In addition to gathering feedback via issues and use cases, we would also like to gather feedback and new use cases from
the community through conversation. To that end we will hold a series of listening sessions, we invite all individuals who
have implemented or are interested in The Oxford Common File Layout to attend.

Below are the dates and times for the listening sessions:
Expand All @@ -86,7 +86,7 @@ ET / 5pm PT | Thursday August 10th 10am AEST
13th 4pm GMT / 11am EST / 8am PST | Thursday September 14th 1am AEST
* iPres Birds of a Feather session - Date and time TBD

We look forward to hearing from you during these sessions and please reach out if you have any questions.
We look forward to hearing from you during these sessions and please reach out if you have any questions.

### The OCFL Editors

Expand All @@ -106,7 +106,7 @@ compatible with version 1.0.

### What new information is available?

The OCFL website at [https://ocfl.io](https://ocfl.io), includes the most up to date version of the specification and
The OCFL website at [https://ocfl.io](https://ocfl.io), includes the most up to date version of the specification and
the implementation notes as well as the latest editors draft.

The [OCFL Specification v1.1](https://ocfl.io/1.1/spec/) defines both OCFL Objects, a simple structure for content and
Expand All @@ -119,10 +119,10 @@ the specification including recommendations for digital preservation, storage ha
practices for dealing with OCFL Objects in motion.

The OCFL Editors are also releasing updated [validation rules](https://ocfl.io/1.1/spec/validation-codes.html) and
additional [fixture objects](https://github.com/OCFL/fixtures) for testing OCFL implementations against the specification.
additional [fixture objects](https://github.com/OCFL/fixtures) for testing OCFL implementations against the specification.

There is an accompanying [Change Log](https://ocfl.io/1.1/spec/change-log.html) that details the changes from version 1.0
to version 1.1. It is designed to assist implementers with updates to their implementations. We welcome your feedback,
to version 1.1. It is designed to assist implementers with updates to their implementations. We welcome your feedback,
questions, use cases, and especially details of any implementations or experimentation with OCFL.

### The OCFL Editors
Expand Down
Loading