| Line 122 was replaced by line 122 |
| - !! Automated Workflow (Thursday, 5th, 2005) |
| + !! Semi-automated workflow composition(Thursday, 5th, 2005) |
| At line 123 added 17 lines. |
| + * Given a connection (relation) between two actors that has been flagged as incompatible, what next? |
| + ** We want to allow for adapter insertion |
| + ** Where the adapter can be "implemented" according to a number of approaches |
| + *** Search for actors/composites that can perform the conversion |
| + **** We want to use the "parameter dependencies" to insert the simple adapters |
| + **** We want to provide simple structural conversions, like map |
| + **** This could employ "planning" style approaches as well |
| + *** If structural and not semantic, apply a DILS-like approach, given as input to SCIA |
| + *** If structural and semantic, apply SCIA |
| + *** Allow user to fill in the adapter itself |
| + |
| + * Changes to SCIA that may be needed |
| + ** Performance issues: |
| + *** Generating XQuery, converting to XML, etc., may not be efficient in certain situations |
| + *** Try outputing R instead |
| + *** Try compiling directly to Java code |
| + *** Search for existing conversions as a user elaborates a mapping (needs to call sms search capabilities ?) |
| At line 126 added 1 line. |
| + |
