-
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
Official name and project dir for "rfb" project #57
Comments
Additional Context==== One of the main questions is which are positive cases (we want to annotate), vs negative cases (we don't care about this). For instance, is the concept to extract all the information as related to useful metadata even when it doesn't occur as a role-filler key-value type pair... (eg. Copyright information, "Produced in collaboration with Winnifred Touhey Studio and Studio Ghibli" & "Special Thanks To: John Singleton and Studio Ghibli") @owencking We may bring this up in a meeting either before or on 10/11 Wed if we are able to find enough cases where both Annotation team and Dev team don't have answers. |
During verbal meeting today, the "Role Filler Binding" name was discussed and chosen. Needs wanted by GBH for metadata extraction were clarified. Difficulties of the rfb pair data structure were discussed, however, were found sufficient for the task at hand for now, noting that there are some instances still there it may be difficult to match text phenomenon to this pairing scheme. |
New Feature Summary
(For the record, the current used name is "role-filler-binding/rfb" annotation project. It has also been called "OCR" or "creditparsing" or "kvparsing", or something related to the word "structure".)
Related
No response
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: