Adding language on POST payloads containing parameters.

It was not easy picking a place for this.  If you add it where we
already talk about POST-s, it would appear twice (in sync and async).
If you add it where we talk about parameter encoding, it would awkwardly
sit next to VOTable content.

In the end, I think this location is the least bad one.

Content-wise, I considered whether to warn people that in urlencoded
parameters they have to replace + with space and in multipart parameters
they don't, but I figured that for almost everyone, this is done by
some library.  And for that reason, I also don't think we should think about
it much more -- *unless* this is becoming an issue and http server
implementations don't necessarily support urlencoded any more.  Do we
have indications that that is the case?

Author: msdemlei

DALI.tex

@@ -162,6 +162,12 @@ \section{Resources}
 having a single DALI-sync resource where the job is a query and the response is
 the result of the query.
 
+When an endpoint supports the POST method to communicate query
+parameters, implementing services must accept payloads with media types
+application/x-www-form-urlencoded \citep{std:RFC1866} and
+multipart/form-data \citep{std:RFC7578}; for file uploads, clients must
+use the latter.
+
 \subsection{Asynchronous Execution: DALI-async}
 \label{sec:dali-async}
 Asynchronous resources are resources that represent a list of asynchronous jobs
@@ -599,7 +605,7 @@ \section{Data Types and Literal Values}
 providers to be more explicit by using a fixed size (e.g. \verb|20|) or fixed
 with a limit (e.g. \verb|20*|) when applicable.
 
-In the following, where we say "VOTable type metadata", we mean either VOTable
+In the following, where we say ``VOTable type metadata'', we mean either VOTable
 \xmlel{FIELD} or \xmlel{PARAM} elements.
 
 Services may use non-standard \xmlel{xtype} values for non-standard datatypes, but if they
@@ -724,7 +730,7 @@ \subsection{Multiinterval}
 The \verb|multiinterval| xtype is a way to convey complex one dimensional extent
 (e.g. the temporal coverage of an observation made by combining several exposures)
 made up of multiple intervals. A multiinterval value is interpreted as the union
-of all component intervals. Multiple intervals may be serialised in a single value and 
+of all component intervals. Multiple intervals may be serialised in a single value and
 described as (possibly) multiple with the following VOTable type metadata:
 
 \begin{verbatim}
@@ -1767,7 +1773,7 @@ \subsection{PR-DALI-1.0-20130521}
 \subsection{WD-DALI-1.0-20130212}
 Simplified DALI-examples to conform to RDFa-1.1 Lite in usage of attributes.
 
-\bibliography{ivoatex/ivoabib,ivoatex/docrepo.bib}
+\bibliography{ivoatex/ivoabib,ivoatex/docrepo.bib,local.bib}
 
 
 \end{document}

local.bib

@@ -0,0 +1,21 @@
+@Misc{std:RFC1866,
+  author =       {T. Berners-Lee and D. Connolly},
+  title =        {Hypertext Markup Language - 2.0},
+  howpublished = {RFC 1866},
+  organization = {{IETF}},
+  url =          {https://datatracker.ietf.org/doc/html/rfc1866},
+  month =        nov,
+  year =         1995
+}
+
+@Misc{std:RFC7578,
+  author =       {L. Masinter},
+  title =        {Returning Values from Forms: multipart/form-data},
+  howpublished = {RFC 7578},
+  organization = {{IETF}},
+  url =          {https://datatracker.ietf.org/doc/html/rfc7578},
+  month =        jul,
+  year =         2015
+}
+
+