-
Notifications
You must be signed in to change notification settings - Fork 38
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
Drop URI Template Support #193
Comments
That means that you couldn't use json-home for generative URLs, which seems like a pretty big deal. |
On 2016-07-22 07:21, Mark Nottingham wrote:
true. it just seems to me that defining the one description format for at least for myself i can safely say that i have tried to come up with but then again, the latest draft does not really describe the variables, |
Hm. Unknown for now -- would have to look at the proto-implementations to see what they're doing here (if at all). More than anything, I just wanted to give the vars unique, global names. I agree that may not be enough motivation. |
On 2016-11-03 23:05, Mark Nottingham wrote:
understood. and yes, it would be good to see how much URI template
understood as well. and i think that's a very useful thing to do, i |
Closing for now, feel free to reopen if it's bugging you still. |
this is a radical proposal but maybe will make it easier to proceed: i am not sure how many people need and use the descriptive structures for URI templates. these seem to introduce quite a bit of complexity in the draft, and maybe will only be used by a small fraction of users. having attempted describing URI templates myself (https://github.com/dret/I-D/tree/master/Abandoned/link-desc) i tend to think that this is a hard problem to get right, so maybe dropping them would speed up the development of the spec, not really impact many users, and make the spec considerably more simple to read and use?
The text was updated successfully, but these errors were encountered: