| | 1 | {{{ |
| | 2 | #!comment |
| | 3 | NB! Make sure that you follow the guidelines: http://trac.posccaesar.org/wiki/IdsAdiEditing |
| | 4 | }}} |
| | 5 | |
| | 6 | [[TracNav(TracNav/IdsAdi)]] |
| | 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 | = Models, Meta-Data and Data = |
| | 15 | |
| | 16 | The convention when modeling information is to divide |
| | 17 | it into model and data, where the model is the schema that |
| | 18 | governs the form of the data and against which it can be |
| | 19 | validated. |
| | 20 | |
| | 21 | == Early Binding == |
| | 22 | |
| | 23 | The temptation when implementing a system is to embed |
| | 24 | all knowledge of the model in the system, but to leave the |
| | 25 | data free. The problem with this approach is that it does |
| | 26 | not allow transmission of models, only transmission of data. |
| | 27 | We term these kinds of system "early-binding" which means |
| | 28 | that they deal with a fixed model. |
| | 29 | |
| | 30 | == Late Binding == |
| | 31 | |
| | 32 | In contrast, in a collaborative reference data library, no |
| | 33 | system can truly embed all knowledge of the model, because |
| | 34 | the model is always expanding. This means that sometimes, |
| | 35 | model needs to be transmitted as data. We term these kinds |
| | 36 | of system "late-binding", which means broadly that they can |
| | 37 | deal with ad-hoc structures. |
| | 38 | |
| | 39 | == Meta-data is Data == |
| | 40 | |
| | 41 | To take this a step further, in order to validate data against |
| | 42 | a model in a late-binding system, all of the meta-data about |
| | 43 | the described structures also needs to be transmitted as data. |
| | 44 | |
| | 45 | These leads us to the conclusion that meta-data and models are |
| | 46 | also just data, and since a machine needs to embed knowledge |
| | 47 | about the structure and meaning of data in order to process it, |
| | 48 | we are therefore well situated by representing all data in |
| | 49 | the same way - models and meta-data look just like data to the |
| | 50 | machine. |
| | 51 | |
| | 52 | == The Role of RDF == |
| | 53 | |
| | 54 | For the RDS/WIP we have chosen RDF as the common representation |
| | 55 | because it reduces all information to simple statements of |
| | 56 | exactly the same form. |
| | 57 | |
| | 58 | |
| | 59 | |
| | 60 | |
| | 61 | |
| | 62 | |
| | 63 | |
| | 64 | ---- |
