RE: Class of an annotation body

Hi Stian, I do like the approach with multiple bodies including one to tie the others together.



I am still confused about the protocol interactions, which is part of the reason I started this, to see if I could nail this down, so let me tease this out a bit.



In my example, http://bd.example.com is the "Bird Description" service.  http://bd.example.com/wtp  is the resource for the description of an individual species (White-Throated Sparrow), essentially a stub, depending on contributed information via annotation.   Me, I'm just a backyard birder who snaps a picture of a bird, maybe records its song/call, and transfers the image and sound clip to my PC (no  server).   Somehow, we got from there to here:

>   <http://bd.example.com/wtp/anno1>     a      oa:Annotation ;

>

>      oa:hasTarget        <http://bd.example.com/wtp/>

>      oa:hasBody       <http://bd.example.com/wtp/anno1/observation>,

>                              <http://bd.example.com/wtp/anno1/call.mp3>,

>                              <http://bd.example.com/wtp/anno1/song.mp3>,

>                              <http://bd.example.com/wtp/anno1/photo.jpeg> .



In other words, somehow the call/song/photo got from my PC to the server.   Do we need to detail in the protocol how that happened, or is this the purview of the interface and out of scope for our spec?



Thanks.



Ray