A lot of the issues currently opened for authentication are IMO more related to how we describe a catalog than authentication or a user's profile.
Several organizations using OPDS are building what is usually called an "OPDS Catalogs registry" and thanks to OPDS 2.0, it's possible to create a collection role specifically for that.
Should we start a draft dedicated to the catalogs role and the metadata that would usually be relevant for such use cases?
Aside from defining a new collection role and metadata, this document could also define how geo-location could work as well (URI template + rel value).
A lot of the issues currently opened for authentication are IMO more related to how we describe a catalog than authentication or a user's profile.
Several organizations using OPDS are building what is usually called an "OPDS Catalogs registry" and thanks to OPDS 2.0, it's possible to create a collection role specifically for that.
Should we start a draft dedicated to the
catalogsrole and the metadata that would usually be relevant for such use cases?Aside from defining a new collection role and metadata, this document could also define how geo-location could work as well (URI template + rel value).