You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an idea for the implementation of MWEs in ParlaMint. We use <linkGrp> and <link> for annotating the relation between pairs of words. It is not possible to use it in MWEs' situation.
I am not sure if this is the best solution and which variant from-to/targer I prefer. This is just the first draft (I am planning to use MWEs in another project, so I am raring to know the ParlaMint solution, so I will be able to reuse it)
The text was updated successfully, but these errors were encountered:
Do we actually need MWEs in ParlaMint? For what exactly?
We annotate MWEs in some Slovene corpora (http://hdl.handle.net/11356/1434), where we simply used linkGrp/link. The definition is "an association or hypertextual link among elements" which seems appropriate. But also note that the reason we used links is that (our) MWEs need not always involve adjecent words, i.e. they can have gaps which then forces you to list the tokens explicitly.
But if the MWE words are always contiguous then why not follow Parla-CLARIN which suggest using in-place <seg> elements?
TomazErjavec
changed the title
specification: MWEs in ParlaMint
Specification: MWEs in ParlaMint
May 23, 2022
related to: #204
I have an idea for the implementation of MWEs in ParlaMint. We use
<linkGrp>
and<link>
for annotating the relation between pairs of words. It is not possible to use it in MWEs' situation.I am suggesting to use
<spanGrp>
and<span>
. 17.3 Spans and InterpretationsIf I correctly understand TEI documentation, there is another solution to how to encode span:
I am not sure if this is the best solution and which variant
from-to
/targer
I prefer. This is just the first draft (I am planning to use MWEs in another project, so I am raring to know the ParlaMint solution, so I will be able to reuse it)The text was updated successfully, but these errors were encountered: