[
https://issues.apache.org/jira/browse/CTAKES-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586213#comment-13586213
]
James Joseph Masanz commented on CTAKES-170:
--------------------------------------------
Troy,
I think we should show ctakes-relation-extractor in the component descriptor
diagram as dependent on Constituency Parser (as a sibling of Coref-Resolver).
Note for right now at least relation extractor, within
RelationExtractorAggregate.xml, does reference a couple analysis engine
descriptors from ctakes-clinical-pipeline, such as
<delegateAnalysisEngine key="ExtractionPrepAnnotator">
<import
location="../../../ctakes-clinical-pipeline/desc/analysis_engine/ExtractionPrepAnnotator.xml"/>
</delegateAnalysisEngine>
See http://s.apache.org/trunk-RelationExtractorAggregate.xml
And the class for that annotator is within package
org.apache.ctakes.clinicalpipeline.ae
Also, it's a little messy as far as the diagram because it looks like
relation-extractor is using StatusAnnotator and NegationAnnotator instead of
AssertionAnnotator.
I just created JIRA issue CTAKES-172 "relation-extractor is using
StatusAnnotator and NegationAnnotator instead of AssertionAnnotator"
Regards,
James Masanz
> relation extractor has dependency on clinical pipeilne
> ------------------------------------------------------
>
> Key: CTAKES-170
> URL: https://issues.apache.org/jira/browse/CTAKES-170
> Project: cTAKES
> Issue Type: Bug
> Reporter: Tim Miller
> Assignee: Dmitriy Dligach
> Priority: Minor
>
> dependency should go in the other direction if it is necessary at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
