[OASIS Issue Tracker] Commented: (CMIS-173) Paging support inAtomPub Binding using rfc5005 is redundant

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

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

Al Brown commented on CMIS-173:
-------------------------------

JIRA Cleanup

> Paging support in AtomPub Binding using rfc5005 is redundant
> ------------------------------------------------------------
>
>                 Key: CMIS-173
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-173
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>    Affects Versions: Draft 0.62
>            Reporter: Ryan McVeigh
>            Assignee: Al Brown
>             Fix For: Draft 0.62
>
>
> Atom was released in Dec 2005, rfc5005 in Sep 2007 and AtomPub in Oct 2007.  It appears that AtomPub gives us nearly everything that rfc5005 does, minus the <fh:complete/> schema extension.  We get that same behavior by excluding the paging links on the response for a collection.  That exclusion indicates a complete feed.  Do we need rfc5005?  AtomPub appears to give us what's needed here.
> The relevant section from AtomPub (rfc5023) is 10.1.

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