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] Created: (CMIS-543) 2.5.3 Paths: Clarify theRS language for paths exposed by other objects.


2.5.3 Paths:  Clarify the RS language for paths exposed by other objects.
-------------------------------------------------------------------------

                 Key: CMIS-543
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-543
             Project: OASIS Content Management Interoperability Services (CMIS) TC
          Issue Type: Bug
          Components: Domain Model
            Reporter: Ryan McVeigh
            Assignee: Ethan Gur-esh


Last sentence: "It is repository-specific whether paths are exposed for folders only or also for non-folder file-able objects."

What does this mean? I see two options (it is ambiguous):

   1. Paths may be exposed for non-folder objects? If so, how (cmis:path? - no, should not add folder properties to documents. custom extension? - meaningless because you can do anything with an extension. custom property? - meaningless because of course you can add custom properties)
   2. Paths do not need to be exposed on non-folder properties. This means that non-folders don't have to include the pathSegment? That it is optional to support getObjectByPath for 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]