1. Metafor Year 3 EU Review CIM Component Services

2. Of itself an Ontology is an inert artefact, i.e. a dictionary. CON-CIM Conceptual CIM

3. Tools & services, give it life, i.e. it becomes a language. APP-CIM Application CIM

4. What is the real world for the CIM?

5. Informational Eco-System SCIENTIFIC COMPUTING CENTRES (DN = DATA NODE) DN-1 (CCRT) DN-N (Meteo-France) DN-3 (CERFACS) DN-2 (IDRIS)... CORE (CMIP5+)OPERATIONAL (R&D) IPSL WEB SERVERS ESG GATEWAY (PCMDI) METAFOR (BADC) IS-ENES (DKRZ) IPSL COMMUNITY (Scientists, Researchers, Students) HTTPS / X509 HTTPS / OpenID HTTPS / X509 HTTPS / OpenID

6. What drives such an eco-system?

7. Supply & Demand

8. Supply Side FRENCH SCIENTIFIC COMPUTING CENTRES (DN = DATA NODE) DN-1 (CCRT) DN-N (Meteo- France) DN-3 (CERFACS) DN-2 (IDRIS)... DATABASE(S) PostGres, RDF-Triple ESG – GATEWAY DATABASE(S) eXist, PostGres METAFOR / IS-ENES WEB SERVICES (RESTful, AtomPub) IPSL DATABASE(S) PostGres XMLXML HTTPS / X509 XMLXML XML Base6 4 CORE (CIMP5)OPERATIONAL

9. Demand Side Max Planck Institute University of Cantabria IPSL WEB PORTALS (HTML / Javascript) DATABASE(S) PostGres, RDF-Triple ESG – GATEWAY DATABASE(S) eXist, PostGres METAFOR / IS-ENES WEB SERVICES (RESTful, AtomPub) IPSL DATABASE(S) PostGres JSON JSON / XML XML HTTPS / OpenID

10. How are we nurturing such an eco- system?

11. Supply Side CIM Web Services

12. Controlled Vocabulary RepositoryValidation Report Metafor CIM Web Services Publishing Ingest Search Advanced Simulations Basic Update Create Delete Retrieve Advanced Experiment Advanced Data Advanced Model Retrieve

13. CIM Web Services Test Consumers ● University of Cantabria ● KNMI

14. Supply Side CIM Tools

15. Demand Side CIM Web Portal (For Human Consumption)

16. CIMHome Overview Tools Viewer Differencing Validator Overview Animation Metafor CIM Web Portal Schemas News Controlled Vocabulary Publishing Registration History Search Advanced Unrestricted Roadmap Keyword

17. How are we implementing ?

18. Databases Technologies PostGres eXist XML Web Server Python Javascript User Interfaces HTML Web Services SOA Security X509 OpenID Ajax REST JSON XML Pylons Apache

19. Development Team

20. Mark Morgan (IPSL) Development Team Architecture User Interface Paul Slavin (Manchester) Validation Exist dB Allyn Treshanksy (BADC) CIM Ontology Gerard Devine (Reading) Viewer Hans Ramthun (DKRZ) TDS 2 CIM ISENES Handover XQuery Deployment Web Services

21. Process

22. June 2010 Agile Technique : Coding Sprints October 2010 Validation April 2010 Initial Web Services Portal UI Shell Solution Architecture Team Roles Assigned Objectives DefinedKeyword Search Basic Search UI CIM 2.0 ISENES Handover Roadmap Defined

23. Planned Release Dates May 2011 August 2011

24. Summary

25. ● Well defined solution architecture

26. Summary ● Well defined solution architecture ● Well defined individual & collective objectives

27. Summary ● Well defined solution architecture ● Well defined individual & collective objectives ● Development progress slowed early 2011

28. Summary ● Well defined solution architecture ● Well defined individual & collective objectives ● Development progress slowed by CMIP5 Questionnaire focus ● Development impeded by necessity of working with raw XML (i.e. xquery/xpath)

29. Summary ● Well defined solution architecture ● Well defined individual & collective objectives ● Development progress slowed early 2011 ● Development impeded by necessity of working with raw XML (i.e. xquery/xpath) ● Risk due to team members either leaving or not having time to commit

30. Summary ● Well defined solution architecture ● Well defined individual & collective objectives ● Development progress slowed by CMIP5 Questionnaire focus ● Development impeded by necessity of working with raw XML (i.e. xquery/xpath) ● Risk due to team members either leaving or not having time to commit ● Risk due to lack of CIM instances