We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi Mike,
How would you represent radio options/drop-down menu items within collection-json? My idea is to use links in items like this:
{ "collection" : { "version" : "1.0", "href" : "http://example.org/friends/profile/jdoe", "links" : [ {"rel" : "feed", "href" : "http://example.org/friends/jdoe/rss"} ], "items" : [ { "href" : "http://example.org/friends/profile/edit/jdoe", "data" : [ {"name" : "Field", "value" : "Occupation", "prompt" : "Occupation"}, ], "links" : [ {"rel" : "options", "href" : "http://examples.org/field/options/occupations", "prompt" : "Available Options in occupations", "render": "link}, ] }, ........
By doing this, the client requires making GET calls to the links, which increases transaction overheads. How would you go about representing it? :)
The text was updated successfully, but these errors were encountered:
i found this pending merge: mamund/collection-json#6
can't recall why it never got merged in.
does this help you out?
mamund +1.859.757.1449 skype: mca.amundsen http://amundsen.com/blog/ http://twitter.com/mamund https://github.com/mamund http://linkedin.com/in/mamund
On Sun, Nov 2, 2014 at 4:35 AM, John Lim [email protected] wrote:
Hi Mike, How would you represent radio options/drop-down menu items within collection-json? My idea is to use links in items like this: { "collection" : { "version" : "1.0", "href" : "http://example.org/friends/profile/jdoe", "links" : [ {"rel" : "feed", "href" : "http://example.org/friends/jdoe/rss"} ], "items" : [ { "href" : "http://example.org/friends/profile/edit/jdoe", "data" : [ {"name" : "Field", "value" : "Occupation", "prompt" : "Occupation"}, ], "links" : [ {"rel" : "options", "href" : "http://examples.org/field/options/occupations", "prompt" : "Available Options in occupations", "render": "link}, ] }, ........ By doing this, the client requires making GET calls to the links, which increases transaction overheads. How would you go about representing it? :) — Reply to this email directly or view it on GitHub #4.
{ "collection" : { "version" : "1.0", "href" : "http://example.org/friends/profile/jdoe",
"links" : [ {"rel" : "feed", "href" : "http://example.org/friends/jdoe/rss"} ], "items" : [ { "href" : "http://example.org/friends/profile/edit/jdoe", "data" : [ {"name" : "Field", "value" : "Occupation", "prompt" : "Occupation"}, ], "links" : [ {"rel" : "options", "href" : "http://examples.org/field/options/occupations", "prompt" : "Available Options in occupations", "render": "link}, ] },
........
— Reply to this email directly or view it on GitHub #4.
Sorry, something went wrong.
No branches or pull requests
Hi Mike,
How would you represent radio options/drop-down menu items within collection-json? My idea is to use links in items like this:
By doing this, the client requires making GET calls to the links, which increases transaction overheads. How would you go about representing it? :)
The text was updated successfully, but these errors were encountered: