[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-167) Property NameProjection
[ http://tools.oasis-open.org/issues/browse/CMIS-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10679#action_10679 ] Ethan Gur-esh commented on CMIS-167: ------------------------------------ TC review --we need a proposed solution. SAP to propose a WG meeting to come up with one. > Property Name Projection > ------------------------ > > Key: CMIS-167 > URL: http://tools.oasis-open.org/issues/browse/CMIS-167 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Bug > Affects Versions: Draft 0.61 > Reporter: David Nuescheler > > reported by SAP / OpenText during the PlugFest in Basel in keywords, so my interpretation may be off. > Currently there is now way to understand the projection of a property name in the source repository into cmis. > This means that it is not clear what will appear in CMIS if i add a property of name "x" into my source repository. > What's even harder (possibly not possible) is to understand what I will have to go through to make a property > "y" appear on the CMIS layer. This means that an application currently is fully repository vendor dependent > that goes beyond using the properties defined in cmis, even if it only uses application specific properties. -- 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]