| | 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 | = RDS/WIP World View: Paths to Interoperability = |
| | 15 | |
| | 16 | There are also at least three common approaches to interoperability: |
| | 17 | |
| | 18 | 1. Force everyone to speak your language natively. That |
| | 19 | means push ISO 15926 definitions out into every software |
| | 20 | application that counts in your domain and force software |
| | 21 | |
| | 22 | developers to adapt to its structures and way of thinking. |
| | 23 | |
| | 24 | 2. Translate from your language to every other language that |
| | 25 | you need to. Costly for everyone and a problem that I |
| | 26 | think ISO 15926 was conceived to redress by the former |
| | 27 | or the latter options. |
| | 28 | |
| | 29 | 3. Collectively identify a language as usefully common and |
| | 30 | translate only to and from it. And again, ISO 15926 has |
| | 31 | a role to play here as that common language. |
| | 32 | |
| | 33 | What I think is important though, is that for the latter |
| | 34 | the *cost* of translating peer to peer or peer to common, |
| | 35 | by investing in definitional machinery that can then be |
| | 36 | used to create a cheap, strong translation engine. |
| | 37 | |
| | 38 | If we take the top-down approach and run it to its |
| | 39 | conclusion right down at the FOL level on existing |
| | 40 | templates, and |
| | 41 | |
| | 42 | In one case, you force everyone to speak your language. |
| | 43 | |
| | 44 | |
| | 45 | |
| | 46 | |
| | 47 | |
| | 48 | |
| | 49 | |
| | 50 | ---- |
