Closed jnothman closed 9 years ago
Ignore crossing mentions by default, or nested mentions?
On Mon, Nov 10, 2014 at 12:23 AM, jnothman notifications@github.com wrote:
This raises an error upon duplicate mentions. It also warns on nested or crossing mentions.
This is somewhat flexible in its handling, but no interface is provided to affect that setting.
Should we ignore crossing mentions by default so that it's silent when
processing TAC?
You can merge this Pull Request by running
git pull https://github.com/wikilinks/neleval fix6
Or view, comment on, or merge it at:
https://github.com/wikilinks/neleval/pull/10 Commit Summary
- Add data validation
File Changes
- M neleval/annotation.py https://github.com/wikilinks/neleval/pull/10/files#diff-0 (14)
- M neleval/document.py https://github.com/wikilinks/neleval/pull/10/files#diff-1 (43)
- M neleval/test.py https://github.com/wikilinks/neleval/pull/10/files#diff-2 (50)
Patch Links:
- https://github.com/wikilinks/neleval/pull/10.patch
- https://github.com/wikilinks/neleval/pull/10.diff
— Reply to this email directly or view it on GitHub https://github.com/wikilinks/neleval/pull/10.
Dr Ben Hachey benhachey.info +61 416 550 174
Nested ;)
OK. Agreed it should be silent for annotations that are valid according to the TAC spec. But good to have a flag to request warnings for nested mentions.
On Mon, Nov 10, 2014 at 10:46 AM, jnothman notifications@github.com wrote:
Nested ;)
— Reply to this email directly or view it on GitHub https://github.com/wikilinks/neleval/pull/10#issuecomment-62325995.
Dr Ben Hachey benhachey.info +61 416 550 174
Merging.
Fixes #6. This raises an error upon duplicate mentions. It also warns on nested or crossing mentions.
This is somewhat flexible in its handling, but no interface is provided to affect that setting.
Should we ignore crossing mentions by default so that it's silent when processing TAC?