Sheet: 'ISM Attributes'
- Last UpdatedJun 26, 2025
- 5 minute read
This sheet defines Attribute (or Characteristic) classes.
|
Item |
Column Name |
Constraint |
Description |
|---|---|---|---|
|
1 |
Id |
Required |
|
|
2 |
Name |
A human readable name for the Attribute definition |
|
|
3 |
Name {language} |
|
|
|
4 |
Description |
An arbitrary description of the purpose/role of the Attribute |
|
|
5 |
Description {language} |
|
|
|
6 |
Presence |
|
Dictates the requirements for a value being provided for the Attribute when a data object is provided. For example, when data is loaded by AVEVA Gatekeeper, the constraint dictated by this property will be enforced for all instances of the target Attribute |
|
7 |
Presence {maturity} |
|
|
|
8 |
Discipline |
The discipline "owning" the Attribute |
|
|
9 |
Discipline {maturity} |
|
|
|
10 |
GroupId |
|
|
|
11 |
MinOccurs |
- A positive integer value |
Specifies the minimum number of values that has to be provided for the Attribute when an instance of a class is provided. For example, when data is loaded by AVEVA Gatekeeper, the constraint dictated by this property will be enforced for all instances of the target Attribute |
|
12 |
MaxOccurs |
- A positive integer value >= Min Occurs, or "unbounded" |
Specifies the maximum number of values that can to be provided for the Attribute when an instance of a class is provided. For example, when data is loaded by AVEVA Gatekeeper, the constraint dictated by this property will be enforced for all instances of the target Attribute |
|
13 |
UomClassId |
- {UoMClass @id} |
|
|
14 |
UomRequired |
|
|
|
15 |
Validation Type |
|
|
|
16 |
Validation Rule |
|
|
|
17 |
Concept |
|
|
|
18 |
DataType |
|
|
|
19 |
Size |
|
|
|
20 |
Aspect |
Annotating an Attribute with an aspect is a way to associate the Attribute with a specific semantic definition. Application logic will look for these aspects, and apply associated processing rules. Definition of available aspect values is outside the scope of this document |
|
|
21 |
Obsolete |
|
When evolving a Class Library over time, removing previously existing definitions might cause issues with consuming software systems (for example, they might not support deleting an Attribute that is in use for existing data). Obsoleting deprecated definitions might therefore be a less intrusive approach. How, or whether, obsoleting is implemented might vary across consuming software though |
|
22 |
SortOrder |
- A signed integer value |
|