Re: [cmis] Considering use cases for relationships in CMIS

[Julian Reschke <julian.reschke@greenbytes.de>]

Al Brown wrote:
> ECM typically exposes three basic modelling constructs to its end-users: 
> documents, folders and relationships. ECM providers also expose more 
> modeling constructs such as a generic object holding only metadata. 
> However, those other modeling constructs (to my knowledge) are not 
> consistent enough across vendors for standardization.

Understood.

But why is it necessary to expose them as something special within CMIS? 
Why can't they just be exposed as documents?

> globalUniqueName was added, I believe, to type definitions and property 
> definitions. As such it should be on all types and properties.
> ...

I was just looking at 0.62a, Part 1, and couldn't find them. Am I 
looking in the wrong place?

BR, Julian