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. Thanks for help, Bogdan
