Summary of XML fragment typed records.

Issue:

Records are escaped to strings (&lt; for <) in version 1.  This means that
XSLT processors cannot handle the records, only the response wrapping
elements. It is desirable for this reason to be able to return real XML
embedded in the response as opposed to a string encoded form.

Solution:

The solution takes several parts, one of which is still under discussion.

* A <recordPacking> element of type string is proposed to be added to the
request.  This would contain the packing type requested.  The default, if
not supplied, would be 'string' for version 1 compatability.

* New diagnostic for unsupported/illegal recordPacking.

* Change to the response to permit different types of recordPacking.
Still under discussion. Options discussed:

A:  Add an additional element <recordXML> of type XMLFragment, which is
optional and is exclusive with <recordData>.

B:  Change the type of recordData to allow either string or XMLFragment.
The data type would be obvious from the type attribute.

C:  Add a recordPacking element to contain the recordPacking type of
recordData.

D:  Add a new recordData element under a new version 1.1 namespace.  This
would allow version 1.1 recordData to be XML while version 1.0 record
data could only be string.


--
      ,'/:.          Rob Sanderson ([log in to unmask])
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Twin Cathedrals:  telnet: liverpool.o-r-g.org 7777
____/:::::::::::::.              WWW:  http://liverpool.o-r-g.org:8000/
I L L U M I N A T I