Once more, let's look into how we can support discontinuity in DKPro Core.
For a start, I suggest that we implement a common practice of how discontinuity should be represented: a pattern:
- a common type which represents the "fragments" that go beyond the first element of the discontinuous annotation, e.g.
Fragment
- a common feature on a annotation type that holds the additional fragments, e.g.
fragments Array of Fragment
First case for us to implement would be adding the fragments feature to SemPred and SemArg and allow TigerXML reader to read discontinuous semantic annotations.
Any comments?
Once more, let's look into how we can support discontinuity in DKPro Core.
For a start, I suggest that we implement a common practice of how discontinuity should be represented: a pattern:
Fragmentfragments Array of FragmentFirst case for us to implement would be adding the
fragmentsfeature to SemPred and SemArg and allow TigerXML reader to read discontinuous semantic annotations.Any comments?