Thanks for this!
A couple of comments.
1. The concept of a "Data Lake" is deeply rooted in the print metadata landscape, and doesn't reflect the reality of today's digital world. You can't try to clean your digital metadata and carefully monitor the inflow for its pristine nature. Managing metadata for the digital world is like managing a river with many sources and many different downstream usages. It's new metadata everyday; things that were true yesterday are false today. The most poisonous thing about the "lake" model of metadata is that it requires gatekeeping, leaving large populations excluded from contributing to the lake.
2. I'm sure many other community participants were unexamined by the WP5 authors, but Unglue.it is in an adjacent position and has tackled most of the problems considered in the report. COPIM can learn from its successes and shortcomings, and the code is all free open source software. Unglue.it was built as a crowd-funding platform and has pivoted to being primarily a cataloguing and distribution platform for free ebooks. The catalogue has over 80,000 entries and has distributed almost 2 million ebooks. It's worth learning from
i. we implemted a metadata harvesting, editing and creation facitlity.
ii. we implemented faceted ONIX, OPDS and MARC feeds, as well as custom APIs. The OPDS feed was built to supply NYPL's Simply-E server.
iii. we implemented a FRBR model so that editions are grouped into works; many different ebook formats can be grouped onto editions if needed.
3. Deduplication and edition management are REALLY hard. Free licenses make this much harder than otherwise, because books can appear in so many guises, in so many places. For many types of works, OA books can be revised, sometimes quite often, and for these works, the lake is irrelevant. It would be a shame if WP5 precluded support for revision metadata. Ironically, the only contemplation of revisions in the report is self-referential!
4. The discussion of chapter metadata seems to omit consideration of the impact of OA licenses. The question is of scope. When is an article a chapter and not an article? Should COPIM be managing articles? How do you deal with book remixes? The OA world has long had the concept of "overlay journals" perhaps this idea will come into its own with "overlay" books. This is not a hard issue, but it's easy to get wrong, and easy to get tripped up by the lack of support in legacy metadata supply chains.
5. The only problem ISBN solves for Free Ebooks is fitting them into a sales-oriented system. Not that that's a bad thing.
Always happy to discuss!
Eric