33 lines
712 B
Plaintext
33 lines
712 B
Plaintext
|
head 1.1;
|
||
|
|
access;
|
||
|
|
symbols;
|
||
|
|
locks; strict;
|
||
|
|
comment @# @;
|
||
|
|
|
||
|
|
|
||
|
|
1.1
|
||
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
||
|
|
branches;
|
||
|
|
next ;
|
||
|
|
|
||
|
|
|
||
|
|
desc
|
||
|
|
@Initial revision
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.1
|
||
|
|
log
|
||
|
|
@Initial revision
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@---+++ Instructions for Software
|
||
|
|
|
||
|
|
The protocol might include a section holding optional instructions for processing software.
|
||
|
|
|
||
|
|
For example when trying to respond to a search request having a filter which specifies a concept a provider has not mapped. What is the wrapper software supposed to do? Abort the search with an error? Return an emtpy recordset? Ignore the unknown concept in the filter and set this COP to true?
|
||
|
|
|
||
|
|
It could be useful for a client to be able to specify such behavior in a request.
|
||
|
|
|
||
|
|
@
|