-
Notifications
You must be signed in to change notification settings - Fork 67
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
BratReader does not support N1 Reference tags #1391
Comments
So far, normalizations ( |
Any plans to add them?
Btw we noticed that you guys released the fix we sent you last month thx.
I started the process for getting the paperwork done to allow us to
contribute to dkpdo. So if you give me an idea of how to go about adding
support for reference brat lines into the Brat reader and writer we can
implement it.
Le dim. 7 juil. 2019 à 06:03, Richard Eckart de Castilho <
[email protected]> a écrit :
… So far, normalizations (N) are not supported by the BratReader/BratWriter
in DKPro Core.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1391?email_source=notifications&email_token=AAIMA4BBAIFAHXSKRB3PQDTP6G5PFA5CNFSM4H6UMP3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZLIM6I#issuecomment-508987001>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIMA4FEGIRQVAGRBXYBBJ3P6G5PFANCNFSM4H6UMP3A>
.
|
On Sun, Jul 7, 2019 at 6:42 AM Alain Désilets ***@***.***> wrote:
So if you give me an idea of how to go about adding support for reference
brat lines into the Brat reader and writer we can implement it.
Also:
- Are there coding guidelines to follow?
- Are there unit tests for BratReader and BratWriter to be updated?
|
The contribution guidelines include links to coding convention templates. Yes, there are unit tests for the brat module. If I understand it correctly, then the normalization annotations in brat are essentially like attributes. The BratReader could probably just treat them as String attributes. The BratWriter would need some way of configuring which attributes should be rendered as normalization attributes instead of regular attributes. |
Thx.
Le lun. 8 juil. 2019 à 05:46, Richard Eckart de Castilho <
[email protected]> a écrit :
… The contribution guidelines <https://dkpro.github.io/contributing/>
include links to coding convention templates.
Yes, there are unit tests for the brat module.
If I understand it correctly, then the normalization annotations in brat
are essentially like attributes. The BratReader could probably just treat
them as String attributes. The BratWriter would need some way of
configuring which attributes should be rendered as normalization attributes
instead of regular attributes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1391?email_source=notifications&email_token=AAIMA4FDLTBX6QXDXN4UVWTP6MEIDA5CNFSM4H6UMP3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZMSCUI#issuecomment-509157713>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIMA4BSLBBKDPCWCYVJBZ3P6MEIDANCNFSM4H6UMP3A>
.
|
If you run ReadBrat.java in the attached Maven project, you get this errror:
Yet, the annotation in question is perfectly valid, according to the brat format specification:
https://brat.nlplab.org/standoff.html
I should point out that we are encountering this problem because we are using BratReader to read some files that were previously annotated by MetamapLite, and that tool makes use of the Reference line in the .ann files.
The text was updated successfully, but these errors were encountered: