[http://creativecommons.org/licenses/by/3.0/]
This work is licensed under a CC
Attribution 3.0 Unported License [http://creativecommons.org/licenses/by/3.0/]
Identification, identity and the uniform interface (how to interact with identified things) are the most basic constraints of REST. Today, we look at two more constraints of the REST architectural style: Representations are the only thing that are actually available in a RESTful system, and when interacting with a resource, the interactions use self-describing representation. This means that it is possible for actors in a RESTful system to interact with resources without prior knowledge of what media types to expect or to use. We will look at different metamodels that can be used to define specific representations, HTML, XML, JSON, and RDF are popular examples. Since interactions yield representations that are supposed to be starting points for further interactions, representing links is another core constraint of REST. Links often have (implicit or explicit) types which guide clients of RESTful services through the set of available resources. We will look at links from the RESTful perspective, looking at popular patterns such as directories, search services, and typical purchasing workflows.
PATCH
[http://tools.ietf.org/html/rfc5789] exists but requires agreement on how to patch resourceson-demand granularitywould be useful
best natural fitin terms of the metamodel
link overlay
eatsor
lives in symbiosis with
loosely coupled zoothat can be built with those principles?
part of the zooanimals must be described in a standardized way
link overlay(guiding
visitorsto/through the resources)
zoobecomes a narrative that is not bound to any physical location
submit orderor
accept prepared food
loosely coupled food courtthat can be built with those principles?
part of the food courtrestaurants must be described in a standardized way
link overlay(guiding
customersto/through the resources)
one-ended links(text linked to a page)
explicit human-assisted PageRank
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>An exciting Sidewiki Test!</title> <!-- Load Sidewiki element Javascript API --> <script src="http://www.google.com/sidewiki/static/sidebar_element/sidebar-element-compiled.js"></script> </head> <body> <!-- Initialize element --> <script> // Create the element, show entries for the current webpage. var sidebarElement = new google.elements.sidewiki.SidebarElement(window.location.href, true); </script> <h1>An exciting Sidewiki Test!</h1> <p>Here's some fascinating content!</p> </body> </html>