At the risk of overwhelming the OCFL editors’ inboxes (a risk I’m willing to take, not being one of them), please see the request for comments, below. What’s OCFL?
a. Orange County, Florida b. Oxford Common File Layout c. an emerging best practice for LTDP file storage d. Something "sorely needed and I would be surprised if it didn't become just as critical a tool as BagIt is”, per digital preservation expert and community thought leader, Sibyl Schaefer e. all of the above (except A) [The correct answer is E.] - Tom Begin forwarded message: From: Andrew Woods <awo...@duraspace.org<mailto:awo...@duraspace.org>> Subject: [ocfl-community] Ready for Review: OCFL 0.1 (Alpha) Date: October 18, 2018 at 1:30:36 PM PDT To: pasig-disc...@mail.asis.org<mailto:pasig-disc...@mail.asis.org>, ocfl-commun...@googlegroups.com<mailto:ocfl-commun...@googlegroups.com> Cc: ocfl-editors <ocfl-edit...@googlegroups.com<mailto:ocfl-edit...@googlegroups.com>> Hello All, Think of it as an opportunity to participate in shaping the definition of the persistence layout for digital information, focused on long-term preservation. Many of us have a deep concern and responsibility for the preservation of slices of our shared digital, cultural heritage. The Oxford Common File Layout (OCFL) specification describes an application-independent approach to the storage of digital information in a structured, transparent, and predictable manner. It is designed to promote standardized long-term object management practices within digital repositories. Through a series of community conversations [1] starting in December of 2017, the OCFL 0.1 alpha specification release is now ready for your detailed review and feedback! https://ocfl.io/0.1/spec/ Please review the (short) specification and provide your feedback either as discussion on the ocfl-community [2] mailing list or as GitHub issues [3]. We will be discussing/incorporating the feedback during next month's community call [4] (November 14th @11am ET). In addition to feedback on the content of the specification, you are encouraged to join the November community call to share interest in implementing OCFL locally. More detail and implementation notes can be found at https://ocfl.io . Best regards, Andrew Woods, on behalf of the OCFL editorial group [1] https://github.com/OCFL/spec/wiki/Community-Meetings [2] ocfl-commun...@googlegroups.com<mailto:ocfl-commun...@googlegroups.com> [3] https://github.com/ocfl/spec/issues [4] https://github.com/OCFL/spec/wiki/2018.11.14-Community-Meeting -- You received this message because you are subscribed to the Google Groups "Oxford Common File Layout Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to ocfl-community+unsubscr...@googlegroups.com<mailto:ocfl-community+unsubscr...@googlegroups.com>. To post to this group, send email to ocfl-commun...@googlegroups.com<mailto:ocfl-commun...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/ocfl-community/CADz%3D0UmuTyTSx3OG0JXVJceXc1AtLqmYeBd%3D1TMxy41-FBG1eQ%40mail.gmail.com<https://groups.google.com/d/msgid/ocfl-community/CADz%3D0UmuTyTSx3OG0JXVJceXc1AtLqmYeBd%3D1TMxy41-FBG1eQ%40mail.gmail.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout.
