Uploaded image for project: 'OASIS Content Management Interoperability Services (CMIS) TC'
  1. OASIS Content Management Interoperability Services (CMIS) TC
  2. CMIS-762

Clarify the impact of repository specific collation

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: V1.1 Errata
    • Fix Version/s: V1.1 Errata
    • Component/s: Domain Model
    • Labels:
      None
    • Proposal:
      Hide

      I think a note in 2.1.14.2.4.1 something like:

      The collation rules used to evaluate comparison predicates for String properties are repository specific.
      For example, a predicate of the form
      ... where cmis:name LIKE 'a%' ...
      MUST match a cmis:name starting with 'a' and may match a cmis:name starting with 'A'

      Show
      I think a note in 2.1.14.2.4.1 something like: The collation rules used to evaluate comparison predicates for String properties are repository specific. For example, a predicate of the form ... where cmis:name LIKE 'a%' ... MUST match a cmis:name starting with 'a' and may match a cmis:name starting with 'A'

      Description

      The 1.1 specification only mentions repository specific collation with respect to query and ordering - section 2.1.14.2.5

      Repository specific collation may also be expected to affect any string comparison predicates and LIKE.
      (SQL 92 says the behaviour depends on the collation)

      For example, some databases have a default collation which is case-sensitive and others the reverse.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              andy.hind Andy Hind (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: