You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2012/04/27 09:42:55 UTC
[jira] [Created] (STANBOL-595) Add support for ValueConstraints
with multiple values
Rupert Westenthaler created STANBOL-595:
-------------------------------------------
Summary: Add support for ValueConstraints with multiple values
Key: STANBOL-595
URL: https://issues.apache.org/jira/browse/STANBOL-595
Project: Stanbol
Issue Type: Improvement
Components: Entity Hub
Reporter: Rupert Westenthaler
Assignee: Rupert Westenthaler
Priority: Minor
Fix For: 0.10.0-incubating
ValueConstraints as used by the FIeldQuery of the Entityhub currently support only a single value. This is also true for ReferenceConstraint as this internally uses ValueConstraint and only sets the data type to URIs.
This will allow to query for Resources that do have any of the parsed values (e.g. searching for Entityies of rdf:type dbpedia-ont:Person or dbpedia-ont:Place)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (STANBOL-595) Add support for ValueConstraints
with multiple values
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-595.
-----------------------------------------
Resolution: Fixed
fixed with revision #1334950
> Add support for ValueConstraints with multiple values
> -----------------------------------------------------
>
> Key: STANBOL-595
> URL: https://issues.apache.org/jira/browse/STANBOL-595
> Project: Stanbol
> Issue Type: Improvement
> Components: Entity Hub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
> Fix For: 0.10.0-incubating
>
>
> ValueConstraints as used by the FIeldQuery of the Entityhub currently support only a single value. This is also true for ReferenceConstraint as this internally uses ValueConstraint and only sets the data type to URIs.
> This will allow to query for Resources that do have any of the parsed values (e.g. searching for Entityies of rdf:type dbpedia-ont:Person or dbpedia-ont:Place)
> In addition the new "mode" parameter will allow to treat multiple values as "any" (at least one) or "all". The default will be "any"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (STANBOL-595) Add support for ValueConstraints
with multiple values
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler updated STANBOL-595:
----------------------------------------
Description:
ValueConstraints as used by the FIeldQuery of the Entityhub currently support only a single value. This is also true for ReferenceConstraint as this internally uses ValueConstraint and only sets the data type to URIs.
This will allow to query for Resources that do have any of the parsed values (e.g. searching for Entityies of rdf:type dbpedia-ont:Person or dbpedia-ont:Place)
In addition the new "mode" parameter will allow to treat multiple values as "any" (at least one) or "all". The default will be "any"
was:
ValueConstraints as used by the FIeldQuery of the Entityhub currently support only a single value. This is also true for ReferenceConstraint as this internally uses ValueConstraint and only sets the data type to URIs.
This will allow to query for Resources that do have any of the parsed values (e.g. searching for Entityies of rdf:type dbpedia-ont:Person or dbpedia-ont:Place)
> Add support for ValueConstraints with multiple values
> -----------------------------------------------------
>
> Key: STANBOL-595
> URL: https://issues.apache.org/jira/browse/STANBOL-595
> Project: Stanbol
> Issue Type: Improvement
> Components: Entity Hub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
> Fix For: 0.10.0-incubating
>
>
> ValueConstraints as used by the FIeldQuery of the Entityhub currently support only a single value. This is also true for ReferenceConstraint as this internally uses ValueConstraint and only sets the data type to URIs.
> This will allow to query for Resources that do have any of the parsed values (e.g. searching for Entityies of rdf:type dbpedia-ont:Person or dbpedia-ont:Place)
> In addition the new "mode" parameter will allow to treat multiple values as "any" (at least one) or "all". The default will be "any"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (STANBOL-595) Add support for ValueConstraints
with multiple values
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-595.
-----------------------------------------
Resolution: Fixed
implemented with #1333433
> Add support for ValueConstraints with multiple values
> -----------------------------------------------------
>
> Key: STANBOL-595
> URL: https://issues.apache.org/jira/browse/STANBOL-595
> Project: Stanbol
> Issue Type: Improvement
> Components: Entity Hub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
> Fix For: 0.10.0-incubating
>
>
> ValueConstraints as used by the FIeldQuery of the Entityhub currently support only a single value. This is also true for ReferenceConstraint as this internally uses ValueConstraint and only sets the data type to URIs.
> This will allow to query for Resources that do have any of the parsed values (e.g. searching for Entityies of rdf:type dbpedia-ont:Person or dbpedia-ont:Place)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (STANBOL-595) Add support for ValueConstraints
with multiple values
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler reopened STANBOL-595:
-----------------------------------------
Reopen to add the feature to treat multiple features as OPTIONAL or REQUIRED. The default should be optional
> Add support for ValueConstraints with multiple values
> -----------------------------------------------------
>
> Key: STANBOL-595
> URL: https://issues.apache.org/jira/browse/STANBOL-595
> Project: Stanbol
> Issue Type: Improvement
> Components: Entity Hub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
> Fix For: 0.10.0-incubating
>
>
> ValueConstraints as used by the FIeldQuery of the Entityhub currently support only a single value. This is also true for ReferenceConstraint as this internally uses ValueConstraint and only sets the data type to URIs.
> This will allow to query for Resources that do have any of the parsed values (e.g. searching for Entityies of rdf:type dbpedia-ont:Person or dbpedia-ont:Place)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira