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
In ParlaCAP sentiment scores and labels will be added to sentences and utterances and this issue serves to document the needed changes:
how to encode sentiment
changes to the schema and documentation
changes to the conversion programs
changes to the registry files
Note that I have made a new milestone ParlaCAP (and assigned this issue to it) which should be used for issues pertaining to the project.
The debate here should be releveant to @matyaskopp, @katjameden, @nljubesi.
The text was updated successfully, but these errors were encountered:
For SI we have already added sentiment to <u> and <s> as well as modifying the schema and conversion to vertical file + adding a new sentiment taxonomy, currently local to SI (this is a draft and might well change, esp. the description part).
In short:
the sentiment label is encoded in u/@ana and s/@ana, and makes reference to the sentiment taxonomy and uses the extended prefix senti.
the sentiment score is encoded in u/@n and s/@n; this is not a very good solution, as @n is a very general attribute but I currently do not have a better idea how to preserve the score in the encoding.
The documentation and other conversions (in particular, to TSV) still need to be implemented.
The problem right now is that I've added the new taxonomy to all the relevant programs that deal with taxonomies but now the CI validation complains that this taxonomy is missing from all the corpora (except SI). @matyaskopp, how best to solve this? Make (somehow) the taxonomy optional or (manually) insert the taxonomy, it's XInclude and prefixDef into all the samples? Or something else?
In ParlaCAP sentiment scores and labels will be added to sentences and utterances and this issue serves to document the needed changes:
Note that I have made a new milestone ParlaCAP (and assigned this issue to it) which should be used for issues pertaining to the project.
The debate here should be releveant to @matyaskopp, @katjameden, @nljubesi.
The text was updated successfully, but these errors were encountered: