1. Specifications document A number of revisions & refinements done => upcoming revision of design document Summary: –support smart data discovery find data that matches some semantic constraints –support matching of pipeline steps and data sets –support chaining of pipeline steps dependent on what type of AP/“director” is used –know about and reason with data/type/unit conversions

2. Semantic Mediation System notes from the breakout session

3. Software Components/Products 1.ontology languages/handler –languages for semantic types, data types, other constraints 2.system for type checking and reasoning with semantic types

4. Relations to other Components EcoGrid uses SMS for smart data discovery 2do: What is an analytical step?  AMS –Eco-model, piece of a model, (sub-)workflow, data- massaging step, visualization 2do: Use cases where two analytical steps can/can’t be chained together  BEAM 2do: Use Ptolemy to do some Ecology models and find out which Ptolemy directors are relevant for SEEK (discrete event models, process networks,...) 2do: (within SMS) –type systems for parametric polymorphism vs reasoning with measurement scales, aggregation, sampling protocols, scaling theory,...

5. Calendaring, Meetings yes

6. Milestones Milestone0: finish hiring asap Milestone1 (?May/June 2003): –initial choice of ontology language for SW1 (RDF, RDF(S), DAML+OIL, OWL,...) and –initial tools (Fact, Protege,... Jena (HP sem web activity)... –prelim. overview on possible type checking, query planning and reasoning procedures for SMS

7. Deliverables for June 1 SMS design document –initial choice of ontology languages, and frameworks for reasoning with them –initial design of API: SMS  AMS/EcoGrid