Assigning URIs and creating RDF vocabulary documents
When you create type definitions in your project area, assign a unique URI to each of those definitions before you share them with other Global Configuration Management (GCM) project areas. Otherwise, you might end up with inconsistencies such as unintended type definition duplication.
For more information, see URIs for Custom Attributes, Types, and Values.
The URIs identify a type definition. Assigning the same URI to different type definitions means that they are logically equivalent. Using the same URI for equivalent type definitions ensures consistency across different project areas and applications, and with querying. It also facilitates accurate reporting, for example, with Jazz® Reporting Service.
Before you begin
- To assign URIs to type definitions, you must have the Configuration Lead role or the Create and modify type definitions privilege.
About this task
Search standard vocabularies for a term that matches your type definition, and use the URI for that term. If you can't find a standard term, create your own and assign a URI in a namespace that you control.
Use these vocabulary terms to define URIs for your GCM type definitions, which include artifact attributes, data types, link types, and enumeration values.
Procedure
- Create a vocabulary document that defines new RDF URIs required for your project area. For more information, see Defining URIs for artifact types, attributes, and other resources.
- Open the Manage Type Definitions page. Click Administration
> Manage Type Definitions.
- Assign URIs from standard vocabularies and your custom vocabularies to GCM type definitions. On the Attributes, Data Types, and Link Types tabs, click user-defined type definitions and assign a URI; then, click Save.
What to do next
- Data types: After you define data types, you can define attributes of that data type on the Attributes tab.
- Attributes or Link Types: If you are ready to share the attributes or link types with your team, select the Artifact Types tab and add them to the global configuration or global component type.
Share or reuse the type definitions of a project area by exporting them and then importing them into other GCM project areas. To ensure that a set of project areas uses the same type definitions, and to prevent further changes those definitions, mark them as final when you export or import them. For more information, see the related topic.