[cmis] [CMIS 1.1 Draft Review] CMIS 1.1 Working Draft 01b: discussion of section 2.1.4.3.3 and Secondary Types

[Jay Brown <jay.brown@us.ibm.com>]

This might be the tip of a bigger issue with Secondary types but I will start it out this way and we can make it a Jira issue if necessary.

Section 2.1.4.3.3 says of Property Definitions:

The document base object-type MUST have the following property definitions, and MAY include
additional property definitions. Any attributes not specified for the property definition are repos-
itory specific. For all property definitions on base types, the query name MUST be the same as
the property id. The repository MUST have the following property definitions on the document
object-type:

Then the document proceeds to list all of the property definitions that we know and love for CMIS 1.0 documents.   However I think this is no longer the case that documents MUST have all of these.  

For example say that in my repository I need to expose a type of cmis:Document that does not have content.  So I define a secondary type called hasContent.  This secondary type has the properties related to content that were formerly in Document.  Specifically 
	cmisContentStreamFilename
	cmisContentStreamLength
	cmisContentStreamMimeType
	cmisContentStreamID

I have two subclasses of cmis:Document one with this secondary type applied and one without.    My basetype must no longer have these formerly mandatory document properties.  This applies to all of the document properties. I.e. Added to the definition for cmis:Object in the domain model. 

This also applies to verbs that are applicable to Document, like set/get/delete content stream.  (though verbs related to secondary types may also need to be a separate subject/ issue)


Jay Brown
Senior Engineer, ECM Development
IBM Software Group
jay.brown@us.ibm.com