This is a parent page of the current use cases. The intention of describing these use cases is to identify the project scope and define the design requirements that will guide the system architecture and its implementation. All developers and users are invited to share their notes and thoughts. Currently, four use cases are defined. The model side can be CSDMS or simple model that is developed in any research group. The data side are always represented by Medici II. Two use case aims to provide a semantic wrapper for the queries coming from the model side, a use case aims to provide a semantic annotation for data stored in medici II, and the final use case aims to send queries backward from data to semantic equations to calculate new variables. More details about each use case is provided in the child pages. 

Semantic annotation and resource alignment 

Scenario:

•  A user added a new dataset to clowder.
• Data can be annotated using the Semantic Annotation Service (SAS), which proivdes spatial, temporal,  standard names, and encapsulated annotation, scientific provenance, and statistical features annotation of the data 
• A user can choose the Semantic Annotation Service (SAS) to annotate his data
• Then he uses a model and 

Applications

Main Success Scenario

Image Added

Linked Standard Names and knowledge integration

Scenario:

Applications:

Main Success Scenario:

Image Added

Knowledge discovery

Scenario:

Applications:

Main Success Scenario:

Image AddedEach used case is a written description of how users will perform tasks using the Geosemantic framework. A use case will be presented as a simple steps, beginning with the user goal and ending when that goal is fulfilled. Use cases explains how the system should behave.