Semantic eScience Meeting June 15, 2012

Printer-friendly version

Welcome to TitanPad!

General Meeting Information




  • Massimo
  • Patrick
  • Deborah
  • Stephan

Past Action Items

Action Items

  • Patrick and Massimo will get together later today to discuss ECOOP



  • Project page
  • Use Cases Page
  • Use Case
  • Conceptual map :
  • ontology development :
  • related rpi project :
  • Ipython notebook : (password: geohab ; notebook: ECO-OP)
  • GUI prototype :
  • Andrew is wanting a web-based GUI instead of a desktop application
  • iPython Notebook is too complicated for people to use
    • Users are used to using (HA) matlab, R, IDL, and other utilities
  • patrick says he has seen the use case, where is the use case?
    • Sounds like there is a picture of a white board, but that's about it.
    • No document anywhere that describes what the admin interface is supposed to do
    • No document anywhere that describes what the user should be able to do

(there is a 2 slides pdf to be showed to the noaa group at the end of june that becomes with the video demo, a file is attached to the ecoop mailing list)

  • This is a throw-away prototype

"Also called close-ended prototyping. Throwaway or Rapid Prototyping refers to the creation of a model that will eventually be discarded rather than becoming part of the final delivered software. After preliminary requirements gathering is accomplished, a simple working model of the system is constructed to visually show the users what their requirements may look like when they are implemented into a finished system."

"Rapid Prototyping involved creating a working model of various parts of the system at a very early stage, after a relatively short investigation. The method used in building it is usually quite informal, the most important factor being the speed with which the model is provided. The model then becomes the starting point from which users can re-examine their expectations and clarify their requirements. When this has been achieved, the prototype model is 'thrown away', and the system is formally developed based on the identified requirements."

SUMMARY:-In this approach the prototype is constructed with the idea that it will be discarded and the final system will be built from scratch. The steps in this approach are:

  1. Write preliminary requirements
  2. Design the prototype
  3. User experiences/uses the prototype, specifies new requirements
  4. Repeat if necessary
  5. Write the final requirements
  6. Develop the real products

  • Time frame
    • demo is end of this month
    • ECOOP is a two year project
    • First phase is to generate a demonstration
    • Later we develop information model, ontology, add semantics, etc...
    • No timeline yet
    • Massimo has started an concept map for DPSIR

stephan is helping to build a use case for data integration with colleagues at usgs
been able to get a use case together and to start information modeling in 2 weeks.
probably start off with a vertical prototype
what minerals have been discovered up stream from certain fish populations
looking for correlations between certain chemicals

mineral is coming from MRDATA

stephan coming in mondayish morning a little before 10am (deborah also flying in on monday - around 1:30)

cdi group within usgs put together a semantic web working group
community for data integration

stephan will do an update to stom.
simon has done an update to O&M ontology
stom - vsto o&m integration
trying to use auto documantion of ontologies