search

hvdsomp / signposting

8 stars 0 forks source link

API Catalog name #27

Closed hvdsomp closed 11 months ago

hvdsomp commented 12 months ago

While the work is based on the api-catalog Internet Draft, I am wondering whether using API Catalog as the term to refer to the document that provides an overview of a repository's interoperability affordances is the best we can do. Especially since it goes quite a bit beyond what is commonly understood as being APIs and includes support for specs like PMH, SPARQL, ... and even things like Signposting, RO-Crate, ...

What to do? Ideas for catchy alternative names?

martinklein0815 commented 12 months ago

Reading the updated spec just now, I had the same thought. The spectrum of examples provided already goes beyond what is commonly referred to as APIs. The text uses "affordances" but, IMO, "affordance catalog" does not sound great. Maybe: "interoperability services", "FAIR support services (FAIRssCat)" are better options?

hvdsomp commented 12 months ago

I was just thinking of InterOPS

abollini commented 11 months ago

Is 'standards' catalog too pretentious? Machine's features?

phonedude commented 11 months ago

FAIRcat

(for FAIR Catalog)

rolls of the tongue nicely, incorporates the appropriate acronym (FAIR), captures "catalog"

hvdsomp commented 11 months ago

Loving it! Even works when the long name is FAIR Interoperability Catalogue. FAIRcat is great IMO!

EnnoMeijers commented 11 months ago

On second thoughts, adding the 'i' to make it FAIRiCat would be a more precise name for a 'FAIR interoperability Catalog' spec and gives the name cheerful twist.

huberrob commented 11 months ago

Great! both versions FAIRiCat or FAIRiCAT are perfect

hvdsomp commented 11 months ago

Thanks all for input. Changed name to FAIRiCat. Made necessary changes in document. Made publicly available at https://signposting.org/FAIRiCat/. Put redirect in place from API Catalog URL.