Allow passing arbitrary synthesis/recognition headers to resources.

Allows including any MRCP headers without having to duplicate them in this specification, or being tied to MRCP.

Fixes #91. Fixes #96.

extensions/xep-0327.xml

@@ -1244,7 +1244,7 @@
     ]]></example>
 
     <section3 topic='Output Component' anchor='session-component-execution-output'>
-      <p>Media output is a core concept in Rayo, and is provided by the output component. The component allows media to be rendered to a call or a mixer, using the server's local media server. A server MUST support audio file playback and MUST support the text/uri-list document format. A server MAY support speech synthesis and MAY support SSML. The component is created using an <link url='def-component-output'>&lt;output/&gt; command</link>, containing one or more documents to render, along with a set of options to determine the nature of the rendering.</p>
+      <p>Media output is a core concept in Rayo, and is provided by the output component. The component allows media to be rendered to a call or a mixer, using the server's local media server. A server MUST support audio file playback and MUST support the text/uri-list document format. A server MAY support speech synthesis and MAY support SSML. The component is created using an <link url='def-component-output'>&lt;output/&gt; command</link>, containing one or more documents to render, along with a set of options to determine the nature of the rendering. When header elements are included in the command, these should be passed along to the synthesizer resource for tuning.</p>
 
       <example caption='Client renders a simple SSML document to a call'><![CDATA[
 <iq from='[email protected]/balcony'
@@ -1448,7 +1448,7 @@
     </section3>
 
     <section3 topic='Input Component' anchor='session-component-execution-input'>
-      <p>Media input is a core concept in Rayo, and is provided by the input component. The component allows input to be collected from a call by way of either DTMF (dual-tone multi-frequency) or ASR (automatic speech recognition), using the server's local media server. A Rayo server MUST support DTMF input and MUST support SRGS XML grammars (application/srgs+xml). A server MAY suport speech input, and MAY support other grammar formats. The component is created using an <link url='def-component-input'>&lt;input/&gt; command</link>, containing one or more grammar documents by which to control input, along with a set of options to determine the nature of the collection.</p>
+      <p>Media input is a core concept in Rayo, and is provided by the input component. The component allows input to be collected from a call by way of either DTMF (dual-tone multi-frequency) or ASR (automatic speech recognition), using the server's local media server. A Rayo server MUST support DTMF input and MUST support SRGS XML grammars (application/srgs+xml). A server MAY suport speech input, and MAY support other grammar formats. The component is created using an <link url='def-component-input'>&lt;input/&gt; command</link>, containing one or more grammar documents by which to control input, along with a set of options to determine the nature of the collection. When header elements are included in the command, these should be passed along to the recognizer resource for tuning.</p>
 
       <example caption='Client requests DTMF input collection from a call'><![CDATA[
 <iq from='[email protected]/balcony'
@@ -2376,7 +2376,7 @@ Art thou not Romeo, and a Montague?
 
       <section4 topic='Output Element' anchor='def-component-output-output'>
         <p>Instructs the server to begin an output component executing on the target call or mixer with the specified document and parameters.</p>
-        <p>The &lt;output/&gt; element MUST contain one or more <link url='#def-component-output-output-document'>&lt;document/&gt; elements</link>. A server MUST support the application/ssml+xml content type, but MAY additionally support others.</p>
+        <p>The &lt;output/&gt; element MUST contain one or more <link url='#def-component-output-output-document'>&lt;document/&gt; elements</link> and may contain any number of <link url='#def-header'>&lt;header/&gt; elements</link>. A server MUST support the application/ssml+xml content type, but MAY additionally support others.</p>
         <p>The attributes of the &lt;output/&gt; element are as follows.</p>
         <table caption='Attributes of Output Element'>
           <tr>
@@ -2547,7 +2547,7 @@ Art thou not Romeo, and a Montague?
 
       <section4 topic='Input Element' anchor='def-component-input-input'>
         <p>Instructs the server to begin an input detector of the specified mode, with certain attributes, governed by the rules provided in one or more grammar documents.</p>
-        <p>The &lt;input/&gt; element MUST contain one or more <link url='#def-comoponent-input-input-grammar'>&lt;grammar/&gt; elements</link>.</p>
+        <p>The &lt;input/&gt; element MUST contain one or more <link url='#def-comoponent-input-input-grammar'>&lt;grammar/&gt; elements</link> and may contain any number of <link url='#def-header'>&lt;header/&gt; elements</link>.</p>
         <p>The attributes of the &lt;input/&gt; element are as follows.</p>
         <table caption='Attributes of Input Element'>
           <tr>
@@ -3730,6 +3730,7 @@ Art thou not Romeo, and a Montague?
             </documentation>
           </annotation>
         </element>
+        <element name="header" type="tns:headerType" minOccurs="0" maxOccurs="unbounded" />
       </sequence>
     </complexType>
   </element>
@@ -4002,6 +4003,7 @@ Art thou not Romeo, and a Montague?
               </documentation>
             </annotation>
           </element>
+          <element name="header" type="tns:headerType" minOccurs="0" maxOccurs="unbounded" />
         </sequence>
       </simpleContent>
     </complexType>