> looking for workflows. For example, if I have a workflow that outputs a > SwissProt ID, find all workflows that take SwissProt IDs. Or find shims > that convert SwissProt IDs into GenPept IDs.
The SADI plug-in does this (for SADI services); however I don't think the semantic type information is written into the SCUFL... would be useful! w.r.t. the broader conversation about representation of SCUFL2 - I agree 100% that it should be RDF for the sake of being able to attach annotations to any part of the workflow without breaking a "schema" (in fact, reversing that argument convinces me that Schema-based approaches are simply wrong, since then you break validation by doing "the right thing" and annotating!). v.v. the serialization of that RDF, I'm ambivalent... human-readable (e.g. Turtle) would be my preference, I guess, but I don't really want to ever read a workflow document by-eye anyway, I only want to visualize it and manipulate it using tools... so whatever RDF serialization is supported by the most tools might be the real deciding factor. -1 for XML-Schema-based approaches, for sure. I have no problem with distributing multiple files as a .zip - it's pretty standard, na?? $0.02 Mark W ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/ Developers Guide: http://www.taverna.org.uk/developers/
