El 2020-06-15 17:13, Xavi Ivars escribió:
Missatge de Francis Tyers <fty...@prompsit.com> del dia dl., 15 de
juny 2020 a les 17:26:

[...]

And pass it to the lexical selection module which will choose the
one with the highest weight.

This would mean a new module, but it would require only minor
changes to the bilingual dictionary and lexical selection, and
wouldn't have any effect on transfer.
[...]

The difference between your approach and mine is that your proposal is
extremely coupled to the order of the modules in the pipeline. The new
module would write <2.0> and apertium-lex-tools would need to read and
remove it from the pipeline.

Doing that part is really trivial.

Ideally, I'd like to decouple setting the "domain" of a word from
using it. If something just after tagger, still as part of the
"analysis" phase of the translation, puts that information in there,
then it can be used by "lex-tools", but also by other modules that may
need it. If we don't do this, multiple modules may need to read the
"domain list" data to assign the right domain to a given word.

What are the other cases aside from lexical selection where the domain
list would be required? Are there examples of needing to do
morphological disambiguation or transfer differently depending on semantic
domain?

And if this information might help in disambiguation or transfer, would it help substantially over implementing, e.g. word embeddings for the tagger
and lexical selection?

When I wrote the lexical selection component, I looked into doing
word-sense disambiguation on the source side. I didn't find any evidence
that it would substantially increase translation performance, e.g.
doing WSD without reference to the target language is usually more
trouble than it is worth. Although I'm open to being convinced,
with evidence...

Just because we "can" add information, does not mean we "should".

Fran


_______________________________________________
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Reply via email to