Should optional type capabilities be returned separately outside of RepositoryInfo

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Affects Version/s: V1.1
    • Component/s: Domain Model
    • None
    • Hide

      Creating this record (as requested in meeting) for group discussion.

      I am proposing that we leave the information as is to eliminate the need for an additional method and since all of this information is static and has repository wide scope.

      Show
      Creating this record (as requested in meeting) for group discussion. I am proposing that we leave the information as is to eliminate the need for an additional method and since all of this information is static and has repository wide scope.
    • Hide

      It was suggested that the spec points to the schema. Issue closed 23 January 2012.

      Show
      It was suggested that the spec points to the schema. Issue closed 23 January 2012.

      Karsten had asked (in the TC meeting on 1/09/2012) if the type mutability info should perhaps be retrieved separately from the rest of the repository information.

      Text from Karsten's original email here:
      Here is a comment regarding the two new Optional Type Capabilities:

      • NewTypeSettableAttributes
      • CreatablePropertyTypes

      All existing optional capabilities have a limited list of distinct values, either true/false or other specific responses.

      The two new optional capabilities have an unlimited list of possible responses. This is inconsistent, a capability should be a clearly defined level of functionality.

      I suggest to have an optional capability defined as capabilitySetTypes, with possible responses e.g. "none", "create", "modify", and then introduce two separate service calls to obtain the list of available attributes and data types for repositories that support this capability.

      Jays response here:
      A little more explanation may be needed here:

      The NewTypeSettableAttributes are enumerated in the CMIS-core.xsd as follows: (this is from my original separate spec)

      <xs:complexType name="NewTypeSettableAttributes">
      <xs:sequence>
      <xs:element name="id" type="xs:boolean" minOccurs="1"
      maxOccurs="1" />
      <xs:element name="localName" type="xs:boolean" minOccurs="1"
      maxOccurs="1" />
      <xs:element name="localNamespace" type="xs:boolean"
      minOccurs="1" maxOccurs="1"/>
      <xs:element name="displayName" type="xs:boolean" minOccurs="1"
      maxOccurs="1" />
      <xs:element name="queryName" type="xs:boolean" minOccurs="1"
      maxOccurs="1" />
      <xs:element name="description" type="xs:boolean" minOccurs="1"
      maxOccurs="1" />
      <xs:element name="creatable" type="xs:boolean" minOccurs="1"
      maxOccurs="1" />
      <xs:element name="fileable" type="xs:boolean" minOccurs="1"
      maxOccurs="1" />
      <xs:element name="queryable" type="xs:boolean" minOccurs="1"
      maxOccurs="1" />
      <xs:element name="fulltextIndexed" type="xs:boolean"
      minOccurs="1" maxOccurs="1" />
      <xs:element name="includedInSupertypeQuery" type="xs:boolean"
      minOccurs="1" maxOccurs="1"/>
      <xs:element name="controllablePolicy" type="xs:boolean"
      minOccurs="1" maxOccurs="1" />
      <xs:element name="controllableACL" type="xs:boolean"
      minOccurs="1" maxOccurs="1" />
      </xs:sequence>
      </xs:complexType>

      The schema for the CreateablePropertyTypes looks like the schema below (also from the new CMIS-core.xml)
      Note that it can only contain a cmis:enumPropertyType which is already defined in 1.0.

      <xs:complexType name="cmisCreateablePropertiesListType">
      <xs:sequence maxOccurs="unbounded" minOccurs="0">
      <xs:element name="canCreate"
      type="cmis:enumPropertyType">
      </xs:element>
      </xs:sequence>
      </xs:complexType>

            Assignee:
            Unassigned
            Reporter:
            Jay Brown (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: