[OASIS Issue Tracker] Commented: (CMIS-87) Type Id vs Query Nameconfusion

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

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

David Caruana commented on CMIS-87:
-----------------------------------

Correction to above: v0.6 has introduced constants for the Object Type Definition attribute named 'baseType'.

I'd like to propose the following changes...

Part I...

1) 2.7.2.1 Attributes common to all Object-Type Definitions
a) typeId value no longer repository specific. Instead is one of Document, Folder, Relationship, Policy
b) remove baseType
c) add baseTypeId; type ID whose value is one of Document, Folder, Relationship, Policy
d) remove baseTypeQueryName
e) rename parentId to parentTypeId

This gives us:
- three IDs for all Object Type Definitions; typeId, parentTypeId & baseTypeId
- one Query Name for all Object Type Definitions; queryName

2) 2.7.4.1.2, 2.7.4.2.2, 2.7.4.3.2, 2.7.4.4.2  Object-Type Property Definitions
a) add BaseTypeId; type ID whose value is the type id of base type i.e. one of Document, Folder, Relationship, Policy

This gives us:
- two type ID properties for all object instances; ObjectTypeId, BaseTypeId

Part II: AtomPub and SOAP bindings

a) No special treatment is given to base type. The ObjectTypeId and BaseTypeId properties are represented as any other property i.e. mapped to cmis:property/cmis:value.

> 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