W3C home > Mailing lists > Public > public-openannotation@w3.org > January 2013

Re: Comments to “SE Free text tagging a Image”

From: Paolo Ciccarese <paolo.ciccarese@gmail.com>
Date: Wed, 30 Jan 2013 15:53:14 -0500
Message-ID: <CAFPX2kDZShQ7b0+YPqygY_4=9z82m7ZXk8AQTTB4xM=bARLy8w@mail.gmail.com>
To: Leyla Jael García Castro <leylajael@gmail.com>
Cc: public-openannotation <public-openannotation@w3.org>
Hi Leyla,
thank you for the feedback!

On Wed, Jan 30, 2013 at 3:40 PM, Leyla Jael García Castro <
leylajael@gmail.com> wrote:

> Comments to “SE Free text tagging a Image” at
> www.w3.org/community/openannotation/wiki/SE_Free_text_tagging_a_Image(and the corresponding section)
> About the example:
> The title should be “SE Free text tagging an Image”, the “n” at “an” is
> missing
> The description of the example says “A Tag is a label attached to someone
> or something for identification or other information.” I think a comment
> could also be used for “other information” so maybe a better description is
> required? Maybe we can use Wikipedia definition at
> http://en.wikipedia.org/wiki/Tag_(metadata)

That is a good idea, would you like to try and update the description?

> In the RDF we have <http://alturl.com/wxidq> a dt:Image. Does dt stand
> for Dublin Core Terms? If it does, then we should use the namespace defined
> in the Introduction, i.e., dcterms. If it does not, then we should include
> that namespace in the Introduction or at least in the example

I will introduce a table with the namespaces for each example. It is a fair

> A nice variation including the selection of a particular feature within
> the protein would be nice. That would probably include selectors and
> specific resources. However, the required selector would be tricky as it is
> not a portion of the image but a portion of the protein region represented
> by the image. Maybe that this is a 3D structure and just working with
> selected pixels in the image, or some kind of freehand selection? I think
> this would be a nice example. Ideas/suggestions on how to model the
> selection are welcome.

The tag  on a fragment of an image is certainly something we should add.
Later in the cookbook scenarios list there is a "Comment on Image
Fragment", an example with a Tag can be added. In general the list is far
from being complete. I invite anybody that has ideas in provide new
scenarios  even by just putting a title in the list.

> About the section:
> We have a section “2.1.3 Tags and Semantic Tags” and there we introduce
> the class oa:Tag. However, we do not use it in this example; I think it is
> missing.
> From the description in the section, it seems that semantic tags are those
> tags corresponding to URIs? I do not think that is always the case. “
> http://dbpedia.org/resource/Paris” does correspond to a semantic entity
> but “http://wikipedia.org/Paris/”  does not. I think that for semantic
> tags only URIs corresponding to semantic entities should be use, any other
> thoughts about it?

In that particular example I used a free text tag and so I am assuming the
motivation ao:tagging is enough. However, in general the point you raise is
a general issue. The current spec allows classifying a URI as semantic tag
by using oa:Tag. However, the spec says  also:

"It is NOT RECOMMENDED to use the URI of a document as a semantic tag, as
it might also be used as a regular Body in other Annotations which would
inherit the oa:Tag class assignment. Instead a new URI should be created
and linked to the document using an ontology appropriate to the situation."

Which I believe it is addressing what you are asking.
The problem arises when somebody uses document URIs as tags (not that

> One question not necessarily related to tags. Could I use annotations to
> say that a 3D version of that image can be retrieved from “PDB link” in
> format “XXX”? If yes, how could that being expressed in OA? In general, the
> question is how to express links to other resources with annotations?

Rob, was that the usage of the oa:linking motivation we removed?

Received on Wednesday, 30 January 2013 20:53:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:38:21 UTC