Skip to content

A couple of edits/fixes in hyperschema spec #470

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Nov 6, 2017
Merged

A couple of edits/fixes in hyperschema spec #470

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bdcb32a
Fix 'to for' typo in hyperschema examples
Nov 3, 2017
0ecd5dd
Fix "submission MediaType" typo in hyperschema examples
Nov 3, 2017
2609c89
Fix "colletion" typo in hyperschema HTTP section
Nov 3, 2017
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
6 changes: 3 additions & 3 deletions jsonschema-hyperschema.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1289,7 +1289,7 @@ for varname in templateData:
</t>
<t>
This section provides guidance on how to use each common HTTP method with a link,
and how colletion resources impose additional constraints on HTTP POST.
and how collection resources impose additional constraints on HTTP POST.
Additionally, guidance is provided on hinting at HTTP response header values and
describing possible HTTP request headers that are relevant to the given resource.
</t>
Expand Down Expand Up @@ -1635,7 +1635,7 @@ Link: <https://schema.example.com/entry> rel=describedBy
input, as well as using them alongside of resolving the URI Template with
input. Unlike HTML forms, which require either constructing a URI or
sending a payload, but do not allow not both at once, JSON Hyper-Schema can
describe both sorts of input to for the same operation on the same link.
describe both sorts of input for the same operation on the same link.
</t>
<t>
The "submissionSchema" and "submissionMediaType" fields are for
Expand All @@ -1650,7 +1650,7 @@ Link: <https://schema.example.com/entry> rel=describedBy
a message for sending. Since there is no concept of a retrievable,
replaceable, or deletable target resource, "targetSchema" and
"targetMediaType" are not used. Non-representation payloads are
described by "submissionSchema" and "submission MediaType".
described by "submissionSchema" and "submissionMediaType".
</t>
<t>
Therefore, we use "submissionMediaType" to indicate a multipart/alternative
Expand Down