When naming Design Studio entities, consider the following:
A namespace is a collection of names used in XML documents as element types and attribute names. The namespace functionality in Design Studio enables you to differentiate between elements and attributes that have the same name but come from different sources.
For example, using namespaces in Oracle Communications Order and Service Management (OSM) enables you to separate OSM models (tasks, processes, order templates, workgroups, and worklists) into specific services in your Operational Support System (OSS) environment. Each service can be implemented independently by a different team, then deployed into a single OSM run-time environment.
Use Design Studio folders to organize entities within a single project. Design Studio folders are not group-specific; rather, they can contain different types of entities. For example, you can create a single folder to contain all of your task and process entities. In this example, the folder appears under the Studio Projects view Process directory and under the Studio Projects view Tasks directory. If you rename the folder in one location, Design Studio updates the name in all locations. When you are creating new entities, Design Studio uses the last used folder name, irrespective of entity type, as the folder default value.
When naming entities in Design Studio, you must ensure that the entity names are unique by entity type. For example, you cannot name two task entities with the same name. However, because Design Studio enforces a naming restriction to define name uniqueness by entity name and entity type, you can create identical names for different entity types. For example, you can model a task entity and a process entity with the name AddDSL.
If you create, rename, or import an entity with a name that is identical to the same type of existing entity, Design Studio generates a problem marker. You cannot deploy a cartridge until you have corrected all existing problem markers in the cartridge.
Some Design Studio features have additional conventions. Additionally, operating systems may impose naming restrictions. Oracle recommends that you comply with these naming conventions.
Note:
Rename Design Studio entities in the Studio Design perspective only. Do not rename entities from within the Navigator view.