[OASIS Issue Tracker] Commented: (CMIS-139) Add namespace forproperty name

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

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

Al Brown commented on CMIS-139:
-------------------------------

Thre are a lot of repositories that do not have namespace support for properties.  They require the name to be unique per type.  Introducing a two part identiffication scheme complicates implementations on these repositories.

I, personally, do not want to see namespaces added to property definitions.

I am however, happy to see and support, a single part identification system with an addition attribute/field that contains a namespace, package, etc.

1 - Prefix or a package/orgattribute would solve that as long as the attribute is not part of the identification (still a single part identification system)
2 - Yes, this was the intent of the id attribute on the property definition - to identifiy occurances of different and same semantic meanings of the name.
3 - A prefix can solve that use case.
4 - This can still be accomplished by a single identification system.  a - use 'package1.package2.foo' as the proeprty name or b - we can add a package/organization attribute

Given that some (maybe a majority) of ecm systems do not support a two identification system for property resolution, and that it would be inconsistent to have it for properties and not for types, I'd really like to avoid supporting a two part identification system.


> Add namespace for property name 
> --------------------------------
>
>                 Key: CMIS-139
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-139
>             Project: OASIS Content Management Interoperability Services TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Draft 0.50, Draft 0.6
>            Reporter: Florian Mueller
>            Assignee: Ethan Gur-esh
>
> Introducing namespaces provides the following advantages: 
> 1.  The CMIS specification defines a set of standard properties. An existing repository may have its own properties with the same names but with different semantics or different sets of constraints. A namespace allows clearly distinguishing between CMIS properties and repository or type specific properties. 
> 2.  Certain repositories allow using the same name of a property to be used at more than one place with a different meaning. Common property names like "Name" or "Invoice" might exist in different flavors an in different application contexts. 
> 3.  Future versions of the CMIS specifications may define additional standard properties (e.g. for Records Management). By introducing a separate namespace for the CMIS standard we can guarantee backward compatibility between a newer version of the specification and an existing repository or application implementation. 
> 4.  A namespace can be the foundation to introduce extended properties (e.g. hierarchies). Here are some relationships to other upcoming proposals, for example Aspects/Mixins that should be synchronized.

-- 
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