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

Agenda for RDFCore WG Telecon 2003-05-16

From: <bwm@hplb.hpl.hp.com>
Date: Thu, 15 May 2003 20:23:03 +0100 (BST)
Message-ID: <19583390.1053026636280.JavaMail.bwm@MCBRIDE-B-7>
To: w3c-rdfcore-wg@w3.org

Time:
10:00:00 Fri May 16 2003 in America/New York duration 120 minutes

which is equivalent to
15:00:00 Fri May 16 2003 in Europe/London

Phone: +1-617-761-6200 (Zakim)#7332
irc: irc.w3.org #rdfcore

1: scribe: Jan being unavailable - call for volunteer

Please could the minutes conform to:
  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Apr/0216.html




2: Roll Call



3: Update on embedding RDF in XML


4: Review Agenda


5: Next telecon 30 May 2003 1000 Boston Time
Volunteer Scribe



6: Minutes of 09 May 2003 telecon 

See:
  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0138.html


7: Confirm Status of Completed Actions

ACTION: 20030509#1 jang
send comments in 0074 on S+AS.

see:
  http://lists.w3.org/Archives/Public/public-webont-comments/2003May/0050.html

ACTION: 20030509#2 bwm
Send rdfcore-np-complete rdfcore-bnodes-restriction from 0099

see:
  http://lists.w3.org/Archives/Public/public-webont-comments/2003May/0052.html

ACTION: 20030509#3 jang
Not send comment on np-completeness

ACTION: 20030509#4 bwm
Send msg 0124 on OWL Ref.

see:
  http://lists.w3.org/Archives/Public/public-webont-comments/2003May/0053.html

ACTION: 20030509#5 bwm
fix issue list resolution for rdfms-literal-is-xml-structure

see:
  http://www.w3.org/2000/03/rdf-tracking/#rdfms-literal-is-xml-structure

ACTION: 20030509#14 bwm
Review issue list and update those affected.

see:
  http://www.w3.org/2000/03/rdf-tracking/#rdfms-literal-is-xml-structure

ACTION: 20030509#17 jjc
Inform I18N-WG of literals decision.

see:
  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0147.html



8: Issue pfps-08
Proposal as in:
  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0181.html



9: Issue pfps-01
  http://www.w3.org/2001/sw/RDFCore/20030123-issues/#pfps-01

As per Pat's message
  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0162.html

Propose:
  - accept
  - note that it has been addressed by the following text (between **-**) in
    the editors draft:
    http://www.w3.org/2001/sw/RDFCore/TR/WD-rdf-mt-20030117/#dtype_interp
[[
The datatype map which also contains the set of all pairs of the form
<http://www.w3.org/2001/XMLSchema#sss , sss>, where sss is a built-in
datatype **which has well-defined lexical and value spaces and a
lexical-to-value mapping and** is named sss in XML Schema Part 2: Datatypes
[XML-SCHEMA2], eg decimal, string, is referred to here as XSD.
]]



10: issue pfps-03 LBase appendix is pointless
  http://www.w3.org/2001/sw/RDFCore/20030123-issues/#pfps-03

I've been trying to get some evidence to support a decision on this.
See thread beginning:
  http://lists.w3.org/Archives/Public/www-rdf-interest/2003May/0111.html

I have had one person offlist saying that they would prefer to see the
LBase appendix published separately.

Do we have any evidence or anecdotal experience from other specs, e.g
DAML, that similar axiomatic systems have been useful?

As per Pat's message
  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0162.html

Propose:
  - not accept
  - note that the purpose of the appendix is informative (for a certain 
    class of readers) rather than definitive. 
  - note that document states:
[[
"The editor believes that both of these descriptions, and also the closure
rules described in section 4, are all in exact correspondence, but only the
directly described model theory in sections 1- 3 should be taken as
normative."
]]   



11: Issue pfps-05 RDFS closure rules

Per Pat's message

  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0162.html

and Graham's additions:

  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0175.html

Propose 
  - accept it
  - addressed by rule rdfs1 in section 4.2 of the editor's draft
    http://www.w3.org/2001/sw/RDFCore/TR/WD-rdf-mt-20030117/#dtype_interp 
so that using rdfs1 +  rdfs3 + rdfs7a + rdfs9

   rdfs:subClassOf rdfs:range rdfs:Class .       (sect 3.3 axiom)
   rdf:XMLLiteral rdfs:subClassOf rdfs:Literal . (sect 3.3 axiom)
gives:
   rdfs:Literal rdf:type rdfs:Class .            (by rdfs3)
gives:
   rdfs:Literal rdfs:subClassOf rdfs:Resource .  (by rdfs7a)

then, from rdfs1, we have:
   _:nnn rdf:type rdfs:Literal
hence:
   _:nnn rdf:type rdfs:Resource                  (by rdfs9)



12: Issue timbl-03
We are awaiting a response from WEBONT.  They had hoped to respond in
time for this telecon, but I note they had a last call vote at their last
telecon.



13: Issue xmlsch-05 Character Sequences

  http://www.w3.org/2001/sw/RDFCore/20030123-issues/#xmlsch-05

Per Jeremy's message:
  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0151.html

PROPOSE: to not accept this comment.
Rationale:
It feels like a fairly extensive editorial change. Also in the semantic web 
activity documents xsd:string is always refered to in its qualified form, and 
so the possible confusion is diminsihed.



14: Issue xmlsch-06 natural language data
  http://www.w3.org/2001/sw/RDFCore/20030123-issues/#xmlsch-06

Per Jeremy's message
  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0151.html

PROPOSE to accept; with rewording (added 'not' and 'except for')

[[
A plain literal is a string combined with an optional language
        identifier. This should be used only for plain text 
        in a natural language. As recommended in the RDF formal semantics
        [RDF-SEMANTICS], these plain literals are self-denoting.
]]

(Note this an informative "should not", not a normative "SHOULD NOT")

An alternative is to use 'may be used for plain...' rather than
 'should not ...'
  http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003May/0182.html




------------------------------------------------------------
This agenda was produced by Jema, the Jena WG assistant, running on Jena 2
Received on Thursday, 15 May 2003 15:23:28 EDT

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