Re: inverse property of oa:hasTarget

I have mixed feelings about this.

On one hand, there's the problem of multiple representations for the same
thing (cf.
http://richard.cyganiak.de/blog/2006/06/an-rdf-design-pattern-inverse-property-labels/
).

But in my own work with OA, I have introduced a 'hasAnnotation' property
(not in the oa namespace) for the specific purpose of having a tracking
(some of) its annotations.  The annotations still use 'hasTarget'.

I think there are times when this is useful (especially when working with
JSON-LD), but I question whether it's s good idea to encourage this use
more generally by actually defining inverse properties in the oa namespace.

On further reflection, prompted by this discussion, I'm wondering if I
might not just use 'rdfs:seeAlso' rather than my new 'hasAnnotation'
property.  I.e. a new not-quite-inverse property that can be used for
discovery, but which doesn't replicate 'hasTarget' semantics.

#g

On Thu, 19 Sep 2019, 01:35 James Smith, <jgsmith@gmail.com> wrote:

> My gut reaction to the proposal of the inverse was that the same thing
> might be achievable by swapping the subject and object while keeping the
> oa:hasTarget predicate.
>
> Discovering which annotations are targeting something is nontrivial. And
> we don't expect targets to track annotations targeting them. They don't
> have that agency in the model.
>
> So I would expect annotations to be loaded into a graph before running the
> query. In which case, oa:hasTarget will be there.
>
> If we do expect targets to track annotations targeting them or targets are
> otherwise discoverable without the annotation, then oa:targetedBy or
> similar might fill a need.
>
> -- Jim
>
> On Wed, Sep 18, 2019, 7:48 PM Robert Sanderson <azaroth42@gmail.com>
> wrote:
>
>>
>>
>> All,
>>
>> This seems very reasonable to me.  Although there wasn't a use case in
>> the CG / WG timeframe for inverse relationships, it would not hurt to add
>> them to the ontology.
>> Given that the ontology isn't covered by publication rules, I also think
>> that we could add them as a CG.  Similarly, when the JSON-LD 1.1 work
>> finishes, we could also consider a 1.1 context that works more seamlessly
>> with other contexts.
>>
>> The full set of properties defined by the ontology are here:
>> https://www.w3.org/TR/annotation-vocab/#properties
>>
>> In particular, I would foresee the need for:
>>
>> hasTarget -> isTargetOf
>> hasBody -> isBodyOf
>> hasSource -> isSourceOf
>> hasSelector -> isSelectorOf
>> hasState -> isStateOf
>> hasScope -> isScopeOf
>> hasStartSelector -> isStartSelectorOf
>> hasEndSelector -> isEndSelectorOf
>> refinedBy -> refines
>> styledBy -> styles
>>
>> We clearly do not need inverses where the range is a literal. And I do
>> not think we need inverses for the properties where the range is a
>> Motivation, as the inverse would have an enormous number of values in any
>> system.  (The same way as an inverse of rdf:type would be pointless)
>>
>> Thoughts?
>>
>> Rob
>>
>>
>> On Wed, Sep 18, 2019 at 11:21 PM Marilena Daquino <
>> marilena.daquino2@unibo.it> wrote:
>>
>>> Hi all!
>>> I'm currently working on extending the OpenCitations data model [1] with
>>> terms from the OA ontology.
>>>
>>> I was wondering whether is possible to have the inverse property of
>>> oa:hasTarget. Specifically I'm mining full-text articles and I'd need
>>> to link in-text references (individuals of the class
>>> c4o:InTextReferencePointer [2]) with individuals of the class cito:Citation
>>> [3] and further annotate the latter.
>>>
>>> We are going to process and query massive amounts of data and we would
>>> like to have something like to build the following pattern (expanded
>>> for the sake of readability):
>>>
>>> ?article frbr:part ?sentence .
>>> ?sentence c4o:isContextOf ?intextReference .
>>> ?intextReference oa:inverseOfHasTarget ?referenceAnnotation .
>>> ?referenceAnnotation oa:hasBody ?citation .
>>>
>>> Many thanks in advance for your attention!
>>>
>>> [1] http://opencitations.net/model
>>> [2] http://www.sparontologies.net/ontologies/c4o
>>> [3] http://www.sparontologies.net/ontologies/cito
>>>
>>> Marilena Daquino
>>> Research assistant /DH.arc, Digital Humanities Advanced Research Centre.
>>> Department of Classic Philology and Italian Studies, University of
>>> Bologna,
>>> 40126, Bologna. Italy
>>>
>>> @emmedaquino
>>>
>>
>>
>> --
>> Rob Sanderson
>> Semantic Architect
>> The Getty Trust
>> Los Angeles, CA 90049
>>
>