Object IDs and Namespace Prefixes 

Use

Each object of the Portal Content Directory (PCD) has an ID that uniquely identifies the object.

The following table shows the components that make up an ID.

Component of the ID	Example
Complete path of the object in the PCD, separated by slashes.	<pcd:portal_content/administrator/content_admin/>
Base name of the ID: a string that may not contain any dots.	·        <content_admin_role>
Namespace prefix, which is optional and is located in front of the base name of the ID. The namespace prefix may contain dots.	<com.sap.portal>

Features

Note that content objects delivered by SAP may contain namespace prefixes. The following prefixes are possible:

·        com.sap*

·        com.sap.portals*

·        com.sap.km*

You may not change SAP objects in the above-specified SAP namespaces. For more information, see Delta Links and SAP Content Objects.

Activities

We recommend that you use namespace prefixes for your own content objects as well as for the names of folders in the Portal Catalog.

We also recommend that you develop a global namespace concept. The purpose of this is to

·        clearly identify objects by assigning them to a certain organizational unit by means of a namespace prefix

·        handle objects of a certain organizational unit separately from objects of another organizational unit in content administration

·        not touch or change objects of other organizational units

Example

Example for a complete ID for a role without a namespace prefix:

pcd:portal_content/administrator/content_admin/content_admin_role

Example for a complete ID for a role with a namespace prefix:

pcd:portal_content/com.sap.pct/administrator/content_admin/com.sap.portal.content_admin_role