A Data Specification Framework for the Foundation Spatial Data Framework

ion Adjacency A vertical mapping must cross one and only one vertical boundary. This ensures that there is just one level of abstraction between two mapped elements. Derivation, Transformation Binary Elements A mapping must be binary meaning there must be two and only two endpoints defined. This ensures that there is not complexities such as splitting and merging elements. Binding, Annotation No cycles A series of mappings must not result in any circular references. This ensures that a dependent model can be removed without collapsing the model ecosystem. Binding, Derivation, Transformation NonReflexive An element cannot be mapped to itself. This ensures that the mapping is relating two distinct elements in the model. Binding, Derivation, Transformation, Annotation The following matrix describes the models based on two orthogonal dimensions: level of abstraction on the vertical axis and model governance on the horizontal axis. The key phases of the process and the key models produced in these phases are shown on the y axis and the model governance level on the x axis. Table 4 Model matrix showing the level of abstraction and model governance Standards Core (Common) Thematic Conceptual Requirements Placeholder for requirements that describe the standards. Core canonical requirements, naming and versioning requirement. Requirements for a theme. e.g. the gazettal rules that apply to gazetteers in the FSDF Place Names Theme. Use Cases Placeholders that describe the use case. Core canonical use cases. Use cases for a theme.