Valid Context
Multiple occurrencesNoRequiredYes
Defines the context of a ecoSpold02 distribution, database or library.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
@originalSource7500newanyURINoNoNoNo
Reference to the location of the original document. Can be used to verify the data and/or to check for updates in the future.
@majorRelease7501newintegerNoYesNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The release version number is used as follows: with a major update (e.g. every second year) the major release number is increased by one (1.00, 2.00, etc.).
@minorRelease7502newintegerNoYesNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The release version number is used as follows: minor updates (corrected errors) within the period of two major updates increase the minor release version.
@majorRevision7503newintegerNoNoNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The revision version number is used to discern different versions during the working period until the dataset is entered into the database). The revision is generated automatically with each change made in the dataset or related file.
@minorRevision7504newintegerNoNoNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The revision Version number is used to discern different versions during the working period until the dataset is entered into the database). The revision is generated automatically with each change made in the dataset or related file.
@id7515newTUuid36NoYesNoNo
Unique identifier of the context.
name7520newTString8080NoYesYesNo
The name of the context
requiredContext7535newTRequiredContextReferenceYesNoNoNo
References to master data files that are needed to open a dataset from this context.
comment7540newTString3200032000NoNoYesNo
A description of the context.

Top

Required Context Reference
Multiple occurrencesYesRequiredNo
This type allows to specify which context(s) must be known if a dataset is to be read using the master data referenced by it.
It can be used signal that master data entries from different contexts are needed to read this dataset. The software reading the dataset must be aware of those contexts and must know where to find the actual master data files of each context.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
@majorRelease7810newintegerNoYesNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity.
@minorRelease7820newintegerNoYesNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity.
@majorRevision7830newintegerNoNoNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity.
@minorRevision7840newintegerNoNoNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity.
@requiredContextId7850newTUuid36NoYesNoNo
Reference to the context of the master data file.
If this attribute is omitted the context of the dataset itself should be used instead.
requiredContextName7855newTString8080NoYesYesYes
The name of the context referenced by field 7850.
@requiredContextFileLocation7860newanyURINoNoNoNo
Optional URI reference to the directory containing the master data files of this context.

Top