| | 1 | {{{ |
| | 2 | #!comment |
| | 3 | NB! Make sure that you follow the guidelines: http://trac.posccaesar.org/wiki/IdsAdiEditing |
| | 4 | }}} |
| | 5 | |
| | 6 | [[TracNav(TracNav/RdsWip)]] |
| | 7 | [[Image(wiki:IdsAdiBranding:Logo-128x128.gif)]] |
| | 8 | = POSC-Caesar FIATECH IDS-ADI Projects = |
| | 9 | == Intelligent Data Sets Accelerating Deployment of ISO15926 == |
| | 10 | == ''Realizing Open Information Interoperability'' == |
| | 11 | |
| | 12 | ---- |
| | 13 | |
| | 14 | = Conclusions = |
| | 15 | |
| | 16 | The RDS/WIP can be used to hold reference data for many different systems and within each system, for many different methodologies. This richness is intentional and desirable because interoperability problems exist with different degrees of necessary fidelity, breadth of content, paths to standardization and time to delivery. |
| | 17 | |
| | 18 | By analogy, there was no need to delay the creation of the steam engine just because fluid mechanics was not yet fully understood; but you don't want to go firing neutrons at a lump of plutonium without having a grasp of nuclear physics. |
| | 19 | |
| | 20 | This richness makes it incumbent on the user to limit themselves to the right set of reference data and the right approach to solve their interoperability problem. |
| | 21 | |
| | 22 | == Simple, Low-Fidelity Integration == |
| | 23 | |
| | 24 | At its lowest level, informal templates in any system backed by linguistic methodology may be sufficient to create a useful point to point integration. |
| | 25 | |
| | 26 | == Complex, High-Fidelity Integration == |
| | 27 | |
| | 28 | On the other hand, if the task was a high fidelity integration across many live data systems dealing with users of different disciplines then it would be necessary to select a reference data set to use as a lingua franca. That reference data set would require a mapping language that had sufficient richness to address the ''union'' of the data systems involved. The high fidelity requirement would in turn select methodologies that were fine-to-coarse, rather than coarse-to-fine. |
| | 29 | |
| | 30 | == Practical Route == |
| | 31 | |
| | 32 | In practice, the best solution is probably not going to be available at the project outset; and so the choice might be made instead to accept an initial reference data set with a coarse-to-fine methodology, but in a system that has a fine-to-coarse methodology and a powerful mapping language available. The intent of this approach would be to accommodate a smooth migration towards the better solution over time. |
| | 33 | |
| | 34 | ---- |
