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-693) CMIS RepositoryExtensions



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

Florian Mueller commented on CMIS-693:
--------------------------------------

Although I support the idea of repository extensions, I don't think that extension documents as described on the Wiki page are the right way to do it.

Technically, these documents have to be either virtual documents that are provided by the CMIS connector or real documents in the repository. Both approaches can be difficult to implement.

If they are virtual documents they need special object ids and all operations have to be aware of these 'virtual object ids'.  That would require code changes and extra checks all over the place. Also, getChildren and a query of the root folder would return different results.

If they are real documents they have to be protected and maybe even hidden from native clients, which can be difficult. Some repositories don't allow or are not able to create such a folder under the root folder. In particular, specialized repositories that are perfect candidates for extensions might not be able to do that.

So, it seems to be easy to use from a client perspective, but it could be a major undertaking for a repository to support that.

Why don't we put these extensions into the repository info? That would be a central and logical place. In the end, an extension is described by a name and a handful of key-value pairs. The current CMIS spec allows those kinds of extensions already. 


> CMIS Repository Extensions
> --------------------------
>
>                 Key: CMIS-693
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-693
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: V1.0
>         Environment: n/a
>            Reporter: Jay Brown
>            Priority: Minor
>
> As discussed in the TC meeting today. I have posted a wiki page describing the best practice for CMIS repository extensions. 
> Anyone interested, please comment. 
> Wiki page here:  http://wiki.oasis-open.org/cmis/Repository%20Extensions

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