Linkml based UCO

[noelmcloughlin]

Consider converting UCO model into LinkML schemas:

Benefit:

• Easy to Author Schemas
• Rich modelling language
• Increasing Data-Centric adoption (datalad, risk-atlas-nexus, gaia-x, biolink, etc)
• Key benefit for UCO community is Bridge between Frameworks
• Toolchains and Polygot generators (25 last count)

From my perspective the "LinkML import" feature is great allowing reuse of disparate/modular schemas from different vendors (i.e. Enterrprise, uco-core, risk-atlas-nexus, datalad) to build applications in language humans can understand (YAML).

Cost

• Learn Linkml
• Convert UCO to Linkml Schema
• Workaround any SHACL/Shex gaps while waiting to contribute/receive fix

Demo

I am not Ontologist but Engineer learning Data-Centric approaches.

A few years ago, I ported UCO 1.1.0 to LinkML as learning exercise, which could be useful starting point. At the time I was unsure of LinkML traction outside Bio-medical but now I see LinkML used in other industries. See:

https://github.com/lmodel/uco-master
https://github.com/lmodel/uco-observable
https://github.com/lmodel/uco-tool
https://github.com/lmodel/uco-analysis
https://github.com/lmodel/uco-action
https://github.com/lmodel/ucs-core
https://github.com/lmodel/uco-victim
https://github.com/lmodel/uco-time
https://github.com/lmodel/uco-role
https://github.com/lmodel/uco-pattern
https://github.com/lmodel/uco-marking
https://github.com/lmodel/uco-location
https://github.com/lmodel/uco-identity
https://github.com/lmodel/uco-configuration
https://github.com/lmodel/uco-core
https://github.com/lmodel/uco-types
https://github.com/lmodel/uco-vocabulary
https://github.com/lmodel/collections # concept dependency