Example of interoperability validation on real time with PDL services
Workflow that exemplifies the use of PDL (parameter description language) descriptions for rest services. This workflow is using two types of PDL descriptions. - the artifact provides as output the response from the service (rest config). - the web service provides a VOTable that is processed according to the PDL description. Some of the columns in the votable are provided as output in the artifacts (smartVORest config). To check interoperability we have to validatate the connections between outputs and inputs of the artifacts. The tests for the connections between the smart pdl cone search services are passed because they have the same metadata. However, dec output is connected to ra input and ra output is connected to dec input for the last two artifacts in the workflow. As they have different metadata, the validation report shows warnings for these connections (a mismatch in the metadata).
Preview
Run
Run this Workflow in the Taverna Workbench...
Option 1:
Copy and paste this link into File > 'Open workflow location...'
http://myexperiment.org/workflows/3827/download?version=1
[ More Info ]
Workflow Components
![]() | ![]() |
![]() | ![]() |
![]() | ![]() |
![]() | ![]() |
Inputs (0) | ![]() |
Processors (6) | ![]() |
Beanshells (0) | ![]() |
Outputs (5) | ![]() |
Datalinks (14) | ![]() |
Coordinations (0) | ![]() |
Reviews
(0)
Other workflows that use similar services
(0)
There are no workflows in myExperiment that use similar services to this Workflow.
No comments yet
Log in to make a comment