...
To inactivate a
a new row is added, containing the same data as the final valid version of the
but with the
field set to false and the timestamp in the
Specref |
---|
RefType | (field) |
---|
t | effectiveTime |
---|
|
fi eld field indicating the nominal date of the release in which the final version ceased being valid.
...
The following example demonstrates how the history mechanism works on the
, but the same rules apply equally well to the
and
member files. In this example, the
associated with the
and
Specref |
---|
RefType | (field) |
---|
t | definitionStatusId |
---|
|
have been shown in place of their
values.
A new
(101291009) is
ad ded added on the 1st July 2007:
Id | Specref |
---|
RefType | (field) |
---|
t | effectiveTime |
---|
|
| | | Specref |
---|
RefType | (field) |
---|
t | definitionStatusId |
---|
|
|
---|
101291009 | 20070701 | 1 | | Concept |
---|
t | 900000000000074008|Primitive| |
---|
|
|
In the next following release (on 1st January 2008), the
is moved from |Module 1| to |Module 2|. Because the moduleId field is not immutable, the
may be updated simply by adding a new record with the same Id.
...
Id | Specref |
---|
RefType | (field) |
---|
t | effectiveTime |
---|
|
| | | Specref |
---|
RefType | (field) |
---|
t | definitionStatusId |
---|
|
|
---|
101291009 | 20070701 | 1 | | Concept |
---|
t | 900000000000074008|Primitive| |
---|
|
|
101291009 | 20080101 | 1 | | Concept |
---|
t | 900000000000074008|Primitive| |
---|
|
|
In the next following release (on 1st July 2008), the
is changed from being
to being
...
Id | Specref |
---|
RefType | (field) |
---|
t | effectiveTime |
---|
|
| | | Specref |
---|
RefType | (field) |
---|
t | definitionStatusId |
---|
|
|
---|
101291009 | 20070701 | 1 | | Concept |
---|
t | 900000000000074008|Primitive| |
---|
|
|
101291009 | 20080101 | 1 | | Concept |
---|
t | 900000000000074008|Primitive| |
---|
|
|
101291009 | 20080701 | 1 | | Concept |
---|
t | 900000000000073002|Defined| |
---|
|
|
In the next following release (on 1st January 2009), the
is deactivated:
...
At no stage in this process are previously written records ever amended. Once a record has been released in a
it will continue to be released in exactly the same form in future Changes are only recorded at the point of release in the
If a record is changed a number of times between releases (during an edit and review process), only the most recently amended record will be appended to the not individual records showing each separate edit to the released In the last example, as well as inactivating the concept (active=0), the
Specref |
---|
RefType | (field) |
---|
t | definitionStatusId |
---|
|
is changed from Concept |
---|
t | 900000000000073002|Defined| |
---|
ShowFormat | inline |
---|
|
to to Concept |
---|
t | 900000000000074008|Primitive| |
---|
|
. In practice this change is not essential since the value of data columns is ignored when a is inactive. Although the change is unnecessary and insignificant, it typically occurs since all the relationships of an inactive concept must also be inactive, and as a result, from the perspective of the authoring environment the concept cannot be regarded as Concept |
---|
t | 900000000000073002|Defined| |
---|
|
.
...