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

Re: Critical literal semantics issue

From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
Date: Tue, 14 Jan 2003 08:40:30 -0500 (EST)
Message-Id: <20030114.084030.34985794.pfps@research.bell-labs.com>
To: Patrick.Stickler@nokia.com
Cc: jjc@hplb.hpl.hp.com, w3c-rdfcore-wg@w3.org

The LCC version of the RDF Semantics as referenced on the RDF Core WG home
page, at http://www.w3.org/2001/sw/RDFCore/TR/WD-rdf-mt-20030117/,
*explicitly* does not make the class extension of rdfs:Literal have
any relationship whatsoever to LV.  There is even an entire section of the
document on the non-relationship between ICEXT(I(rdfs:Literal)) and LV.

This decoupling of ICEXT(I(rdfs:Literal)) and LV causes lots of problems,
as detailed in a message I sent to RDF comments

Peter F. Patel-Schneider
Bell Labs Research
Lucent Technologies.

From: Patrick.Stickler@nokia.com
Subject: RE: Critical literal semantics issue
Date: Tue, 14 Jan 2003 11:27:57 +0200

> > > All this means is that rdfs:Literal denotes a class, but it 
> > says nothing
> > > about the class extension of rdfs:Literal.  
> > 
> > The class extension of rdfs:Literal is understood to be a subset of LV
> > (see further comments below), i.e. all resources which are 
> > denoted by a 
> > plain (untyped) literal or a valid typed literal are in LV and hence
> > instances of rdfs:Literal.
> Or rather, the class extension of rdfs:Literal *is* LV.
> Patrick
Received on Tuesday, 14 January 2003 08:42:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:54:03 UTC