175 lines
5.5 KiB
Plaintext
175 lines
5.5 KiB
Plaintext
head 1.6;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.6
|
|
date 2006.04.17.17.28.55; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.5;
|
|
|
|
1.5
|
|
date 2006.04.14.20.18.48; author MattJones; state Exp;
|
|
branches;
|
|
next 1.4;
|
|
|
|
1.4
|
|
date 2006.04.14.19.42.53; author MattJones; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2006.04.14.03.44.31; author MattJones; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2006.04.14.03.38.36; author MattJones; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2006.04.14.03.36.52; author MattJones; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@
|
|
.
|
|
@
|
|
|
|
|
|
1.6
|
|
log
|
|
@Changed page title
|
|
.
|
|
@
|
|
text
|
|
@---++ LSID Resolver for Analytical Models
|
|
|
|
*Coordinator(s):* Matt Jones
|
|
|
|
*Participants:* Matt Jones, Chad Berkley, and the Kepler team
|
|
|
|
----
|
|
---+++ Description
|
|
This group will make available an LSID resolver that can serve information about analyses and models in the form of scientific workflows that might be used with ecological and biological and other scientific data.
|
|
----
|
|
---+++ Technical Information
|
|
|
|
*URL for prototype user interface:* http://library.kepler-project.org
|
|
*LSID authority(ies):* kepler-project.org
|
|
*LSID namespace(s):* actor, kar
|
|
*Hardware platform:* Dell rackmount server, 4GB RAM, 2.5Terabyte storage array
|
|
*Server platform:* RHEL4, postgres 7.4, Apache 2, Tomcat 5, Metacat 1.6
|
|
*LSID Software stack used:* Java
|
|
*RDF/OWL ontology used for metadata:* In development
|
|
*Approximate number of LSIDs stored:* 150
|
|
*Benchmarchs:*
|
|
*Other resources:*
|
|
|
|
----
|
|
---+++ Roadmap, Milestones, Timeline
|
|
|
|
* Spring 2006: Set up prototype analysis and model workflow repository and LSID resolver
|
|
* Spring 2006: Modify Kepler to be able to publish models with LSIDs to this repository
|
|
|
|
----
|
|
---+++ Discussion, Implementation Issues
|
|
|
|
In the Kepler scientific workflow system (http://kepler-project.org), scientific analyses and models can be represented as workflows that model the flow of data from one processing step to another. Processing steps, called 'actors' in Kepler, can be as fine grained (e.g., simple addition) or coarse-grained (e.g., the GARP model) as desired by the scientist. Kepler models are published in the Modeling Markup Language (MoML) and are executable using the Kepler Scientific Workflow system. Within Kepler, each analytical component that is published or that ships with Kepler is assigned its own LSID. The component is serialized in a Kepler archive (.kar) file that contains a manifest listing its LSID and other metadata. The .kar file can be shipped between Kepler systems (e.g., via email or web, etc) and opened by other Kepler users, allowing people to share their analytical work. Combined with strongly-versioned data sets that are also referenced by LSIDs in the models (See LSIDResolverForObservations), the KAR file can represent a complete scientific model and all of the data need to execute that model.
|
|
|
|
Analytical models in Kepler that might be of more general use can be saved from Kepler and published to the Kepler actor library (http://library.kepler-project.org), which makes them available for download and use by other Kepler users. Most of this system is currently functional in prototype form.
|
|
|
|
Future features include the ability to search the Kepler actor library from directly within the Kepler user interface and directly import and use analytical components found through this search. This is analogous to the current EcoGrid data search that is available in Kepler for locating ecological data, observational data, specimen data, and geophysical data through the EcoGrid web service interfaces.
|
|
|
|
|
|
----
|
|
---+++ Lessons Learned, Conclusions, Recommendations
|
|
|
|
|
|
|
|
|
|
|
|
----
|
|
---+++++ Categories
|
|
CategoryWorkingGroup
|
|
CategoryPrototypingWG
|
|
@
|
|
|
|
|
|
1.5
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
---++ SEEK Taxon Resolution Server
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d14 2
|
|
a15 2
|
|
*LSID authority(ies):* library.kepler-project.org
|
|
*LSID namespace(s):* actor
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d14 1
|
|
a14 1
|
|
*LSID authority(ies):* kepler-project.org
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d3 1
|
|
a3 1
|
|
*Coordinator(s): Matt Jones
|
|
d5 1
|
|
a5 1
|
|
*Participants: Matt Jones, Chad Berkley, and the Kepler team
|
|
d13 8
|
|
a20 8
|
|
*URL for prototype user interface: http://library.kepler-project.org
|
|
*LSID authority(ies): kepler-project.org
|
|
*LSID namespace(s): actor
|
|
*Hardware platform: Dell rackmount server, 4GB RAM, 2.5Terabyte storage array
|
|
*Server platform: RHEL4, postgres 7.4, Apache 2, Tomcat 5, Metacat 1.6
|
|
*LSID Software stack used: Java
|
|
*RDF/OWL ontology used for metadata: In development
|
|
*Approximate number of LSIDs stored: 150
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@Initial revision
|
|
@
|
|
text
|
|
@d33 1
|
|
a33 1
|
|
In the Kepler scientific workflow system (http://kepler-project.org), scientific analyses and models can be represented as workflows that model the flow of data from one processing step to another. Processing steps, called 'actors' in Kepler, can be as fine grained (e.g., simple addition) or coarse-grained (e.g., the GARP model) as desired by the scientist. Kepler models are published in the Modeling Markup Language (MoML) and are executable using the Kepler Scientific Workflow system. Within Kepler, each analytical component that is published or that ships with Kepler is assigned its own LSID. The component is serialized in a Kepler archive (.kar) file that contains a manifest listing its LSID and other metadata. The .kar file can be shipped between Kepler systems (e.g., via email or web, etc) and opened by other Kepler users, allowing people to share their analytical work. Combined with strongly-versioned data sets that are also referenced by LSIDs in the models (See), the KAR file can represent a complete scientific model and all of the data need to execute that model.
|
|
@
|