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-669) add CMIS TypeMutability for next version of spec



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

Florian Mueller commented on CMIS-669:
--------------------------------------

createType:

Many repositories cannot accept arbitrary object type ids and property type ids. There is usually a certain pattern and some mapping logic from the native types to the CMIS types. There might be also a length or character set restriction.
Therefore, the proposed createType operation might not be implementable by many repositories. The repository should be in charge of the ids and report them back after the type has been created.


deleteType:

The deletion of orphaned objects is problematic. The user that is trying to delete the type might not have the permissions to delete the objects. In my opinion, types should only be deletable if there are no objects of that type.


deleteTypeTree:

I don't think it is necessary. The number of types managed by an application is usually rather small. Since deleting types doesn't happen very often, there is no huge advantage of having this operation. 


Another suggestion:

The capabilityTypeMutability enum should be moved to the type definition. There could be some types that cannot be altered or used as a super type ("final") while there might be others that can be changed and extended. Also, not all types might accept the same set of property data types.The implementations and capabilities of documents and relationships, for example, are often different in repositories. 



> add CMIS Type Mutability for next version of spec
> -------------------------------------------------
>
>                 Key: CMIS-669
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-669
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>         Environment: n/a
>            Reporter: Jay Brown
>
> Have submitted a draft to the TC documents, to get this discussion started.   See proposal for URL. 

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