Re: Bodies translations: use cases and thoughts

That is a good point. So if we have same target and a motivation such as
'oa:translating' or similar we can infer the relationship.

On Tue, Feb 12, 2013 at 2:33 PM, Bernhard Haslhofer <
bernhard.haslhofer@univie.ac.at> wrote:

> they all have the same target (the translated piece of text), so they are
> related implicitly. Or did I miss something?
>
>
> On Tuesday, February 12, 2013 at 8:51 AM, Paolo Ciccarese wrote:
>
> > Hi Bernard,
> > I agree, that could be a good approach especially when provenance for
> each translation is different.
> > We would have multiple annotation objects but then we would need a way
> to relate them.
> > That way does not have necessarily part of OA though.
> >
> > I guess I could say it at the annotation level
> > <ann1> translationof <ann2>
> > or at the body level
> > <body1> translationof <body2>
> >
> > On Tue, Feb 12, 2013 at 9:45 AM, Bernhard Haslhofer <
> bernhard.haslhofer@univie.ac.at (mailto:bernhard.haslhofer@univie.ac.at)>
> wrote:
> > > Hi Paolo,
> > >
> > > my straight-forward approach would be to create one annotation per
> translation, each having the same target (the translated piece of text) but
> different bodies (the translations). Then you can assign different times
> (and possibly) agents to each annotation and maybe also make the motivation
> "translation" explicit.
> > >
> > > To indicate the language of the body I would use RDF's language tag
> with the body label.
> > > This of course doesn't work if all translations were created at the
> same moment in time; but I guess this doesn't happen too often in the real
> world, does it?
> > >
> > > Bernhard
> > >
> > >
> > > On Tuesday, February 12, 2013 at 8:09 AM, Paolo Ciccarese wrote:
> > >
> > > > 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
> > > > [2]
> http://lists.w3.org/Archives/Public/public-openannotation/2012Nov/0001.html
> > > > [3]
> http://lists.w3.org/Archives/Public/public-openannotation/2012Nov/0006.html
> > > >
> > > >
> >
>