- From: Robert Sanderson <azaroth42@gmail.com>
- Date: Thu, 25 Jul 2013 13:44:51 -0400
- To: Paolo Ciccarese <paolo.ciccarese@gmail.com>
- Cc: public-openannotation <public-openannotation@w3.org>
- Message-ID: <CABevsUEvgM9B1SzhamKJ4iRQKXo_fG4eupU2AdafqFpZtCSXdw@mail.gmail.com>
Hi Paolo, While I'm happy with using the geo ontology, I'm not sure that geo:location is the right predicate to use with the Annotation, given the collapsing of the annotation document/concept. Is it the annotating or serializing activity, in PROV terms, which the location is referring to? The ontology defines geo:location as: "The relation between something and the point, or other geometrical thing in space, where it is." I'm not sure that the location of the annotator at the time they created the annotation concept is "where it [the annotation] is." That seems more like the location of the storage system (annotation as document) or just not a point in space (annotation as a concept). Could you explain how you would see the mapping into the PROV model? Thanks! Rob On Thu, Jul 25, 2013 at 1:27 PM, Paolo Ciccarese <paolo.ciccarese@gmail.com>wrote: > I was looking into recording the geolocation at the annotation level > (where the annotation has been generated, not the body). > > Is the vocabulary: > http://www.w3.org/2003/01/geo/wgs84_pos# > the best option? > > How do we recommend to link it to the annotation? > > I was looking at this: > http://www.ebusiness-unibw.org/wiki/GoodRelations_and_Geo_/_Location_Data > > Are we good with this? > geo:location [ geo:lat "48.0802626"; geo:long "11.6407428". ]. > > vCard seems another options as explained in that page. > > Best, > Paolo > > > -- > Dr. Paolo Ciccarese > http://www.paolociccarese.info/ > Biomedical Informatics Research & Development > Instructor of Neurology at Harvard Medical School > Assistant in Neuroscience at Mass General Hospital > Member of the MGH Biomedical Informatics Core > +1-857-366-1524 (mobile) +1-617-768-8744 (office) > > CONFIDENTIALITY NOTICE: This message is intended only for the > addressee(s), may contain information that is considered > to be sensitive or confidential and may not be forwarded or disclosed to > any other party without the permission of the sender. > If you have received this message in error, please notify the sender > immediately. >
Received on Thursday, 25 July 2013 17:45:19 UTC