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-168) URL to id mapping



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

Al Brown commented on CMIS-168:
-------------------------------

How do you propose collections address this?  I see two ways - a) define new cmis collection types that take uri arguments as input b) overload an existing collection with different uri arguments that if provided the collection returns a different object on get.

a) this method may introduce collections that do not act as atompub collections.  we could turn off post by specifying an empty app:accept.  Would we be limited to returning feeds instead of other formats such as atom entry since collections usually return a feed on get?  

b) we could get probably get away with this, but the behavior of a selected collection would vary between a get without arguments and a get with uri arguments (could be an atom entry for example).  These collections would be overloaded which leads to complexity.

Based on what I thought of, a new extension to atompub in the workspace was more straightforward.  

Which of the above (or something else) are you proposing for 168, 169, 170?  I'd be happy for collections to provide this functionality and close those issues.

> URL to id mapping
> -----------------
>
>                 Key: CMIS-168
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-168
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>    Affects Versions: Draft 0.61
>            Reporter: David Nuescheler
>            Assignee: Al Brown
>
> reported in various discussions during the PlugFest in Basel, my interpretation may be off.
> Currently there is no way to map document and folder ids to urls on the client side.
> This will either lead to a large number of additional roundtrips or to very stateful clients
> that rely on the stability of that mapping (which i am not sure if this would be legal).
> So it would be great if there was a simple mapping from id's to URLs for both folders and
> documents.

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