We are setting up to generate all of the specifications for glyphs in SBOL Visual from machine-readable ontology entries, which will enable assurance of:
1) tool usage of glyphs is always kept in sync with the specification, and
2) full programmatic support for glyphs as soon as they are adopted.
Can we do something similar for the SBOL data, in which the hand-written portion of the specification is only information at the meta-level, while the class descriptions and verification rules are organized via an ontology?
This has the potential to greatly simplify the maintenance of libraries and tools.
We are setting up to generate all of the specifications for glyphs in SBOL Visual from machine-readable ontology entries, which will enable assurance of: 1) tool usage of glyphs is always kept in sync with the specification, and 2) full programmatic support for glyphs as soon as they are adopted.
Can we do something similar for the SBOL data, in which the hand-written portion of the specification is only information at the meta-level, while the class descriptions and verification rules are organized via an ontology?
This has the potential to greatly simplify the maintenance of libraries and tools.