-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Optional) tone enhancement #2
Comments
This could be a diverting question, but why not just attach the human-readable conversion as a free text elaboration? This would give more flexibility in the future and would let more nuanced conversions be reflected. |
@brandomr this issue might be stale, both because per the meeting on July 20th, it makes more sense to just add tone tokens, and also per Jataware's update at the more recent meeting that you might not be including tone at all in upcoming data collection. |
@ezubaric My understanding is that the tokens are handy for those of us who are not interested in NLU from human-readable to DAIDE. Is this issue still active? |
It seems like given Jataware is not gathering tone at all, while a free text field would be more consistent with their current plan for data collection. |
What functionality will your new tokens add?
By providing optional tonal modifiers to DAIDE statements DAIDE can be made more expressive and closer aligned to human language. Invariably in real negotiations, tone is conveyed either mechanistically through verbal intonation, through word selection, or a combination of the two. The proposed modifiers support the latter.
Describe the precise changes you'd like
Currently we support the following tones:
Objective
Hostile
Friendly
Fearful
Confident
Empathetic
Upset
In our version of the game engine these are not treated as additional tokens in DAIDE but rather external modifiers. For example:
would be modified by one of the tones. This could be embedded into DAIDE itself:
or these tones could be treated separately altogether.
Additional context
From Jataware's standpoint tones should be ignored by teams that do not wish to support them, but if others are interested in using them we should have a broader discussion about whether this should be included as an addendum to DAIDE or whether we should treat tone separately (as we do currently).
For reference, our module that converts DAIDE + tone to human language can be found here.
The text was updated successfully, but these errors were encountered: