[Soaplab2-dev] Re: acd development terms

[Jon I. <ji...@eb...>]

Hi Peter

These terms relate to a piece of software I'm designing for (amongst
other things) capturing user requirements for EMBOSS applications ...
there were some discussions at the EBI which you missed.  I'll forward
you the messages off-list, 'cause it's not strictly soaplab stuff, just
related.

Cheers

Jon


> Sorry if I missed something, but what are:
>
>  1. JACD-GUI
>  2. ACD-XML
>  3. ACD-XML schema ??
>
> Cheers,
>
> 	Peter
>
>
> On Fri, 26 May 2006, Jon Ison wrote:
>
>> It's more obvious to me now how the dashboard and acdtools / JACD
>> fit together. The Service Editor and JACD-GUI have common ground,
>> but I face an easier proposition because JACD-GUI only need support
>> what can be defined in an ACD file / by the XML-ACD schema, whereas
>> the service editor needs (presumably) to handle stuff outside that
>> scope / in an extended schema.
>>
>>  Both might need to handle dependencies between options of the type,
>> "The value of option X depends on the the value of option Y" - not
>> easy, perhaps we could help each other with that part?
>>
>> Last thought is that it might be sensible if the XML schema used by
>> SOAPLAB (or indeed any interface to EMBOSS) was managed as an
>> extension to the (more basic) ACD-XML schema.
>