After a little walk, I think we have a problem if we don't specify in a direct way a preferred direction in the symmetric properties: annotations. I think we don't want to annotate triples of both directions with different annotations, provenance, sources, etc. that wouldn't make sense. So when we want to annotate, we have to chose one direction...
So what do you think about defining that for all symmetric properties? For many cases it could be an annotation adm:preferredDirection true on some objectProperties (like hasChild, hasSon, hasDaughter, teacherOf, etc. But some cases are not that easy, and could be marked with adm:directionAmbiguous true (like hasBrother, hasSister, etc.), in these cases what I propose we do is use the direction that goes from the smaller URI to the larger URI, for instance if we have:
After a little walk, I think we have a problem if we don't specify in a direct way a preferred direction in the symmetric properties: annotations. I think we don't want to annotate triples of both directions with different annotations, provenance, sources, etc. that wouldn't make sense. So when we want to annotate, we have to chose one direction...
So what do you think about defining that for all symmetric properties? For many cases it could be an annotation
adm:preferredDirection trueon some objectProperties (likehasChild,hasSon,hasDaughter,teacherOf, etc. But some cases are not that easy, and could be marked withadm:directionAmbiguous true(likehasBrother,hasSister, etc.), in these cases what I propose we do is use the direction that goes from the smaller URI to the larger URI, for instance if we have:then the first direction would be the preferred one (for annotations, etc.). Wdyt?