Hello Javier, I do agree with 2 and 3. And I agree with accepting multiple concept nameservers, but why should we force every TAPIR service to understand a concept nameserver? In principle I would leave this optional, unless I'm missing something... Regards, -- Renato On 13 Mar 2006 at 12:19, Javier de la Torre wrote:
I hope no one disagree with:
3) partial element from search request integrated into searchTemplateType. So partial is now part of a searhc template as well as a search request.
Javi.
On 3/13/06, tdwg-tapir@lists.tdwg.org <tdwg-tapir@lists.tdwg.org> wrote:
Author: markus Date: 2006-03-13 12:04:20 +0100 (Mon, 13 Mar 2006) New Revision: 513
Modified: trunk/protocol/tapir.xsd Log: incorporates 3 changes: 1) Allow any number of concept name servers, but require 1 (capabilities) 2) simpleXpathType is a string now 3) partial element from search request integrated into searchTemplateType. So partial is now part of a searhc template as well as a search request.