Re: Annotating realworld objects

And, in a separate message so as to be clear about the tongue firmly in
cheek nature of the suggestion:

A google glass interface for viewing them?  :)
    http://www.google.com/glass/start/

R



On Mon, Apr 22, 2013 at 9:18 PM, Robert Sanderson <azaroth42@gmail.com>wrote:

>
> Dear Bart,
>
> Yes you can annotate real world objects that have a URI to identify them,
> we make no restrictions on what can be annotated :)
>
> It would be good to have a class associated with the resource so it is
> clear that the URI identifies a real world object and thus clients know not
> to try to use the representation.  And it is definitely good practice to
> not have a representation returned from that URI directly, to ensure that
> annotations on the RDF representation do not collide with annotations on
> the real world object.
>
> You might consider the Pelagios project, which does this for linking
> ancient places and objects:
>     http://pelagios-project.blogspot.com/2012_08_01_archive.html
>
> Hope that helps!
>
> Rob
>
>
>
> On Mon, Apr 22, 2013 at 9:01 PM, Bart van Leeuwen <
> Bart_van_Leeuwen@netage.nl> wrote:
>
>> Hi All,
>>
>> I've been reading the webpages and the specs and it seems that the oa
>> ontology looks very usable for my use case, I can make statements and
>> classify these statements.
>> The only issue I have is that I want to make the annotations on real
>> world objects, e.g. buildings. These real world objects do have a RDF
>> Resource describing them.
>> My questions are:
>> - Does os allow to annotate real world objects which have a RDF
>> representation?
>> - Are there some hints / tips or best practices that would fit such a
>> case?
>>
>> Looking forward to the answer / discussion already
>>
>> Met Vriendelijke Groet / With Kind Regards
>> Bart van Leeuwen
>> @semanticfire
>>
>> ##############################################################
>> # netage.nl
>> # http://netage.nl
>> # Enschedepad 76
>> # 1324 GJ Almere
>> # The Netherlands
>> # tel. +31(0)36-5347479
>> ##############################################################
>
>
>