Jerome Louvel

Renamed issue from "Real-time" to "Server-Push" requirement

I agree that versionning is not a feature, it just comes in the blog post to illustrate the Custom Interface constraint and the properties it results in. This should likely...

that's fine with me, I changed the label. In some way a property is a requirement that has been full-filled, but it is more logically anyway to start from requirements.

that's clear for me. REST requirements are actually specified in chapter 4: http://roy.gbiv.com/pubs/dissertation/web_arch_domain.htm

For now I renamed it to "Mobile Aware" constraint

With the explosion of mobile devices (smartphone, tablet and other connected devices), mobile clients are today the biggest driver for API traffic growth. This is a fundamental shift along with...

The Extensibility requirement can lead into versioned web APIs. The Dist. Hypermedia requirement should very likely be removed for the Web API style. Even though URIs (relative or absolute) should...

If I adapt the extensibility requirement from REST to the Web API style, I get this: "While simplicity makes it possible to deploy an initial Web API, extensibility allows us...

I agree that hypermedia shouldn't be a requirement for the Web API style. This GitHub issue/ticket is only about considering REST requirements and see if they match (or not) with...

Regarding the Low-barrier for entry, we should aim at the simplicity of the web. Being able to use a web API without having to write a program, using a simple/raw...