Asbjørn Ulsberg

@BeeWarloc You're starting to convince me. :wink: Especially by using URIs as a scheme for identifying `type`, which I think is a good idea. It's the same standard defined for...

In essence, the `Link` header doesn't need to represent anything other than what's already within the HTTP body, but it can. See [this blog post by Mark Nottingham](https://www.mnot.net/blog/2012/10/29/NO_OPTIONS) and [RFC...

@BeeWarloc, you need to consider the work required to query and process the data to deliver the JSON body too. Accumulated, this repeated querying, processing and serialization might not be...

Another option would be to use the [`profile` link relation](https://www.ietf.org/rfc/rfc6906.txt).

Haven't we agreed verbally to use `application/ld+json` as the next serialization format slash content type? If so, we should close this and create a new issue for implementing JSON-LD for...

It might be worth looking at [Nancy.Swagger](https://github.com/khellang/Nancy.Swagger) as well.

Relatedly, [JSON.NET will get JSON Schema Draft 4 Support](/JamesNK/Newtonsoft.Json/issues/115#issuecomment-67729494) soon.

Scrap all of the above. [Hydra](http://www.hydra-cg.com/) is the format we should use as a basis for generating both the client library and the documentation. It is based on [JSON-LD](http://json-ld.org/) and...

I'm not sure. I find that when there's several ways to achieve something, the simplest and most obvious one should be the "best" for at least 80% of the use...

Given @timorzadir's example, the thing that is completed is: ``` csharp var restClient = new RestClient.Client("http://example.com", new HttpWebRequestClient()); restClient.LazyLoadingEnabled = false; //Disable lazy for entire client ``` I.e. "opt-out lazy-loading...