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.