-
-
Notifications
You must be signed in to change notification settings - Fork 348
Add non-http "method": "post" LDO example #282
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
Conversation
jsonschema-hyperschema.xml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: minItems
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
heh. Maybe I should remember to validate my examples against the meta-schema :-P
Add an example showing how a non-HTTP URI scheme can be used, showing a form for constructing an email with two different representations, as well as requiring a subject.
0bf1b24 to
e06c358
Compare
I think this makes sense. This is a lot like how you would do it with an HTML Form.
@awwright if you agree with @jdesrosiers that this is reasonable, should we go ahead and add it to Draft 06? It shouldn't change anything, only clarify.
It's maybe a bit more verbose than ought to be necessary, but still, a good illustration of this behavior is probably warranted.
@awwright I tend to be verbose, unfortunately. Anything in particular you'd trim?
@awwright did that comment count as an approval?
I think I just needed to sit on it another day. Looks good.
@awwright thanks! Totally reasonable, just wasn't quite clear :-)
This PR need not necessarily go into Draft 06
I'm posting this mostly to illustrate some of the arguments in #280, particularly around avoiding coupling of JSON Hyper-Schema and any particular URI scheme or protocol.
If we can't figure out a reasonable mapping for
mailto:then we might be missing something. Although that something will probably need to wait until Draft 07 for a fix.I am aware that it's more common to use an HTTP request to ask the server to send mail, but I think this still makes a good example. If the client for this resource runs in a known environment, it could be reasonable to expect the client to send mail if it wants to.
Add an example showing how a non-HTTP URI scheme can be used,
showing a form for constructing an email with two different
representations, as well as requiring a subject.