In fact I do not see any disagreement. But I also do not what is a wrong
with a profile that says that there should be at least a single common
default minimal record schema that can always be returned. The answer
could be "ask for that schema". But I do not see why specifically
asking for it is better than sending it instead of the schema that was
asked for but could no be provided.
I would rather prefer to let the user select out of Zeerex an available
recordschema AFTER he has seen that are were records that interested
him. In that case a single record can be presented in line with its
schema with the right stylesheet. For a list of records returned in
different schemas I find this more difficult.
But, I give up on this one and try to find a way to solve this in our
>>> [log in to unmask] 8/7/03 6:22:12 nm >>>
> Date: Thu, 7 Aug 2003 17:32:06 +0200
> From: Theo van Veen <[log in to unmask]>
> I am not asking for richer diagnostics or something that is "sloppy,
> unpredictacle, non-interoperable". I am asking for something that
> allows me to broadcast the same request to different servers and
> getting usefull responses rather than first finding out
> automatically what servers (that are not known before) can and
> cannot handle, sending different queries to each server and then
> still having to deal with different responses.
If the servers all adhere to the profile that the client is trying to
implement, there is no problem. If they do not then there is NO WAY
to build a slopless, predictable, interoperable system out of them,
and we do users no favours if we pretend there is.
/o ) \/ Mike Taylor <[log in to unmask]>
)_v__/\ "Schmeichel is beaten for the first time today." -- Andy
17th December 1995, after Robbie Fowler's second goal made
the score 2-0.
Listen to my wife's new CD of kids' music, _Child's Play_, at