| Line 16 was replaced by line 16 |
| - __Semantic Annotation__ |
| + __Semantic Annotationa__ |
| Lines 20-22 were replaced by lines 20-22 |
| - ** 'Items' |
| - *** __Datasets__: An entire dataset or some portion (a single table, one or more attributes, one or more data values, etc.) |
| - *** __Workflows and components__: A workflow, a workflow component, or some portion (parameters, ports, substructures of a port type, etc.). |
| + ** ''Items'' |
| + *** ''Datasets'': An entire dataset or some portion (a single table, one or more attributes, one or more data values, etc.) |
| + *** ''Workflows and components'': A workflow, a workflow component, or some portion (parameters, ports, substructures of a port type, etc.). |
| Line 24 was replaced by line 24 |
| - ** 'Item Selection' |
| + ** ''Item Selection'' |
| Lines 27-30 were replaced by lines 27-59 |
| - ** 'Ontology Expressions' |
| - |
| - An ontology expression defines the semantic "context" of the item |
| - selected |
| + ** ''Ontology Expressions'' |
| + *** An ontology expression defines the semantic "context" of the item selected |
| + *** Ontology expressions can be as complex as SQL-style update queries or simpler, e.g., as single concepts or paths in an ontology |
| + **** Path Example: {{Measurement.spatialContext.loc.latDeg}} specifies the location of a Measurement's spatialContext as a latitude in degrees |
| + |
| + __Architecture__ |
| + |
| + * Repositories |
| + ** Ontology(ies) |
| + ** Datasets (or metadata stating how to obtain the datasets) |
| + ** Workflows and Workflow Components (or metadata, etc.) |
| + ** Semantic Annotations |
| + |
| + * "Smart discovery and integration" needs access to each of these components: |
| + ** For example, to search for a workflow component, the sms engine would search through semantic annotations, and when an annotation matches, obtain the corresponding component. |
| + ** You might also want to organize (for browsing) all actors according to their annotations; so need to iterate over actors, or similarly, for datasets. |
| + |
| + * SMS-Based Applications |
| + ** Browsing/Keyword Search |
| + ** Workflow and/or dataset browsing and keyword-search based on ontology terms |
| + ** Find "compatible" actors |
| + *** Given an actor, find semantically compatible actors that can be connected as an input or output to the actor (this might result in a dataset as input, e.g.) |
| + *** Requires port inputs/outputs to be semantically annotated |
| + ** Workflow "analysis" |
| + *** Given a workflow, check that each connection (input/output) is semantically compatible. |
| + *** As part of analysis, annotation propagation ... |
| + ** Workflow-component structural integration |
| + *** Given two components that are semantically compatible, determine a structural transformation (either another component or a transformation step) to make them structurally compatible. |
| + *** May be a place where SCIA can contribute, to derive structural transformations. |
| + ** Dataset merging/integration |
| + *** Search for "similar" datasets (that could be potentially "merged" or integrated) |
| + *** Define a dataset of interest (via an ontology-style query), find/combine datasets as integrated "view". |
| + **** Perhaps a place for SCIA to contribute? |
| Lines 32-34 were replaced by line 61 |
| - Ontology expressions can be as complex as SQL-style update |
| - queries or simpler, e.g., as single concepts or paths in an |
| - ontology |
| + * Tools |
| Removed lines 36-113 |
| - |
| - *** Path Example: |
| - |
| - Measurement.spatialContext.loc.latDeg, specifying the |
| - location of a Measurement's spatialContext as a latitude in |
| - degrees |
| - |
| - |
| - * Architecture |
| - |
| - ** Repositories |
| - |
| - *** Ontology(ies) |
| - |
| - *** Datasets (or metadata stating how to obtain the datasets) |
| - |
| - *** Workflows and Workflow Components (or metadata, etc.) |
| - |
| - *** Semantic Annotations |
| - |
| - Basically, SMS "smart discovery and integration" needs access to |
| - these components. |
| - |
| - For example, to search for a workflow component, the sms engine |
| - would search through semantic annotations, and when an annotation |
| - matches, obtain the corresponding component. |
| - |
| - You might also want to organize (for browsing) all actors |
| - according to their annotations; so need to iterate over actors, |
| - or similarly, for datasets. |
| - |
| - |
| - ** SMS-Based Applications |
| - |
| - *** Browsing/Keyword Search |
| - |
| - Workflow and/or dataset browsing and keyword-search based on |
| - ontology concepts |
| - |
| - *** Find "compatible" actors |
| - |
| - Given an actor, find semantically compatible actors that can |
| - be connected as an input or output to the actor (this might |
| - result in a dataset as input, e.g.) |
| - |
| - Requires port inputs/outputs to be semantically annotated |
| - |
| - *** Workflow analysis |
| - |
| - Given a workflow, check that each connection (input/output) |
| - is semantically compatibly. |
| - |
| - As part of analysis, annotation propagation. |
| - |
| - |
| - *** Workflow component structural integration |
| - |
| - Given two components that are semantically compatible, |
| - determine a structural transformation (either another |
| - component or a transformation step) to make them structurally |
| - compatible. |
| - |
| - May be a place where SCIA can contribute, to derive |
| - structural transformations. |
| - |
| - *** Dataset merging/integration |
| - |
| - Search for "similar" datasets (that could be potentially |
| - "merged" or integrated) |
| - |
| - Define a dataset of interest (via an ontology-style query?), |
| - find/combine datasets as integrated "view". |
| - |
| - Perhaps a place for SCIA to contribute? |
| - |
| - |
| - ** Tools |
| - |
