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-112) Expose display namewith a property value and allow property name to be a technical name



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

Jens Huebel commented on CMIS-112:
----------------------------------

In my opinion displaying the label along with the property value is the 90% use case for CMIS clients. And I would prefer streamlining the protocol for those most common kind of use case. Yes there are technical clients that do not use this information, but do we really care so much about these few extra bytes in a protocol that uses XML? Is optimizing bandwidth our primary goal?

@1: Sure this is possible, but makes things more complicated then necessary. In my opinion the server should serve what the client needs. Why have properties then in getChildren()/getDescendentants/getRelations() if we have a getProperties() call. This is redundant too. Sometimes it just makes sense.
@2: The whole I18N issue is out of scope currently. This argument would apply to many other aspects of the spec.
@3: I just consider this the main use case
@4: The cases where you need the other information are rarer and mostly relevant for write scenarios where you will need additional roundtrips anyway (e.g. checkout) before you can write

Seems to be a question of philosophy. Both approaches work. But I still like the idea Al brought up. I would not object against an additional flag if we consider this necessary, but do we really need this? 

> 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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]