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] (CMIS-807) Add a generic "call" operation


Florian Mueller created CMIS-807:
------------------------------------

             Summary: Add a generic "call" operation
                 Key: CMIS-807
                 URL: https://issues.oasis-open.org/browse/CMIS-807
             Project: OASIS Content Management Interoperability Services (CMIS) TC
          Issue Type: New Feature
          Components: Domain Model
    Affects Versions: Proposals for 2.0
            Reporter: Florian Mueller


CMIS never indented to cover all features and capabilities of a repository. But sometimes a repository wants to expose a few features that are not part of the CMIS spec and probably never will.
A few examples: basic recycle bin operations (list, restore, permanently delete), publishing a document, triggering the generation of a rendition.

It would be nice to a have generic "call" operation that takes an undefined input (stream of bytes) and returns an undefined output (stream of bytes).
Most CMIS clients would ignore it but if a client knows the repository it can easily call specific operations without leaving the CMIS realm (endpoint, binding, session, authentication,etc.). 

I'm not advocating that repository vendors should expose each and every repository feature through this. That's what proprietary APIs are for. I'm just talking about a few, selected operations that makes sense in the CMIS context and play nice with the CMIS data model.




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]