[OASIS Issue Tracker] (OSLCCORE-111) Query spec and relative operators for string literals

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/OSLCCORE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Honey updated OSLCCORE-111:
---------------------------------

    Description: 
https://open-services.net/bin/view/Main/OSLCCoreSpecQuery says for comparison_op:

"Semantics of datatypes and operations on these datatypes MUST work as defined in the SPARQL Query Language (reference: SPARQL). "

This potentially makes the spec unimplementable on RDB based applications that probably form the vast majority of implementations.

The problem is that for string properties, querying for ">", ">=", "<", and "<=" may be unimplementable, or the ordering might be determined by an RDB vendor and different from the SPARQL spec. The spec places too high a burden, and assumes an RDF persistence layer, on implementations. For example, some RDB vendors might use Locale-specific collators.

  was:
https://open-services.net/bin/view/Main/OSLCCoreSpecQuery says for comparison_op:

"Semantics of datatypes and operations on these datatypes MUST work as defined in the SPARQL Query Language (reference: SPARQL). "

The problem is that for string properties, querying for ">", ">=", "<", and "<=" may be unimplementable, or the ordering might be determined by an RDB vendor and different from the SPARQL spec. The spec places too high a burden, and assumes an RDF persistence layer, on implementations. For example, some RDB vendors might use Locale-specific collators.


> Query spec and relative operators for string literals
> -----------------------------------------------------
>
>                 Key: OSLCCORE-111
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-111
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> https://open-services.net/bin/view/Main/OSLCCoreSpecQuery says for comparison_op:
> "Semantics of datatypes and operations on these datatypes MUST work as defined in the SPARQL Query Language (reference: SPARQL). "
> This potentially makes the spec unimplementable on RDB based applications that probably form the vast majority of implementations.
> The problem is that for string properties, querying for ">", ">=", "<", and "<=" may be unimplementable, or the ordering might be determined by an RDB vendor and different from the SPARQL spec. The spec places too high a burden, and assumes an RDF persistence layer, on implementations. For example, some RDB vendors might use Locale-specific collators.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)