Modeling tool requirements

[VladimirAlexiev]

@OR13 @nissimsan
We should start tomorrow's discussion with Requirements for your modeling tool/language. Hopefully #295 will cover them but we first need to agree what we need.
YAML (for ease if use) is a given.

Here's some list

• Modeling
  • Inheritance
    • Single, multiple
    • Overriding inherited props (covariant)
  • Local (per class) props
  • Union range? For better polymorphism
  • Nested vs referenced sub-object
  • Reference by ID vs Reference by URI
    • do we need union of object vs data prop, as in schema.org?
  • Cardinalities
  • Inverses (virtual) for improved KG navigation
• Outputs
  • JSON Schema
  • JSONLD Context
  • JSONLD Frame
  • RDF ontology
  • RDF shapes (SHACL or SHEX)
  • GraphQL schema and queries?

[VladimirAlexiev]

Some of the above comes from my experience designing SOML, which is a simple schema language to map RDF to GraphQL schemas: https://platform.ontotext.com/soml/index.html

We should compare the above list against https://linkml.github.io/linkml-model/docs/ (#295). It has more stuff eg Mixins.

[OR13]

these are very good suggestions, i'm struggling to tell how this issue is different than #295 can we perhaps group these by 'what we get with link ML" vs. "what we might need custom code to support" ?

[VladimirAlexiev]

Well, if you've already selected LinkML then we don't need to investigate this one.
But it's always good to have a list of things you want to evaluate tools you can have.

Eg I'm not sure how LinkML does RDF->JSONLD, in particular JSONLD Frame.

[nissimsan]

This is great, but we can't afford to start over with our modelling. Closing.