Re: [cmis] unreadable property names and current clients?

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

That is an interesting issue. I thought clients would display the name directly. Please open an issue for this. It might be better to leverage the property id and include the display name in atom entry/getProperties call.

-Al

Al Brown
Emerging Standards and Industry Frameworks
CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home
Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home

Office 714 327 3453
Mobile 714 263 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.

Jens Hübel ---03/04/2009 03:24:36 AM---Hi all,

From:	Jens Hübel <jhuebel@opentext.com>
To:	<cmis@lists.oasis-open.org>
Date:	03/04/2009 03:24 AM
Subject:	[cmis] unreadable property names and current clients?

---

Hi all,
 
I have a question how the typical clients behave in regards of property names today.
 
Properties have a name, an id and a query name. A property definition also has a display name. In a getChildren() or getProperties() call a property is identified by its name. Property names  have certain syntax constraints. So it might happen that a repository needs to map its internal property identification to something that fulfills the CMIS syntax. This could be a generated, meaningless string  like PROP_4711. Only the property definition then contains something readable in the displayName like "Invoice number". All the examples in the spec however contain readable property names.
 
So my question is: Will existing CMIS clients today display the property name directly in the user interface or will they typically do a look-up in the property definition for the display name before presenting this in the user interface?
 
Any feedback is welcome how you have implemented this today. Would I break clients by using a generated, unreadable property name like PROP_4711? Do we need to define a recommendation in the spec (in this case I would create a JIRA issue).
 
Thanks Jens