| Line 1 was replaced by lines 1-35 |
| - !!! Intended Use |
| + !!! Intended audience |
| + |
| + This document is intended for __SEEK and Kepler developers__. |
| + |
| + It is a __DRAFT DESIGN DOCUMENT__ and does not reflect functionality as it |
| + currently exists in Kepler or SEEK. Comments and feedback are appreciated. |
| + |
| + !!! Core principles |
| + |
| + This description reflects the agreement reached at the [San Antonio KR meeting|http://seek.ecoinformatics.org/Wiki.jsp?page=KRMeetingJan06]. The core |
| + Observation Ontology is referred to as OBOE in the following only for |
| + reference and with no pretense of proposing a name. |
| + |
| + (to be written) |
| + |
| + !!! Abstract overview of the annotation process |
| + |
| + Annotation of a dataset according to OBOE starts with the instantiation of a oboe:Observation instance at the user's request. Its Observable property points initially to a new instance of the generic Observable class. |
| + |
| + The user is then assisted through the annotation process following the pattern: |
| + |
| + # Define the oboe:Observable. This can be left general, or its class can be found through a lookup in the knowledge base (concept name search, ontology browsing, google-like search on annotation properties and related docs...) A process should be identified to propose a concept if none is found matching the desired Observable. The procedure instantiates the Observable in the top-level annotation. |
| + # Define one new Observation (recurse to step 1) per each trait of the observable that is measured in the dataset. This can be assisted by the ontology, filtering Observables to represent the know traits of the top-level observable. Note: hasTrait->Observable should probably be a property in oboe:Observable, to use as superproperty for "traits" in domain ontologies. Such observations are linked to the top-level observation instance through the hasObservation property. This definition ginstantiates an oboe:Measurement and the relative oboe:ObservedDimensionality. More semantic lookups are involved in this definition. |
| + # Define one new Observation (recurse to step 1) per each context of each trait represented in the dataset. Interface assists by predefining common contexts (time, space) and preloading templates relative to the correspondent Observables. The semantics of the specific observables guides the definition. Measurements and dimensionality may be defined as in step 2 if the semantics of the context requires it. |
| + # Per each context defined, define the mapping between the Observation representing the context and the oboe:Measurement entered for the trait contextualized. This process is also assisted by the context ontologies and must be defined (see examples). |
| + |
| + !!! Annotation user stories |
| + |
| + This section contains examples of annotation of hypothetical datasets, detailing the user steps according to the "grammar": |
| + |
| + {{ user_story := (user_step)* |
| + |
| + user_step := (System_question System_example Answer_pattern) }} |
| + |
| + * LeafBiomassDataset example |
