[OASIS Issue Tracker] Commented: (CMIS-377) Clarify distinctionbetween collections and feeds

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Al Brown commented on CMIS-377:
-------------------------------

I think CMIS does two things:

1. Defines a set of collections (children, etc)
2. Specifies that some must be in the services document
3. States that repositories should include the app:collection element inside a feed that is a collection (important for children since there are too many to include in the services document).
4. States that OPTIONS verb if supported MUST return the http verbs cmis specifies on an object

#3 is stronger than AtomPub which is may as it is perceived #3 is a best practice.  Any client that is CMIS-aware (developer read the spec) won't need #3.  It's for the not-cmis aware clients to be able to do a right thing. #3 also provides app:accept which allows clients to submit the right document type if they know how.  As Roy points out that is an optimization since HTTP takes care of it
#4 is the HTTP way for advertizing which HTTP verbs are supported on an URI. This provides interoperability with basic HTTP clients (if supported)

> Clarify distinction between collections and feeds
> -------------------------------------------------
>
>                 Key: CMIS-377
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-377
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>            Reporter: David Caruana
>            Assignee: Al Brown
>
> Part 2 AtomPub binding distinguishes between collections and feeds i.e.
> collections: relationships, folder children, policies
> feeds: object parents, folder descendants, folder tree, type descendants, changes
> plus, some collections are described in the service document section which could easily be described as feeds e.g. types children
> Need to clarify distinction between collection and feed. It seems that collections allow create etc.

-- 
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