Changes between Version 3 and Version 4 of RdsWipWorldView/PathsToInteroperability

Show
Ignore:
Timestamp:
09/02/08 01:01:23 (16 years ago)
Author:
jbourne (IP: 70.48.152.174)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RdsWipWorldView/PathsToInteroperability

    v3 v4  
    1414= RDS/WIP World View: Paths to Interoperability = 
    1515 
    16 There are also at least three common approaches to interoperability - these are outlined here, making analogy to human languages: 
     16The RDS/WIP has been conceived to support many different approaches to interopability.  The need for this is clear: the source of information ([wiki:RdsWipWorldView/ThoughtAndLanguage human thought and language]) uses generalization at many different levels for the same information, largely depending on the discipline and the need for precision. 
     17 
     18== Approaches == 
     19 
     20There are several approaches to interoperability - these are outlined here, making analogy to human languages: 
    1721 
    18221. Point to Point: translate directly from any language to every other 
     
    3034and way of thinking. 
    3135 
    32 The RDS/WIP provides support for all of these approaches.  In all 
     36== Support == 
     37 
     38The RDS/WIP must provide support for all of these approaches.  In all 
    3339cases, it provides a place to publish reference data for the language and mappings to and from other languages. 
    3440 
    35 Note however that the mappings themselves must be written in some sort of language, and in many cases, it is the expressive power of at least one of the addressed languages that determines how precise and fidelity-retaining a mapping can be. 
     41== Mapping Languages == 
     42 
     43Note however that the mappings themselves must be written in some sort of language, and in many cases, it is the expressive power of this language that determines how precise and fidelity-retaining a mapping can be. 
     44 
     45Yet, a mapping language can be (necessarily) reduced to specification just as well as any other language, and so, a mapping language itself must also be able to be recorded in the RDS/WIP, just as its rules must be.  
     46 
     47== Summary == 
     48 
     49The RDS/WIP needs to be neutral to many different types of interoperability and mapping language: capable of storing reference data in a highly generic manner and yet retaining the ability to make this information consumable by both automatons and humans. 
    3650 
    3751---- 
Home
About PCA
Reference Data Services
Projects
Workgroups