push bioportal/ontoportal client code upstream

[cmungall]

We have a bioportal implementation here:

https://github.com/INCATools/ontology-access-kit/tree/main/src/oaklib/implementations/bioportal

(despite the name this is actually a more general ontoportal client)

Currently the focus has been on text annotator, mapping provider

The logic here could be scooped out so it can be used for people who want a more bare metal ontoportal client - or in fact it looks like this has been done:

https://github.com/cthoyt/ontoportal-client

cc @cthoyt @graybeal @jonquet

[cthoyt]

Yup I’d be happy to facilitate moving this code upstream

[graybeal]

Sorry to be naive, but just to be sure: This is an OAK (ontology access kit) client that could interface with some 'external' BioPortal or OntoPortal instance, right? (It isn't a whole OntoPortal installation.)

So a user would use this repo to create a working area for developing an ontology, that could then be stored/managed/published in the BioPortal or OntoPortal repository. Yes?

[cmungall]

I think you're about ten steps ahead @graybeal. Right now we are only talking about client code that wraps an ontoportal API

[jonquet]

cc @syphax-bouazzouni for possible feedback.