[tdwg-tapir] Schema modification: r513 - trunk/protocol
m.doering at BGBM.org
Mon Mar 13 13:18:30 CET 2006
its exactly the way it was before. you can ommit the conceptNameServer element in the capabilities, but if its there, at least one server element must be present. So we dont force tapir services to use a CNS.
sorry for the confusion,
Von: tdwg-tapir-bounces at lists.tdwg.org [mailto:tdwg-tapir-bounces at lists.tdwg.org] Im Auftrag von Renato De Giovanni
Gesendet: Montag, 13. März 2006 12:58
An: tdwg-tapir at lists.tdwg.org
Betreff: Re: [tdwg-tapir] Schema modification: r513 - trunk/protocol
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...
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.
> On 3/13/06, tdwg-tapir at lists.tdwg.org <tdwg-tapir at 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.
tdwg-tapir mailing list
tdwg-tapir at lists.tdwg.org
More information about the tdwg-tag