On 05/12/06, Jan Algermissen <[EMAIL PROTECTED]> wrote: > > > > > > > > On Dec 5, 2006, at 12:34 AM, Steve Jones wrote: > > > And if names are obfuscated and not meaningful then how do you > > communicate to clients what the URI actualy means and what request > > they should make? > > From a REST POV, it is important that the client knows the meaning > of traversing a certain link (the meaning of the state transition > perfromed by traversing that link). The client knows this from the > media type. The URI is *not* providing any meaning in terms of > traversing through the application's state machine, it is just an > object identifier.
What is the media type for an invoice? How do I know how to get from invoice to customer? I'm getting really confused as to how a link traversals meaning is documented via a media type, unless of course you create a whole new ontology of media types for every project. > > If you have a URI and no clue what to do...do a GET and follow your > nose[1]. Sounds like debugging via printf on an application someone else wrote.... > > Jan > >
