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

[drn05r]

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.
> 	
> 	
> 	On 18/02/2009 14:53, "Don Cruickshank" <address@hidden> wrote:
> 	
> 	
> > 		Hi,
> > 		
> > 		The API allows you to query for the separate components of a workflow, e.g.:
> > 		
> > 		http://www.myexperiment.org/workflow.xml?id=172&elements=components
> > 		
> > 		This is available for Taverna 1 workflows at present.  If Taverna 2 beta
> > 		workflows
> > 		are important for this, then I can prioritise getting that available.
> > 		
> > 		David Newman will correct me if I'm wrong, but this breakdown hasn't made it
> > 		into
> > 		the RDF yet, so right now you would have to trawl myExperiment live via the
> > 		API for
> > 		all the workflow components.
> > 		
> > 		It's a query that looks like SPARQL might be the best way forward.  The
> > 		myExperiment
> > 		SPARQL endpoint is at:
> > 		
> > 		http://rdf.myexperiment.org/sparql
> > 		
> > 		So I think David Newman and myself are probably the best people to talk to
> > 		about
> > 		doing this.
> > 		
> > 		Regards,
> > 		Don.
> > 		
> > 		
> > 		-----Original Message-----
> > 		From: address@hidden
> > 		[mailto:address@hidden] On
> > 		Behalf Of Alan R Williams
> > 		Sent: 18 February 2009 14:28
> > 		To: address@hidden
> > 		Subject: [Myexperiment-discuss] "Intelligent" storage of workflows
> > 		
> > 		Hello,
> > 		
> > 		I'm at the Taverna workshop.  One of the Taverna users is interested in
> > 		the storage of workflows so that they can be queried for their content
> > 		e.g. what processors are used, what connections are made.  For
> > 		example:
> > 		
> > 		display all workflows that have a connection between a blast
> > 		and an alignment service
> > 		
> > 		Does anyone here know of where to look for ideas on how to do this, or
> > 		people for him to co-operate with?
> > 		
> > 		His e-mail is address@hidden - but I'm interested in the answers
> > 		as well :-)
> > 		
> > 		Thanks in advance,
> > 		
> > 		Alan
> > 		
> > 		
> > 		
> > 		_______________________________________________
> > 		Myexperiment-discuss mailing list
> > 		address@hidden
> > 		http://lists.nongnu.org/mailman/listinfo/myexperiment-discuss
> > 		
> > 		
> > 		
> > 		_______________________________________________
> > 		Myexperiment-discuss mailing list
> > 		address@hidden
> > 		http://lists.nongnu.org/mailman/listinfo/myexperiment-discuss
> > 		
> > 		
> > 	
> 	
> 	
> 	-- 
> 	Tony Linde
> 	Project Manager
> 	Department of Physics & Astronomy
> 	University of Leicester
>