Lines 4-37 were replaced by line 4 |
- ''Wednesday Breakout (Dec 13)'' |
- |
- * __OBOE Core__ |
- ** ''Current status'' (Josh) |
- ** ''Open issues'' |
- *** Clarification of Entities and Measurement Standards (in particular, Classification Elements) |
- *** Other issues? |
- ** ''Tasks' |
- *** Documentation and examples |
- **** Compare to other approaches |
- **** Formally publish the ontology |
- **** A paper (ISEI) |
- **** Do we need another KR meeting |
- |
- |
- 2 OBOE extensions / other ontologies |
- |
- current status & open issues (Josh): |
- - LTER Controlled Vocab |
- - Collaborative (web-based) approach for extensions (e.g., Thinkcap) |
- - What would the interface be |
- - Complexity versus simplicity |
- - Browsing/viewing ontologies |
- - How to store/manage the ontologies |
- - Additional Metadata |
- - Reuse(cycle) existing ontologies (e.g., Rich Williams', existing ontologies?) |
- |
- tasks: |
- - finish up three different extension approaches |
- - document and publish extensions |
- - figure out additional extensions needed |
- |
- |
- 3 Applications |
+ [Notes from breakouts|KR SMS AHM Dec 2006 Breakout Notes] |
Removed lines 39-57 |
- current status: |
- - semantic annotation interchange language |
- - the oboe-web prototype |
- - kepler tools |
- |
- open issues: |
- - interface design for oboe annotations |
- - where should the oboe applications/demos live? (Kepler, Morhpo, Web, ...) |
- - connecting up eml (metacat/morpho/kepler) and oboe |
- - ontologies for annotating actor ports and annotation interface |
- design (e.g., ontos based on oboe, simpe types?) |
- - how should we extend the kepler tools, e.g., adding ontologies, |
- using port annotations in search |
- - overall KR/SMS architecture |
- |
- tasks: |
- - concrete demos showing advantages of KR/SMS |
- - what tools do we want to work on in the next year |
- - implementation plan (who will work on what ...) |
At line 58 added 1 line. |
+ !Wed Dec 13 Breakouts: OBOE |
At line 59 added 29 lines. |
+ __OBOE Core__ |
+ * ''Current status'' (Josh) |
+ * ''Open issues'' |
+ ** Clarification of Entities and Measurement Standards (in particular, Classification Elements) |
+ ** Discussion of generic context property (e.g., Is context just a spatial and temporal property? Can it be used for mereological relationships?) |
+ ** Are there specific extension points, and can their development progress independent of the core? (e.g., Will different core models have analygous extension points?) |
+ ** Other issues? |
+ * ''Tasks'' |
+ ** Documentation and examples |
+ *** Compare to other approaches |
+ *** Formally publish the ontology |
+ *** A paper (ISEI) |
+ *** Do we need another KR meeting |
+ __OBOE extensions__ |
+ * ''Current status & open issues'' (Josh) |
+ ** LTER Controlled Vocab (Corinna/Sree) |
+ ** Reuse(cycle) existing ontologies (e.g., Rich Williams' ontologies and existing ontologies/standards) |
+ *** GeoSpatial extensions (Serguei) |
+ ** Collaborative (web-based) approach for extensions (e.g., Thinkcap) |
+ *** What would the interface be |
+ *** Complexity versus simplicity |
+ *** Browsing/viewing ontologies |
+ *** How to store/manage the ontologies |
+ *** Additional Metadata |
+ * ''Tasks'' |
+ ** finish up three different extension approaches |
+ ** document and publish extensions |
+ ** figure out additional extensions needed |
+ |
At line 60 added 1 line. |
+ !Thu Dec 14 Breakouts: Applications |
At line 61 added 16 lines. |
+ * ''Current status'' |
+ ** [Semantic annotation interchange language|KRSMS Semantic Annotation Language] (Shawn) |
+ ** The oboe-web prototype (Shawn/Josh) |
+ ** Kepler tools (Shawn/Josh) |
+ * ''Open issues'' |
+ ** Interface design for oboe annotations |
+ ** Where should the oboe applications/demos live? (Kepler, Morhpo, Web, ...) |
+ ** Connecting up eml (metacat/morpho/kepler) and oboe |
+ ** Ontologies for annotating actor ports |
+ ** Annotation interface design (e.g., ontos based on oboe, simpe types?) |
+ ** Extending the kepler tools, e.g., adding ontologies, using port annotations in search |
+ ** An overall KR/SMS architecture |
+ * ''Tasks'' |
+ ** Concrete demos showing advantages of KR/SMS |
+ ** What tools do we want to work on in the next year |
+ ** Implementation plan (who will work on what ...) |