Page History

The effectiveTime

Specref
RefType (field) t effectiveTime

and

Gloss
Space true t active

fields in the

Gloss
Space true t release file

enable the use of a "log style" append-only data model to track all changes to each

Gloss
t component

, providing full traceability. Once released, a row in any of these files will always remain unchanged. Historic data is supplied in the

Gloss
Space true t RF2

Gloss
Space true t release files,

dating back to the first release in

Gloss
Space true t RF1

format in 2002.

In order to change the properties of a current

Gloss
t component

(and, therefore, to create a new version of it), a new row is added to the applicable file, containing the updated fields, with the

Gloss
Space true t active

field set to true and the timestamp in the effectiveTime

Specref
RefType (field) t effectiveTime

field indicating the nominal date on which the new version was released.

To inactivate a

Gloss
Space true t component,

a new row is added, containing the same data as the final valid version of the

Gloss
Space true t component,

but with the

Gloss
Space true t active

field set to false and the timestamp in the effectiveTime

Specref
RefType (field) t effectiveTime

fi eld indicating the nominal date of the release in which the final version ceased being valid.

Where editorial policy does not allow a particular property of a

Gloss
Space true t component

to be changed whilst keeping the same

Gloss
Space true t Identifier,

the

Gloss
Space true t component

as a whole is inactivated (as described above), and a new row added with a new id, the effectiveTime

Specref
RefType (field) t effectiveTime

set to the nominal date of the release in which this version of the

Gloss
Space true t component

became valid, and the

Gloss
Space true t active

field set to true.

...

The following example demonstrates how the history mechanism works on the Concept file

Specref
RefType file t Concept

, but the same rules apply equally well to the

Gloss
Space true t Description,

Gloss
Space true t Relationship

and

Gloss
Space true t Reference set

member files. In this example, the

Gloss
Space true t descriptions

associated with the moduleId

Specref
RefType (field)

and definitionStatusId

t moduleId

and

Specref
RefType (field) t definitionStatusId

have been shown in place of their SCTID

Specref
RefType (data type) t SCTID

values.

A new

Gloss
t concept

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

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

Gloss
Space true t concept

is moved from |Module 1| to |Module 2|. Because the moduleId field is not immutable, the

Gloss
Space true t concept

may be updated simply by adding a new record with the same Id.

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

Gloss
Space true t concept

is changed from being

Gloss
Space true t Primitive

to being

Gloss
Space true t Fully defined.

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

Gloss
Space true t concept

is deactivated:

...

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

   Gloss
   Space true t release file,

   it will continue to be released in exactly the same form in future

   Gloss
   t release files.

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

   Gloss
   Space true t RF2

   Gloss
   Space true t release files.

   If a

   Gloss
   Space true t component

   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
   Space true t release file,

   not individual records showing each separate edit to the released

   Gloss
   t component.

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

   Specref
   RefType (field) t definitionStatusId

   is changed from

   Concept
   t 900000000000073002|Defined| ShowFormat inline

   to

   Concept
   t 900000000000074008|Primitive|

   . In practice this change is not essential since the value of data columns is ignored when a

   Gloss
   Space true t component

   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|

   .

...