[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-157) Support for string pattern matching
[ https://issues.oasis-open.org/browse/OSLCCORE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Honey updated OSLCCORE-157:
---------------------------------
Description:
OSLC Query 2.0 does not define any means for a client to query a specified textual property for a partial match, such as "contains", or other string pattern-matching capabilities. I found a number of discussions in Jazz.net forums asking for such a feature. A common requirement is to query for change reqeusts whose summary/title contains a keyword. While oslc.searchTerms provides some means of finding change requests of interest, the result could contain results where text of interest is used in any textaul properties.
RTC appears to allow "*" in a string literal value as a match anything.
GCM supports the use of "%" and "_" in string values and the "=" operator is then implemented using a case-insenstive SQL LIKE.
Since we have a few implementation attempting to address this requirement, I'd like to see such a feature standardized but a MAY rather than a MUST.
The use of "%" and "_" from SQL like is preferable because it is easily implementable on RDB based applications, and can easily be transformed into a SPARQL regular expression for RDF/SPARQL based applications.
was:
OSLC Query 2.0 does not define any means for a client to query a specified textual property for a partial match, such as "contains", or other string pattern-matching capabilities. I found a number of discussions in Jazz.net forums asking for such a feature. A common requirement is to query for change reqeusts whose summary/title contains a keyword. While oslc.searchTerms provides some means of finding change requests of interest, the result could contain results where text of interest is used in any textaul properties.
RTC appears to allow "*" in a string literal value as a match anything.
GCM supports the use of "%" and "_" in string values and the "=" operator is then implemented using a case-insenstive SQL LIKE.
Since we have a few implementation attempting to address this requirement, I'd like to see such a feature standardized but a MAY rather than a MUST.
Proposal: State that a server MAY support pattern matching using the "%" and/or "_" characters with the same semantics as SQL LIKE. If an implementation does not support pattern matching, a server MAY treat "%" and "_" as literal characters.
> Support for string pattern matching
> -----------------------------------
>
> Key: OSLCCORE-157
> URL: https://issues.oasis-open.org/browse/OSLCCORE-157
> Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
> Issue Type: Bug
> Components: Query
> Reporter: David Honey
> Assignee: James Amsden
>
> OSLC Query 2.0 does not define any means for a client to query a specified textual property for a partial match, such as "contains", or other string pattern-matching capabilities. I found a number of discussions in Jazz.net forums asking for such a feature. A common requirement is to query for change reqeusts whose summary/title contains a keyword. While oslc.searchTerms provides some means of finding change requests of interest, the result could contain results where text of interest is used in any textaul properties.
> RTC appears to allow "*" in a string literal value as a match anything.
> GCM supports the use of "%" and "_" in string values and the "=" operator is then implemented using a case-insenstive SQL LIKE.
> Since we have a few implementation attempting to address this requirement, I'd like to see such a feature standardized but a MAY rather than a MUST.
> The use of "%" and "_" from SQL like is preferable because it is easily implementable on RDB based applications, and can easily be transformed into a SPARQL regular expression for RDF/SPARQL based applications.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]