Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "STEM Design Document"
(STEM Design Documentation) |
(→Dublin Core Metadata) |
||
Line 12: | Line 12: | ||
==== Dublin Core Metadata ==== | ==== Dublin Core Metadata ==== | ||
− | [[http://www.dublincore.org/ | + | The [[http://www.dublincore.org/ Dublin Core Metadata]] standard was developed by the library science community to define a consistent set of attributes that could be attributed to a "Resource". The definition of a Resource is deliberately unspecified by the standard, but would typically be something like a book, a movie, a video, or a musical score. Most of the attributes are simple and easy to understand and basically specify familiar details of something like a book such as its "Title", its "Creator", and the "Date" it was created. The usefulness of the standard is extended by the rest of the attributes that define such things as "Spatial" characteristics, a "License" and a date range for which a Resource is valid; there are several others. |
+ | |||
+ | STEM makes use of the standard by incorporating it as a required feature of each composable component of the graph it uses as its representational framework for each Simulation. Thus, when a simulation is created, every component (i.e., all data and all computation) is specifically labeled and identified as to its origin and applicability. | ||
== Plug-in Descriptions == | == Plug-in Descriptions == |
Revision as of 13:06, 20 June 2007
STEM Design Documentation
Contents
- 1 Overview
- 2 Plug-in Descriptions
- 2.1 org.eclipse.ohf.stem.core
- 2.2 org.eclipse.ohf.stem.definitions
- 2.3 org.eclipse.ohf.stem.diseasemodels
- 2.4 org.eclipse.ohf.stem.diseases
- 2.5 org.eclipse.ohf.stem.doc
- 2.6 org.eclipse.ohf.stem.geography
- 2.7 org.eclipse.ohf.stem.internal.data
- 2.8 org.eclipse.ohf.stem.jobs
- 2.9 org.eclipse.ohf.stem.jobs.nl1
- 2.10 org.eclipse.ohf.stem.sample
- 2.11 org.eclipse.ohf.stem.sequencers
- 2.12 org.eclipse.ohf.stem.tests.core
- 2.13 org.eclipse.ohf.stem.tests.definitions
- 2.14 org.eclipse.ohf.stem.tests.diseasemodels
- 2.15 org.eclipse.ohf.stem.tests.jobs
- 2.16 org.eclipse.ohf.stem.tests.ui
- 2.17 org.eclipse.ohf.stem.tests.util
- 2.18 org.eclipse.ohf.stem.ui
- 2.19 org.eclipse.ohf.stem.ui.diseasemodels
- 2.20 org.eclipse.ohf.stem.ui.ge
- 2.21 org.eclipse.ohf.stem.ui.nl1
- 2.22 org.eclipse.ohf.stem.ui.reports
- 2.23 org.eclipse.ohf.stem.utility
Overview
Overview of the design of STEM.
Standards
ISO-3166
Describe the ISO-3166 Standard.
Dublin Core Metadata
The [Dublin Core Metadata] standard was developed by the library science community to define a consistent set of attributes that could be attributed to a "Resource". The definition of a Resource is deliberately unspecified by the standard, but would typically be something like a book, a movie, a video, or a musical score. Most of the attributes are simple and easy to understand and basically specify familiar details of something like a book such as its "Title", its "Creator", and the "Date" it was created. The usefulness of the standard is extended by the rest of the attributes that define such things as "Spatial" characteristics, a "License" and a date range for which a Resource is valid; there are several others.
STEM makes use of the standard by incorporating it as a required feature of each composable component of the graph it uses as its representational framework for each Simulation. Thus, when a simulation is created, every component (i.e., all data and all computation) is specifically labeled and identified as to its origin and applicability.
Plug-in Descriptions
This section contains descriptions of the different plug-ins that comprise STEM.
org.eclipse.ohf.stem.core
The org.eclipse.ohf.stem.core plug-in contains the definitions and implementations of the Unified Modeling Language (UML) models that are used to represent the composable components that define a simulation in STEM. These models are Common, Graph, Model, Sequencer and Scenario. These models are implemented using the Eclipse Modeling Framework (EMF).
Common Model
Common Model UML Diagram goes here.
Describe the Dublin Core standard.
Describe how Sanity Checking works.
Graph Model
Graph Model UML Diagram goes here
Model Model
Model Model UML Diagram goes here
Sequencer Model
Sequencer Model UML Diagram goes here
Scenario Model
Scenario Model UML Diagram goes here