> Date: Sat, 26 Jul 2003 00:17:41 +0100
> From: Robert Sanderson <[log in to unmask]>
> > Seems wrong to me. Though I admit I don't see a better way, with
> > the current set of primitives, to express "this server can't do
> > case-insensitive sorting". There are at least four possible
> > approaches: (1) kludge it as he suggests; (2) augment the ZeeRex
> > DTD to allow an explicit <doesntSupport> statement; (3) specify
> > that in the absence of a <supports> tag, the client can assume
> > that a facility is not supported; (4) get him to fix his server so
> > it supports case-insensitive sorting, then the problem doesn't
> > arise :-)
> 5) <supports value="false"> ... </supports>
That's not bad.
> 1: I like it because it does what it says. Setting is something
> that can't be changed, as opposed to a default. It just happens
> that this particular setting is a boolean, but it's (extremely
> unlikely) possible it could be a numeric setting.
Hmm, OK, I guess I can appreciate that.
> 2: Would rather have an attribute on supports that gives the truth
> value, and the default for it would be true. But this doesn't fix
> the numeric issue for things which are set, rather than not
> supported at all.
Yes. This is your option 5, right?
> 3: Urgh. We'd need to completely enumerate all the
> possibilities. ZeeRex files would become Very long.
Yes, I am not fond of this approach for precisely this reason. I just
thought I ought to mention it for completeness.
BTW., why are we discussing this on the ZNG list instead of the
/o ) \/ Mike Taylor <[log in to unmask]> http://www.miketaylor.org.uk
)_v__/\ "Everything is deeply intertwingled" -- Ted Nelson.
Listen to my wife's new CD of kids' music, _Child's Play_, at