One suggestion at METIS 2013 was to include relationships in the glossary.
One could use rules like: always include inheritance and subtypes, consider including components and aggregates, can include other associations.
Alternatvely one could have always mention the nearest neighbours of any information object in the explanatory text.
Description of the relationships should include the text and notation of the UML diagrams and these should be maintained in a consistent fashion.
If the UML text on the association doesn't work in the glossary, then the UML text should be changed.
| # | Term | Action |
|---|---|---|
| Data Point | No attributes Mandatory relationship to unit?! | |
| 10 | Representation (to be renamed to Presentation) | No attributes |
| 4 |
| Need to make it a subtype of Business Service Review relationships and attributes (there are no attributes) |
| 4 | Business Service | Need to make Dissemination Service a subtype Review relationships and attributes |
1 16 | Unit Type | review proposed relationships and attributes add relationship to logical record |
| 13 | Unit | review relationships and attributes following removal of subtypes |
| 13 | Population | review relationships and attributes following removal of subtypes |
| 28 | Business Process and Process Step Instance | relationship between these objects? |
| 30 | Question and *Multiple Question Item (to be removed) | Pending outcome of 35, these will become subtypes of a new abstract question object |
| 36 | Exchange Channel | Following removal of subtypes, need to implement relationship changes |
| 11 | ||
| # | Term | Action |
|---|---|---|
| #8 | Level | Add new diagrams to include Level in the next release |
| #21 | Classification Version | Remove |
| Classification Variant | Remove | |
Classification (Classification Series), Classification Scheme(Statistical Classification) | Revise relationships according to proposal | |
| #26 | Index (Classification Index) Index Entry (Classification Index Entry) | Ensure only have relationships to Classification objects and not to nodesets. |
| object | issue |
|---|---|
| Data Point | Mandatory relationship to unit but data point is abstract? |
| Enumerate Value Domain | Relationship to Code List described as "is" - should be something like "takes value from" |
Variable Represented Variable Instance Variable | Currently all reference a concept, population. Do they all need these relationships? |
| Rule | Text says that there should be a self referential relationship (nested rules) but there is no relationship |
Attributes Table (did not have permission to add it in the Attributes Page: please move)