On 28 Jun 2007, at 12:23, Bogdan wrote:
Richard,
XML: a <Filter> tag
Perl API: addFilter
webservice query API: described by type=attributes
martview webpage: displayed in the attributes section
What you are suggesting is for it to be treated solely EITHER as an
Attribute OR as a Filter OR as a third, independent, AttributeFilter
entity throughout all four sections mentioned above, rather than
treated
as different things in different parts of the system.
Yes. Maybe even not across all four sections. For my specific case,
the inconsistency is with 'XML' and 'webservice query API' (more
precisely - with a single query, which retrieves the list of filters
for dataset). However, XML is generated (at least in part) to be later
used with 'webservice query API' - thus the feeling of inconsistency.
Arek, what do you think?
Arek, this isn't an urgent problem, but I'd be glad to know for the
future what is the trend here.
Hi Bogdan,
Yes you are right, this is a little but rather annoying inconsistency.
We'll try to come up with something cleaner for 0.7. Hope you can put
up with that for a little while longer
a.
Thanks for help,
Bogdan
------------------------------------------------------------------------
-------
Arek Kasprzyk
EMBL-European Bioinformatics Institute.
Wellcome Trust Genome Campus, Hinxton,
Cambridge CB10 1SD, UK.
Tel: +44-(0)1223-494606
Fax: +44-(0)1223-494468
------------------------------------------------------------------------
-------
