Purpose
An 900000000000521006 |Association type reference set| represents a set of unordered associations of a particular type between.
Data structure
Anis aused to represent associations between. Its structure is shown in the following table.
Table 50. Association reference Set - Data structure |
|
|
---|---|---|
Field | Data type | Purpose |
A 128 bit unsigned Integer (data type), uniquely identifying this. Different versions of a reference set member share the same id (field) but have different effectiveTime (field). This allows a reference set member to be modified or made active (field) (i.e. removed from the active set) at a specified time. | ||
The inclusive date or time at which this version of the identifiedbecame the current version. The current version of thisat time T is the version with the most recent effectiveTime (field) prior to or equal to time T . | ||
The state of the identifiedas at the specified effectiveTime (field) . If active (field) = 1 (true) theis part of the current version of the set, if active (field) = 0 (false) theis not part of the current version of the set. | ||
Identifies thethat contains thisas at the specified effectiveTime (field) . The value must be aof 900000000000443000 |Module (core metadata concept)| within the metadata. | ||
Identifies theto which thisbelongs. In this case, set to aof 900000000000521006 |Association type reference set| . This indicates the nature of the association between the source and target. | ||
The identifier of the sourceof the association. | ||
The identifier of the targetof the association. |
Metadata
The following metadata in the "Foundation metadata"supports this:
Figure 16. Association Reference Sets in the Metadata Hierarchy
Notes on usage
Each member of a |Historical association| represents a Reference from anto other equivalent or relatedthat were current in thein which thatwas inactivated.
Each |Historical association| holdsof a different nature between the. The |Historical association| contains associations:
from eachto one or more otherthat are current in thein which thewas inactivated;
from each inactivefor which there is a current replacement to the replacement;
from anto athat is current in thein which thewas inactivated, and which is correctly described by the Term of the;
From eachto one or morethat replace it.
Theidentified by the targetComponentId (field) must be an instance of the same class ofas theidentified by the referencedComponentIdfor all |Historical association|apart from the |REFERS TOassociation|.
Within the |REFERS TOassociation|, the referenced ComponentId field must be aand the targetComponentIdmust be a.
The targetComponentId (field) is used differently in the |MOVED TO association|. In this case, the targetComponentId (field) does not refer directly to a replacement, but rather to the namespace to which thewas moved to. The targetComponentId (field) actually refers to thethat represents the namespace. This approach is used since the organization sourcing themay not always be able to determine the precise reference that is applicable in the receiving organization (namespace). Thus the responsibility for these references lies with the new responsible (receiving) organization.
See also more further information about 4.2.3 Historical Association Reference Sets.
Descriptor template and examples
The tables below show examples of the descriptors for specificthat follow the 900000000000521006 |Association type reference set| pattern.
Table 51. Refset Descriptor rows for 900000000000527005 |SAME AS association reference set| . |
|
|
|
| |
---|---|---|---|---|---|
refsetId | referencedComponentId (Referenced component) | attributeDescription (Attribute description) | attributeType (Attribute type) | attributeOrder (Attribute order) |
|
0 |
| ||||
1 |
| ||||
Table 52. Refset Descriptor rows for 900000000000531004 |REFERS TO concept association reference set| . |
|
|
|
| |
refsetId | referencedComponentId (Referenced component) | attributeDescription (Attribute description) | attributeType (Attribute type) | attributeOrder (Attribute order) |
|
0 |
| ||||
1 |
|
Note: The tables above omit the initial four columns of data present in the release file. These follow the standards versioning pattern id (field), effectiveTime (field), active (field), active (field). Additionally, to aid understanding, the tables above also show thefrom one of theassociated with each of the identified. The release file only contains the.
Association reference set example
The following table holds example entries for the |Replaced by| .
Table 53. Sample content from 900000000000526001 |REPLACED BY association reference set| . |
|
|
---|---|---|
refsetId | referencedComponentId (Association source component) | targetComponentId (Association target component) |
Note: The tables above omit the initial four columns of data present in the release file. These follow the standards versioning pattern id (field), effectiveTime (field), active (field), active (field). Additionally, to aid understanding, the tables above also show thefrom one of theassociated with each of the identified. The release file only contains the.
Feedback