hi
1)
Pg. 81:
"If two parts of a resource are independently updatable, they should be separately addressable resources."
a) So if order resource would allow <milk> state to be independently updatable from other parts of order resource, then we could (should?) create a separate resource containing just <milk> state?
b) If my assumption in a) is correct, then we'd have two resources R1 and R2, where R2 would only contain <milk> state, while R1 would contain all other state. But should R1 also contain <milk> state?
c) I assume even if R1 also contains <milk> state, consumers shouldn't be able to also set <milk> state when updating R1?
d) Assuming R1 shouldn't contain <milk> state, then how do we indicate to consumers that R1 and R2 combined represent order?
2) At https://groups.google.com/forum/#!topic/restinpractice/hE3wQ2U9UaQ Jim Webber implied that it's still REST if one uses the following two links, each updating different parts of coffee order:
<dap:link rel="http://relations.restbucks.com/addition"
... uri="http://restbucks.com.order/1/additions" />
<dap:link rel="http://relations.restbucks.com/cupsize" ... uri="http://restbucks.com.order/1/cups" />
a) I assume http://restbucks.com.order/1/additions and http://restbucks.com.order/1/cups identify two different resources, one representing addition state and other cupsize state?
b) If my assumption in a) is correct, is then order represented