The Common Schema must be allowed to evolve because the scope of what the schema defines will change over time. However, objects and the properties and relationships between them have been modeled to support HxGN SDx work processes and to meet industry-standard data exchange.
Unless explicitly stated otherwise, all rules defined here apply to both the meta-schema
and the Common Schema.
For more information about how schema evolution rules allow for forward and backward compatibility with authoring tools, see SmartPlant Schema Modification Rules.
Use these links to find more information about rules for creating and modifying specific schema objects:
Rule enforcement
Every schema object is stamped with the official revision and version forwhich it was created. Objects that predate the latest released version must adhere to the rules defined here. These rules are supported by the delivery and setup procedures.
Creation rules
Keep the following rules in mind when making changes that affect object or relationship creation.
-
New objects of any type can be created, but, the relationships between new objects and existing objects cannot violate a revision rule.
-
New relationships between existing objects can be created, but, the new relationship cannot violate a revision rule.
Deletion rule
An object (including the relationships of the object) that supports ISchemaObj cannot be deleted if its revision or version predates the current software revision or version.
Revision rule
If a schema object type is not included in this section, any type of revision to that object is allowed.