This article covers a Bloomreach Experience Manager version 13. There's an updated version available that covers our most recent release.

Content Model Naming Conventions

 

When creating new namespaces, document types, compound types, node types, nodes and properties, please follow the best practices as outlined below:

Item Naming Convention Example(s)
Namespace Prefix All lower case myproject
Namespace URI URI (include organization, project and version number) http://www.mycompany.com/myproject/1.0
Node Type (Document Type, Compound Type) Name camelCase myproject:newsArticle
Node Name lower case with dashes best-beaches-in-europe
Property Name camelCase myproject:firstName
Note that some existing JCR items in the content repository may not follow this best practice for backward compatibility.
All names must conform to the JCR 2.0 specification (see section 3.2 "Names").
Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?