-
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
add clause_type to resolved graid #3
Comments
Do you have GRAID annotated data - as in https://multicast.aspra.uni-bamberg.de/ ? I so, how did you end up storing the GRAID tier? Just as another column in ExampleTable? I was looking into converting multicast into CLDF at one point, and that's what I did. But considering that GRAID encodes relations, one could think of supporting GRAID via validation rules in pycldf or similar. |
I meant to reach out to you regarding this. What I ended up doing was to store tab-aligned GRAID annotations in a column. Problem: this will require "empty" items on the other aligned tiers (zero reference, maybe some stuff with clause boundaries IIRC?). So it hasn't made it into the CLDF dataset yet. I've also created a library for parsing graid annotations. That way, I can explode a tab-aligned text with a GRAID column into a table where lines are words (+ their graid data) or clauses. |
If I find time, I'll give pygraid a go. Did you already try it with all of the multicast corpora? |
No, I haven't and I think there will be issues. I haven't seen an explicit specification for the format, and the MC corpora I looked at had annotations that should be illegal according to the graid manual. Have you worked with the R package? |
No description provided.
The text was updated successfully, but these errors were encountered: