W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > November 2002

Some semantics comments - more later.

From: Jeremy Carroll <jjc@hpl.hp.com>
Date: Sat, 09 Nov 2002 19:47:55 +0100
To: w3c-rdfcore-wg@w3.org
Message-id: <BHEGLCKMOHGLGNOKPGHDMEKCCAAA.jjc@hpl.hp.com>


Some more important ones first:
===
<<
3.4 Datatyped Interpretations

Suggest-delete:
[[We will assume that ]] A datatype is defined by 
a uriref and [[suggest-delete: itself]] defines ..
>>

Next paragraph on XMLLiteral - delete it all.
My section in concepts is better and clearer,
(IMHO!)
given that, there is no need to talk about these
at all in the Semantics.

Next paragraph:
... A 'datatype-aware' RDF engine should be competent
to recognize the 
<suggest-add: 
<a href="http://www.w3.org/TR/rdf-concepts#section-XMLLiteral">
rdfs:XMLLiteral 

(Note I am not online and have probably got the fragID wrong).
======

Section 4, should largely be informative, in case of errors, 
the other sections should take precedence.
I suggest one of two fixes:
My preference is:

<<suggest new heading>>
4.1 RDF-entailment and RDF closures (informative)
<<suggest new heading>>
4.2 RDFS-entailment and RDFS closures (informative)
<<suggest new heading>>
4.3 Datatype entailments

Linked with this edit I would
<<suggest new heading>>
Appendix C: Translation into Lbase (informative)

<<suggest-delete, from introduction 0.1>>
[[We believe that the two ... normative.]]

alternatively
In the introduction in section 0.1
suggest-change
[[
We believe that both these descriptions, 
and also the closure rules of section 4, 
are all in exact correspondence, but only
the direct model theory ...
]]


==========

Abstract
suggest-change
... RDF and RDFS, with some entailment results. It ...


=======

0.1 typo
[[reserver truth]]=>[[preserve truth]]

======
**sorry fragids missing****
0.2 Graph Syntax
Suggest delete 1st two paras
[[Any semantic theory ...
set containing that triple]]

New text:
[[[[[
This semantic theory is attached to the abstract
syntax of RDF [RDF_CONCEPTS].
We use the following terminology defined there:
+ uriref, defined as 
<a href="http://www.w3.org/TR/rdf-concepts#section-??
>
RDF URI Reference 
+  
<a href="http://www.w3.org/TR/rdf-concepts#section-??
>
literal 
+  
<a href="http://www.w3.org/TR/rdf-concepts#section-??
>
plain literal 
+  
<a href="http://www.w3.org/TR/rdf-concepts#section-??
>
typed literal 
+  
<a href="http://www.w3.org/TR/rdf-concepts#section-??
>
blank node
+  
<a href="http://www.w3.org/TR/rdf-concepts#section-??
>
triple


]]]]

Continue with [[The convention that ...]]

========

1.3 Assertions, meanings and inference

suggest-add
[[Editor's note: further work on the overlap with 
RDF_CONCEPTS is needed here.]]

(sorry I am not sufficiently on top of the 
assertion issue to help)       

===

Section 0.1
suggest-replace
[[See @@Jeremy ...discussion.]]
with
[[NOTE: This may duplicate material in RDF Concepts,
more editorial work is needed]]

===

Section 0.1

Suggest insert one word:
[[..same semantic theory: directly, and also (in an
**informative** appendix) an 'axiomatic semantics'..]]

Suggested Lbase ref:

Lbase, Hayes and Guha, in preparation.

===

Global replace untyped with plain

===
Global search for the word labelled - it is always an error.

===

0.2 Graph Syntax 

[[We refer to urirefs and literals]]
suggest:
[[We refer to urirefs and typed literals]]

[[
In the interests of brevity, we use 
the imaginary URI prefix 'ex:'
]]
=>

[[
In the interests of brevity, we use 
the imaginary URI scheme 'ex:'
]]

Suggest-delete-para:
[[However, the reader is cautioned that this Qname convention..
orthographic convenience.]]

===

1.2  Urirefs, resources and literals.

1st para:
[[The meaning of a literal is <<suggest-add: principally>> determined ]]]

****

out of time, I have more, but you will have to wait.

Jeremy
Received on Saturday, 9 November 2002 13:48:51 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 3 September 2003 09:54:02 EDT