Re: lexical resources with n-ary translations

Hi Christian,

Much of this was discussed during the development of the vartrans module,
but I will try to recap:

https://www.w3.org/2016/05/ontolex/#translation

The main way to represent translations is by 'shared reference' that is
using a single concept for entries in multiple languages. The use of an
explicit `Translation` object is only needed when additional information
about the translation needs to be recorded (e.g., a source, a process, a
confidence score). When multiple translations are created by a single
source they can be documented as a `TranslationSet` and the shared
information can be recorded there. in addition, translation can also be
denoted as a simple relation between senses (or even entries).

The use case you mention here is already covered by the `LexicalConcept` as
described in Sec 6.2.1 of the specification.

Regards,
John

Ar Aoine 26 Meith 2020 ag 09:05, scríobh Christian Chiarcos <
christian.chiarcos@web.de>:

> Dear all,
>
> as an afterthought to the discussion on n-ary translations, I can see that
> MT translation tables for more than two languages are somewhat artificial.
> However, (print) dictionaries with more than one target translations are
> actually very common in the technical domain, see
> https://www.springer.com/de/book/9789020116670 as an example. For a
> possible revision of OntoLex core, it might thus be worth considering to
> drop the functional restriction for vartrans:target (but not for
> vartrans:source).
>
> Best,
> Christian
>