W3C home > Mailing lists > Public > www-tag@w3.org > April 2008

RE: Uniform access to descriptions

From: Williams, Stuart (HP Labs, Bristol) <skw@hp.com>
Date: Wed, 9 Apr 2008 16:53:26 +0000
To: "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com>, "wangxiao@musc.edu" <wangxiao@musc.edu>, Pat Hayes <phayes@ihmc.us>
CC: Jonathan Rees <jar@creativecommons.org>, "www-tag@w3.org WG" <www-tag@w3.org>, Phil Archer <parcher@icra.org>
Message-ID: <9674EA156DA93A4F855379AABDA4A5C611CE63E56A@G5W0277.americas.hpqcorp.net>

> -----Original Message-----
> From: www-tag-request@w3.org [mailto:www-tag-request@w3.org]
> On Behalf Of Williams, Stuart (HP Labs, Bristol)
> Sent: 09 April 2008 17:26
> To: wangxiao@musc.edu; Pat Hayes
> Cc: Jonathan Rees; www-tag@w3.org WG; Phil Archer
> Subject: RE: Uniform access to descriptions

> Tempted to answer... ok... I will... Well certainly (1) but
> what it is that is important is *not* to confuse a
> [awww:representation of [a 'thing']] with a
> [awww:representation of [a description/depiction of [a 'thing']]].

In the light of a para in Pat's most recent response:

        All that matters (to me, and I may not be exactly aligned with the TAG here)
        is the distinction between things that can send, or be, messages over wires
        (I don't really care about making this sub-distinction exact) and things
        that cannot.

I would add... "Particularly in the case of things that cannot (possibly) have webarch:representations." to my response above.

Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England
Received on Wednesday, 9 April 2008 16:57:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:20 UTC