Day 2 minutes

Sunday 20191110

http request

• Geert and Achim present a proposal for changes in the p:http-request step
• Take some of the information from the c:request document to maps?
  • Some people better like creating a c:request document
  • But in 3.0 its easy to wrap something around that transforms one approach to the other
• Break it into two or more versions?
• Multiple output ports, one for the result and one for the headers?

Decisions:

• All attributes of c:request go to options
  • method will have a default value GET
  • status-only is gone because you can use HEAD or simply ignore the result
  • detailed is gone because this information is gone, this now comes out of a separate output port
  • There will be a new option to set the global headers, as a map
• Authentication information (username, password, etc.) will go into a single auth option using a map
• Headers for the request go into a header option, as a map
• There will be a separate output port for the header information
• If you get a multipart response, you will have multiple documents on the output port.
  • Header information for the separate documents goes into the document-properties of these, as straight properties
• The same happens on multipart requests
  • The document-properties become the headers
  • Exceptions are base-uri and serialization: these are never send.
  • The serialization document property is used to serialize the document in the request

Final results of discussion on: https://github.com/xproc/Workshop-2019-11/wiki/p:http-request-notes

Geert and Achim will write the spec for this.

XVRL

• Work is still being done on this by Gerrit
• Default report format for the validation steps is xvrl or implementation defined?
  • Values for this are implementation defined
  • We decide on:
    • svrl as default for the schematron validation
    • xvrl as default for all the others