search

w3c-social / social-arch

This document takes a broad look at all the social technologies and specifications under development, including summarizing their contribution and tracking their adoption. The document will then demonstrate how a subset of these can be used as a unified architecture.
http://w3c-social.github.io/social-arch/
6 stars 2 forks source link

automated form generation #3

Open elf-pavlik opened 9 years ago

elf-pavlik commented 9 years ago

Modern applications often render forms. Hypermedia APIs also need ways to describe expected inputs. Many efforts exist nowadays but no standard yet to address it.

See also

dret commented 9 years ago

URI templates http://tools.ietf.org/html/rfc6570 are one possible foundation, even though they are only part of a solution. @mamund's UBER https://github.com/mamund/media-types/blob/master/uber-hypermedia.asciidoc and my own link descriptions http://tools.ietf.org/html/draft-wilde-link-desc are attempts and bridging the gap between RFC 6570 and associating template variables with concepts. of course this is all about the "machine form" idea and not so much about the HTML-ish notion of UIs for form data. at https://github.com/dret/hyperpedia i am in the process of describing general hypermedia concepts (https://github.com/dret/hyperpedia/blob/master/concepts.md#traversal-hints is where i am covering forms under the general concept of "traversal hints"), so maybe that's a good opportunity to look at some formats in more detail and see if and how they do provide sufficient information so that link traversal can include form-like interaction semantics.