Review Feedback
For consideration, a Model Transformation (MT) rule to retain additional instances of child elements after flattening nested structures. This rule can be used with Alternative Encodings that support related child elements to avoid loss of data.
MT00X: (PROPOSED) Retain Additional Child Elements
Category
Simplification Rule
Description
The complex structure of model elements is reduced by applying Model Transformation rule MT001 “Flatten Nested Structures.” The derived flattened model structure in the parent level includes the first instance of nested child elements. When there is multiplicity greater than 1 in the child elements, additional occurrences of the child may be retained in a related structure.
UML Model
Not applicable (there is no single UML model that results from this transformation rule)
Original instance in default encoding
..
Transformed instance in default encoding
..
Model transformation rule
Parameters:
• separator: The character to use to separate the original property name from the type name of the components.
Solves usability issues
This rule, when combined with MT001 Flatten Nested Structures, establishes a simplified parent-child structure that may prevent loss of information given different use cases.
For example, if multiple occurrences of child elements are not present in the data then the completely flat structure of the parent (MT001) can be used alone with encodings, such as GeoJSON, as Alternative Encodings. In cases where multiple occurrences of children are present, the completely flat structure of the parent may only be used as Additional Encodings. In such cases where multiple occurrences are present, the simplified parent-child structure created when combining MT001 and this rule can be used with encodings that support related child elements, such as the default encoding, file geodatabase, or GeoPackage, as Alternative Encodings.
Known usability issues
None.
INSPIRE Compliance
Data transformed using this rule is INSPIRE compliant as long as there is no information loss from the source data.
Review Feedback For consideration, a Model Transformation (MT) rule to retain additional instances of child elements after flattening nested structures. This rule can be used with Alternative Encodings that support related child elements to avoid loss of data.
MT00X: (PROPOSED) Retain Additional Child Elements
Category Simplification Rule
Description The complex structure of model elements is reduced by applying Model Transformation rule MT001 “Flatten Nested Structures.” The derived flattened model structure in the parent level includes the first instance of nested child elements. When there is multiplicity greater than 1 in the child elements, additional occurrences of the child may be retained in a related structure.
UML Model Not applicable (there is no single UML model that results from this transformation rule)
Original instance in default encoding ..
Transformed instance in default encoding ..
Model transformation rule Parameters: • separator: The character to use to separate the original property name from the type name of the components.
Solves usability issues This rule, when combined with MT001 Flatten Nested Structures, establishes a simplified parent-child structure that may prevent loss of information given different use cases.
For example, if multiple occurrences of child elements are not present in the data then the completely flat structure of the parent (MT001) can be used alone with encodings, such as GeoJSON, as Alternative Encodings. In cases where multiple occurrences of children are present, the completely flat structure of the parent may only be used as Additional Encodings. In such cases where multiple occurrences are present, the simplified parent-child structure created when combining MT001 and this rule can be used with encodings that support related child elements, such as the default encoding, file geodatabase, or GeoPackage, as Alternative Encodings.
Known usability issues None.
INSPIRE Compliance Data transformed using this rule is INSPIRE compliant as long as there is no information loss from the source data.
Examples of this encoding rule
Other comments
Examples to be developed.