[OASIS Issue Tracker] Commented: (CMIS-747) Metadata inclusion in reponses for properties is verbose and there is no option to control it. Objects do not include any type metadata which is not consistent.

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

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

Jens Hübel commented on CMIS-747:
---------------------------------

It seems like that the proposal has a reasonable impact for this specific use case. What I still do not like is that this only works for the browser binding and that there exist other areas where we send much information across the wire (RepositoryInfo, AllowableActions for example). Be also aware that the default is still being chatty. Or that we send way too many properties in many cases. I also see that adressing any of those issues will break 1.0 compatibility and requires major spec redesign. Therefore as stated in the last call this is out of scope for 1.1.

Every extra parameter, option and flags adds complexity, makes implementing the spec more difficult, leads to more bugs, requires more test cases and gives less interoperability. Keep in mind what the original idea of CMIS is and where we come from.

If the community believes that it is worth the effort I do not hesitate to agree to the proposal.


> Metadata inclusion in reponses for properties is verbose and there is no option to control it. Objects do not include any type metadata which is not consistent.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CMIS-747
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-747
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Domain Model
>    Affects Versions: Committee Draft 05
>            Reporter: Andy Hind
>
> The AtomPub binding and browser bindings include metadata when representing properties.
> Some of the metadata is optional in the schemata but there is no way for the client to control what is included in the response (Domain model and bindings)
> => Add options for the client to control what property metadata is required.
> Some of the metadata that is mandatory is repeated many times if there are many objects in the response.
> The two combined, increase the reposonse size significantly above the minimum that would be required for a client capable of caching the metadata.
> The response size is still important for the mobile use case.
> Compression, filtering and paging help, but so too will reducing the verbosity of the response.
> Are optional but unset properties included in object representations?
> (e.g. for driving forms) 
> If so can these be omitted?
> => Allow metadata to be excluded for properties.
> => Represent propertyId and value in an alternative compact form.
> => Exclude optional but unset properties
> While metadata is include for properties it is not included for objects.
> You can get the display name etc for the properties but not the object.
> This implies that type metadata is cached,  never required, or implied by the available actions. 
> => Support optional metadata for objects?
> browser binding property metadata example:
>             "cmis:contentStreamLength":{
>                 "id":"cmis:contentStreamLength",
>                 "localName":"cmis:contentStreamLength",
>                 "queryName":"cmis:contentStreamLength",
>                 "value":33987,
>                 "type":"integer",
>                 "displayName":"Content Length",
>                 "cardinality":"single"
>                 }
> Could be:
>  
>             "cmis:contentStreamLength":33987
> + dictionary cache

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