Problem description / use case
OntoME ontologies are given an internal namespace, i.e. https://ontome.net/ns/xyz/. Currently this IRI resolves to an error page (Oops! An Error Occurred. The server returned a "404 Not Found".)
Functional Requirements
It would be nice if this name resolved to the OWL file, to use direct imports in OWL.
It would be even better if OntoME reads the User-Agent header in the request and recognises whether it is a browser access, then refers to the Indentification Page, otherwise to the OWL file.
Technical Specification
You could do something like that:
Problem description / use case OntoME ontologies are given an internal namespace, i.e. https://ontome.net/ns/xyz/. Currently this IRI resolves to an error page (Oops! An Error Occurred. The server returned a "404 Not Found".)
Functional Requirements It would be nice if this name resolved to the OWL file, to use direct imports in OWL. It would be even better if OntoME reads the User-Agent header in the request and recognises whether it is a browser access, then refers to the Indentification Page, otherwise to the OWL file.
Technical Specification You could do something like that: