W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > February 2003

Re: Social meaning discussion 6th March

From: Brian McBride <bwm@hplb.hpl.hp.com>
Date: Thu, 27 Feb 2003 10:34:12 +0000
Message-Id: <>
To: Jeremy Carroll <jjc@hplb.hpl.hp.com>, pat hayes <phayes@ai.uwf.edu>, Bijan Parsia <bparsia@isis.unc.edu>, Graham Klyne <GK@ninebynine.org>, tim Berners-Lee <timbl@w3.org>
Cc: RDF Core <w3c-rdfcore-wg@w3.org>

Sans chapeau:

My bath time this morning was spent thinking about social meaning.  I came 
to the conclusion that 'meaning' is a difficult and slippery a concept that 
we should try to stay away from, sticking to things that are more 
concrete.  We should leave talk about 'meaning' to the 
philosophers.  Perhaps we can get all we need by describing intended use.

And then I see this is exactly what Jeremy has done in his draft 
alternative text.


This is a significant shift in approach that may have considerable merit, 
and I wanted to draw attention to it.

The mininalist approach looks good too, though we might go a bit further:

   1 An RDF triple is intended to be used to represent an assertion
   2 A set of RDF triples is intended to be used to represent the 
conjunction of the assertions represented by each individual triple
   3 The assertion represented by an RDF triple is determined by the 
specifications of its subject, predicate and object.
   4 RDF triples representing false assertions SHOULD NOT be used to mislead.

The above being non-normative.

I'm not happy with 4.  RDF triples representing true assertions SHOULD NOT 
be used to mislead either, yet "RDF triples SHOULD NOT be used to mislead" 
is vacuous.  So maybe strike 4, though I'm inclined to leave it in.


At 00:02 27/02/2003 +0100, you wrote:

>BCC-ed to three groups, sorry for duplicates.
>I have put together a preliminary agenda for this session to be found at:
>Note I suggest reading the relevant text and Bijan's comments on it as
>I would particularly welcome feedback if the list of issuettes is incomplete.
>(I have tried to include substantial concerns rather than ones that could be
>addressed by editorial changes).
Received on Thursday, 27 February 2003 05:33:57 UTC

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