Re: [web-annotation] Definitions of Specific Resources: Example

Hi Rob,

Mybe I'm to picky, but I would like ot ask why is the purpose a 
property of SpecificResources only and not any regular external 
resources? With regard to this I discovered a set of inconsitencies:

1. The definition of the purpose is outdated now, as it doesn't 
includes the posibility to use it in the SpecificResources

http://w3c.github.io/web-annotation/model/wd2/#motivation-and-purpose
```
purpose Relationship    The relationship between a TextualBody and a 
Motivation.
There MAY be 0 or more purposes for each TextualBody.
```

2. There is contradiction between the definition of the purpose as 
shown above, and the definition of the purpose in the SpecificResource

 ```
The types of additional specificity that are defined by this document:
    Purpose: Describe the purpose of including the source resource in 
the Annotation

```
Is purpose relationship between Resource (including here the 
TextualBody) and the Annotation, or the Motivation? I think that 
consistency is required. 

3. I have a question about the modeling of Bodies. It seems at least 
for now as the Body is a Resource. However, I think that in the real 
world, the body includes a resource (which has own properties as url, 
language, mime-type, propably also a label or title) and other 
metadata describing actually the sope and role of the body within the 
context of the Annotation (basically ... all what the motivation is 
not able to say about the body ... like purpose, selector, scope, 
etc.).

So ... my suggestion would be se separate these concerns, otherwise 
they will get more and more confusing...

I would suggest to consider the following representation for bodies:
```
body : {
  resource:{
     @id : myurl.com,
     language : en,
     mime-type: text/html,
     title/label: mywebpage
  },
 @type: TextualBody/ExternalResourceBody/SpecificResourceBody,
  purpose: roleOfBody
  selector: {...}
   .....
}

Of course ther can be the minified representation 
body:  myurl.com
equivalent for 
body : {
resorce:{ @id: myurl.com}
} 

... body .. should have no @id as the body should be serialized only 
whitin the annotation.

BR,
Sergiu


   

-- 
GitHub Notification of comment by gsergiu
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/138#issuecomment-188169756
 using your GitHub account

Received on Wednesday, 24 February 2016 09:51:37 UTC