cmis:changeToken should not be mandatory if the repository doesn't support change tokens

XMLWordPrintable

    • Type: Bug
    • Resolution: Applied
    • Priority: Major
    • V1.0 Errata
    • Affects Version/s: None
    • Component/s: Domain Model
    • None
    • Hide

      Sections 2.1.4.3.3, 2.1.5.4.2, 2.1.6.1.3, 2.1.7.1.2:
      "Repository MUST return this property with non-empty values when an object is requested and the property filter does not exclude them. If the repository does not support change tokens, this property SHOULD not be set."

      Show
      Sections 2.1.4.3.3, 2.1.5.4.2, 2.1.6.1.3, 2.1.7.1.2: "Repository MUST return this property with non-empty values when an object is requested and the property filter does not exclude them. If the repository does not support change tokens, this property SHOULD not be set."

      The spec says about cmis:changeToken: "Repository MUST return this property with non-empty values when an object is requested and the property filter does not exclude them"
      If a repository does not support change tokens, it should not be forced to return an artificial string.

      It also conflicts with section 2.2.1.3:
      "If a Repository provides values for the ChangeToken property for an Object, then..."

            Assignee:
            Florian Müller (Inactive)
            Reporter:
            Florian Müller (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: