1. ANVIL – A Rough Idea Martin Ford – ISLinkup (for GEOBASE + OGCE Team)

2. Traditional Levels of Interoperability 1 – Hardware Layer Stable interoperability between hardware platforms more or less achieved 2 – Software Layer Appearance of platform independent software is permitting increased interoperability within programs 3 – Semantic Layer Big Problem! As there are no recognized standards for terminology, metadata……..

3. ANVIL Levels of Interoperability 1 – Hardware Layer 2 – Software Layer 3 – Semantic Layer 4 – ANVIL Modelling Layer

4. Modelling Interoperability Standards: International Regional National Use Case Scenarios Data Schema Data Set Metadata Set DataTesting Software Semantic Management (thesaurus, gazetteer) (functional description) Modelling Interoperability

5. Data, Metadata, Data Schemas, Semantics (1) –It is necessary to determine if a given Software can handle a given Data Schema e.g. there are schemas (public surveying) in Germany which cannot be handled by all commercial GIS Metadata in general can also be treated like other Data Schemas (e.g. ISO 19115) Since data schemas are also a subject for standardization (e.g. ISO 19115 and all InsDOM domain models), ANVIL may also be used to test the usability and implementation aspects of a given data schema

6. Data, Metadata, Data Schemas, Semantics (2) –Specific data sets must be concurrently tested with the corresponding metadata sets To determine whether a given Software can handle not only the schema but also the given types of data (e.g. aerial photos, vector, raster, etc.) In order to test data integration capabilities a semantics module (thesauri, gazetteers, glossaries, functional constraint descriptions, etc.) must be tested

7. The Rough Idea Create model “plug-ins” (components) for: –Use Case Scenarios –Standards –Semantics –Test suites –Cultural and linguistic adaptability –Other areas software interoperability is required Create Framework Model –To allow the “plug-ins” to fit according to requirements

8. Interop Hub SDOs Web Information System Vendor Direct Access (Industry or Consortia) Vendor Independent Testing (Universities or Other) Testing Station Testing Station Testing Station Testing Station Vendor A Vendor B Vendor C Vendor D Modellers (Use Cases) Test Providers SDIs CLAs SAs DP Commercial UsersGovernment Interest Groups Vendor Self- Testing ANVIL Rough Idea

9. The Virtual Laboratory Establish a secure server to: –Test against “plug-ins” –Act as an information gateway for providers –Act as a hub for locally stored data and information –Act as testing platform for potential users or investors

10. Testing Phase: Part I Self Test Company “A” can retrieve applicable self testing software from the Web to produce a report of what is interoperable and what is not with their products in specific markets IDL test code can be produced from the interoperable model

11. Testing Phase: Part II Test Stations Requires a self test certificate first Testing Stations established around Europe offering independent testing –(e.g. Universities, other independent institutions) Company “A” can utilize the testing station of the country in which they plan to offer their product in order to conform with local laws and standards Reports (testing results) will be available

12. Testing Phase: Part III Direct Access Allow Direct Access to ANVIL if: –Successfully completed self test; and –Successfully completed independent testing (according to the local specifications in at least one country) Value to software vendor: –Allows the testing of interoperability between products such as Web-based Test Beds –Acts as a showcase –Higher certification

13. ANVIL Management: Technical Management Team To run ANVIL a permanent team will need to be established: –Modellers –Programmers –Domain experts –Testers –A core of “remote members” will also be needed for virtual input

14. ANVIL Management: Information Management Team To run the Web-based service for self certification and storage of test software additional teams will be needed: –Web Designers –Marketing

15. ANVIL Management: Web Information Service To complete ANVIL, an interactive Web-based information service will need to be set up to provide: –4 th, 5 th and 6 th Framework project information –Free software and test suites –Free Use Case Scenarios –Discussion forum –Virtual committee for technology convergence –A “Technology Watch” to report on the interoperability testing –Future submission framework interpretation

16. Web Information Service Those participating will include: –Commercial –Government –Users –Interest Groups –Universities –SDOs and SDIs –Investors?

17. ANVIL – Summary ANVIL tests for interoperability against an interoperable plug-in model ANVIL provides a forum to allow users and vendors to get together and work towards common goals ANVIL offers 3 levels of testing (Self Test, Independent Test, and Direct Access)

18. ANVIL – Summary Certification requirements will help the take-up of ANVIL ANVIL will attract the Geospatial vendors first. GIS vendors are mainly selling to other businesses or local authorities.

19. ANVIL – Summary Meanwhile, many Geospatial vendors are developing mobile communication services. Mobile phone service vendors are selling to the consumer and do not require certification. The GIS market may attract the mobile phone vendor to the GIS certification process The access to readily available test software will also help

20. ANVIL – Summary Neither market will reach critical mass for testing interoperability without economic rationale and their belief that they need this program to succeed. This Rough Idea needs to be developed; the Window of Opportunity is closing. We also need major corporate and government recognition and cooperation in order to succeed.