W3C home > Mailing lists > Public > public-annotation@w3.org > January 2016

Re: [web-annotation] Definition of specific resources: @Type

From: gsergiu via GitHub <sysbot+gh@w3.org>
Date: Fri, 15 Jan 2016 11:57:11 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-171943476-1452859030-sysbot+gh@w3.org>
well ... should every parser and serializer implement some complicated
 rules in order to extract type which is already explicit in the 
client applications that create the annotation?

Yes, I agree that type is not mandatory for Body and Targets, but I 
would expect that in this case, the default one should be used ... 
which is the simple resource identified by @id. 

Maybe this issue is closely related to the one indicated in the text:
Issue 2
A future version of the specification may REQUIRE the use of 
SpecificResources for Body and Target in order to ensure consistency 
at the expense of additional structure. 

If this change will be implemented and all resources are considered by
 default Specific Resources, the situation will be changed. 

In support to that change:
I also must confess that I had the feeling that the representation of 
specific resources is a kind og "buttom-up" approach and I find the 
"top-down" a more natural representation.
(e.g. the face detector on freebase is just a circle overlay on an 
image. So .. wenn tagging a person in an image you basically have only
 the URL to the image and the Selector for the Circle, but not id for 
the image region).... I think that in many cases the "Specific 
Resources" are not required to have an own ID (like the sections in an
 HTML document, that might have an anchor defined or they might not 
...)  

-- 
GitHub Notification of comment by gsergiu
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/137#issuecomment-171943476
 using your GitHub account
Received on Friday, 15 January 2016 11:57:13 UTC

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