Presentation on theme: "Ecoinformatics International Technical Collaboration"— Presentation transcript:
1 Ecoinformatics International Technical Collaboration Technical Projects WorkgroupUpdateOctober 5, 2009Bruce BargmeyerLawrence Berkeley National LaboratoryTel:
2 Topics Introduction Current Activities Uses of terminology and Ontology
3 Ecoinformatics Cooperation Background Initiated about 1994Leverage resources of agencies with major health and environmental programs in their missionsEEA (and DG Environment, Research, Information Society)US Government--EPA, USGS, NSF, DOD, …Intergovernmental organizations (IGOs)--UNEPScientific research organizations—LBNL, JRCCooperate on standards and technology development, demonstration, deployment.EPA and EEA play leadership roleEvolving name: Initiated the use of term “ecoinformatics” for the participants: Interagency/International Cooperation on Ecoinformatics, Ecoinformatics International Technical Collaboration (EITC)Ecoterm group was created under umbrella of this group
4 Ecoinformatics International Technical Collaboration Purpose The following are major purposes for the projects and activities of the EITCShare experiences and resultsEstablish and foster an ecoinformatics marketplace and the pillars that will support it: common vision, standards, sharable designs and practices.Cooperate on emerging technologiesCooperate on key elements for interoperabilityCooperate on developing and deploying interagency/international environmental information systemsShare the costs and benefits of key elements for interoperationDemonstrate resultsPublicityTwo levels: Principals (top-level government) and technical-level workgroupsPrimary organizers William Sonntag (EPA) David Stanners (EEA)
5 Ecoinformatics Activities & Research Two kinds of activities:Advances/activities as part of current operations with internal agency resourcesEcoinformatics result: primarily technology transfer by sharing ideas.Activities requiring additional resources (contracts, research grants, …)Ecoinformatics result: technology transfer of ideas, research results, and tools/infrastructure.
6 Coordinate R&D in Ecoinformatics Share cost and benefits through coordination of US & EU (& Asia?) ecoinformatics R&DIdentify key advances needed at the core of ecoinformaticsSemantics management, semantics services, semantic computingTerminology web servicesIT support for indicators,…Demonstrate in ecoinformatics “Test Bed”Develop an “architecture” of advanced ecoinformatics technologies?Research, Development and Demonstration projects ranging from improvements in operations to strategic breakthroughs
7 Ecoinformatics Technologies Identify existing and emerging technologies useful for ecoinformatics, e.g.,Environmental data grids and computer gridsSemantic WebMetadata registriesXML registries and XML data exchangeTerminology systemsOntologyAddress earlier stages of technology adoptionStages of adoption are, e.g.: examine technology that is interesting, determine that technology is potentially useful, develop a prototype, implement a pilot, develop for broad deployment, deploy, operate as mature technologyShare costs and increase benefits of early stages
8 Ecoterm I Nee:1st Environmental Terminology Meeting 15-16 April 2004 in GenevaHosted by UNEP with programming support by EPA, EEA, JRC and USGS> 30 participantsParticipants included terminology developers, IT professionals, and those interested in multilingual issues from governments, intergovernmental organizations (especially UN agencies), scientific institutions, corporations and vendorsThis is the fifth meeting of the Ecoterm group. USGS support has done much to advance this group
9 Ecoinformatics Collaboration Current Activities Ecoterm activities (as updated at this meeting)EPA, EEA, UNEP collaboration with MicrosoftEEA – Microsoft Partnership AgreementEye on EarthUNEP – Microsoft MOUEPA, LBNL, Berkeley Water Center, Microsoft Research – R&D collaborationSciScope
10 Ecoinformatics Collaboration Current Activities Global Standards Array for InteroperabilityInitiated at the March 2009 EITC meeting in CopenhagenChallenge is to develop an interoperability solution for global environmental assessment, reporting and observations networksUsing the talent and expertise of the EITC as the forum and primary resource. EITC discussions resulted in an understanding that an array of global standards for the environmental information domain would do the most to further interoperability. This recommended array would be based on the best of current standards and approaches now adopted by the Ecoinformatics partners and standards currently in use by national, regional, global networks, communities of practice of portions of the environmental information domain and consensus processes like GEO.Draft scoping document under preparation Participants agreed to provide their initial thoughts on the starting list of standards that they believe would be potential constituent parts in the potential standards array.Next Telecon October 7, 2009
11 Ecoinformatics Collaboration Current Activities GEMET - GEneral Multilingual Environmental ThesaurusDeveloped as an indexing, retrieval and control tool.The basic idea for the development of GEMET was to use the best of the available multilingual thesauri. GEMET was conceived as a “general” thesaurus, aimed to define a common general language, a core of general terminology for the environment.Use widened to include INSPIRE and other new applicationsDiscussion beginning about how to extend GEMETUpdate tomorrow from Stefan Jensen
12 Ecoinformatics Collaboration Current Activities Cooperation with Earth Science Information Partners (ESIP) and GEOSSESIP Water Cluster ActivitiesEPA Office of Water - Water Quality Exchange (WQX)CAUHSI Activities – Water ontology development related to Hydroseek (Bora Beran) and potentially SciScopePotential for use of EPA OEI Substance Registry System (SRS) chemicals and other terminology related to waterGEOSS Related activities (in consultation with EPA/EEA/NASA/NOAA)Metadata registry and ontology standardsISO/IEC and families of standards
13 Current ActivitiesWater Information System for Europe, Shared Environmental Information SystemSPIRE - Semantic Eco-blogging; Aquatic Invasive Prediction, linked dataUSGS initiatives, NBII Metadata Catalog, Gap AnalysisEPA terminology and registry advancementsOffice of Research and Development + Office of Environmental InformationEcoinformatics Implementing Arrangement under US – EU Science and Technology Agreement- coordinated researchCo-operation and coordination with GMES, GEOSS, GEO - strengthening data integration and data exchangeWork with EEA and EPA to explore possible interaction with National Cancer Institute relating to caBIG approaches to interoperability of dispersed data.
14 Modeling, Ontology, Terminology ConceptConcept）“person”“Employee”EmployeeTerminologyTermSource: Hajime Horiuchi, Tokyo International University
15 Areas of Interoperability There are four areas of compatibility—an application must meet the guidelines in all four areas to be considered "caBIG Compatible:”Syntactic Interoperability1. Programming and Messaging InterfacesSemantic Interoperability2. Information Models3. Common Data Elements4. Vocabularies and OntologiesVocabulariesInformation ModelsAPIsCDEscaBIG: NCI cancer Biomedical Informatics Grid
16 Semantics for Data Management & Semantics Services – ISO/IEC 11179 (E3) Conceptual DomainAgentObject ClassChemopreventiveAgentValid ValuesCyclooxygenase InhibitorDoxercalciferolEflornithine…UrsodiolData Element ConceptChemopreventive AgentNSC NumberValue DomainNSC CodeClassification SchemescaDSRTrainingPropertyNSCNumberRepresentationCodeEVS=Enterprise Vocabulary Services. We talked about a Data Element being formed by a concept taking on a specific representation. In ISO terms this translates to the combination of a specific Data Element Concept and a specific Value Domain, you see this denoted in the middle of this chart by the yellow box outlined in red. caDSR administered items are backed by the use of externally defined terminologies and controlled vocabularies. With UMLS as a framework NCI has developed vocabulary services that are accessed via API – application to application interfaces – to provide touch points during creation of content, resulting in administered components that are bound to immutable concept codes. These touchpoints, denoted by the EVS logos, are currently implemented at the Object Class, Property, Representation Term, Value Domain and Valid Value levels of the metadata model.Data ElementChemopreventive Agent NameContextcaCOREEnterprise Vocabulary Services (EVS) Concepts Unite NCI MDRSource: Denise Warzel, National Cancer Institute
18 Acknowledgements Thanks to: Yangfan HE, Wuhan University Gail Hodge, IIA/USGSHarold Solbrig, Mayo ClinicDenise Warzel, NCIThis material is based upon work supported by the National Science Foundation, under Grant No , by USEPA, and by NCI. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation, NCI, or USEPA.