Re: [web-annotation] Rename `role` to `motive`

@BigBlueHat 
1. I think that the relationship between the body and the annotation 
is very clear. The Body is the "payload" of the annotation, and that 
is all. The body is not about annotation but the body is about the 
target as basic fundament for annotations. 

2. Currently the Movitation should say, why I user creates an 
annotaion, expressing so the relationship between the Body and Target,
 still they are again very general statements, which (currently) 
impose no restriction on bodies. So ... they cannot be used for any 
kind inference (right now)!

3. I think that specifications of a standard should be technology 
independent, and must represent a conceptual model.
... Yes ... it is a Web Related standard and must be compliant with 
web technologies.  And I think that big improvements where made when 
the JSON-LD serialization was introduced (which is in fact the bridge 
between the Object and RDF world, showing that they are not mutually 
exclusive concepts)

4. I'm sorry, if I sent a lot of text that at the first glace doesn't 
seems to be relevant for the original question. But now I can conclude
 my questions:

a) Does the "role" have a clear definition and an clear naming so that
 a proper name can be found?
I find the definition and the example quite ambigous 
http://w3c.github.io/web-annotation/model/wd/#roles-for-external-resources
What I would expect in the annotation is to say that the resource 
indicated by the given URL is a "place" or a city. Motivation:tagging 
+ role:tagging is redundant and confusing.

b) Shouldn't the "role" indicate types or relationships? 
As it is written in the definition "as the role specifies the way in 
which the resource is used in the context of the Annotation"

Through the context of annotation I understand: the BODY saying 
something about the TARGET driven by the MOTIVATION. 
What is missing in this content is the "something" , what the body 
tries to say (as the URL doesn't provide much information, especially 
when the mime type is not provided) 

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

Received on Thursday, 17 December 2015 17:00:59 UTC