-
Notifications
You must be signed in to change notification settings - Fork 0
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
Adding Events and Times #56
Comments
I think TimeExpression is better, but it’s kinda long.
… On Jun 6, 2017, at 12:46 PM, marcverhagen ***@***.***> wrote:
It is probably not very controversial to use Event here and we could go with the TimeML attributes. My hunch would be to not add things like Process and State as subtypes, but deal with them in the same way as we deal with kinds of NamedEntities.
As for times, Is it okay to use Timex or does that get us to close to Timex2 and Timex3 and is something more generic like TimeExpression better?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#56>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD7Nv-81zSV_nGeS-NJjzSMJ24BiZ7cUks5sBYJLgaJpZM4Nxnc4>.
-----------------------------------------------------
Nancy Ide
Professor of Computer Science
Department of Computer Science
Vassar College
Poughkeepsie, New York 12604-0520
USA
tel: (+1 845) 437 5988
fax: (+1 845) 437 7498
email: [email protected]
http://www.cs.vassar.edu/~ide
-----------------------------------------------------
|
Still much shorter than DependencyStructure so there is precedent. |
I like the brevity of |
Bump. I notice this is marked with milestone 1.3.0 which is the next version of the vocabulary to be released. I don't think there is anything controversial here so we should just go ahead and do it. To backtrack on my above comment, I think we should use |
How about |
It is probably not very controversial to use Event here and we could go with the TimeML attributes. My hunch would be to not add things like Process and State as subtypes, but deal with them in the same way as we deal with kinds of NamedEntities.
As for times, is it okay to use Timex or does that get us to close to Timex2 and Timex3 and is something more generic like TimeExpression better?
The text was updated successfully, but these errors were encountered: