Create schema that can be used for validation

[cmungall]

We want to be able to constrain APs, for example

• cardinality: max one text definition
• required: rdfs:label required
• domain: term-replaced-by should be used on obsolete classes only
• range, broad: should created-by be an object, string, or URI?
• range, specific: created-by should be filled with an orcid URI; term_tracker range #47
• lexical

We cannot encode these in OWL obviously, so we need another mechanism, e.g.

1. sparql queries
2. shex
3. shacl
4. linkml

We are effectively doing 1 in robot. In fact I outlined some of the same requirements here:

https://github.com/ontodev/robot/issues/205#issuecomment-353497795

I think this is great but I think it would be better to get the declarative specification into OMO. There may be a bit of redundancy between robot sparql query checks and omo in the short term but this is OK I think.

[jamesaoverton]

Sounds good to me.

For ROBOT report we've decided that we like the fine-grained error reporting that we can get out of SPARQL queries, and we've tried to link those fine-grained error messages with specific help documents. There are downsides to this approach but I plan to stick with it for ROBOT report.

The shape languages are clearly better at giving a concise, declarative description of the desired shape. I can see how they fit this use case better. We just have to make sure to coordinate with ROBOT report.

[cmungall]

@balhoff has a lot of experience getting informative reporting out of shex. AFAICR the out the box support is not great.