| 7 | | • Interaction with the Component Registry such that the user can use its particular views to select components for processing in the editor. |
| 8 | | • Creation of a new metadata component as a flat list of metadata elements. The metadata element is a name/value pair whereof he value can be of a specific type and adheres to a scheme that is also documented in the schema. Metadata element value constraints can be dependent on the value of other metadata attribute. The choice of a value from a Controlled Vocabulary (CV) for one metadata attribute leads to a different CV for the dependent attribute. In other words the CVs can be coupled. To not complicate matters we assume that this dependency can only take place between attributes in a single list component. An element or list can also be an existing metadata component from the registry. For semantic interoperability every element and component must have a reference to a concept registry. See Figure 1 for a UML diagram of a metadata component. Every aggregated metadata element and component should have an attribute specifying its cardinality in the metadata description: 0-1, 1, 0.., 1.. |
| 9 | | • Modification of an existing component by adding new metadata element(s) or deleting elements or components, creating a new component. Initially there will be no versioning of components so every modified component is a new one. |
| 10 | | • Combination of two or more components creating a new component. |
| | 7 | * Interaction with the Component Registry such that the user can use its particular views to select components for processing in the editor. |
| | 8 | * Creation of a new metadata component as a flat list of metadata elements. The metadata element is a name/value pair whereof he value can be of a specific type and adheres to a scheme that is also documented in the schema. Metadata element value constraints can be dependent on the value of other metadata attribute. The choice of a value from a Controlled Vocabulary (CV) for one metadata attribute leads to a different CV for the dependent attribute. In other words the CVs can be coupled. To not complicate matters we assume that this dependency can only take place between attributes in a single list component. An element or list can also be an existing metadata component from the registry. For semantic interoperability every element and component must have a reference to a concept registry. See [wiki:TitleIndex Figure 1] for a UML diagram of a metadata component. Every aggregated metadata element and component should have an attribute specifying its cardinality in the metadata description: 0-1, 1, 0.., 1.. |
| | 9 | * Modification of an existing component by adding new metadata element(s) or deleting elements or components, creating a new component. Initially there will be no versioning of components so every modified component is a new one. |
| | 10 | * Combination of two or more components creating a new component. |
