>>>> [log in to unmask] 06/01 5:46  >>>
>> The problem is that a client won't know that it makes sense to ask
for
>> it and I do not expect clients to search in explain if there is
anything
>> they might ask for. My feeling is that it would be better to have it
as
>> a standard option.
>
>If the sever returns diagnostic 67 "Record not available in this
schema",
>the client could then request that specific record, along with the
extension
>request.

This is an option, but it would require extra requests only for showing
the client the possibility of requesting another recordSchema.
I expect two cases:
1) A client is aware of this situation and will _always_ request the
extension when doing a search to notify the user beforehand about the
availability of the recordSchemas.
2) A client is not aware of this situation and will use the
recordSchemas mentioned in Explain and will provide the user with a
diagnostic if the recordSchema is not available for a specific record.
The client cannot anticipate on this situation without always requesting
the extension.

We will use x-info-accept=any to handle this but others will need a
priori knowledge of the KB services in order to be able to deal with
this situation.

Theo