1.6: Allow domain, range, is-a for annotation properties (alternative to #135)

[cmungall]

Alternative to:

• 135

Currently http://owlcollab.github.io/oboformat/doc/obo-syntax.html#5.4 states

Typedef frame with id:Rel-ID	Translation - TP(S)
is_a(SubRel-ID Qualifiers))	SubObjectPropertyOf(T(Qualifiers) T(Rel-ID) T(SubRel-ID))
domain(TargetClass-ID Qualifiers))	ObjectPropertyDomain(T(Qualifiers) T(Rel-ID) T(TargetClass-ID))
range(TargetClass-ID Qualifiers))	ObjectPropertyRange(T(Qualifiers) T(Rel-ID) T(TargetClass-ID))

This assumes the Typedef is an OP. A Typedef can be mapped to an AP via the rules in 5.1:

OBO	Conditions	Translation - TF(S)
Term(Class-id Clause-1..Clause-n)		Class(T(Class-id)) TC(Clause-1)..TC(Clause-n)
Typedef(Rel-ID)	is_metadata_tag(true) ∈ TypedefFrames[Rel-ID]	AnnotationProperty(T(Rel-ID)) TP(Clause-1)..PC(Clause-n)
Typedef(Rel-ID)	is_metadata_tag(true) ∉ TypedefFrames[Rel-ID]	ObjectProperty(T(Rel-ID)) TP(Clause-1)..PC(Clause-n)
Instance(Instance-id)		NamedIndividual(T(Instance-id)) TI(Clause-1)..IC(Clause-n)

under 1.4 spec, if we have:

[Typedef]
id: r
is_metadata_tag: true
range: xsd:string

this will result in illegal punning.

proposal

• change 5.4 table to include alternative rules depending on whether interpretation is AP or DP