Open ericjeangirard opened 9 months ago
Hello @ericjeangirard , thank you for your question.
Our first instinct is to start from what we already produce and transform that into what is needed. So if we have the OWL ontology (currently being developed in the tools branch), we would look into ways of transforming that into a JSON schema. A quick search on the web gives me https://github.com/arhs/owl2json-schema, but we don't have a direct experience with it. Would you perhaps be willing to try that out?
Another approach would involve the Metadata Schema and Crosswalk Registry under development in the FAIRCORE4EOSC project: once a metadata schema (in any format, so OWL in our case) is registered, a user could ask for its alternative representation in another supported format.
Hello
Is there any json schema (similar to this kind of simple one https://github.com/dataesr/bso-parser-html/blob/main/project/server/main/schema.json ) that could be used to easily validate json data to be cerif-core compliant, without calling external services ?
if not, can we help somehow ?
thanks