Uploaded image for project: 'OASIS Content Management Interoperability Services (CMIS) TC'
  1. OASIS Content Management Interoperability Services (CMIS) TC
  2. CMIS-106

Clarify types-children and types-descendants

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: REST/AtomPub Binding
    • Labels:
      None
    • Proposal:
      Hide

      Make getTypeDefinition/getTypeChildren/getTypeDescendants consistent with getProperties/getChildren/getDescendants (in behavior and structure - and note more consistent naming). Specifically:

      • getTypeDefinition should return an Entry describing a single type
      • getTypeChildren should return the direct children of a type (or the root type) as a Feed. The resource should identify the type whose children will be fetched. Optional (query) args include includePropertyDefinintions, maxItems, skipCount.
      • getTypeDescendants should return the descendants of a type (or the root type) as a feed with nesting (child types will be contained in their parent's atom:entry) up to the specified depth. The resource should identify the type whose descendants will be fetched. Optional (query) args include includePropertyDefinintions, and depth.
      Show
      Make getTypeDefinition/getTypeChildren/getTypeDescendants consistent with getProperties/getChildren/getDescendants (in behavior and structure - and note more consistent naming). Specifically: getTypeDefinition should return an Entry describing a single type getTypeChildren should return the direct children of a type (or the root type) as a Feed. The resource should identify the type whose children will be fetched. Optional (query) args include includePropertyDefinintions, maxItems, skipCount. getTypeDescendants should return the descendants of a type (or the root type) as a feed with nesting (child types will be contained in their parent's atom:entry) up to the specified depth. The resource should identify the type whose descendants will be fetched. Optional (query) args include includePropertyDefinintions, and depth.

      Description

      What is the difference between TypesChildren and TypesDescendants? The description of both says they are feeds containing all the types in the repository. If both resources contain all types, then what is the difference?

      1. I suspect that either TypesDescendants is redundant and unnecessary, or
      2. that the descriptions are wrong, and they should be returning feeds of types that are children/descendants of a given type.
      3. Note that there is no "typeDescendants" description in the repository services section (REST)
      4. Also note the description of getTypes in Part 1 has a note that "CMIS will return [the types] as a flat list". It also says that if a typeId parameter is provided, then it will "only return that type and its descendants".
      a. This makes it sound like there is no such thing as TypesChildren, and should only be TypesDescendants? And it is really not exactly descendants, since it also includes the "root" type (identified by the parameter). Gack.

        Attachments

          Activity

            People

            • Assignee:
              albertcbrown Al Brown (Inactive)
              Reporter:
              ryan.mcveigh Ryan McVeigh (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: