Re: [cmis-comment] Real need for a light component smaller than document

[Al Brown <albertcbrown@us.ibm.com>]

Ernst,

Thank you for the input. CMIS has relationships which allows an object, either document or folder, to be the parent of many other objects. These relationship objects can be typed and traversed by the CMIS API.

Since you have put a lot of thought into this - why are documents too heavy? They are basically what you suggested. If you are going to store content, you probably want revisioning which gets versioning. With the combination of relationships you have a compound structure.

Thanks, -Al

Al Brown
Office 714 327 3453
Mobile 714 251 6441
Email albertcbrown@us.ibm.com
CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation.

Ernst Bekker ---05/06/2010 02:14:22 AM---Dear readers, Great work and thank goodness for this.

From: Ernst Bekker <rampokker@gmail.com>
To: cmis-comment@lists.oasis-open.org
Date: 05/06/2010 02:14 AM
Subject: [cmis-comment] Real need for a light component smaller than document

---

Dear readers,

Great work and thank goodness for this. 

Just one small adjustment required. A component smaller than document please. Call it a 'Document part' or perhaps 'Content component'.

My current difficulties with not having a smaller component relates to both writing software and documentation for that software.
*    The majority of Content Managers use smaller components than the Document Managers. 
*    The specified functionality for Document is excessive for a document component.
*    A document is really a composition of components
*    It is difficult to conceptually explain the composition of components where a document is a composition of documents where even the keywords and paragraphs are documents.
*    Language in general for training material or any other writing creates unnecessary complications for the unfortunate readers who have read it with real world eyes. We end up with conceptually cloudy and difficult to understand statements. Example: Simply add that document to the parent document and please remember to document which child document was at which level of which document.

Document vs. Content Management
*    It seems this specification with it's disregard for content in favour of documents is widening the gap between content and document managers which has various political consequences, the biggest being an attitude of simply ignoring it.  

Suggested solution:
*    A simple light weight component which has a name, type and 0 or more child components which could be either a document(as a specific kind of component) or another component. 

Value or Use
*   Bring content managers into the CMIS with the document managers and so closing that gaping hole.
*   Light weight components reduce excessive unused processing.
*   Conceptual space is cleaned up and use of CMIS is easier to explain in natural language.
*   As an abstracted kind component and a specialised kind document, we can use classic design patterns for algorithms dealing with the content.

Kind regards,
ernSt bekker