W3C home > Mailing lists > Public > public-annotation@w3.org > August 2015

Re: roles and multiple bodies

From: Jacob Jett <jjett2@illinois.edu>
Date: Tue, 4 Aug 2015 16:58:16 -0500
Message-ID: <CABzPtBJiZ-DhAU6MGMVCwDuNfEgsg6EVsSYG27Z1zN17O6Gs1Q@mail.gmail.com>
To: "Denenberg, Ray" <rden@loc.gov>
Cc: Paolo Ciccarese <paolo.ciccarese@gmail.com>, Web Annotation <public-annotation@w3.org>
That seems really confusing, I would think that if the blank node was
converted into an IRI or URI then the same identifier would be used for
each instance of that particular blank node after all it's not the case
that the blank node has no identifier at all, just that it's identity is
specific to the graph instance it is a part of.

So the triples would become:

<anno1> hasRoleAssignment <URI>
<URI> for <anno1>
<URI> role <role1>
<URI> assignedTo <body1>

I think the suggested oa:for predicate in this structure looks somewhat
redundant, i.e., it's hard not to imagine that it's just the reciprocal of
the suggested oa:hasRoleAssignment. Other than that potential quibble this
looks pretty reasonable -- more specificity for the cost of more structure.

Regards,

Jacob



_____________________________________________________
Jacob Jett
Research Assistant
Center for Informatics Research in Science and Scholarship
The Graduate School of Library and Information Science
University of Illinois at Urbana-Champaign
501 E. Daniel Street, MC-493, Champaign, IL 61820-6211 USA
(217) 244-2164
jjett2@illinois.edu

On Tue, Aug 4, 2015 at 4:35 PM, Denenberg, Ray <rden@loc.gov> wrote:

