This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11361 - form support for URI templates
Summary: form support for URI templates
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL: http://lists.whatwg.org/pipermail/wha...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-20 18:55 UTC by Julian Reschke
Modified: 2013-02-25 22:56 UTC (History)
7 users (show)

See Also:


Attachments

Description Julian Reschke 2010-11-20 18:55:12 UTC
It would be great if HTML forms could be used not only to generate query parameters but also parts of the URI path, using a templating language.

See 

 http://tools.ietf.org/html/draft-gregorio-uritemplate
Comment 1 Peter Winnberg 2010-11-21 15:15:42 UTC
http://blog.whatwg.org/proposing-uri-templates-for-webforms-20

I think that old discussion at the WHATWG weblog is related to this, right?
Comment 2 Julian Reschke 2012-02-20 16:31:08 UTC
(In reply to comment #0)
> It would be great if HTML forms could be used not only to generate query
> parameters but also parts of the URI path, using a templating language.
> 
> See 
> 
>  http://tools.ietf.org/html/draft-gregorio-uritemplate

In the meantime approved and in the RFC Editor queue: http://www.rfc-editor.org/queue2.html#draft-gregorio-uritemplate
Comment 3 Robin Berjon 2013-01-21 15:59:06 UTC
Mass move to "HTML WG"
Comment 4 Robin Berjon 2013-01-21 16:01:51 UTC
Mass move to "HTML WG"
Comment 5 Edward O'Connor 2013-02-25 22:56:46 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Additional Information Needed
Change Description: No spec change.
Rationale: It's an interesting idea. Would you be interested in pursuing
such a feature in an extension specification?

         http://www.w3.org/html/wg/wiki/ExtensionSpecifications

I note that there's already an extension spec which enhances <form>
features. Perhaps you could coordinate with its editor?

     http://cameronjones.github.com/form-http-extensions/index.html