Science Environment for Ecological Knowledge
Ecoinformatics site parent site of Partnership for Biodiversity Informatics site parent site of SEEK - Home
Science Environment for Ecological Knowledge









 

 

 



All Hands Meeting 2005

Difference between version 53 and version 52:

Lines 110-127 were replaced by lines 110-127
- ** Working exercise: data integration approaches
- *** Case study requirements for integration
- *** Simple "smart" concatenation
- *** Extending to more complex (and realistic) examples
- *** Adequacy of annotations and ontologies for integration
- ** Data Management support for sms
- *** The EML actor as entry point for data integration
- *** How do we deal with multiple output formats from EML?
- *** How do we deal with null values?
- *** How do we carry out integration specifications given by sms?
- **** For example, using "R" to load instance data from multiple voluminous data sets (e.g., 3 100MB data files) and executing data integration "recipes"
- **** A database-style approach? (e.g., SQL)
- ** What approach do we use for representing data conversions?
- *** Examples: unit conversions, count/area = density, rescaling/projection
- *** Represent conversions within ontology?
- *** Represent conversions as actors (searched via annotations, e.g.)
- *** Define a new or leverage an existing representation for conversions (Prolog, SWRL, XML syntax a la STMML, MoML attributes)
- *** Use potpourri approach (i.e., try to accomodate multiple mechanisms)
+ *** Working exercise: data integration approaches
+ **** Case study requirements for integration
+ **** Simple "smart" concatenation
+ **** Extending to more complex (and realistic) examples
+ **** Adequacy of annotations and ontologies for integration
+ *** Data Management support for sms
+ **** The EML actor as entry point for data integration
+ **** How do we deal with multiple output formats from EML?
+ **** How do we deal with null values?
+ **** How do we carry out integration specifications given by sms?
+ ***** For example, using "R" to load instance data from multiple voluminous data sets (e.g., 3 100MB data files) and executing data integration "recipes"
+ ***** A database-style approach? (e.g., SQL)
+ *** What approach do we use for representing data conversions?
+ **** Examples: unit conversions, count/area = density, rescaling/projection
+ **** Represent conversions within ontology?
+ **** Represent conversions as actors (searched via annotations, e.g.)
+ **** Define a new or leverage an existing representation for conversions (Prolog, SWRL, XML syntax a la STMML, MoML attributes)
+ **** Use potpourri approach (i.e., try to accomodate multiple mechanisms)

Back to All Hands Meeting 2005, or to the Page History.