W3C home > Mailing lists > Public > www-rdf-interest@w3.org > April 2000

Re: The semantic web

From: Pierre-Antoine CHAMPIN <pachampi@caramail.com>
Date: Tue Apr 11 09:14:34 2000
To: Tom Van Eetvelde <tom.van_eetvelde@alcatel.be>, "www-rdf-interest@w3.org" <www-rdf-interest@w3.org>, Pierre Maraninchi <penguino@caramail.com>, frankh@cs.vu.nl, Pierre Maraninchi <penguino@caramail.com>, dieter.fensel@aifb.uni-karlsruhe.de
Message-ID: <955449524023236@caramail.com>
> I have read the article "Practical Knowledge 
Representation for the Web" (
) and to my surprise, RDF
> is depicted as an immature and disappointing language for 
representing semantics. This is in clear
> contrast with the promise of RDF as the language to make 
the Semantic Web come true.
> The authors could be biased as they come from the AI 
world, but nevertheless, their arguments seem
> well founded to me.

thanks for the link; very interesting article

> Does anyone have comments on this article?

I do :)

- about nesting (3.3)
I think the author are quite unfair : RDF CAN do nesting. 
Sure it is more verbose than plain XML,  and hence less 
readable - is this what they mean when they write that 
nesting is not expressible "in a natural way" ?
Furthermore, this is a syntactical issue, and I think the 
whole RDF community agrees on the necessity of a simplified 
syntax. (Personnaly, I'm even much confident in an 
attribute-based syntax - in the XLink fashion - allowing to 
interpret any XML tags as RDF).

- about RDF beeing property-centric (4.1)
ah ! This is always the itchy part for people used to 
object oriented models. I believe this is not a mistake, 
though : once a property has been defined, any new schema 
can use it, and therefore be (partially) understood by 
anyone understanding that property.This is the whole point 
- and this is possible because the domain of a property can 
ALWAYS be extended (since it is not bound to be unique).
About translating Ontobtoker ontology into RDFS (4.2) , 
prefixing class-names to property-names is not the best 
solution : using a different namespace for each class is 
much more elegant.

- about inferences (4.3)
here is the most unfair point, IMHO : the kind of inference 
proposed here is straightforward in RDFS with 

 Anyone seeing anything I forgot ?


Vendez tout... aux enchères - http://www.caraplazza.com
Received on Tuesday, 11 April 2000 09:14:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:29 UTC