> Hi Jacob – it’s a tough question  because you get into the weeds of blank
> nodes vs. independent resource, of which there was much discussion today,
> which I have skimmed but not absorbed.  But I think the issue here is that
> the role assignment might originally treat the role assignment as a blank
> node, but someone could turn it into a reusable resource. Then you have:
>
>
>
> <uri>   a   RoleAssignment ;
>
>            role   <roleX> ;
>
>            for   <bodyX>   .
>
> And without the forAnnotation, the annotation is lost.  I don’t know, Let
> Rob figure it out.
>
>
>
> Ray
>
>
>
> *From:* jgjett@gmail.com [mailto:jgjett@gmail.com] *On Behalf Of *Jacob
> Jett
> *Sent:* Tuesday, August 04, 2015 5:27 PM
> *To:* Denenberg, Ray
> *Cc:* Paolo Ciccarese; Web Annotation
>
> *Subject:* Re: roles and multiple bodies
>
>
>
> Hi Ray,
>
>
>
> To follow up on Paolo's question, isn't a roleAssignment a property of the
> Annotation itself in the proposed solution?
>
>
>
> So you get the following triples:
>
>
>
> _:anno1 hasRoleAssignment _:b1
>
> _:b1 for _:anno1
>
> _:b1 role _:role1
>
> _:b1 assignedTo _:body1
>
>
>
> So I suppose the question is how is the oa:for predicate different from
> the reciprocal of the oa:hasRoleAssignment predicate?
>
>
>
> Regards,
>
>
>
> Jacob
>
>
>
>
>
>
> _____________________________________________________
>
> Jacob Jett
> Research Assistant
> Center for Informatics Research in Science and Scholarship
> The Graduate School of Library and Information Science
> University of Illinois at Urbana-Champaign
> 501 E. Daniel Street, MC-493, Champaign, IL 61820-6211 USA
> (217) 244-2164
> jjett2@illinois.edu
>
>
>
> On Tue, Aug 4, 2015 at 4:16 PM, Denenberg, Ray <rden@loc.gov> wrote:
>
> Hi Paolo,
>
>
>
> I felt the forAnnotation to be necessary, because without it, you would be
> saying “this role is assigned to this body”, independent of any particular
> annotation. So if some other role were to be assigned to that body, for a
> different annotation, there would be a conflict.
>
>
>
> Ray
>
>
>
> *From:* Paolo Ciccarese [mailto:paolo.ciccarese@gmail.com]
> *Sent:* Tuesday, August 04, 2015 5:13 PM
> *To:* Denenberg, Ray
> *Cc:* Web Annotation
> *Subject:* Re: roles and multiple bodies
>
>
>
> Hi Ray,
>
> Is the subject of oa:hasRoleAssignment still the annotation?
>
> I would probably  remove oa:forAnnotation as it looks redundant to me.
>
>
>
> It is a little bit indirect in JSON but it seems a possible solution.
>
> Who needs to be more specific could add those sections.
>
>
>
> Paolo
>
>
>
> On Tue, Aug 4, 2015 at 4:55 PM, Denenberg, Ray <rden@loc.gov> wrote:
>
> Has the following approach been considered?  I don’t think it violates any
> of the principles that Rob is defending, because it explicitly narrows the
> scope of the role to the annotation:
>
>
>
>
>
> <http://www.example.org/annotation
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_annotation&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=5hECq5TfN96rXIn1jVdxJjZccwEqUCEfEW1GY-WYCac&e=>>
> a  oa:Annotation ;
>
>
>
>           oa:hasTarget  <http://www.example.org/target
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_target&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=aenpIrvMN6tUgwowQE3_VLlxaLWoX6Ue3KRT8vQgh_0&e=>>
> ;
>
>
>
>           oa:hasBody  <http://www.example.org/body1
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_body1&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=vVlBuqPDsswj2vE1zNds9DmKw3MkrRzJkxWx_73H35Q&e=>>
>  ;
>
>           oa:hasBody  <http://www.example.org/body2
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_body2&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=anRcp9_bFjDMdhyk6UnkjlwNHbKAUlriR0ZKOKtlYjg&e=>>
> ;
>
>           oa:hasBody  <http://www.example.org/body2
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_body2&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=anRcp9_bFjDMdhyk6UnkjlwNHbKAUlriR0ZKOKtlYjg&e=>>
> ;
>
>
>
> oa:hasRoleAssignment [
>
>                       oa:role                   <role1>   ;
>
>                        oa:assignedTo     <http://www.example.org/body1
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_body1&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=vVlBuqPDsswj2vE1zNds9DmKw3MkrRzJkxWx_73H35Q&e=>>
> ;
>
>                       oa:forAnnotation  <http://www.example.org/annotation
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_annotation&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=5hECq5TfN96rXIn1jVdxJjZccwEqUCEfEW1GY-WYCac&e=>>
> ] ;
>
>
>
> oa:hasRoleAssignment [
>
>                       oa:role                   <role2>   ;
>
>                        oa:assignedTo     <http://www.example.org/body2
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_body2&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=anRcp9_bFjDMdhyk6UnkjlwNHbKAUlriR0ZKOKtlYjg&e=>>
>  ;
>
>                       oa:forAnnotation  <http://www.example.org/annotation
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_annotation&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=5hECq5TfN96rXIn1jVdxJjZccwEqUCEfEW1GY-WYCac&e=>>
> ] ;
>
>
>
>
>
> oa:hasRoleAssignment [
>
>                       oa:role                   <role3>   ;
>
>                        oa:assignedTo     <http://www.example.org/body3
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_body3&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=K-Vywo-KDw12WmvUM2HlDsyomgdqMsyk5hh5It1NUEo&e=>>
>  ;
>
>                       oa:forAnnotation  <http://www.example.org/annotation
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.example.org_annotation&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=5hECq5TfN96rXIn1jVdxJjZccwEqUCEfEW1GY-WYCac&e=>>
> ] .
>
> --Ray
>
>
>
>
>
> --
>
> Dr. Paolo Ciccarese
>
> Principal Knowledge and Software Engineer at PerkinElmer Innovation Lab
>
> Assistant Professor of Neurology at Harvard Medical School
>
>
> Assistant in Neuroscience at Mass General Hospital
>
> ORCID: http://orcid.org/0000-0002-5156-2703
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__orcid.org_0000-2D0002-2D5156-2D2703&d=AwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=FgXE3Py8DP9ZR2E1CvubZFrbjIgqiy0v_1XBzDcctL8&s=E-EN7VZum-gHElx-U74k-dGlYuo0DHr55IRcOtIjVfI&e=>
>
>
>
Received on Tuesday, 4 August 2015 21:59:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:39 UTC