W3C home > Mailing lists > Public > www-talk@w3.org > March to April 2003

Re: RDF Description of HTTP headers/meta-data

From: S. Mike Dierken <mdierken@hotmail.com>
Date: Wed, 2 Apr 2003 21:39:58 -0800
To: "Justin Chapweske" <justin@chapweske.com>
Cc: <www-talk@w3.org>
Message-ID: <OE50WuLn5U9T3TGJ2TU0000a82d@hotmail.com>

Hmm.
A URI doesn't have metadata that corresponds to HTTP headers (like
content-type).

Resources also don't innately have metadata - they handle requests and
provide responses. The responses can easily vary over many of the
interesting pieces of metadata - so there isn't a one-to-one mapping from a
resource to a single canonical content-type for example.

It would be sensible to describe the requests a particular resource
supports - especially in terms of the Accept type of headers - and perhaps
reflect the kind of responses the might be given.

For example, you might say that a response would contain a
content-type='text/plain' when the request contains an accept='text/plain',
or if the request contains a user-agent='Mozilla *' or something.

Alternatively, you may be simply trying to describe the response to a GET
request - but since there are many possible varying representations, you
probably need to include something of the request that generated that
response.


----- Original Message -----
From: "Justin Chapweske" <justin@chapweske.com>
To: "S. Mike Dierken" <mdierken@hotmail.com>
Cc: <www-talk@w3.org>
Sent: Wednesday, April 02, 2003 8:51 PM
Subject: Re: RDF Description of HTTP headers/meta-data


>
> Thanks for the link, but I'm looking for something subtly different.
>
> XMTP is a format for serializing MIME into XML.
>
> I'm looking for an RDF syntax that makes statements about the metadata
> of a URI, using HTTP headers as the source data.
>
> S. Mike Dierken wrote:
> > A most excellent approach is documented here:
> > http://www.openhealth.org/xmtp/
> >
>
>
>
> --
> Justin Chapweske, Onion Networks
> http://onionnetworks.com/
>
>
Received on Thursday, 3 April 2003 00:35:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:27 GMT