The type ids for the secondary types defined in 2.1.6 are not valid QNames

    • Type: Bug
    • Resolution: Applied
    • Priority: Major
    • None
    • Affects Version/s: CD04 Substantial Changes
    • Component/s: Domain Model
    • None

      While CMIS object type Ids are opaque, they are currently all valid QNames
      Section 2.1.6 "Retentions and Holds" introduces the first object Ids that are not valid QNames.

      These should be fixed for consistency and to avoid conflict where a repository uses QNames for type Ids.

      For example:
      "cmis:rm:repMgtRetention"

      Alternative suggestions:
      "cmis.rm:repMgtRetention"
      "cmisrm:repMgtRetention"
      "cmis:repMgtRetention"
      "cmis:rm.repMgtRetention"
      which all conform

      the queryName should be changed to match

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

              Created:
              Updated:
              Resolved: