1. A data flow approach to interoperability By Arve Meisingset

2. Purpose 1.Provide a generic architecture of one system Not (p) and (¬ p) within one system 2.Provide a methodological basis for architecture specifications Mappings between data (format), not function blocks

3. Program: (X-3)*2+(Y+1) X3Y ? ? -+1 uw * 2 v + Z x y x y 1a

4. Control: (X-3)*2+(Y+1) 3 ? ? -+1 * 2 + x y x y 1b

5. Data flow: (X-3)*2+(Y+1) X3Y -+1 uw * 2 v + Z 1c

6. Precedence graph: (X-3)*2+(Y+1) (X-3)*2+(Y+1) X3Y Z 2a

7. Precedence graph: as relations between data only (X-3)*2 +(Y+1) X3Y Z (X-3)*2 +(Y+1) Functions as subordinate (algorithmic) methods Generic processes 2c

8. Schema input schema output 3a Generic processor enforcing data instances according to Schema of data classes

9. Instances input schema output 3b Two-way transformations internal data instances processors

10. Population schema 3c Reading and writing in population processors population

11. External and Internal Schemata schemata 4 External and Internal populations populations ES IS EP IP

12. Central Application Schema schemata 5 populations ES IS EP IP AS AP

13. Three Schema Architecture i.e. a compiler architecture for data transformation System schema 6 ESIS IP AS APEP System population System processor IrArEr ILALEL

14. Data Transformation Architecture Application schema 7 IP TrOrTr Internal schemaExternal schema CrLrPrDr TSOSLSCSTSDSPS System schema TPOPCPTPDPPPLP Internal processorApplication processorExternal processor

15. Data Flow between Layers 8 LS CS LSTSOS TS DS PS DS Application schema enforcement of terminologies and consistency Presentation schema PS IP All data may not be transformed to the concept form

16. Candidate interfaces Lr LS Cr CS Cr CS Tr TS Li Tr TS Dr DS Tr TS Or OS Or OS Tr TS TiOiTiDiCi Transformation between different data within processes Communication of same data between processes Therefore, implementation processes (yellow) are dual to the schema architecture (pink) 9 communication transformation

17. Nesting 10 Schema access to end user help Processor Meta schema Database Developer & system manager End user

18. Code generation 11 Executable code code generation Processor IS Database Developer & system manager End user Dictionary Database of schemata ESASIS Meta schema

19. Bootstrapping 12 Executable code Processor Database Developer & system manager End user Executable code Processor Dictionary database Executable code Processor Tool specification Tool developer

20. The Schema Cube tD pLpCpOpTpDpTpPlLlClOlTlDlTlP dL tL oL tL cL End user view Developer & system manager view plP Tool developer’s view 13

21. Example tD pLpCpOpTpDpTpP lLlClOlTlDlTlP dL tL oL tL cL X.11BER Presentation of dictionary data to developer The notations are placed in a two dimensinal grid

22. Reguirements tD pLpCpOpTpDpTpPlLlClOlTlDlTlP dL tL oL tL cL for the seven schemata and mappings between them and different requirements for different media

23. Approaches to architecture Control flow Data flow Precedence graphs Data transformation Nesting

24. Usage ? Focus of SG17 ?

25. Future work Development of RM 1. other candidate reference models, 2. criteria and perspectives of reference models, 3. comparisons with other reference models, such as the ODP, Use of RM 4. requirements for each element of the reference model, 5. each notation has to be evaluated for use in each element of the reference model, 6. a map has to be developed on the combined use of notations.