Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add change logs and update my contact info #741

Merged
merged 2 commits into from
May 27, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 16 additions & 2 deletions jsonschema-core.xml
Original file line number Diff line number Diff line change
Expand Up @@ -30,14 +30,15 @@
</author>

<author fullname="Henry Andrews" initials="H" surname="Andrews" role="editor">
<organization>Riverbed Technology</organization>
<address>
<postal>
<street></street>
<street>680 Folsom St.</street>
<city>San Francisco</city>
<region>CA</region>
<country>USA</country>
</postal>
<email>henry@cloudflare.com</email>
<email>handrews@riverbed.com</email>
</address>
</author>

Expand Down Expand Up @@ -3272,9 +3273,22 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0
<list style="hanging">
<t hangText="draft-handrews-json-schema-02">
<list style="symbols">
<t>Update to RFC 8359 for JSON specification</t>
<t>Moved "definitions" from the Validation specification here as "$defs"</t>
<t>Moved applicator keywords from the Validation specification as their own vocabulary</t>
<t>Moved the schema form of "dependencies" from the Validation specification as "dependentSchemas"</t>
<t>Formalized annotation collection</t>
<t>Specified recommended output formats</t>
<t>Defined keyword interactions in terms of annotation and assertion results</t>
<t>Added "unevaluatedProperties" and "unevaluatedItems"</t>
<t>Define "$ref" behavior in terms of the assertion, applicator, and annotation model</t>
<t>Allow keywords adjacent to "$ref"</t>
<t>Note undefined behavior for "$ref" targets involving unknown keywords</t>
<t>Add recursive referencing, primarily for meta-schema extension</t>
<t>Add the concept of formal vocabularies, and how they can be recognized through meta-schemas</t>
<t>Additional guidance on initial base URIs beyond network retrieval</t>
<t>Allow "schema" media type parameter for "application/schema+json"</t>
<t>Better explanation of media type parameters and the HTTP Accept header</t>
</list>
</t>
<t hangText="draft-handrews-json-schema-01">
Expand Down
11 changes: 8 additions & 3 deletions jsonschema-hyperschema.xml
Original file line number Diff line number Diff line change
Expand Up @@ -31,14 +31,15 @@
</title>

<author fullname="Henry Andrews" initials="H" surname="Andrews" role="editor">
<organization>Riverbed Technology</organization>
<address>
<postal>
<street></street>
<street>680 Folsom St.</street>
<city>San Francisco</city>
<region>CA</region>
<country>USA</country>
</postal>
<email>henry@cloudflare.com</email>
<email>handrews@riverbed.com</email>
</address>
</author>

Expand Down Expand Up @@ -2751,7 +2752,11 @@ Link: <https://example.com/api/trees/1/nodes/456>; rev="up"
<list style="hanging">
<t hangText="draft-handrews-json-schema-hyperschema-02">
<list style="symbols">
<t></t>
<t>Allow multiple values for "rel"</t>
<t>Clarify that "headerSchema", like "targetHints", should use array values</t>
<t>Clarified link behavior with conditional applicator keywords such as "if"</t>
<t>Added and clarified various examples</t>
<t>Avoid accidentally implying that only POST can be used to create in HTTP</t>
</list>
</t>
<t hangText="draft-handrews-json-schema-hyperschema-01">
Expand Down
10 changes: 8 additions & 2 deletions jsonschema-validation.xml
Original file line number Diff line number Diff line change
Expand Up @@ -41,14 +41,15 @@
</author>

<author fullname="Henry Andrews" initials="H" surname="Andrews" role="editor">
<organization>Riverbed Technology</organization>
<address>
<postal>
<street></street>
<street>680 Folsom St.</street>
<city>San Francisco</city>
<region>CA</region>
<country>USA</country>
</postal>
<email>henry@cloudflare.com</email>
<email>handrews@riverbed.com</email>
</address>
</author>

Expand Down Expand Up @@ -1292,6 +1293,11 @@
<t>Moved "definitions" to the core spec as "$defs"</t>
<t>Moved applicator keywords to the core spec</t>
<t>Renamed the array form of "dependencies" to "dependentRequired", moved the schema form to the core spec</t>
<t>Added "contentSchema" to allow applying a schema to a string-encoded document</t>
<t>Also allow RFC 4648 encodings in "contentEncoding"</t>
<t>Added "minContains" and "maxContains"</t>
<t>Update RFC reference for "hostname" and "idn-hostname"</t>
<t>Add "uuid" and "duration" formats</t>
</list>
</t>
<t hangText="draft-handrews-json-schema-validation-01">
Expand Down
5 changes: 3 additions & 2 deletions relative-json-pointer.xml
Original file line number Diff line number Diff line change
Expand Up @@ -28,14 +28,15 @@
</author>

<author fullname="Henry Andrews" initials="H" surname="Andrews" role="editor">
<organization>Riverbed Technology</organization>
<address>
<postal>
<street></street>
<street>680 Folsom St.</street>
<city>San Francisco</city>
<region>CA</region>
<country>USA</country>
</postal>
<email>andrews_henry@yahoo.com</email>
<email>handrews@riverbed.com</email>
</address>
</author>

Expand Down