diff --git a/request-module-1.0-specification.html b/request-module-1.0-specification.html index 5ae24a5..8e17bd6 100644 --- a/request-module-1.0-specification.html +++ b/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,10 +38,10 @@ // 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. @@ -49,8 +49,8 @@ // 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 @@

Namespaces and Prefixes

Accessing the HTTP Context

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.

-

By default this module provides a function to access the HTTP Request Context, which returns an XML Document whoose root element is http:request.

+

By default this module provides a function to access the HTTP Request Context, which returns an XML Document whoose root element is http:request.

The reasons for using function passing to access the HTTP Context include:

  1. Enable easy mocking of the HTTP Context for testing.
  2. Easier optimisation by substitution of the function with an implentation specific version which does not serialize to an XML data model until absolutely nessecary.
  3. -
  4. Enable the functions of this module to be used with other http:request XML documents, for examples as those used by the EXPath HTTP Client Module.
  5. +
  6. Enable the functions of this module to be used with other http:request XML documents, for examples as those used by the EXPath HTTP Client Module.
@@ -423,7 +423,7 @@

request:cookie

Request Body Functions

-