[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-87) Type Id vs Query Nameconfusion
[ http://tools.oasis-open.org/issues/browse/CMIS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10154#action_10154 ]
Florent Guillaume commented on CMIS-87:
---------------------------------------
I like David's proposal, it's clean and orthogonal.
> Type Id vs Query Name confusion
> -------------------------------
>
> Key: CMIS-87
> URL: http://tools.oasis-open.org/issues/browse/CMIS-87
> Project: OASIS Content Management Interoperability Services TC
> Issue Type: Bug
> Components: Domain Model, REST/AtomPub Binding
> Affects Versions: Draft 0.50
> Reporter: David Caruana
> Assignee: Ethan Gur-esh
>
> The definition of type ids and query names is disjoint between part I and part II of the spec.
> As I understand there are six concepts:
> - ObjectTypeId (value is repo specific)
> - ParentTypeId
> - BaseObjectTypeId
> - ObjectTypeQueryName (spec defines values for root types e.g. Document, Folder, ...)
> - ParentTypeQueryName
> - BaseTypeQueryName
> However, part I of the spec does not define properties for all above even though part II defines a serialization mapping for them e.g. base type id.
> I would like to see the spec (Part I) also define well known ObjectTypeId values for root types. This would then allow Object Type Definition to support following attributes:
> - ObjectTypeId
> - ParentTypeId
> - BaseTypeId
> - TypeQueryName
> And Base Object Type to support the following properties
> - ObjectTypeId
> - BaseTypeId
> Part 2 is then a direct serialization of above. This means Query Name must be retrieved via Type Definition (I think that's ok, as it's generally used to drive query builders). However cmis:object provides its actual type id and a known base type id that can be switched on by a client (e.g. split between item and container) without requiring retrieval of Type Definition (a common use case).
--
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]