> > Yes, but the client must be prepared to receive more than one schema.
> > 'Must' because the server can return a diagnostic rather than the
> > record.
> I was not aware of the fact that unrequested schemas could be returned.

Only the diagnostic schema can be returned if unrequested. (Obviously you
wouldn't /request/ a surrogate diagnostic! :))

> > Short names can be anything.  You'd need to know the explain to know which
> > XSL to use.

> You know which XSL to use because you have somewhere a table saying
> which schema uses which XSL. The server and the schema both do not know
> which XSL you have available.

Right. So by using the URI, there's -one- string to look for, and we don't
need the explain map.

> I agree that using URIs give more "precision" but at the same time more
> divergence. I belief that different schema's can sometimes be handled
> the same stylesheet, but by the increased "precision" the chance of
> matching becomes smaller. That is the reason that we will start using
> DCX at the KB. The overlap in different record types is in case of

Uhhh, how does this have any bearing on the URI vs URI or short name
discussion?  If you don't recognise the URI, then you certainly won't
recognise the short name either... even worse, you have a chance of
recognising the short name as the /wrong/ schema.

Even so, the default XSLT template to apply further templates will filter
them through regardless. So just import all your stylesheets and ignore
the URI in the recordSchema.  If it was a short name, you don't gain
anything either.

> > If so, then they can also have access to the parameters of the request
> > they just sent, and we can ditch echoedRequest.  But I can't see how to do
> > either without significant Javascript hackery.
> The echoedRequest is needed to make the response self containing, which
> allows easy navigation without much Javascript. Clients can do a lot

Right. Ditto for the full URI in the response, not short names.
Allowing one and not the other is not something that I could explain the
reasoning behind.


      ,'/:.          Dr Robert Sanderson ([log in to unmask])
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Nebmedes: