> Regarding surrogate-diagnostic terms and suchlike: I think we should
> avoid getting sidetracked by such considerations. Rob's issue is not
> a Scan problem. It's a transport problem. Let's address the root
It is a transport problem but one that will only occur in Scan.
Of course we should be aware of it in the future too.
The only other place where we have data returned which isn't generated by
the server as part of the protocol is <recordData>, and there's already a
rule that says recordData must be legal XML.
The query terms can already be handled via a XXX.base64 relation modifier.
Anyone writing a context set or identifier with names that include
unserializable characters is just taking the piss, and the characters
couldn't be transferred in a URL (?) or via SOAP anyway.
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. University of Liverpool
I L L U M I N A T I L5R Shop: http://www.cardsnotwords.com/