This also changes the spec to allow any annotation type at the top level (printf annotation, list annotation, IRI value annotation)—not sure why it was limited to printf annotation before? All the annotations keys in nested structures allowed both types.
This also changes the spec to allow any annotation type at the top level (printf annotation, list annotation, IRI value annotation)—not sure why it was limited to printf annotation before? All the
annotations
keys in nested structures allowed both types.The purpose of this new annotation type is to be able to have an annotation axiom where the value is the IRI of an OWL entity, not a string. E.g. for https://github.com/geneontology/go-ontology/pull/16508
Parsers can distinguish this annotation type from the other kinds because it has a
var
property with a string value, rather thanvars
with a list.@dosumis I only edited the YAML. Do you create the JSON automatically?