FW: [Myexperiment-discuss] "Intelligent" storage of workflows

[Linde, A.E.]

Ah! Not something we’d likely want to use after all...

T.

------ Forwarded Message

From: drn05r <drn...@ecs.soton.ac.uk>
Date: Wed, 18 Feb 2009 17:16:38 -0000
To: "Linde, A.E." <ae...@leicester.ac.uk>
Cc: myexperiment-discuss <myexperime...@nongnu.org>
Subject: Re: [Myexperiment-discuss] "Intelligent" storage of workflows

Hi All,

I will see if I can answer the all questions in one email.  Apologies if I have missed answering a question.  The list has been quite busy this afternoon.

>  Any pointers on how the RDF side of myExperiment is coded up? Any developer documentation?

The RDF API is generated by querying a database (currently the previous night's snapshot) and using PHP to generate RDF/XML output.  The way I have written it is fairly extensible and requires only minimal effort to update when the myExperiment data model changes.  http://rdf.myexperiment.org/ gives some examples of how to make a request to retrieve the RDF/XML for a particular object.  However the last example (e.g. http://rdf.myexperiment.org/User/26/Groups) is not currently implemented.  Only public data (i.e. stuff that you can view through the myExperiment site when you are not logged in) can be accessed.

> Does he have to use myExperiment, or is the RDF-generator accessible or stand-alone?  When will the contents of the workflow make it into the RDF?

As only public data is exposed you do not need to be a myExperiment user to access the RDF data.  As I sit opposite Don it should be possible for me to add workflow contents data fairly quickly.

 

Regards

David Newman  

 

On Wed, 18 Feb 2009 16:38:35 +0000, "Linde, A.E."  wrote:

Re: [Myexperiment-discuss] "Intelligent" storage of workflows Any pointers on how the RDF side of myExperiment is coded up? Any developer documentation?

T.

...

------ End of Forwarded Message

[Linde, A.E.]

Neat workflow. Also worth noting that the reference to the workflow is the webpage for that uploaded workflow rather than the api reference (which would return XML).

I wonder: could we take the api reference for an object, say http://www.myexperiment.org/workflow.xml?id=648, and stick that through some sort of XSL processor to return the RDF? Would be guaranteed to be correct but would need XSL for each api call. And of course we’d not be able to SPARQL the whole collection. Depends what LOD is looking for: a reference which returns RDF or a pointer into a triplestore.

Oooh! My brain hurts.

T.

--
Tony Linde
Project Manager
Department of Physics & Astronomy
University of Leicester

------ Forwarded Message

From: <I.H.C....@ewi.utwente.nl>
Date: Thu, 19 Feb 2009 08:01:12 -0000
To: <M.R...@uva.nl>, <pmis...@cs.man.ac.uk>
Cc: <em...@science.uva.nl>, myexperiment-discuss <myexperime...@nongnu.org>
Subject: RE: [Myexperiment-discuss] "Intelligent" storage of workflows

Dear All,

Last week, We (Me together with many other people, among others, Katy, Marco, Pieter) have submitted a paper to a workshop that is about analysing workflows stored at myExperiment. The funny part is that it is implemented as a workflow too!

The workflow download the xml of the workflows stored at myExperiment and analyses the tasks that are used (BioMoby, Biomart etc). The workflow further analyses the amount of tasks spend to local workers, web services, scripting and sub-workflows. An R script is used to perform the statistical analysis. The workflow makes use of the Xpath processor to easily collect the information about the processors.

It will be easy to adapt the workflow to collect the data-links between these processors.

An advantage of implementing your analysis as a workflow too is that you can share it, but also refer to it in your papers (the referee and others are able to validate your analysis).

The workflow can be found at:
http://www.myexperiment.org/workflows/648

I hope this will be helpful.

Kind regards,

Ingo