Re: User Hypermedia format

yep - you got it right.

i might add some prose that sets expectations on which level of support for
RFC6570 is needed in order to be uber-compliant. that might lower the bar
for implementation.




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 Mon, Feb 24, 2014 at 12:48 AM, Alexander Johannesen <
[email protected]> wrote:

> Hiya,
>
> > as for the use of @model. this is applied to the associated @url in the
> same <data> element. That means you have full control over how much is in
> the @model and how much is in the @url. That includes path segements, etc.
> just as outlined in RFC6570.
> >
> > Does this clarify things?
>
>
> Only where RFC6570 is clear. :) I guess I'm responding to the examples
> from the website where for example we've got ;
>
> <data name="search" rel="search" url="http://example.org/search"
> model="{&title}" />
>
> Which I assume is applied to that URL with a ?param structure, but what
> with ;
>
> <data name="search" rel="search" url="http://example.org/search"
> model="/{&type}/{&title}" />
>
> Will that resolve to http://example.org/search/{type}/{title}? If yes,
> then I understand how RFC6570 applies to the format. If no, I need
> education.
>
>
> Cheers,
>
> Alex
>
> --
>  Project Wrangler, SOA, Info Alchemist, UX, RESTafarian, Topic Maps
>  http://shelter.nu/blog  |  google.com/+AlexanderJohannesen
>  http://xsiteable.org  |  http://www.linkedin.com/in/shelterit
>
>
> ------------------------------------
>
> Yahoo Groups Links
>
>
>
>