SESF Project Meeting Notes

From Semantic Portal Wiki

Semantic eScience Framework

Project Information

Presentations Glossary

Project Organization

Meeting Notes Scheduled Milestones Working Groups Project Members

Design

Use Cases Functional Requirements Non-Functional Requirements Design Documents Architecture Documents Technology Infrastructure

SESF Meeting May 11, 2010

Attendees

• Peter Fox
• Patrick West
• Cynthia Chang
• Stephan Zednik

Action Items

• Begin work with working groups
  • organization

Notes

• Assessing the current deployment
  • technology infrastructure
  • current ontology
  • clarification on use cases
  • looking at the requirements, functional requirements
• Use Cases
  • Ontology
  • client use cases
  • domain use cases
    • VSTO domain
    • SESDI
    • BCO-DMO
• Ontologies
  • Portal Ontology
  • Framework Ontology
  • Domain Ontology
• Software Design needs to be modular component based
  • Can handle anything from sophisticated pre-computed inference rules to simple SPARQL queries
  • Depends on the community where the framework is deployed

Three Components

• each will have a design document

1. Use Cases
2. Ontology
3. Software Design

Function Requirements

• metrics
• log
• reporting
• administration
• auth n/z
• provenance (2nd iteration)

Working Groups

• triples (Cynthia)
• facet (Shangguan/Patrick)
• ontology modularization (Eric)
• rendering types (Patrick)
• interaction/input
  • Block Head Publication (aka Charlie Brown Publication) (Patrick)
  • Human Flesh Input (aka Zombie Input) (DLM)
• Ontology Language Encoding Evaluation (Eric)
  • OWL 2 - XL
  • SKOS
  • RDFS
• Domain Ontology Refactor (See c) (Eric)
  • eg OEM
• Ontology Tool Development
  • Protege
  • CMAP
• Methodology write-up - best practices
• Java code generation (was Protege, ELMO?) (Stephan)
• Evaluate OPeNDAP return as RDF and/or OWL (Patrick)

Design

• Technology Infrastructure Design (Cynthia)
• Architecture Design (Stephan)
• Ontology Design (All)
• Configuration Design
• Use Cases (Patrick

Schedule

• May
  • Till end of May, Preliminary Workgroup activity -> Preliminary design content
• June
  • IPAW 15-17
  • Semtech 21-25
• July
  • By end of July, Active workgroups and filled out design content
• August
  • By end of August, SESF design docs v0.1 base on evolution of VSTO
  • Prototype scope worked out by end of August
• September
  • AGU Abstracts due 2nd
  • By end of September, preliminary architecture and technology design
• October
  • By end of October prototype
• November
  • Middle of November
    • Assess where we are
    • another planning meeting for next 6-8 months
• December
  • AGU 13-17