- From: Paolo Ciccarese <paolo.ciccarese@gmail.com>
- Date: Tue, 4 Aug 2015 17:13:12 -0400
- To: "Denenberg, Ray" <rden@loc.gov>
- Cc: Web Annotation <public-annotation@w3.org>
- Message-ID: <CAFPX2kBy=GVYeVYOt--hBvQFE7y+cUQornuNsQcu6BcbW9yP4w@mail.gmail.com>
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> a oa:Annotation ; > > > > oa:hasTarget <http://www.example.org/target> ; > > > > oa:hasBody <http://www.example.org/body1> ; > > oa:hasBody <http://www.example.org/body2> ; > > oa:hasBody <http://www.example.org/body2> ; > > > > oa:hasRoleAssignment [ > > oa:role <role1> ; > > oa:assignedTo <http://www.example.org/body1> ; > > oa:forAnnotation <http://www.example.org/annotation> > ] ; > > > > oa:hasRoleAssignment [ > > oa:role <role2> ; > > oa:assignedTo <http://www.example.org/body2> ; > > oa:forAnnotation <http://www.example.org/annotation> > ] ; > > > > > > oa:hasRoleAssignment [ > > oa:role <role3> ; > > oa:assignedTo <http://www.example.org/body3> ; > > oa:forAnnotation <http://www.example.org/annotation> > ] . > > --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
Received on Tuesday, 4 August 2015 21:13:42 UTC