Merge enumRelationshipDirection and enumIncludeRelationships, remove "none"

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Hide

      Replace uses of enumIncludeRelationships by enumRelationshipDirection:
      <xs:element name="includeRelationships" type="cmis:enumRelationshipDirection" minOccurs="0" maxOccurs="1" nillable="true" />

      Show
      Replace uses of enumIncludeRelationships by enumRelationshipDirection: <xs:element name="includeRelationships" type="cmis:enumRelationshipDirection" minOccurs="0" maxOccurs="1" nillable="true" />
    • Hide

      TC - reject

      Show
      TC - reject

      Contingent to CMIS-41 being resolved in favor of keeping enumIncludeRelationships, then I propose that it and enumRelationshipDirection be merged into one enum with values: "source", "target" and "either".
      The value "none" of enumIncludeRelationships is redundant because the attribute includeRelationships is always nillable in the schemas.

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

              Created:
              Updated: