Re: User Hypermedia format

Alex:

Glad to hear this looks promising. This is a first draft so it's likely
some things will drift.  I am also very much interested in what you find as
you start your implementation. feedback on confusions/shortcomings in the
design will be most helpful.

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?



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, Feb 23, 2014 at 8:50 PM, Alexander Johannesen <
[email protected]> wrote:

>
>
> Hi there,
>
> I like it a lot, and might just rewrite some of my stuff into using this
> instead of my own (similar) format, just for the heck of it. :)
>
> Quick question; using the @model, is it assumed the model works as an
> extension to the current URI? Ie, if the current URI is "
> http://test.com/page" and there's a model there "?param=data" we just
> plonk it on the current URI, but using a more RESTful approach can often be
> @model="/{fiddle}/{foo}" so would that work as an appender to the current
> URI? I have a lot of URI templates around that use the structure like this,
> so would be good to just confirm that.
>
>
> Cheers,
>
> Alex
>
>
> On Mon, Feb 24, 2014 at 12:35 PM, mike amundsen <[email protected]> wrote:
>
>>
>>
>> /* pardon the cross-posting */
>>
>> I just published a first working draft of a new hypermedia format I am
>> (humbly) calling "Uber Hypermedia"[1]. I'm maintaining it in github[2]
>> where you can post issues, clone/PR, etc. if you like.
>>
>> It is designed to be *very* minimal. It has only three elements, 11
>> attributes, and seven reserved strings.
>>
>> Here is some text from the opening:
>> <snip>
>> The Uber message format is a minimal read/write hypermedia type designed
>> to support simple state transfers and ad-hoc hypermedia-based transitions.
>> This document describes both the XML and JSON variants of the format and
>> provides guidelines for supporting Uber messages over the HTTP protocol.
>>
>> The Uber message model has a number of design goals:
>> - Keep the message structure as lean as possible.
>> - Support all the H-Factors [HFactor] in hypermedia controls.
>> - Be compatible with multiple protocols (e.g. HTTP, CoAP, etc.)
>> - Maintain fidelity for more than one base message format (XML, JSON,
>> etc.)
>> </snip>
>>
>> I'm looking for any/all feedback here or in the repo space.  Thanks in
>> advance.
>>
>>
>> [1] https://rawgithub.com/mamund/media-types/master/uber-hypermedia.html
>> [2] https://github.com/mamund/media-types
>>  <https://github.com/mamund/media-types>
>>
>> mamund <https://github.com/mamund/media-types>
>> +1.859.757.1449
>> skype: mca.amundsen
>> <https://github.com/mamund/media-types>http://amundsen.com/blog/
>> http://twitter.com/mamund
>> https://github.com/mamund
>> http://linkedin.com/in/mamund
>>
>>
>>
>
>
> --
>  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
>
>
> 
>