Change Request Requirements

This page contains information about basic information about requirements to a Change Request (CR). Change Requests can be submitted as an owl file or according to a predefined excel spreadsheet. The CR must conform to the following: The data model that is the basis for the entity types and relationships that are used in the spreadsheets is available here:

http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003

It contains all the entity types defined in ISO 15926-2:2003 represented as owl:classes. The file is generated by translating the EXPRESS file lifecycle_integration_schema.exp which ISO 15926-2 (2003) annex B references, to an XML serialization of OWL.

Type of information	Description	Related predicate
PCA ID
defaultRdsId	Unique ID of the class according to the JORD ID spec. Can be filled out by Proposer or PCA.
RDL Designation	The name of the object (class, relationship or individual). All new classes need a unique name. It is mandatory to provide a unique name for all RD objects submitted.
Fragment	The fragment corresponds to the designation in Camel Case and must also be unique. Exceptions – abbreviations in designation in capital letters and special characters. This column is optional and will created by the system if not provided. E.g. a class with designation DESIGNATION IN CAMEL CASE would be designationInCamelCase in this field. The address for this resource would after processing become: http://posccaesar.org/rdl/designationInCamelCase
Entity Type	Every class needs to have a entity type according to the data model. The column is defined by the ISO 15926-2 entity type from which the current RD object is instantiated. The file http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003 contains all the entity types defined in ISO 15926-2:2003 represented as owl:classes.
Creator	The (editor) user who created the Reference Data object. Leave blank when importing new data, leave unchanged when updating or deleting data. Only for internal use.