OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[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=10194#action_10194 ] 

Al Brown commented on CMIS-87:

(copy from email to list) - suggestion:

a) remove typeId, baseType, baseTypeQueryName from type
b) remove baseType
c) add baseTypeName; whose value is one of the defined cmis base types (cmis:Document)
d) rename parentId to parentTypeName
e) add globalUniqueName to property and type definition:
This attribute contains a a globally unique name either in namespace format or Clark  format which uniquely identifies this type or property.
f) remove id, package from property definition
g) clarify name may contain prefixes utilizing ':'
h) clarify all cmis defined types and properties utilizes cmis prefix
g) extend query grammar to support multiple prefixes:
<prefixedidentifier> ::= [ ( <prefixedidentifier> | <identifier> ) ":" ] <identifier> 

<identifier> ::= !! As defined by SQL-92 grammar. 

This leaves on type definition:
- name, globalUniqueName, baseTypeName

property definition:
- name, globalUniqueName

> 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 (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model, REST/AtomPub Binding
>    Affects Versions: Draft 0.50
>            Reporter: David Caruana
>            Assignee: Ethan Gur-esh
>             Fix For: Draft 0.61
> 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]