You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2008/01/30 03:19:49 UTC
[jira] Created: (UIMA-730) Fix definition of containsType/Feature
for Resut Spec for corner case involving x-unspecified language
Fix definition of containsType/Feature for Resut Spec for corner case involving x-unspecified language
------------------------------------------------------------------------------------------------------
Key: UIMA-730
URL: https://issues.apache.org/jira/browse/UIMA-730
Project: UIMA
Issue Type: Bug
Reporter: Marshall Schor
Based on a long discussion in uima-dev, we conclude that containsType(aType) should be equivalent to containsType(aType, "x-unspecified"), and should return false if the result spec has an entry for aType with languages that do *not* include x-unspecified.
This was broken in previous implementations, but should not affect users (except for some corner cases where uses had improperly specified their capability specifications, perhaps).
With this change, the function of CapabilityContainer as used in the framework is equivalent to that provided by the Result Specification. Remove CapabilityContainer and switch usage of it to the Result Spec, for space/time efficiency reasons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-730) Fix definition of containsType/Feature
for Resut Spec for corner case involving x-unspecified language
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor resolved UIMA-730.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.3
> Fix definition of containsType/Feature for Resut Spec for corner case involving x-unspecified language
> ------------------------------------------------------------------------------------------------------
>
> Key: UIMA-730
> URL: https://issues.apache.org/jira/browse/UIMA-730
> Project: UIMA
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Marshall Schor
> Fix For: 2.3
>
>
> Based on a long discussion in uima-dev, we conclude that containsType(aType) should be equivalent to containsType(aType, "x-unspecified"), and should return false if the result spec has an entry for aType with languages that do *not* include x-unspecified.
> This was broken in previous implementations, but should not affect users (except for some corner cases where uses had improperly specified their capability specifications, perhaps).
> With this change, the function of CapabilityContainer as used in the framework is equivalent to that provided by the Result Specification. Remove CapabilityContainer and switch usage of it to the Result Spec, for space/time efficiency reasons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-730) Fix definition of containsType/Feature
for Resut Spec for corner case involving x-unspecified language
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-730:
--------------------------------
Affects Version/s: 2.2.1
> Fix definition of containsType/Feature for Resut Spec for corner case involving x-unspecified language
> ------------------------------------------------------------------------------------------------------
>
> Key: UIMA-730
> URL: https://issues.apache.org/jira/browse/UIMA-730
> Project: UIMA
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.3
>
>
> Based on a long discussion in uima-dev, we conclude that containsType(aType) should be equivalent to containsType(aType, "x-unspecified"), and should return false if the result spec has an entry for aType with languages that do *not* include x-unspecified.
> This was broken in previous implementations, but should not affect users (except for some corner cases where uses had improperly specified their capability specifications, perhaps).
> With this change, the function of CapabilityContainer as used in the framework is equivalent to that provided by the Result Specification. Remove CapabilityContainer and switch usage of it to the Result Spec, for space/time efficiency reasons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-730) Fix definition of containsType/Feature
for Resut Spec for corner case involving x-unspecified language
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-730.
-------------------------------
opened new jira to capture remaining cleanup work still to be done on this (removing unused CapabilityContainer class
> Fix definition of containsType/Feature for Resut Spec for corner case involving x-unspecified language
> ------------------------------------------------------------------------------------------------------
>
> Key: UIMA-730
> URL: https://issues.apache.org/jira/browse/UIMA-730
> Project: UIMA
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.2.2
>
>
> Based on a long discussion in uima-dev, we conclude that containsType(aType) should be equivalent to containsType(aType, "x-unspecified"), and should return false if the result spec has an entry for aType with languages that do *not* include x-unspecified.
> This was broken in previous implementations, but should not affect users (except for some corner cases where uses had improperly specified their capability specifications, perhaps).
> With this change, the function of CapabilityContainer as used in the framework is equivalent to that provided by the Result Specification. Remove CapabilityContainer and switch usage of it to the Result Spec, for space/time efficiency reasons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-730) Fix definition of containsType/Feature
for Resut Spec for corner case involving x-unspecified language
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor reassigned UIMA-730:
-----------------------------------
Assignee: Marshall Schor
> Fix definition of containsType/Feature for Resut Spec for corner case involving x-unspecified language
> ------------------------------------------------------------------------------------------------------
>
> Key: UIMA-730
> URL: https://issues.apache.org/jira/browse/UIMA-730
> Project: UIMA
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.3
>
>
> Based on a long discussion in uima-dev, we conclude that containsType(aType) should be equivalent to containsType(aType, "x-unspecified"), and should return false if the result spec has an entry for aType with languages that do *not* include x-unspecified.
> This was broken in previous implementations, but should not affect users (except for some corner cases where uses had improperly specified their capability specifications, perhaps).
> With this change, the function of CapabilityContainer as used in the framework is equivalent to that provided by the Result Specification. Remove CapabilityContainer and switch usage of it to the Result Spec, for space/time efficiency reasons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.