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

3.4.1.3 createDocument exceptions and 3.4.2.3 createDocumentFromSource versioningState param needs clarification

    XMLWordPrintable

    Details

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

      Remove statement from 2.9.6. For the versioningState parameter, the repository will ignore its value for a non-versionable object.

      Show
      Remove statement from 2.9.6. For the versioningState parameter, the repository will ignore its value for a non-versionable object.
    • Resolution:
      Hide

      FIxed for createDocument, missed for createDocumentFromSource

      Show
      FIxed for createDocument, missed for createDocumentFromSource

      Description

      The versioningState parameter is optional and defaults to "major". However, for non-versionable object types, it is required to be "none", which makes versioningState a required parameter in this case. This makes no sense. Proposal - make the default major for versionable documents, none for non-versionable. Or make the parameter not allowed at all for non-versionable.

      Note also that 2.9.6 says that repos which do not support versioning "MAY create new Document objects in a Major Version state". If this is so, why is the versioningState param not allowed to be "major"?

        Attachments

          Activity

            People

            • Assignee:
              ryan.mcveigh Ryan McVeigh (Inactive)
              Reporter:
              ryan.mcveigh Ryan McVeigh (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: