﻿<?xml version="1.0" encoding="utf-8"?>
<etgov:EmergingTechnology xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:etgov="www.cio.gov/AIC/ETgov/">
  <etgov:ComponentDetails>
    <etgov:ComponentName>Energy Water Nexus</etgov:ComponentName>
    <etgov:XMLGenerationDate>2010-01-17</etgov:XMLGenerationDate>
    <etgov:ComponentType>Software</etgov:ComponentType>
    <etgov:ComponentDescription>For the "Ontology Summit 2010", construct a Case Study that builds an ontology with the focus on a tipping point of three tightly entangled strategic goods - the Energy (i.e., Physical Fuel Cycle) - Water Nexus vis-a-vis the Climate</etgov:ComponentDescription>
    <etgov:GovernmentBenefits>This is an effort to create the Case Study on: "Energy - Water Nexus vis-a-vis the Climate", based on the theme of the Ontology Summit 2010. 
The theme is “Creating the Ontologists of the Future” and is dedicated to discussing and defining a systematic approach to training and ensuring the quality of the next generation of ontologists. You can read more about the summit at http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2010. (note: it is already underway as a 3-month discussion, and will finish in mid-March at a 2-day event at the National Institute of Standards and Technology in Gaithersburg, MD, USA.) 





Discussions between the Summit’s organizers have identified the need for good case studies. Focusing any new case study on an important topic would logically lead to intelligent discussions and movement toward solutions of problems/issues associated with the topic. In this case, the focus is not just on a single strategic good, such as Energy or Water, or on Climate Change, but on the nexus of the three: the Energy-Water Nexus vis-a-vis the Climate. Supporting the development of this case study will support the Summit's goal by making sure that the resulting ontology functions in a way that meets your requirements. 





For subject matter and policy folks who are not familiar with ontologies, let’s just say they are an important/vital emerging technology in computer science that uses relationships and metadata in Knowledge Management. Your subject matter knowledge is important – you can define the relationships between the various aspects of the subject being considered.




Building bridges to network "Policy" (on the three subjects) to associated knowledge requires involving computer-based, trusted, ontological approaches that combine computer semantics, metadata, human intelligence and linguistics. To begin with, on the Enterprise Architecture side we have a specific Formal Information Model (FIM) in the form of the Physical Fuel Cycle graphic. This becomes the Graphic Face of the Cube (GFC). But Layers and cells behind the GFC (and, of course, the interoperable Relationships associating each, every, and all of these) need specification and standardization. 





This case study is currently an open but slightly moderated process intended to have a rapid organic growth through Google Docs (acct name: EnergyWaterNexus@gmail.com ; pwd: ontology2010 ). You can add yourself to the Google Docs editors list, or I can do it for you. You will find the FIM /GFC in a pdf at this site. In addition, I expect that shortly there will be a CIM3 interface for blogging and conferencing – which will also document the process as we construct the Case Study. This will contribute to the development of a more robust and open set of Standards for Ontologies.




While a beginning of this hyperlinked data cube has been constructed, and a master file is available for expansion into a robust operational ontologically-driven knowledge management network covering all aspects of the physical fuel cycle, water systems, and the climate (whether it changes in character or not) – this does not mean the beginning represents the way to build an ontology. We are open to suggestions. But please keep in mind that we don’t have much time to do this, and there is a need to stay focused.

We hope you will accept our invitation – all we ask for is your attention and involvement when you feel that you can contribute to the discourse. If you are interested in participating, please let me know. If you are interested in observing how this unfolds, there is sufficient information in this email to allow you to do so. Or if you have extraordinary colleagues who relish the subjects or this particular technology, please forward this to them. 




ET.gov is functioning to focus attention on this Case Study (as described in XML at: http://ambur.net/et/EnergyWaterNexus.xml ). 


</etgov:GovernmentBenefits>
    <etgov:Categorizations>
      <etgov:Categorization etgov:categorizationScheme="FEA">
        <etgov:ServiceReferenceModelInformation>
          <etgov:ServiceType>Knowledge Management</etgov:ServiceType>
        </etgov:ServiceReferenceModelInformation>
        <etgov:TechnicalReferenceModelInformation>
          <etgov:ServiceArea>Service Interface and Integration</etgov:ServiceArea>
          <etgov:ServiceCategory>Interoperability</etgov:ServiceCategory>
          <etgov:ServiceStandard>Data Transformation</etgov:ServiceStandard>
          <etgov:ProposedSpecification>Ontological Associations and Operators</etgov:ProposedSpecification>
        </etgov:TechnicalReferenceModelInformation>
      </etgov:Categorization>
    </etgov:Categorizations>
  </etgov:ComponentDetails>
  <etgov:OrganizationAndRepresentativeDetails>
    <etgov:OrganizationDetails>
      <etgov:OrganizationName>Energy-Water Nexus</etgov:OrganizationName>
      <etgov:WebAddress>http://eeck.us http://docs.google.com/fileview?id=0BzLPIOUuPgpwMzI1NzkzMTctM2FjMy00OWQ4LTkyM2ItOTJkZmQxZTkxNjY0&amp;hl=en</etgov:WebAddress>
      <etgov:OfficeDetails>
        <etgov:TelephoneNumber etgov:telephoneNumberType="Phone">540-522-9407</etgov:TelephoneNumber>
        <etgov:OfficeAddressDetails>
          <etgov:StreetName>507 13ths St SE</etgov:StreetName>
          <etgov:City>Washington</etgov:City>
          <etgov:StateOrProvinceCode>DC</etgov:StateOrProvinceCode>
          <etgov:CountryCode>UNITED STATES</etgov:CountryCode>
          <etgov:PostalCode>20003</etgov:PostalCode>
        </etgov:OfficeAddressDetails>
      </etgov:OfficeDetails>
    </etgov:OrganizationDetails>
    <etgov:RepresentativeDetails>
      <etgov:FirstName>Jim</etgov:FirstName>
      <etgov:MiddleInitial />
      <etgov:LastName>Disbrow</etgov:LastName>
      <etgov:ElectronicMailAddress>jim@eeck.us</etgov:ElectronicMailAddress>
      <etgov:RepresentativeAddressDetails>
        <etgov:StreetName>507 13th St SE</etgov:StreetName>
        <etgov:City>Washington</etgov:City>
        <etgov:StateOrProvinceCode>DC</etgov:StateOrProvinceCode>
        <etgov:CountryCode>UNITED STATES</etgov:CountryCode>
        <etgov:PostalCode>20003</etgov:PostalCode>
      </etgov:RepresentativeAddressDetails>
    </etgov:RepresentativeDetails>
  </etgov:OrganizationAndRepresentativeDetails>
</etgov:EmergingTechnology>
