Domain model should state objects are not constrained

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Affects Version/s: V1.0 Errata
    • Component/s: Domain Model
    • None
    • Hide

      Add something like the following at the bottom of Section 2.1.2 Object:

      CMIS objects may expose additional information, such as vendor-specific workflow data, beyond the attributes described above. In this respect, the data model can be extended as desired. This specification does not standardize such extensions.

      Show
      Add something like the following at the bottom of Section 2.1.2 Object: CMIS objects may expose additional information, such as vendor-specific workflow data, beyond the attributes described above. In this respect, the data model can be extended as desired. This specification does not standardize such extensions.
    • Hide

      Accepted for inclusion in Errata.

      Show
      Accepted for inclusion in Errata.

      The domain model (section 2.1.2 Object) describes that every CMIS object has a set of Properties, and may have a Content Stream, one or more Renditions, and possibly an ACL.

      Based on our discussions in the TC, as well as in the bindings, additional repo-specific data can also be exposed via these objects. For example, a repository could expose document workflow information at runtime within the CMIS Document object.

      Since this is an important extensibility area for CMIS, it would be helpful if the domain model states this (without going into details).

            Assignee:
            Unassigned
            Reporter:
            Steve Roth (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: