|
I like David's proposal, it's clean and orthogonal.
(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 Changed to swap id & name:
was: 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 e) remove name from type |
|||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Major
Type Id vs Query Name confusion
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.