[TAVERNA-288] Local world must go!

• Type: Bug
• Status: To Do
• Priority: Critical
• Resolution: Unresolved
• Component/s: Taverna Plugin Component
• Labels: component
• Assignee: Unassigned
• Reporter: Stian Soiland-Reyes
• Created: 27/May/14 11:43
• Updated: 28/Apr/15 11:43

Description

When editing a complex component annotation, we currently store the resulting RDF in a local world TTL file. We then put an unqualified reference to the local world inside the Taverna model as the actual annotation.

Which works until you send the component workflow to someone else (e.g., via myExperiment, though sending it to yourself in another version of Taverna would be just as bad); they can't resolve the reference, and so they have an entirely broken workflow annotation. This is Bad.

We need to not have a local world; it's fundamentally incompatible with the sharing of the workflow with anyone. We should instead copy the referenced object graph (but only the explicit parts of it) into the workflow so that the workflow has its own annotations. If someone wants a “local world”, let them write TTL (e.g., with Protégé) and put that up somewhere on the web; Taverna will then be able to reference it as an external RDF source.

Taverna is a workflow editor, not an RDF repository.