Search



Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To inactivate a

Gloss
Spacetrue
tcomponent,
a new row is added, containing the same data as the final valid version of the
Gloss
Spacetrue
tcomponent,
but with the
Gloss
Spacetrue
tactive
field set to false and the timestamp in the
Specref
RefType(field)
teffectiveTime
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

Specref
RefTypefile
tConcept
, but the same rules apply equally well to the
Gloss
Spacetrue
tDescription,
Gloss
Spacetrue
tRelationship
and
Gloss
Spacetrue
tReference set
member files. In this example, the
Gloss
Spacetrue
tdescriptions
associated with the
Specref
RefType(field)
tmoduleId
and
Specref
RefType(field)
tdefinitionStatusId
have been shown in place of their
Specref
RefType(data type)
tSCTID
values.

A new

Gloss
tconcept
 (101291009) is ad ded added on the 1st July 2007:


Id

Specref
RefType(field)
teffectiveTime

 

Gloss
tactive
 

Specref
RefType(field)
tmoduleId

Specref
RefType(field)
tdefinitionStatusId

101291009

20070701

1

Concept
t|Module 1|

Concept
t900000000000074008|Primitive|

In the next following release (on 1st January 2008), the

Gloss
Spacetrue
tconcept
is moved from |Module 1| to |Module 2|. Because the moduleId field is not immutable, the
Gloss
Spacetrue
tconcept
may be updated simply by adding a new record with the same Id.

...

Id

Specref
RefType(field)
teffectiveTime

 

Gloss
tactive
 

Specref
RefType(field)
tmoduleId

Specref
RefType(field)
tdefinitionStatusId

101291009

20070701

1

Concept
t|Module 1|

Concept
t900000000000074008|Primitive|

101291009

20080101

1

Concept
t|Module 2|

Concept
t900000000000074008|Primitive|

In the next following release (on 1st July 2008), the

Gloss
Spacetrue
tconcept
is changed from being
Gloss
Spacetrue
tPrimitive
to being
Gloss
Spacetrue
tFully defined.

...

Id

Specref
RefType(field)
teffectiveTime

 

Gloss
tactive
 

Specref
RefType(field)
tmoduleId

Specref
RefType(field)
tdefinitionStatusId

101291009

20070701

1

Concept
t|Module 1|

Concept
t900000000000074008|Primitive|

101291009

20080101

1

Concept
t|Module 2|

Concept
t900000000000074008|Primitive|

101291009

20080701

1

Concept
t|Module 2|

Concept
t900000000000073002|Defined|

In the next following release (on 1st January 2009), the

Gloss
Spacetrue
tconcept
is deactivated:

...

  1. At no stage in this process are previously written records ever amended. Once a record has been released in a

    Gloss
    Spacetrue
    trelease file,
    it will continue to be released in exactly the same form in future
    Gloss
    trelease files.

  2. Changes are only recorded at the point of release in the

    Gloss
    Spacetrue
    tRF2
    Gloss
    Spacetrue
    trelease files.
    If a
    Gloss
    Spacetrue
    tcomponent
    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
    Gloss
    Spacetrue
    trelease file,
    not individual records showing each separate edit to the released
    Gloss
    tcomponent.

  3. In the last example, as well as inactivating the concept (active=0), the

    Specref
    RefType(field)
    tdefinitionStatusId
    is changed from
    Concept
    t900000000000073002|Defined|
    ShowFormatinline
    to  to
    Concept
    t900000000000074008|Primitive|
    . In practice this change is not essential since the value of data columns is ignored when a
    Gloss
    Spacetrue
    tcomponent
    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
    t900000000000073002|Defined|
    .

...