Object IDs and Namespace Prefixes
Use
Each object in 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/ |
Base name of the ID. This string cannot include periods (.). |
<content_admin_role> |
Namespace prefix. This ID component is optional and is located in front of the base name of the ID. The namespace prefix can include periods. |
<com.sap.portal> |
Features
Note that content objects delivered by SAP may contain one of the following namespace prefixes:
● com.sap*
● com.sap.portals*
● com.sap.km*
We recommend that you 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
The portal includes a naming conventions service that enables you to create rules for valid namespaces. For more information, see Naming Conventions for Namespaces.
Example
Example of a complete ID for a role without a namespace prefix:
pcd:portal_content/administrator/content_admin/content_admin_role
Example of 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