Object IDs and Namespace Prefixes
Use
Each object in the Portal Content Directory (PCD) has an ID that uniquely identifies the object. For example:
pcd:portal_content/com.sap.pct/administrator/content_admin/
com.sap.portal.content_admin_role
The following table shows the components that make up the content object ID:
ID Component |
Example |
Complete path of the object in the PCD |
pcd:portal_content/administrator/ |
Namespace. This component is optional. This string can include periods (.). |
com.sap.portal Note that a period (.) separates between the namespace and the name of the PCD object. |
Atomic name of the PCD object. This string cannot include periods (.). |
content_admin_role |
Features
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 do not change SAP objects in these SAP namespaces. More information: Delta Links and SAP Content Objects.
Activities
We recommend to use namespace prefixes for your own content objects as well as for the names of folders in the Portal Catalog.
We also recommend to develop a global namespace concept. The purpose of this is to:
· clearly distinguish between objects by assigning namespaces that indicate the relevant organizational unit
· separately handle objects of different organizational units in content administration
The portal includes a naming conventions service that enables you to create rules for valid namespaces. More information: Defining Naming Conventions for Content Object Namespaces.
Example
· Example of a complete ID for a role without a namespace:
pcd:portal_content/administrator/content_admin/content_admin_role
· Example of a complete ID for a role with a namespace:
pcd:portal_content/administrator/content_admin/
com.sap.portal.content_admin_role