Re: Bodies translations: use cases and thoughts

I am assuming option 2) is the one you contributed here
http://lists.w3.org/Archives/Public/public-openannotation/2012Nov/0001.html
I don't think the dc:language is compatible with that one.

I was thinking of using dc:language with option 1), especially the second
variant.

However, regarding option 2:
Pro: it is very explicit on what the intent is and very
compact/straightforward in RDF
Cons: the approach requires a new kind of Body in place, cannot model
different provenance (with multiple bodies I could have different
translators)


On Tue, Feb 12, 2013 at 9:28 AM, Antoine Isaac <aisaac@few.vu.nl> wrote:

> Hi Paolo,
>
> OK, this quite clarifies it then: how much is your option 2) compatible
> with the idea of text body in CNT with dc:language?
>
> And further: what would this would say about the potential awkwardness of
> the idea of text body in CNT with dc:language in the first place?
> Because option 2) does look like a very natural alternative for handling
> translations in RDF...
>
> Antoine
>
>
>
>  Hi Antoine,
>> sorry, I have not been clear on that point.
>>
>> <comment-in-english> for me could mean a text body in CNT with
>> dc:language.
>> As specified in the specs in http://www.openannotation.org/**
>> spec/core/core.html#BodyEmbed<http://www.openannotation.org/spec/core/core.html#BodyEmbed>
>>
>> Paolo
>>
>> On Tue, Feb 12, 2013 at 9:18 AM, Antoine Isaac <aisaac@few.vu.nl <mailto:
>> aisaac@few.vu.nl>> wrote:
>>
>>     Hi Paolo,
>>
>>
>>         Additional use cases? Thoughts?
>>
>>
>>
>>     There was also the option of using a custom attribute (e.g.
>> dc:language) on a body-as-resource to indicate this language. This solution
>> (which I didn't like) was addressing a different problem (the one of
>> representing language of a text body represented as a CNT resource). But if
>> people want to use it then there might be a dependency with the options you
>> raise below.
>>
>>     In fact your option 1 would need some of this: right now nothing says
>> you <comment-in-english> is in English, actually. So either the "label" of
>> <comment-in-english> has to be tagged as "en", or you have to use a
>> dedicated property (e.g. dc:language) to create a new statement with
>> <comment-in-english> as subject.
>>
>>     Cheers,
>>
>>     Antoine
>>
>>
>>
>>
>>
>>         Dear all,
>>         now that the new draft of the specs has been published, I would
>> like to discuss further some aspects that have been dropped along the way.
>> One of them is languages and translations.
>>
>>         This is my scenario: I have a textual content written in one
>> language. As curator, I pick an important sentence within that text and I
>> provide, through annotation, the translations in different languages of
>> that particular passage. And it could be even a little more complicated and
>> we might need to keep track of multiple translations for each language
>> performed at different moments in time or by different agents in different
>> moments in time.
>>
>>         Does any other member have use cases about translations?
>>
>>         A couple of solutions have been discussed in previous emails
>> exchanges [1][2][3]:
>>
>>         1) Translations "by oa:Choice". This seems well representing
>> those cases in which we are modeling an actual choice.
>>
>>         _:x a oa:Annotation ;
>>         oa:hasBody <choice1> ;
>>         oa:hasTarget <ny-times-article> .
>>
>>         <choice1> a oa:Choice ;
>>         oa:default<comment-in-french> ;
>>         oa:item<comment-in-english> ;
>>         oa:item<comment-in-spanish> .
>>
>>         However, it does not seem fitting the above use case where all
>> the translations are meant to be provided at the same time.
>>         So I wonder what you think about:
>>
>>         _:x a oa:Annotation ;
>>         oa:motivatedBy blah:translating
>>         oa:hasBody <comment-in-english> ;
>>         oa:hasBody <comment-in-spanish> .
>>         oa:hasTarget <ny-times-article> .
>>
>>         2) Translate "by multilingual body":
>>
>>         _:x a oa:Annotation ;
>>         oa:hasBody <multilingualcomment> ;
>>         oa:hasTarget <ny-times-article> .
>>
>>         <multilingualcomment> rdfs:label "comment-in-french"@fr ;
>>         rdfs:label "comment-in-english"@en ;
>>         rdfs:label "comment-in-spanish"@es .
>>
>>         This could look more explicit, however it introduces a new kind
>> of Body.
>>
>>         Additional use cases? Thoughts?
>>
>>         Best,
>>         Paolo
>>
>>         [1] http://lists.w3.org/Archives/_**
>> _Public/public-openannotation/**__2012Oct/0004.html<http://lists.w3.org/Archives/__Public/public-openannotation/__2012Oct/0004.html><
>> http://lists.w3.org/Archives/**Public/public-openannotation/**
>> 2012Oct/0004.html<http://lists.w3.org/Archives/Public/public-openannotation/2012Oct/0004.html>
>> >
>>         [2] http://lists.w3.org/Archives/_**
>> _Public/public-openannotation/**__2012Nov/0001.html<http://lists.w3.org/Archives/__Public/public-openannotation/__2012Nov/0001.html><
>> http://lists.w3.org/Archives/**Public/public-openannotation/**
>> 2012Nov/0001.html<http://lists.w3.org/Archives/Public/public-openannotation/2012Nov/0001.html>
>> >
>>         [3] http://lists.w3.org/Archives/_**
>> _Public/public-openannotation/**__2012Nov/0006.html<http://lists.w3.org/Archives/__Public/public-openannotation/__2012Nov/0006.html><
>> http://lists.w3.org/Archives/**Public/public-openannotation/**
>> 2012Nov/0006.html<http://lists.w3.org/Archives/Public/public-openannotation/2012Nov/0006.html>
>> >
>>
>>
>>         --
>>         Dr. Paolo Ciccarese
>>         http://www.paolociccarese.__**info/ <http://www.paolociccarese.**
>> info/ <http://www.paolociccarese.info/>>
>>
>>         Biomedical Informatics Research & Development
>>         Instructor of Neurology at Harvard Medical School
>>         Assistant in Neuroscience at Mass General Hospital
>>         Member of the MGH Biomedical Informatics Core
>>         +1-857-366-1524 <tel:%2B1-857-366-1524> (mobile) +1-617-768-8744<tel:%2B1-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 immediately.
>>
>>
>>
>>
>>
>>
>> --
>> Dr. Paolo Ciccarese
>> http://www.paolociccarese.**info/ <http://www.paolociccarese.info/>
>> Biomedical Informatics Research & Development
>> Instructor of Neurology at Harvard Medical School
>> Assistant in Neuroscience at Mass General Hospital
>> Member of the MGH Biomedical Informatics Core
>> +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
>> immediately.
>>
>
>
>


-- 
Dr. Paolo Ciccarese
http://www.paolociccarese.info/
Biomedical Informatics Research & Development
Instructor of Neurology at Harvard Medical School
Assistant in Neuroscience at Mass General Hospital
Member of the MGH Biomedical Informatics Core
+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
immediately.

Received on Tuesday, 12 February 2013 14:42:34 UTC