OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


     [ 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 specification should be persistence technology agnostic.

The problem is that for string properties (and for URIs - see https://issues.oasis-open.org/browse/OSLCCORE-153), querying for ">", ">=", "<", and "<=" may be unimplementable, or the ordering might be determined by an RDB vendor and different from the SPARQL spec. For example, string order might be based on locale-dependent Collators that are often case insensitive.

  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). "

This potentially makes the spec unimplementable on RDB based applications that probably form the vast majority of implementations. The specification should be persistence technology agnostic.

The problem is that for string properties (and for URIs - see , 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 specification should be persistence technology agnostic.
> The problem is that for string properties (and for URIs - see https://issues.oasis-open.org/browse/OSLCCORE-153), querying for ">", ">=", "<", and "<=" may be unimplementable, or the ordering might be determined by an RDB vendor and different from the SPARQL spec. For example, string order might be based on locale-dependent Collators that are often case insensitive.



--
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]