W3C home > Mailing lists > Public > public-openannotation@w3.org > August 2012

Re: Textual Note example

From: Paolo Ciccarese <paolo.ciccarese@gmail.com>
Date: Fri, 17 Aug 2012 07:16:31 -0400
Message-ID: <CAFPX2kBSMF7MuKMALcDHs8RfJTX2o6Tc=aFdbavsGaWjTFhzng@mail.gmail.com>
To: Leyla Jael García Castro <leylajael@gmail.com>
Cc: Bob Morris <morris.bob@gmail.com>, public-openannotation <public-openannotation@w3.org>
I believe the problem here - body with text in multiple languages - is the
fact that multiple bodies are not allowed and that, in the past, has been
my natural choice for translations. I am less concerned with expressing the
language of the text. In fact, as Layla pointed out, there are ways of
specifying the language within the current methodology.

Translations are certainly an argument in favor of supporting multiple
bodies. However, there might be an alternative. We were discussing here
idea of having a Composite Annotation that allows for sub-annotations.
The idea would be having the different translations as sub-annotations of a
main annotation.

The idea of the CompositeAnnotation would be to collect sub-annotations
that have been created at the same time/context and that are meant to go
stick together. Then it would be possible to relate the sub-annotations as
alternative translations. Now the question is if it is possible to use a
CompositeAnnotation to create sub-annotations of different nature AND
translations. I will try to put down an example asap.


On Fri, Aug 17, 2012 at 6:21 AM, Leyla Jael García Castro <
leylajael@gmail.com> wrote:

> Hi Bob,
> The range for cnt:chars is a Literal so you can use a language tag to
> specify the language used in that particular text. Another possibility
> would be dct:language property.
> As for expressing in different languages the same annotation, I guess
> there are different approaches. The same body, for instance, could be
> applied to multiple targets representing the same content in different
> languages; another scenario as you mentioned is having the same textual
> body in different languages, all of them applied to the same target.
> For the second scenario, having different bodies is not possible in OA,
> but maybe having a List or Sequence as body would work? Each member of the
> list would be then a cnt:ContextAsText with its own language and
> corresponding text.
> any thoughts?
> Leyla
> On Fri, Aug 17, 2012 at 4:22 AM, Bob Morris <morris.bob@gmail.com> wrote:
>> Paolo-
>> http://www.w3.org/community/openannotation/wiki/Annotating_a_Webpage_with_a_Textual_Note
>> With the oa:Body typed as cnt:ContentAsText, is there a way to specify
>> the language of the cnt:chars?  It doesn't seem that there is a way in
>> cnt.  I wonder why? One might have to annotate with ContentAsXML to
>> express the language, which is overkill.
>> A related use case is the expression of an Annotation in several
>> different languages. If forced to make them as separate Annotations,
>> it would be tricky to express that they are meant all to express the
>> same Textual Note.  Maybe this means that the cnt:ContentAsText should
>> not be the type of the oa:Body, but rather of something that can hang
>> on the Body without any cardinality restrictions.
>> Bob
>> --
>> Robert A. Morris
>> Emeritus Professor  of Computer Science
>> UMASS-Boston
>> 100 Morrissey Blvd
>> Boston, MA 02125-3390
>> IT Staff
>> Filtered Push Project
>> Harvard University Herbaria
>> Harvard University
>> email: morris.bob@gmail.com
>> web: http://efg.cs.umb.edu/
>> web: http://etaxonomy.org/mw/FilteredPush
>> http://www.cs.umb.edu/~ram
>> ===
>> The content of this communication is made entirely on my
>> own behalf and in no way should be deemed to express
>> official positions of The University of Massachusetts at Boston or
>> Harvard University.

Dr. Paolo Ciccarese
Biomedical Informatics Research & Development
Instructor of Neurology at Harvard Medical School
Assistant in Neuroscience at Mass General Hospital
+1-857-366-1524 (mobile)   +1-617-768-8744 (office)

CONFIDENTIALITY NOTICE: This message is intended only for the addressee(s),
may contain information that is considered
to be sensitive or confidential and may not be forwarded or disclosed to
any other party without the permission of the sender.
If you have received this message in error, please notify the sender
Received on Friday, 17 August 2012 11:17:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:01 UTC