submission-body clarification

Colleagues of mine would like clarification on the event('submission-body')
property from the Forms Working Group in the XForms 1.1 spec.

Here are the questions:

   The xforms-submit-serialize event is dispatched at the beginning of
   submission serialization.   From the XForms 1.1 spec: "If the event
   context submission-body property string is non-empty, then the
   serialization data for the submission is set to be the content of the
   submission-body string." Now, assume the following code:

             <xforms:action ev:event="xforms-submit-serialize">
                    <xforms:setvalue  ref="event('submission-body')"
value="instance('iNewStuff')"/>
              </xforms:action>

   The single-node binding attribute section (b)  states the "ref"
   attribute binds to an instance data node, is the string object returned
   by the event property in (c) considered a single-node binding to an
   instance data node?   Also, is there a conflict from an implementation
   perspective with regard to context of the instance() and
   event('submission-body') not being within the same model (a) in the
   setvalue element above?

   a) 7.10.1
    node-set instance(string?)
   An XForms Model can contain more that one instance. This function allows
   access to instance data, within the same XForms Model, but outside the
   instance data containing the context node.


   b) 3.2.3 Single-Node Binding Attributes


   The following attributes can be used to define a binding between an
   XForms element such as a form control or an action and an instance data
   node defined by an XPath expression.


   ref


   c)  11.3 The xforms-submit-serialize Event
   The submission-body property is a string, but the event() function
   encapsulates the string in a text node so that the string can be
   modified by the setvalue action, which sets a value into a node
   determined by its Single Node Binding.



2)  With regard to the serialization of the 'submission-body' property on a
submission, should it always be treated as text? or as an XML text node? or
converted from a string into an XML node (what about the case "
<price>10</price>")?  Should the content type be set be to  text/plain or
application/xml or something else?


Thanks,


Keith