dead_simple_owl_design_patterns
dead_simple_owl_design_patterns copied to clipboard
INCATools
A simple system for specifying OWL class design patterns for OBO-ish ontologies.
One of the most important pain points during validation is cases when I am using `%` instead of `%s` in pattern strings strings. Example: ``` name: text: "% adenoma" vars:...
I would like to propose to repurpose pattern_name as being human readable. The field is used by no process that I know off, but our documentation pages suffer from ugly...
Right now, we only have classes, relations, dataProperties and annotationProperties - we need individuals as well.
It would be very cool if we could simply tie a pattern to a community discussion (e.g. a GitHub issue or similar) directly.
Simple field we can use to document alternative patterns to the one presented, see [here](https://github.com/obophenotype/upheno/pull/593#issuecomment-588202832). This will help people finding the correct pattern in case its difficult to make a...
``` annotations: - annotationProperty: oio:hasExactSynonym text: "acquired %s" vars: - disease ``` I dont know why, but this all by itself is rejected by dosdp tools (so I assume the...
structure ``` src/schema/dosdp_schema.yaml # = spec/DOSDP_schema_full.yaml src/schema/test/ src/schema/test/generic_test # Is it valid JSON schema. src/schema/test/positive_test_set/ # Some list of passing files to test src/schema/test/negative test_set/# Some list of failing files...
# rationale names will be exposed in documentation for editors, curators, and general end-users who wish to understand the general patterns of the ontology, so it is important to use...
I'd like to spring clean this repo & push simple pattern tested (with embedded schema) to PyPi, but before I move anything, I'd like a PURL for the schema for...
There are similarities and differences in semantics and use cases between templates (dosdps, robot, ottr) and shapes (shex, shacl). We should explore these and formalize the linkages, and possibly even...