Version 5 (modified by jbourne, 16 years ago) |
---|
TracNav menu
-
RDS/WIP project
- RDS/WIP Introduction
-
RDS/WIP World View
- Models, Data & Meta-Data
- Paths to Interoperability
- Automated Mapping
- Thought and Language
- Coarse to Fine
- Fine to Coarse
- Template Methodologies
- Choice of System
- Conclusions
- RDS/WIP Sample Queries
- RDS/WIP Staging Diagrams
- RDS/WIP 1.0 Plan
- RDS/WIP 1.0 Testing
- RDS/WIP 1.0 Process
- RDS/WIP 1.0 Inventory
- RDS/WIP 2.0 Plan
- RDS/WIP ID Generator
- RDS/WIP Domain Proposal
- RDS/WIP Requirements Table
- RDS/WIP Use Case: Discrete Editing
- RDS/WIP Use Case: CSV Upload
- RDS/WIP 1.0 General Use Cases
- RDS/WIP 2.0 General Use Cases
- RDS/WIP ISO 15926 Template Definitions
- RDS/WIP OWL/RDF Definition
- RDS/WIP OWL/RDF Project Plan
- RDS/WIP Forums
-
External
- RDS/WIP Use Case: Bulk Upload
POSC-Caesar FIATECH IDS-ADI Projects
Intelligent Data Sets Accelerating Deployment of ISO15926
Realizing Open Information Interoperability
Template Methodologies
N-ary relations, that is "templates" in ISO 15926 parlance, can be defined using a wide variety of different approaches. When such an approach takes the form of a systemic process, we call it a "methodology".
The Purpose of a Methodology
The likelihood of two different templates working well together in any given scenario is much higher for those templates that have been generated using the same methodology.
In general this is the very purpose of a methodology: to create a set of templates that work well together to solve some interoperability problem.
Retain the Record of Methodology
Because multiple methodologies can be used to create definitions in the same modeling system, it is crucial to record the methodology that created a definition, and any other methodologies it has been proven for.
This allows the selection of a cogent, orthogonal set of definitions to solve a specific interoperability problem using a given modeling system. That is to say, the intersection of modeling system and methodology together select the working set of definitions.
Coarse-to-Fine Approach
The Coarse-to-Fine approach takes information and models it in its extant form (as it is exposed from language, data or usage). It then breaks down those "coarse" relations into finer relations to the depth required to address a specific problem set.
Fine-to-Coarse Approach
The Fine-To-Coarse approach seeks to model information from a set of founding principles. These principles determine a starting set of finely-grained relations from which successively coarser and coarser sets of relations are built, until (perhaps) relations that are generally useful for solving specific problem sets can be reached.
The Reach of a Methodology
Coarse-to-fine approaches have a tendency to be more neutral to a modeling system - the shallower the coarse-to-fine approach (that is to say, the coarser the concepts) the more neutral it tends to be. This allows very shallow coarse-to-fine methodologies to be applied across different systems.
Fine-to-coarse approaches are (by definition) founded on a specific modeling system, and so these methodologies are generally confined to a single modeling system.
@todo notes to incorporate/explore included as comments