Hi,
On 12/6/06, Steve Jones <[EMAIL PROTECTED]> wrote:
> What is the media type for an invoice?
Does it matter? If it comes back as a PDF, your only choice is to
print it, if it's a text file I guess you just read it, if it's an XML
application I guess you look at the DOCTYPE or the namespace of the
root element, and so forth. If you view with a browser, you probably
view the document, but if you're an application, then you can do a
number of things with it. An invoice is probably an application of
XML, in which you inspect the XML to see if you understand the schema
it was written in. If it was, then you're good to go.
> How do I know how to get from invoice to customer?
How do you do that on any other stack, or any other technology?
> 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.
When you browse a URL, what does it mean? When you use a SOAP service,
what does it mean? When communicating on this mailing-list, what does
it mean? I think you're stretching the term "meaning" here ... :)
The *meaning* of a URL is whatever we make it. There's guidelines
which says we should make URL's as meaningful as possible, but there's
no requirement to do so. But if we can, we should, just with any other
URL out there; REST builds on some nice human principles of
exploration that I find very attractive.
> > 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....
Sounds like you're trolling...
Alex
--
"Ultimately, all things are known because you want to believe you know."
- Frank Herbert
__ http://shelter.nu/ __________________________________________________
