[Home] [By Thread] [By Date] [Recent Entries]


John Cowan wrote:
> Tim Bray scripsit:
> 
> > (a) have a built-in way to disambiguate between what the 
> > resource "is" 
> > and what it's "about"
> > (b) use different names.
>
> Given this choice, I like
> (a) better.

How do you draw the distinction between representation and resource?  One
man's meat is another man's poison.

What is understood as a representation by X may be seen as a resource by Y.
A web page could be a resource or a representation of a resource, depending
upon the context in which is used. To a browser, every HTML document is a
resource unto itself; the page represents nothing. 

Even Will Shakespeare could be seen as representation of a set of
chromosomes.  If you can't agree on where to draw the
resource/representation dichotomy, how can you agree on an identifier
scheme?  



Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member