• Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Hide

      We can elaborate that ICOM specification is following the Content Management Interoperability Services (CMIS) grammar so that ICOM types (aka. Concepts or classes) can be defined as domain specific type extensions in CMIS. ICOM spaces, folders, and artifacts are extensions of CMIS base types for folders and documents. ICOM integrates the actor, resource actor, group, and role types (primarily from LDAP) with CMIS content types. By defining the actor, resource actor, group, and role types in CMIS grammar, ICOM enables more seamless association between actors and contents, and enhances the access control model.

      Show
      We can elaborate that ICOM specification is following the Content Management Interoperability Services (CMIS) grammar so that ICOM types (aka. Concepts or classes) can be defined as domain specific type extensions in CMIS. ICOM spaces, folders, and artifacts are extensions of CMIS base types for folders and documents. ICOM integrates the actor, resource actor, group, and role types (primarily from LDAP) with CMIS content types. By defining the actor, resource actor, group, and role types in CMIS grammar, ICOM enables more seamless association between actors and contents, and enhances the access control model.
    • Hide

      Resolved as proposed in CSPRD 02 candidate.

      Show
      Resolved as proposed in CSPRD 02 candidate.

      [Comment 2] : Section 2: Modeling language: It would be good to refer to existing other modeling languages, (CIM, MOF, fUML/UML...) and a bit of argumentation why ICOM needs its own.

            Assignee:
            Eric Chan (Inactive)
            Reporter:
            Eric Chan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: