chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vyacheslav Pascarel <vpasc...@opentext.com>
Subject How to handle the "same" properties defined in primary and secondary types?
Date Fri, 02 Jun 2017 18:52:56 GMT
Hello,

My application consumes Alfresco CMIS services and I noticed that many Alfresco primary and
secondary types have a lot of overlapping  properties. For example "cmis:objectId" property
appears in "cmis:document" primary and "P:rn:renditioned" secondary type definitions. The
former secondary type can be applied to objects of "cmis:document" type. When applied, Alfresco
returns two identical "<cmis:propertyId...>" entries in AtomPub response for "cmis:objectId"
property. Apache Chemistry Workbench still works and shows only one occurrence of such properties.

So my questions are:

-          Is Alfresco behavior "compliant" with CMIS 1.1 in sense of having the "same" property
defined in primary/secondary types?

-          If YES, then what assumptions are correct:

o   A "duplicated" property definition should be identical across all the type definitions

o   A "duplicated" property definitions should at least have a compatible "value" type

o   A "single" property value is "shared" across primary and secondary types in object "instance"
(the property may appear multiple times in request/response but only one occurrence is respected)

-          If NO, then what assumptions are correct:

o   As a workaround: only first or last value should be respected for object containing "duplicated"
properties

o   A "duplicated" property should be treated according to its definition in "primary" type

Thank you in advance,

Vyacheslav Pascarel


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message