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

Type Id vs Query Name confusion

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Domain Model, REST/AtomPub Binding
    • Labels:
      None
    • Proposal:
      Hide

      Part I...

      1) 2.7.2.1 Attributes common to all Object-Type Definitions
      a) keep type name
      b) remove baseType
      c) add baseTypeName; whose value is one of Document, Folder, Relationship, Policy
      d) remove baseTypeQueryName
      e) rename parentId to parentTypeId
      e) remove id from type

      Show
      Part I... 1) 2.7.2.1 Attributes common to all Object-Type Definitions a) keep type name b) remove baseType c) add baseTypeName; whose value is one of Document, Folder, Relationship, Policy d) remove baseTypeQueryName e) rename parentId to parentTypeId e) remove id from type

      Description

      The definition of type ids and query names is disjoint between part I and part II of the spec.

      As I understand there are six concepts:

      • ObjectTypeId (value is repo specific)
      • ParentTypeId
      • BaseObjectTypeId
      • ObjectTypeQueryName (spec defines values for root types e.g. Document, Folder, ...)
      • ParentTypeQueryName
      • BaseTypeQueryName

      However, part I of the spec does not define properties for all above even though part II defines a serialization mapping for them e.g. base type id.

      I would like to see the spec (Part I) also define well known ObjectTypeId values for root types. This would then allow Object Type Definition to support following attributes:

      • ObjectTypeId
      • ParentTypeId
      • BaseTypeId
      • TypeQueryName

      And Base Object Type to support the following properties

      • ObjectTypeId
      • BaseTypeId

      Part 2 is then a direct serialization of above. This means Query Name must be retrieved via Type Definition (I think that's ok, as it's generally used to drive query builders). However cmis:object provides its actual type id and a known base type id that can be switched on by a client (e.g. split between item and container) without requiring retrieval of Type Definition (a common use case).

        Attachments

          Activity

            People

            • Assignee:
              ethang Ethan Gur-esh
              Reporter:
              david.caruana David Caruana (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: