* identify and design the data model
- what objects are represented?
- what properties do they have?
- what are the relationships?
* identify the operations needed to operate on the data model
* define the protocol around the above items
I think the last step will just kind of "fall out" once we have the first
two items. Once the operations and data is known, then it becomes
relatively trivial to express that within different protocol models (REST,
SOAP, etc).
This approach also defers the question of protocol representation and
allows us to concentrate on the fundamentals of what we're trying to do.
Any thoughts on trying this approach?