OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (CMIS-106) Clarify types-childrenand types-descendants

    [ http://tools.oasis-open.org/issues/browse/CMIS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10242#action_10242 ] 

Ryan McVeigh commented on CMIS-106:

Yes this is still accurate.  There is no typesChildren service defined in Part I, but Part II defines a collection for this purpose.  Part II adds the distinct concept of types children which isn't specified in Part I.  Should we have a single service to satisfy the types-children and types-desendants behavior or should we define two services?  

Proposal:  Rename getTypes to getTypeChildren.  This service should not return the type requested by the typeId, but only return the children as requested.  Introduce a getTypeDescendants service that behaves similarly but returns the full descendants list.  This mirrors the similar services as defined for folders.

> Clarify types-children and types-descendants
> --------------------------------------------
>                 Key: CMIS-106
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-106
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>    Affects Versions: Draft 0.50
>            Reporter: Ryan McVeigh
>            Assignee: Al Brown
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]