From c57ef6c4112e5e977b4e1dd931671b83e0f7b58f Mon Sep 17 00:00:00 2001 From: Henry Andrews Date: Tue, 7 Nov 2017 00:11:15 -0800 Subject: [PATCH] Better wording in HTTP "targetHints" section --- jsonschema-hyperschema.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/jsonschema-hyperschema.xml b/jsonschema-hyperschema.xml index a53f6626..e8f6d6ae 100644 --- a/jsonschema-hyperschema.xml +++ b/jsonschema-hyperschema.xml @@ -1378,8 +1378,10 @@ for varname in templateData: similarly structured headers wherever possible. - No distinction is made between headers that may appear in responses to - different methods, such as HEAD vs OPTIONS. + Headers for all possible HTTP method responses all share "headerSchema". + In particular, both headers that appear in a HEAD response and those + that appear in an OPTIONS response can appear. No distinction is made + within "headerSchema" as to which method response contains which header. It is RECOMMENDED that schema authors provide hints for the values of