This article covers a Bloomreach Experience Manager version 11. 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 myhippoproject
Namespace URI URI (include organization, project and version number) http://www.mycompany.com/myhippoproject/1.0
Node Type (Document Type, Compound Type) Name camelCase myhippoproject:newsArticle
Node Name lower case with dashes best-beaches-in-europe
Property Name camelCase myhippoproject:firstName
Note that some existing JCR items in Hippo 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?

    We rely on cookies

    to optimize our communication and to enhance your customer experience. By clicking on the Accept and Close button, you agree to the collection of cookies. You can also adjust your preferences by clicking on Manage Preferences. For more information please see our Privacy policy.

    Manage cookies
    Accept & close

    Cookies preferences

    Accept & close
    Back