Sheet: 'ISM N&N Elements'
- Last UpdatedJun 20, 2024
- 5 minute read
This sheet defines Naming & Numbering Elements, to be used when composing Naming Templates.
As an example, a Tag name is typically a composition of multiple values. The rule for each of these values is defined by an Element. A Naming Template is then defined as a collection of Elements, which in sum defines all the aspects of the Tag name. An example from the NORSOK Coding System describes the Naming Template for lines consisting of the following Elements:

The interpretation of the rules described for an Element might vary across different implementing software applications. The description below is based on how the AVEVA Engineering Numbering Clock is implementing the rules.
|
Item |
Column Name |
Constraint |
Description |
|---|---|---|---|
|
1 |
Id |
Required |
|
|
2 |
Name |
A human readable name for the Element definition. |
|
|
3 |
Name {language} |
|
|
|
4 |
Description |
An arbitrary description of the purpose/role of the Element. |
|
|
5 |
Description {language} |
|
|
|
6 |
Source |
|
|
|
7 |
Mandatory |
|
|
|
8 |
HideOn EmptyValue |
|
|
|
9 |
MaxNumber OfCharacters |
- A positive integer value |
This value dictates the maximum number of characters in the value represented by the Element. |
|
10 |
MinNumber OfCharacters |
- A positive integer value |
|
|
11 |
Padding Character |
- A single character |
Specifies the character to use when padding the Element value (see MinNumberOfCharacters). |
|
12 |
Prefix |
- One or more characters |
|
|
13 |
Suffix |
- One or more characters |
|
|
14 |
Temporary Value |
Specifies a value to use as a replacement when the associated Attribute (see Source) is empty. |
|
|
15 |
FixedValue |
|
|
|
16 |
Regular Expression |
- A valid regular expression syntax |
|
|
17 |
SequenceId |
Example: FUNCTIONAL DOCUMENT |
|
|
20 |
Aspect |
Annotating an Element with an aspect is a way to associate the Element 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 Element 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 |
|