State Transitions in a REST-based Network
Recall the Parts Depot example. The parts list resource returns this representation:
<p:Parts xmlns:p="http://www.parts-depot.com"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
"http://www.parts-depot.com
http://www.parts-depot.com/parts.xsd">
<Part id="00345" xlink:href="http://www.parts-depot.com/parts/00345"/>
<Part id="00346" xlink:href="http://www.parts-depot.com/parts/00346"/>
<Part id="00347" xlink:href="http://www.parts-depot.com/parts/00347"/>
<Part id="00348" xlink:href="http://www.parts-depot.com/parts/00348"/>
This document contains hyperlinks to resources that provide detailed
information about each part. When a client application follows one of the
hyperlinks it receives a representation of the resource identified by the hyperlink.
This transfers the client application to the next state.