[bugfix] Use HTTPS instead of HTTP in the RESTXQ 1.0 spec

request-module-1.0-specification.html

@@ -9,7 +9,7 @@
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
           specStatus:           "unofficial",
 
-          // the specification's short name, as in http://www.w3.org/TR/short-name/
+          // the specification's short name, as in https://www.w3.org/TR/short-name/
           shortName:            "xxx-xxx",
 
           // if your specification has a subtitle that goes below the main
@@ -29,7 +29,7 @@
           // previousMaturity:  "WD",
 
           // if there a publicly available Editor's Draft, this is the link
-          // edDraftURI:           "http://dev.w3.org/2009/dap/ReSpec.js/documentation.html",
+          // edDraftURI:           "https://dev.w3.org/2009/dap/ReSpec.js/documentation.html",
           edDraftURI:           "https://exquery.github.io/exquery/expath-specs-playground/request-module-1.0-specification.html",
 
           // if this is a LCWD, uncomment and set the end of its review period
@@ -38,19 +38,19 @@
           // editors, add as many as you like
           // only "name" is required
           editors:  [
-              { name: "Adam Retter", url: "http://adamretter.org.uk/",
-                company: "Adam Retter Consulting", companyURL: "http://adamretter.org.uk/" },
-              { name: "Christian Grün", url: "http://christian-gruen.de/",
-                company: "BaseX GmbH", companyURL: "http://basex.org/" },
+              { name: "Adam Retter", url: "https://adamretter.org.uk/",
+                company: "Evolved Binary", companyURL: "https://www.evolvedbinary.com/" },
+              { name: "Christian Grün", url: "https://christian-gruen.de/",
+                company: "BaseX GmbH", companyURL: "https://basex.org/" },
           ],
 
           // authors, add as many as you like. 
           // This is optional, uncomment if you have authors as well as editors.
           // only "name" is required. Same format as editors.
 
           //authors:  [
-          //    { name: "Your Name", url: "http://example.org/",
-          //      company: "Your Company", companyURL: "http://example.com/" },
+          //    { name: "Your Name", url: "https://example.org/",
+          //      company: "Your Company", companyURL: "https://example.com/" },
           //],
 
           // name of the WG
@@ -164,12 +164,12 @@ <h3>Namespaces and Prefixes</h3>
     <section id="http-context">
       <h2>Accessing the HTTP Context</h2>
       <p>Each function in this module operates on the HTTP Request of a HTTP Context. The HTTP Reqyest is provided to each function by passing another function which returns a model of the context.</p>
-      <p>By default this module provides a function to access the HTTP Request Context, <a href="#request-http" class="sectionRef"></a> which returns an XML Document whoose root element is <a href="http://expath.org/spec/http-client#d2e183" title="The request elements">http:request</a>.</p> 
+      <p>By default this module provides a function to access the HTTP Request Context, <a href="#request-http" class="sectionRef"></a> which returns an XML Document whoose root element is <a href="https://expath.org/spec/http-client#d2e183" title="The request elements">http:request</a>.</p> 
       <p>The reasons for using function passing to access the HTTP Context include:</p>
       <ol>
         <li>Enable easy mocking of the HTTP Context for testing.</li>
         <li>Easier optimisation by substitution of the <a href="#request-http" class="sectionRef"></a> function with an implentation specific version which does not serialize to an XML data model until absolutely nessecary.</li>
-        <li>Enable the functions of this module to be used with other <a href="http://expath.org/spec/http-client#d2e183" title="The request elements">http:request</a> XML documents, for examples as those used by the <a href="http://expath.org/modules/http-client/" title="EXPath HTTP Client Module">EXPath HTTP Client Module</a>.</li>
+        <li>Enable the functions of this module to be used with other <a href="https://expath.org/spec/http-client#d2e183" title="The request elements">http:request</a> XML documents, for examples as those used by the <a href="https://expath.org/modules/http-client/" title="EXPath HTTP Client Module">EXPath HTTP Client Module</a>.</li>
       </ol>
     </section>
     <section id="functions">
@@ -423,7 +423,7 @@ <h4>request:cookie</h4>
       </section>
       <section>
         <h3>Request Body Functions</h3>
-        <!-- Zorba approach is interesting but not consistent, http://www.28msec.com/html/doc/2.0/modules/28msec/http/request#parts-0
+        <!-- Zorba approach is interesting but not consistent, https://www.28msec.com/html/doc/2.0/modules/28msec/http/request#parts-0
           Should rather have extra parameter, header, cookie and body functions that take a multipart identifier as an arg e.g.
           
           request:multipart-identifiers() as xs:string*