W3C home > Mailing lists > Public > public-annotation@w3.org > December 2015

Re: [web-annotation] Justify each Motivation with a behavior

From: gsergiu via GitHub <sysbot+gh@w3.org>
Date: Wed, 16 Dec 2015 15:28:10 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-165142084-1450279687-sysbot+gh@w3.org>
@rtroncy 

Well ... I'm not sure how much I'm confused or not ... There are the 
proposed values for motivation:
bookmarking, classifying, commenting, describing, editing, 
highlighting, identifying, linking, moderating, questioning, replying,
 reviewing, tagging. 

These look for me very like tag labels ... especially when used in 
JSON-LD serialization.
Yes, you are right, you have now definitions for all these lables. The
 most of these definitions follow the same pattern:
"The motivation for when the user intends <motivation_class> to the 
Target".
I'm sorry if I'm to picky ... but these kind of definitions doesn't 
improve much the real semantic. The difference is more technical than 
semantic.

my real point is ... that the motivation and the "roles" should be 
consistent, not all combinations of motivation+target "role" + body 
"role" are valid. And this should be ensured through the model ... we 
shouldn't expect that any client defines which combinations are valid 
and which not!

In order to ensure this, it would be be better that this information 
is packaged in the same object (class). However, this has the drawback
 of imposing restrictions on multiple tags + multiple bodies kind of 
annotations (which I don't find to be a very useful usecase, however I
 have to admit that some stakeholders will chose to use them).

So .. given these, I think that an alternative solution would be to 
add targetRole and bodyRole attributes to the Motivation class, and to
 allow individual targets and bodies to declare a more specific term 
(i.e. norrower from a controlled vocabulary)

concretely the existing example:
{
  "@id": "http://example.org/anno28",
  "@type": "Annotation",
  "body": [
    { 
      "role": "describing",
      "source": "http://example.org/description1"
    },
    {
      "role": "tagging", 
      "text": "tag1"
    }
  ],
  "target": [
    "http://example.org/image1",
    "http://example.org/image2"
  ]
}

should become:
{
  "@id": "http://example.org/anno28",
  "@type": "Annotation",
  "motivation":{
"@id": "http://example.org/motivation/describing",
"bodyRole": "describing",
"targetRole": "depiction"
},
  "body": [
    { 
      "source": "http://example.org/description1"
    },
    {
      "role": "tagging", 
      "text": "tag1"
    }
  ],
  "target": [
    "http://example.org/image1",
    "http://example.org/image2"
  ]
}  


-- 
GitHub Notification of comment by gsergiu
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/113#issuecomment-165142084
 using your GitHub account
Received on Wednesday, 16 December 2015 15:28:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:43 UTC