varstrans.owl

Dear all,

  and the last email for today. I would like to propose a terminological 
change for the vartrans module.

We had a lot of discussion about the notion of translation a few months 
ago, showing that the notion of translation is indeed quite ambiguous, 
between:

1) the process of translation a source string into a target string
2) the result of this process
3) the relation between two "equivalent" senses in to different languages

I would like to propose a deeper change to the vartrans module, that is 
the one of using "translation" only for the result of translating some 
source string into a target string as an opaque relationin some context, 
under some conditions etc.

If we want to be technically precise and say that there is a relation of 
cross-lingual translational equivalence between two senses, then we 
should use a more technical relation such as "CrossLingualEquivalentSense".

Many people use "translation" as an opaque relation denoting the result 
of translating one string into another and are puzzled by the fact.

If we want to be technically precise and say that translational 
equivalence is a relation between senses and not lexical entries, then 
we should also use a more technical term such as 
"CrossLingualEquivalentSense" and leave the more vague "translation" 
term for the relation between two lexical entries that can be translated 
into reach other in *some* context.

Sorry for opening this discussion again, but I believe it is for the 
robustness and usability of the model to rethink this at least once 
more. It is now the right moment given that I am aiming to finalize the 
vartrans module in the near time.

Opinions?

Philipp.

-- 
--
Prof. Dr. Philipp Cimiano
AG Semantic Computing
Exzellenzcluster für Cognitive Interaction Technology (CITEC)
Universität Bielefeld

Tel: +49 521 106 12249
Fax: +49 521 106 6560
Mail: cimiano@cit-ec.uni-bielefeld.de

Office CITEC-2.307
Universitätsstr. 21-25
33615 Bielefeld, NRW
Germany

Received on Thursday, 31 July 2014 20:11:36 UTC