[OASIS Issue Tracker] Commented: (CMIS-170) get folder by path

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

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

Jens Huebel commented on CMIS-170:
----------------------------------

just to make it a bit more complete some problem areas having been discussed around this (please add what is missing):

do we need getFolderByPath() or getObjectByPath()?

Issue: same name siblings, a repository might support more than one item having the same name. In this case it could not implement this function. Should it just throw a specific exception in this case?

do we need a mapping in both directions? In the other direction multi-filing would be an issue (no unique path to an object).

Should path navigation be an optional capability of the repository?

Therefore might be tough to specify. However path navigation is such a common pattern (file system, URL, WebDAV, ..) that we really should think about if this isn't  the 80% part and the issues are the 20%...

Use Cases: WebDAV mapping, simple CMIS browser based on URLs

All in all it would be good to get a decision from the TC how to deal with this as this issue arises over and over again.



> get folder by path
> ------------------
>
>                 Key: CMIS-170
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-170
>             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.
> It would be great to have at least a "get folder by path" that allows to reflect the
> hierarchy that we expose through the parent child relationships of folders.
> Generally there are a lot of usecases (exposure to filesystem like trees, relative links from document to documents) that would 
> benefit from a path. This does not stand in contrast with having multiple paths to the same document or folder.
> Is anyone opposed to introducing paths into CMIS?

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