I’m seeing something from the earlier thread, In Which A Book Lexicon is Born - #32 by omg.jacky.wtf , that I think we can come to agreement on:
- Having a thin but heavy-on-identifier record defined by something under the NSID
community.lexicon.bookso any book-centric app can find out if a user’s repo has things related to it. - Having a separate but referential approach to having a per-app lexicon experience for custom data around a book
This way, Bookhive can keep moving as it is, Hardcover can introduce itself writing these records but both apps can use their own lexicons to define extra behavior like reviews, reading progress and what have you.
For the curious: one using something like https://constellation.microcosm.blue/ can collect these records across services so they can still benefit from the data written, would just need to parse it into a way that your service understands.
How does this sound to folks? If it’s good, we can keep it edition-centric (since a lot of things seem to converge around this over the works approach and it’ll keep AppView implementations a bit more simpler) and start thinking about how to declare the identifiers key.