[OASIS Issue Tracker] Commented: (CMIS-112) Expose display namewith a property value and allow property name to be a technical name

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Florent Guillaume commented on CMIS-112:
----------------------------------------

I must strongly disagree with including property's display names in the object entries.

1. This is highly redundant.
Caching common information is not a burden for a client, it's part of its job; this caching can be lazy and memory-aware, and refetch missing information about the property definitions from the server when needed, if memory constraints are high. Also for a mobile device I would think that having small network packets (thus lower latency) would be at least as important as avoiding the caching of a few property display names.

2. It won't help clients that need to display them.
The display name will have to be i18n'd anyway and the property name is already a good key for that.

3. It won't be used by many clients.
Consider that many clients won't be using this information for display, but just to interact with other systems. Why burden them with useless information?

4. It's not the job of the protocol.
If we wanted to facilitate life in the best possible manner for clients, then why not include the full type definition in every Entry? Also we could include the full set of properties and not filter. Where to stop?

In any case, if others really feel this must be included, I would urge this to be conditional on an "includePropertyDisplayNames" flag that's false by default.


> Expose display name with a property value and allow property name to be a technical name
> ----------------------------------------------------------------------------------------
>
>                 Key: CMIS-112
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-112
>             Project: OASIS Content Management Interoperability Services TC
>          Issue Type: New Feature
>    Affects Versions: Draft 0.50
>            Reporter: Jens Huebel
>
> It is unclear whether the property name is supposed to be exposed in a user interface and/or whether it can be a pure technical name. As the spec mentions to use the property name as part of a query it makes sense to allow this to be a technical name like PROP_1234. To avoid that a client needs to do a lookup in the type definition every time the property name is displayed to an end user the display name should always be exposed together with the query name where a property value appears.

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