index.html 47.6 KB

Raw Blame History Permalink

<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <title>1-2nd August 2001 Meeting of the W3C RDFCore WG</title>
  <meta http-equiv="Content-Type" content="text/html" />
</head>

<body bgcolor="#ffffff" text="#000000">
<p><a href="http://www.w3.org/"><img height="48" alt="W3C"
src="http://www.w3.org/Icons/w3c_home.gif" width="72" border="0" /></a> <a
href="http://www.w3.org/TandS/" accesskey="D"><img
src="http://www.w3.org/Icons/tands" width="212" height="48"
alt="Technology and Society Domain" /></a> <a
href="brian-art-danc-jos-daveB.jpg"><img height="48" width="250"
src="brian-art-danc-jos-daveB.jpg" alt="Meeting" /></a></p>

<p align="center">[<a href="#who">participants</a>] [<a
href="#actions">actions</a>] [<a href="#decisions">decisions</a>] [<a
href="#minutes">minutes</a>] [<a href="#logs">irc logs</a>] [<a
href="#documents">documents]</a> [<a href="#where">venue</a>] [<a
href="#objectives">objectives</a>] [<a href="#agenda">agenda</a>] [<a
href="#reading">reading</a>]</p>

<h1 align="center">1-2nd August 2001 Meeting of the W3C RDFCore WG</h1>

<h3 align="center"><em>Hosted by O'Reilly in <a
href="http://maps.yahoo.com/py/maps.py?Pyt=Tmap&amp;addr=&amp;city=Sebastopol&amp;state=CA&amp;slt=38.395100&amp;sln=-122.844101&amp;name=&amp;zip=95472&amp;country=us&amp;BFCat=&amp;BFClient=&amp;mag=4&amp;desc=&amp;cs=7&amp;newmag=5&amp;poititle=&amp;poi=">Sebastopol</a></em></h3>

<h2><a id="who" name="who">Participants</a><br />
</h2>
<ul>
  <li><a href="mailto:barstow@w3.org">Art Barstow</a>, W3C (<a
    href="brian-art-danc-jos-daveB.jpg">2nd from left</a>)</li>
  <li><a href="mailto:Dave.Beckett@bristol.ac.uk">Dave Beckett</a>, ILRT (<a
    href="brian-art-daveB-danC.jpg">2nd from right</a>)</li>
  <li><a href="mailto:danbri@w3.org">Dan Brickley</a>, University of Bristol
    (<a href="danbri.jpg">picture</a>)</li>
  <li><a href="mailto:connolly@w3.org">Dan Connoly</a>, W3C (<a
    href="rael-danc.jpg">on right</a>)</li>
  <li><a href="mailto:rdaniel@interwoven.com">Ron Daniel</a>, Interwoven <span
    style="font-style: italic"></span></li>
  <li><a href="mailto:mdean@bbn.com">Mike Dean</a>, BBN <span
    style="font-style: italic">(part time) (<a
    href="mike-jos-martyn-pat-frank-graham.jpg">on left</a>)</span></li>
  <li><a href="mailto:jos.deroo.jd@belgium.agfa.com">Jos De Roo</a>, AGFA (<a
    href="brian-art-danc-jos-daveB.jpg">2nd from right</a>)</li>
  <li><a href="mailto:rael@oreilly.com">Rael Dornfest</a>, O'Reilly &amp;
    Associates <span style="font-style: italic">(part time) (<a
    href="rael-danc.jpg">on left</a>)</span></li>
  <li><a href="mailto:arno:adobe.com">Arno Goudol</a>, Adobe
  <i>(observer)</i></li>
  <li><a href="mailto:jan.grant@bristol.ac.uk">Jan Grant</a>, ILRT, University
    of Bristol (<a href="jan-steve-mike.jpg">on the left</a>)</li>
  <li><a href="mailto:phayes:ai.uwf.edu">Pat Hayes</a>, IHMC (<a
    href="mike-jos-martyn-pat-frank-graham.jpg">3rd from right</a>)</li>
  <li><a href="mailto:martyn.horner@profium.com">Martyn Horner</a>, Profium
    Sarl <span style="font-style: italic">(<a
    href="martyn.jpg">picture</a>)</span></li>
  <li><a href="mailto:gk@ninebynine.org">Graham Klyne</a>, Baltimore
    Technologies (<a href="mike-jos-martyn-pat-frank-graham.jpg">on
  right</a>)</li>
  <li><a href="mailto:kwonhj@nca.or.kr">Hyung-Jin Kwon</a> Korean National
    Computerization Agency</li>
  <li><a href="mailto:daml@lassila.org">Ora Lassila</a>, Nokia Research Center
    (<a href="ora.jpg">picture)</a></li>
  <li><a href="mailto:fmanola@mitre.org">Frank Manola</a>, MITRE (<a
    href="frank-daveB-art-jos-jan-danbri.jpg">on left)</a></li>
  <li><a href="mailto:bwm:hplb.hpl.hp.com">Brian McBride</a>, Hewlett Packard
    <i>(chair) (<a href="ericbrian.jpg">on right</a>)</i></li>
  <li><a href="mailto:melnik@db.stanford.edu">Sergey Melnik</a>, Stanford
    University (<a href="dan-sergey.jpg">on right</a>)</li>
  <li><a href="mailto:em@w3.org">Eric Miller</a>, W3C (<a
    href="ericbrian.jpg">on left</a>)</li>
  <li><a href="mailto:spetschu@ca.ibm.com">Steve Petschulat</a>, IBM (<a
    href="jan-steve-mike.jpg">middle</a>)</li>
  <li><a href="mailto:melnik@db.stanford.edu">Aaron Swartz</a>, HWG <span
    style="font-style: italic">(part time) (<a
    href="Aaron-with-Ted-Doug.jpg">between Ted Nelson and Doug
    Englebart</a>)</span></li>
</ul>

<p><span style="font-style: italic; font-size: 10pt">(Photographs by Aaron
Swartz, Steve Petschulat)</span></p>

<h3>Regrets</h3>
<ul>
  <li><a href="mailto:acm@dehora.fsnet.co.uk">Bill dehOra</a></li>
  <li><a href="mailto:guha@guha.com">Guha</a></li>
</ul>
<a id="actions" name="actions"></a>

<h2>Actions</h2>

<table>
  <caption><em><strong></strong></em></caption>
  <tbody>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T17-56-46">2001-08-01#1</a></td>
      <td>Mike Dean</td>
      <td>Provide public URL</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T18-48-43">2001-08-01#2</a></td>
      <td>Pat Hayes</td>
      <td>Get Model Theory Introduction Slides online</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T18-52-19">2001-08-01#3</a></td>
      <td>Pat Hayes</td>
      <td>Include example in model theory slides</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T16-17-52">2001-08-02#4</a></td>
      <td>Pat Hayes</td>
      <td>Re-write model theory as an interpretation of a graph rather than
        n-triple</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T17-00-02">2001-08-02#5</a></td>
      <td>Sergey Melnick</td>
      <td>Send copy of document projected at meeting to the mailing list</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T18-22-32">2001-08-02#6</a></td>
      <td>Brian McBride</td>
      <td>Approach Jeremy Carrol to help with RDF/XML language
      definition.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T18-22-59">2001-08-02#7</a></td>
      <td>Dave Beckett</td>
      <td>With help from Art and Jan, investigate how to represent RDF/XML
        grammar and the specification of the transformation of RDF/XML to a
        graph representation.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T18-56-32">2001-08-02#8</a></td>
      <td>Dan Brickley</td>
      <td>Ensure that the document projected, as amended during the meeting
        goes on line.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-08-53">2001-08-02#9</a></td>
      <td>Dan Brickley</td>
      <td>Update RDF Schema spec to reflect decision to adopt conjunctive
        semantics for domain and range.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-07-14">2001-08-02#10</a></td>
      <td>Jan Grant</td>
      <td>Write up a fix/workaround for folks using the currently defined
        semantics for domain and range constraints.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-25-41">2001-08-02#11</a></td>
      <td>Graham Klyne</td>
      <td>Post message to list describing how CC/PP uses datatypes</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-26-01">2001-08-02#12</a></td>
      <td>Jan Grant</td>
      <td>Post message to list about how EASEL uses datatypes</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-36-28">2001-08-02#13</a></td>
      <td>Pat Hayes</td>
      <td>Post message explaining why having the typing at the top of the
        hierarchy in RDFS is not a set theoretical hole.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T20-01-23">2001-08-02#14</a></td>
      <td>Ora Lassila</td>
      <td>Talk to Ian and Frank and get background on why they require cycles
        in rdfs:subClassOf relationship.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T20-08-21">2001-08-02#15</a></td>
      <td>Pat Hayes</td>
      <td>Discuss cycles in rdfs:subClassOf and rdfs:subPropertyOf with DAML
        folks and report back to us.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T20-28-23">2001-08-02#15</a></td>
      <td>Sergey Melnik</td>
      <td>Discuss reification alterantives with Pat Hayes.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T20-55-24">2001-08-02#17</a></td>
      <td>Dan Brickley</td>
      <td>Update RDFS prose to reflect decision that subproperties should
        inherit conjunctively the range+domain of their superproperties.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-10-17">2001-08-02#18</a></td>
      <td>Jan Grant</td>
      <td>Propose an explanation of why a subproperty of a transitive property
        need not be transititive.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-22-44-1">2001-08-02#19</a></td>
      <td>Dan Brickley</td>
      <td>Submit a new working draft of RDF Schema by 6th September 2001.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-46-22">2001-08-02#20</a></td>
      <td>Ron Daniel</td>
      <td>Post his list of agreed principles to the list.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T22-11-40">2001-08-02#21</a></td>
      <td>Brian McBride</td>
      <td>Propose structure of documents to be produced</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T22-19-23-1">2001-08-02#22</a></td>
      <td>Hyung-Jin Kwon</td>
      <td>Make his presentation available on the web and circulate URL to the
        list.</td>
    </tr>
    <tr>
      <td>2001-08-02#23</td>
      <td>Brian McBride</td>
      <td>Update schedule to aim for WWW2002 announcement.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T20-12-30">2001-08-02#24</a></td>
      <td>Brian McBride</td>
      <td>Open rdfs-no-cycles-in-subClassOf with Frank Manola as owner</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T20-12-30">2001-08-02#25</a></td>
      <td>Dan Brickley</td>
      <td>Update RDF Schema WD to flag possibility of removing no cycles
        restriction on subClassOf and subPropertyOf and seek feedback if this
        will cause problems.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-09-53">2001-08-02#26</a></td>
      <td>Dan Brickley</td>
      <td>Update schema WD and close rdfs-domain-and-range</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-09-53">2001-08-02#27</a></td>
      <td>Dan Brickley</td>
      <td>Update schema WD and close rdfs-domain-unconstrained</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-14-36">2001-08-02#28</a></td>
      <td>Dan Brickley</td>
      <td>Close rdfs-primitive-properties</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T20-56-40">2001-08-02#29</a></td>
      <td>Dan Brickley</td>
      <td>Close rdfs-subPropertyOf-semantics</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-01-54">2001-08-02#30</a></td>
      <td>Dan Brickley</td>
      <td>Clarify rdfs-subClassOf-a-Property as "Are Class and Property
        disjoint"</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-05-16">2001-08-02#31</a></td>
      <td>Dan Brickley</td>
      <td>Fix rdfs-online-char-encoding in the next schema WD and close this
        issue</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-07-30">2001-08-02#32</a></td>
      <td>Dan Brickley</td>
      <td>Close rdfs-versioning</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-09-50">2001-08-02#32</a></td>
      <td>Dan Brickley</td>
      <td>Update rdfs-transitive-subSubProperty with explanatory text privided
        by Jan, include in the next schema WD, but do not close this issue
        yet.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-29-22">2001-08-02#33</a></td>
      <td>Dan Brickley</td>
      <td>Form task force with Graham Klyne, Martyn Horner and Jan Grant to
        investigate the DAML+OIL approach to XML datatypes.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-16-18">2001-08-02#34</a></td>
      <td>Jan Grant</td>
      <td>Post a message explaining how existing/proposed RDF Schema
        mechanisms could be used to express contraints on the types of members
        of containers.</td>
    </tr>
  </tbody>
</table>
<a id="decisions" name="decisions"></a>

<h2>Decisions</h2>

<table>
  <tbody>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T21-11-55">log</a></td>
      <td>The WG agreed that the model theory was a good approach to defining
        a semantics for RDF and would be a useful tool of the WG.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T23-18-30">log</a></td>
      <td>The WG agreed that nodes in an RDF graph arising from description
        elements without and rdf:about or an rdf:ID attribute can be
        distinguished from nodes that had such an attribute.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T17-38-38">log</a></td>
      <td>The model theory will be defined for RDF graphs, not n-triples.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-09-53">log</a></td>
      <td>Multiple domain and range constraints are permissable and will have
        conjunctive semantics and this issue is now closed.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-14-36">log</a></td>
      <td>Domain and range constraints on domain will be included in the next
        version of the schema document and this issue is now closed.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-14-36">log</a></td>
      <td>The issue rdfs-primitive-properties is not a problem and will be
        closed.</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T20-56-40">log</a></td>
      <td>subProperties inherit conjunctively the domain and range of their
        superproperties</td>
    </tr>
    <tr>
      <td><a
        href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-07-30">log</a></td>
      <td>The WG will not address the rdfs-versioning issue</td>
    </tr>
  </tbody>
</table>
<a id="minutes" name="minutes"></a>

<h2>Minutes</h2>

<p>The WG thanks O'Reilly and Rael Dornfest for hosting the meeting.</p>

<p>RDF t-shirts provided by Hewlett Packard were distributed.</p>

<p>The meeting <a href="#objectives">objectives</a> and <a
href="#agenda">agenda</a> were reviewed and approved.</p>

<h3>Establishing a context - users of RDF</h3>

<p>Five speakers described uses of RDF, users of RDF and problems with
RDF.</p>

<h4>RSS</h4>

<p>Rael Dornfest described RSS (<a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T17-21-55">log</a>)
a site description and syndication format based on RDF. RSS is widely used;
RSS 0.91 (which is not RDF) is the most widely used form, but its growth is
slowing. Users of RSS include:</p>
<ul>
  <li><a href="http://slashcode.com/">slashcode</a> (<a
    href="http://slashcode.com/slashcode.rss">rss feed</a>)</li>
  <li><a href="http://www.ximian.com/">Ximian</a>'s Red Carpet update system
    which enables subscribing to a feed of package updates is very close to
    RDF</li>
  <li>AxKit's (www.axkit.org now broken) XML application server</li>
  <li>Take23 (link http://www.take23.org/ broken) is an AxKit application</li>
  <li>Yahoo! finance is using RSS 1.0 internally</li>
  <li>ITN</li>
  <li>O'Reilly's <a href="http://meerkat.oreillynet.com/">Meerkat</a> (<a
    href="http://meerkat.oreillynet.com/?_fl=n3">N3 version</a>, <a
    href="http://meerkat.oreillynet.com/?_fl=rss10">RSS 1.0 version</a>)</li>
</ul>

<p>Rael identified the following issues with RDF:</p>
<ul>
  <li>the specifications are difficult to understand</li>
  <li>namespace prefixes are a problem</li>
  <li>need production quality RDF tools</li>
  <li>need provenance of chunks of XML - Reification doesn't meet the
  need</li>
  <li>need unsquish</li>
  <li>hackers don't read the spec - need better introductory material</li>
</ul>

<h4>Prism</h4>

<p>Ron Daniels presented <a href="http://www.prismstandard.org/">PRISM</a> (<a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T17-36-21">log</a>),a
metadata standard for the magazine publishing industry. The project was
initiated to fill a customer need. Its goal is to help publishers deal with
customers to do better search, personalisation, alerters, portals and
intranets. PRISM users have the following isses with RDF:</p>
<ul>
  <li>RDF is hard to extend</li>
  <li>Reificiation is very hard to understand</li>
</ul>

<p>It was noted that RSS can be easily used to syndicate PRISM data, which was
an unexpected benefit.</p>

<h4>DAML</h4>

<p>Mike Dean <a
href="http://www.daml.org/2001/08/rdfcore-f2f/Overview.html">presented</a>
DAML as an application of RDF. He referred to the communication the WG has
received from the DAML 'joint committee' and went on to highlight the
following issues as the most important from a DAML perspective:</p>
<ul>
  <li>domain/range constraints</li>
  <li>subbclass should allow cycles</li>
  <li>it should be possible to tag statements and 'clumps' of statements with
    provenance information</li>
  <li>there is a need for closed collections</li>
  <li>there is a need for a formal semantics for RDF</li>
  <li>what do URI's mean?</li>
  <li>there is a need to support XML Schema datatypes</li>
</ul>

<h4>XAP</h4>

<p>Arno Goudol of Adobe, who was present as an observer, presented (<a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T18-09-52">log</a>)
information about <a
href="http://www.gca.org/papers/xmleurope2001/papers/html/sid-03-9b.html">XAP</a>,
an Adobe RDF metadata toolkit which will be launched at Seybold. XAP is
already shipping in a limited form in Acrobat 5. Arno's top concerns with RDF
were:</p>
<ul>
  <li>don't want to have to support reification</li>
  <li>stronger datatyping needed</li>
  <li>Need more info in schema for UI support</li>
</ul>

<h4>Dublin Core</h4>

<p>Dan Brickley <a
href="http://lists.w3.org/Archives/Public/www-archive/2001Aug/0000.html">presented</a>
(<a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T18-22-31">log</a>)
the Dublin Core architecture effort and listed their top concerns:</p>
<ul>
  <li>The Dublin Core folks are trying to process RDF as either XML or RDF and
    are finding it painful.</li>
  <li>language support xml:lang</li>
  <li>relationship to XML schema</li>
  <li>ugly syntax</li>
  <li>containers - modelling guidelines to advise on how to use them</li>
  <li>datatyping - need numbers and dates</li>
  <li>NEED SOMETHING SOON</li>
  <li>RDF is often seen as being in danger of falling into the AI trap. There
    is a perception that basic RDF 1.0 is not finished but the RDF community
    is off in the weeds trying to do AI and knowledge representation.</li>
  <li>Don't want to support reification</li>
</ul>

<h3>Presentation of a Model Theory for RDF by Pat Hayes</h3>

<p><a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T18-47-52">log</a></p>

<p>Pat gave a <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/mt/">presentation</a>
introducing the ideas of model theory and a model theory for RDF.</p>

<p>An <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T19-16-01">example</a>
was worked through on the whiteboard.</p>

<p>The following issues arose during the discussion:</p>
<ul>
  <li>what happens with anonymous nodes if the same document is parsed
  twice</li>
  <li>If a document is split, can the anonymous nodes in the split documents
    be recognised as being the same as those in the original</li>
  <li>alternatives interpretations of reification</li>
</ul>

<p>There was some <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T21-05-23">discussion</a>
regarding the role of the model theory in the WG activities. It was <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T21-11-55">agreed</a>
that the model theory would be a useful tool of the WG. There was concern that
it would not be useful or accessible to part of the target audience for the
WG's specifications.</p>

<h3>Model Theory and Abstract Syntax Issues</h3>

<p><a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T21-12-25">log</a></p>

<p>The WG considered the following issues for discussion:</p>
<ul>
  <li>what happens with anonymous nodes if the same document is parsed
  twice</li>
  <li>If a document is split, can the anonymous nodes in the split documents
    be recognised as being the same as those in the original</li>
  <li>alternatives interpretations of reification</li>
  <li>syntactic representation of doc</li>
  <li>formal semantics</li>
  <li>anon resources</li>
  <li>literal is XML structure</li>
  <li>graph</li>
  <li>uri-substructure</li>
</ul>

<p>It decided to discuss literal is XML structure, the syntactic
representation of documents and anon resources first.</p>

<h4><a
href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-literal-is-xml-structure">#rdfms-literal-is-xml-structure</a></h4>

<p><a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T21-18-19">log</a></p>

<p>It was suggested that there had been basic agreement on the mailing list,
that literals with a parseType of "Literal" would be treated as strings, but
the model would contain further information. There are many details to work
out, but this is the basic principle. A list of components that would have to
be in the model was started:</p>
<ul>
  <li>the string</li>
  <li>parseType (string or QName)</li>
  <li>namespaces</li>
  <li>language</li>
  <li>base URI</li>
  <li>entities</li>
</ul>

<p>A number of different approaches were identified:</p>
<ul>
  <li>the XML in the input document must be self sufficient (an incomplete
    solution)</li>
  <li>parser adds namespaces (an incomplete solution)</li>
  <li>replace the literal with an infoset representation of RDF</li>
  <li>serialise the infoset to a string</li>
  <li>use XML fragments</li>
  <li>deprecate and represent as CDATA</li>
</ul>

<p>It was suggested that parseType="Literal" could be dropped but Ron Daniel
and Eric Miller spoke up that there are users who use it.</p>

<p>Some time was spent working through a <a href="01-rdff2f.txt">test
case</a>, though no definitive conclusion was reached.</p>

<p>It was suggested that the parser adding namespace definitions to the
literal might break an XML signature. Concern was raised over entities in the
literal. The existence of the xml fragments work was noted. No one was willing
to own the action of investigating the applicability of the fragments
work.</p>

<h3>Syntactic Representation of Document</h3>

<p>The question was <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T22-01-00">raised</a>
whether there was a need to include in n-triples brackets to bound the
statements in a set of statements to mark the scope of the names of anonymous
nodes. This was objected to on the grounds that it would break current code
which processes n-triples. There was considerable discussion and it was
decided not to add brackets.</p>

<h3>Anonymous Nodes</h3>

<p>(<a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T22-56-22">log</a>)</p>

<p>A long and complex discussion of anonymous nodes began with two
questions:</p>
<ul>
  <li>Are anonymous nodes in a model distinguishable from nodes whose RDF/XML
    representation has assigned URI's?</li>
  <li>If anonymous nodes are distinguishable in the model, what is the
    difference in their semantics? Are they existintially qualified
  variables?</li>
</ul>

<p>On the first question, the objection to being able to distinguish them was
that they served no purpose. For RDF which is only making assertions they have
no use.</p>

<p>Reasons given in support of them included:</p>
<ul>
  <li>the lazy argument - it easier not to have to generate names for
  them</li>
  <li>generating unique ID's is very hard</li>
  <li>they enable description of resources that have no name</li>
  <li>they enable the generation of structures where we don't care about the
    name</li>
  <li>there is information loss if the difference between nodes whose names
    were machine generated and those whose names were given, is lost.</li>
</ul>

<p>It was <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T23-18-30">agreed</a>
that anonymous nodes in the model can be distinguished from nodes with
supplied URI's.</p>

<p>The WG then turned to discuss the second question (<a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html#T23-18-37">log</a>).
Amongst a long discussion the following points/issues/observations were
made:</p>
<ul>
  <li>Must an RDF processor treat URI's as opaque strings or may it examine
    the structure of the URI? Reference was made to the <a
    href="http://www.w3.org/DesignIssues/Axioms.html#opaque">opacity
  axiom</a></li>
  <li>The term's anonymous nodes and anonymous resources tend to mislead.
    <em>[editors note: I like the term suggested by Eric Miller - prince
    nodes. I shall use that term for the rest of these minutes where it seems
    appropriate]</em></li>
  <li>It was suggested that a natural interpretation of prince nodes is that
    they mean "There exists a resource with properties ...". Eric Miller
    confirmed that this had been the intention of the original working
  group.</li>
  <li>There is a difference between "There exists a resource with properties
    ..." and "There exists a resource I am calling foo with properties
  ...".</li>
  <li>There is a need to be very clear about the scope of the existential
    quantifier in the model theory.</li>
  <li>Do the identifiers generated for prince nodes in n-triples behave like
    URI's? If not, what are their characteristics?</li>
  <li>It was suggested that M&amp;S permits prince nodes. It was also argued
    that M&amp;S is not clear on this point.</li>
  <li>If Prince nodes are to be labelled with something that is
    distinguishable from from a URI, that label cannot be a URI.</li>
  <li>If prince nodes cannot be referred to from outside the document that
    contains them, then it is not possible to say anything about them in
    another document. This violates the web axiom that it is possible to say
    anything about anything.</li>
  <li>There was a suggestion that anonymous nodes could be represented by
    fragments of the form"_idnnnn".</li>
</ul>

<p>In response to a request for use cases where the difference mattered, the
following were suggested:</p>
<ul>
  <li>representing queries - but that may be out of scope of the WG</li>
  <li>many cases where the 'proper' URI of a resource is not known (<a
    href="http://lists.w3.org/Archives/Public/www-rdf-interest/2001Jul/0066.html">link</a>),
    so a Prince node is used instead</li>
  <li>people - in general there are no 'proper' URI's for people and the tend
    to be represented with a prince node and identifying properties</li>
  <li>WG's - there are no URI's for WG's - they too tend to be identified with
    unique properties</li>
  <li>Dan Connolly has used Prince nodes extensively in his software
    development. Had he been required to make up explicit URIs in all cases,
    his applications would not have gotten done/developed/deployed.
    Theoretically, he could, perhaps, have made up and managed distinct URIs
    for all the relevant things, but practically, he needed Prince nodes to
    build apps.</li>
  <li>If URI's are generated from prince nodes, there is a serious practical
    problem ensuring those URI's are never used again</li>
</ul>

<p>The meeting adjourned to the bar at the end of the first day without
reaching any further conclusions and resumed (<a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T16-12-35">log</a>)
the next day with a proposal that many of these issues were removed if the
model theory were defined for a graph rather than for n-triples. The meaning
of RDF/XML could be defined in terms of a translation to a graph.</p>

<p>Sergey presented a <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/sergey.txt">document</a>
analysing the different options in terms of their behaviour from an
implementation perspective:</p>
<ul>
  <li>entailment</li>
  <li>parsing twice</li>
  <li>splitting/merging documents</li>
  <li>reference from another document</li>
</ul>

<p>It was <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T16-17-52">agreed</a>
that Pat would update the model theory based on the graph instead of
n-triples.</p>

<h3>RDF/XML Syntax</h3>

<p>Dave Beckett gave a <a
href="http://www.ilrt.bris.ac.uk/people/cmdjb/talks/rdfcore-sebastopol/">presentation</a>on
some experitmental work he has been doing on defining the RDF/XML <a
href="http://ilrt.org/discovery/2001/07/rdf-syntax-grammar/">grammar</a> in
terms of infoset. Two questions were suggested:</p>
<ul>
  <li>how do we represent the grammar</li>
  <li>how do we represent the translation from the RDF/XML to a graph</li>
</ul>

<p>The following technologies were mentioned:</p>
<ul>
  <li>attribute grammars</li>
  <li>schematron</li>
  <li>XSLT (see <a
    href="http://www.xmlhack.com/read.php?item=757">xmlhack</a>)</li>
  <li>XDuce</li>
  <li>Relax</li>
  <li>RelaxNG</li>
</ul>

<p>It was observed that it would be polite to give serious consideration to
using tools from the W3C family of specifications.</p>

<p>Jeremy Carroll's new RDF parser ARP was noted in that it is based on a BNF
representation of the grammar where the symbols are SAX events rather than
characters.</p>

<p>It was decided that Dave Beckett, Jan Grant and Art Barstow would consider
consider this problem and come back with a recommendation. Brian was asked to
invite Jeremy Carroll to help.</p>

<p>There was some discussion of n-triples and the way its role seemed to be
growing. There was some discussion of it causing confusion and being used for
machine to machine communication of RDF versus the need to emphasise the point
that there can be more than one serialization language for RDF graphs. It was
<a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T18-40-16">emphasised</a>
that the key concept is the graph and RDF/XML and n-triples are serializations
of it.</p>

<h3>Schema Issues</h3>

<p>(<a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T18-56-41">log</a>)</p>

<h4>rdfs-domain-and-range</h4>

<p>The working group <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-09-53">decided</a>
that mulitple domain and range constraints would be allowed and have
conjunctive semantics and that this issue be closed.</p>

<h4>rdfs-domain-unconstrained</h4>

<p>The working group decided that due to an editorial oversight, the domain
and range constraints on the domain property had been omitted from the RDF/XML
representation of schema. It as <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-14-36">agreed</a>
that they should be added in the next draft and that this issue be closed.</p>

<h4>rdfs-constraining-containers</h4>

<p>The working group <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-19-55">decided</a>
to make no change to current draft and to close this issue on the grounds
that:</p>
<ul>
  <li>no compelling case had been made for this additional feature for
  1.0</li>
  <li>we already allow subclasses of containers</li>
  <li>other languages such as (DAML+OIL, WebOnt, prose) can express those
    contraints</li>
</ul>

<h4>rdfs-xml-schema-datatypes</h4>

<p>The working group decided to form a task force to investigate the DAML+OIL
approach for using XML datatypes. Dan Brickley, Graham Klyne, Martin Horner
and Jan Grant volunteered for the task force. The next working draft will
explicitly seek implementor feedback on this. We do not consider this a
requirement for the next working draft.</p>

<h4>rdfs-primitive-properties</h4>

<p>The working group <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T19-41-42">decided</a>
that it did not believe this was a problem and will be closed with reasons and
explanatory text. It is not critical path for the next working draft.</p>

<h4>rdfs-no-cycles-in-subClassOf</h4>

<p>The issue requests that the restriction on no cycles in subClassOf
relationships be dropped. The following points were made:</p>
<ul>
  <li>concern that a change might break existing implementations</li>
  <li>is an implementation required to check that RDF conforms to the
    restriction?</li>
  <li>removing this restriction is important to the DAML folks who use cycles
    to respresent equivalence which is accepted description logic
  practice</li>
  <li>there are a number of large scale ontologies with cycles</li>
  <li>the critical case for DAML+OIL was that the subsetting relationship
    might be created by multiple people</li>
  <li>when merging large ontologies we can't prohibit cycles occuring</li>
  <li>prorgammers from a object oriented background don't like cycles in the
    class hierarchy</li>
  <li>this is a must have for DAML+Oil</li>
  <li>the discussion also applies to subPropertyOf</li>
  <li>Some implementors generate java classes for RDF classes - this they
    cannot do if there are cycles</li>
</ul>

<p>The working group <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T20-12-30">decided</a>
to open this as an issue with Frank as its owner and to explicitly seek
feedback via the next working draft and from the DAML+OIL folks.</p>

<h4>rdfs-subPropertyOf-semantics</h4>

<p>It was <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T20-56-40">decided</a>
that subProperties inherit conjunctively the domain and range of their
superproperties and the text of the working draft will be modified to make
this clear.</p>

<h4>rdfs-subClassOf-a-Property</h4>

<p>After some discussion it was <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-01-54">decided</a>
to clarify this issue as "Are Class and Property disjoint" and to do nothing
for the next working draft.</p>

<h4>rdfs-online-char-encoding</h4>

<p>This was an editorial oversight and the editor is <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-05-16">actioned</a>
to fix this in the next working draft and close the issue.</p>

<h4>rdfs-versioning</h4>

<p>The WG <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-06-41">decided</a>
to close this issue without action since it is a known problem that is very
hard to solve and is outside the scope of this WG.</p>

<h4>rdfs-transitive-subSubProperty</h4>

<p>Jan agreed to produce an example to demonstrate that subproperties of
transitive properties are not necessaly transitive..</p>

<h4>rdfs-clarify-subClass-and-instance</h4>

<p>The WG <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-17-28">decided</a>
to take no action for the next WD.</p>

<h4>rdfs-isDefinedBy-semantics</h4>

<p>The WG <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-17-28">decided</a>
to take no action for the next WD.</p>

<h4>rdfs-editorial</h4>

<p>The WG <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T21-17-28">decided</a>
to take no action for the next WD.</p>

<h2>Next Steps</h2>

<p>Dan Brickley will produce a new working draft of RDF schema for 6th
September 2001.</p>

<p>Pat Hayes will produce a new model theory by 11th August 2001 and we will
use Sergey's proposal for evaluating its impact on implementations.</p>

<p>The WG envisages the following deliverables:</p>
<ul>
  <li>A tutorial</li>
  <li>A model specification</li>
  <li>An RDF/XML syntax specification</li>
  <li>An RDF Schema specification</li>
  <li>a collection of test cases</li>
</ul>

<p>A straw poll of the WG members present indicated that 5 would be willing to
work on the primer, 8 on the model, 4 on the syntax, 4 on schema and 2 on test
cases. <em>[Aaron volunteered from irc to work on the primer so consider that
+2]</em> It was noted that we can arrange for extra telephone bridges to
enable faster progress in subgroups.</p>

<p>It was noted that the original WG tried to separate the model and syntax
and found it too hard. There has been considerable support for separating
these two and the working group decided to try again to separate them.</p>

<p>It was <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T22-11-40">decided</a>
that Brian would produce an overall an initial structure for the documents and
then we could start writing pieces.</p>

<p>It was <a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html#T22-22-30">agreed</a>
that we would like to aim to announce recommendation status at WWW2002.</p>

<h2>Short Presentations</h2>

<p>Kwon presented the work in which he is involved in the Korean National
Computerization Agency developing a national metadata repository. He is
looking for advice on whether to use RDF and what tools are available. It was
noted that government projects are often required to use standards. RDF Schema
having not completed its standards process is an inhibitor to acceptance of
RDF. It was noted with awe that we have a whole country waiting for us to
finish. Some of our users and potential users are concerned about us getting
involved in AI and knowledge representation when what they want is relatively
straight forward mechanisms for representing metadata.</p>

<p>Ron Daniels showed a demo done for a customer by InterWoven where the
ability to merge metadata from different sources enabled rapid development of
an excellent demo.</p>

<p>Eric Miller repeated part of his <a
href="http://www.w3.org/Talks/2001/07/30-swws/slide36-1.html">talk</a> from
the semantic web workshop describing some of the work being done in the
Semantic Web Advanced Development group using DAML+OIL to develop tools for to
support W3C processes. It was noted that the biggest bang for the buck comes
from the simpler stuff in DAML.</p>

<h2>Close</h2>

<p>The meeting closed with the chair thanking the participants, the scribes
our hosts O'Reilly.</p>

<h2><a name="logs" id="logs">IRC Logs</a></h2>

<p><a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-01.html">Day 1
(logger time)</a></p>

<p><a
href="http://www.w3.org/2001/sw/RDFCore/20010801-f2f/2001-08-02.html">Day 2
(logger time)</a></p>

<h2><a name="documents" id="documents">Documents Used/produced in the
Meeting</a></h2>
<ul>
  <li><a href="mt/">Model Theory Presentation</a></li>
  <li><a href="01-rdff2f.txt">rdf:parseType="Literal" test case</a></li>
  <li><a href="01-ex1.n3">n3 example</a></li>
  <li><a href="01-ex1.txt">Prince nodes example</a></li>
  <li><a href="01-ex1.rdf">3 Interpretations of Prince nodes</a></li>
  <li><a href="kwon.pdf">Kwon's presentation</a></li>
</ul>

<h2><a id="where" name="where">Venue</a></h2>

<p>Our local host is Rael Dornfest (<a
href="mailto:rael@oreilly.com">rael@oreilly.com</a>) of <a
href="http://www.ora.com/">O'Reilly</a> (800 998 9938) who has provided us
with some <a
href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2001Jun/0009.html">local
information</a>.</p>

<p>Rael recommends the Sebastopol Inn (6751 Sebastopol Avenue, Sebastopol, CA
95472, +1 707 829-2500) which is across the street from the O'Reilly office.
An alternative hotel is the Holiday Inn (101 Gravenstein Hwy So./Cooper Rd.
Sebastopol, CA 95472, 707-829-6677) which is 2 miles from O'Reilly office.</p>

<p>The following directions are taken from <a
href="http://www.oreilly.com/oreilly/seb_directions.html">Direction's to the
O'Reilly Sebastopol Office</a>.</p>

<h3>From San Francisco:</h3>
<ol>
  <li>Take US-101 North out of the city.<br />
  </li>
  <li>Continue along US-101 (approx. 55 miles) until the Hwy 116 West exit
    towards Sebastopol. (Don't be fooled by the earlier Hwy 116 East exit.)<br
    />
  </li>
  <li>Left at the light (at the bottom of the exit ramp).<br />
  </li>
  <li>Continue to follow 116 for approx. 8 miles.<br />
  </li>
  <li>At the the first light in Sebastopol (Hwy 116 and Hwy 12) turn right.<br
    />
  </li>
  <li>Turn left at the next light (Morris St).<br />
  </li>
  <li>Turn into the first driveway on the right.<br />
  </li>
  <li>Welcome to O'Reilly &amp; Associates.</li>
</ol>

<h3>From the East Bay:</h3>
<ol>
  <li>Take I-80 East/I-580 West.<br />
  </li>
  <li>Near University Ave in Berkeley, get in the right lane.<br />
  </li>
  <li>Take the exit ramp towards the Richmond/San Rafael Bridge. (Toll $2.)<br
    />
  </li>
  <li>Take 101-N towards San Rafael/Santa Rosa.<br />
  </li>
  <li>See the SF directions 2-8.</li>
</ol>

<h3>From the South Bay:</h3>
<ol>
  <li>Take US-101 North.<br />
  </li>
  <li>Follow US-101 through the city.<br />
    OR<br />
  </li>
  <li>Take 280-North (it will become 19th Ave).<br />
  </li>
  <li>Follow 19th through the city until it becomes US-101 North.<br />
  </li>
  <li>See the SF directions 2-8.</li>
</ol>
<a id="objectives" name="objectives"></a>

<h2>Meeting Objectives</h2>

<p>The meeting has the following objectives:</p>
<ul>
  <li>WG members meet and get to know each other</li>
  <li>Review the model theory and progress abstract syntax and model theory
    issues</li>
  <li>Review approach to defining the grammar and its translation to
  n-triple</li>
  <li>Progress RDF Schema issues</li>
  <li>Plan for moving forward after the meeting</li>
</ul>

<h2><a id="agenda" name="agenda">Agenda (Tentative and subject to
change)</a></h2>

<h3>Tuesday, July 31st 7pm, Garden Courtyard, Sebastopol Inn</h3>

<p>Informal get together. Head off for dinner about 8pm.</p>

<h3>Wed, August 1st (all day)</h3>
<pre>         1000 Welcome, Introductions, meeting objectives, agenda review

              Establishing a context - users of RDF
         1030 - RSS         - Rael Dornfest
         1045 - PRISM       - Ron Daniel (unconfirmed)
         1100 - DAML+OIL    - Mike Dean
         1115 - Dublin Core - Dan Brickley

         1130 break

         1145 Presentation of the model theory - Pat Hayes

         1300 Lunch

         1400 Model Issues:
              <a href="http://www.w3.org/2000/03/rdf-tracking/#rdf-formal-semantics">rdf-formal-semantics</a>
              <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-identity-anon-resources">rdfms-identity-anon-resources</a>
              <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-graph">rdfms-graph</a>
              <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-uri-substructure">rdfms-uri-substructure</a>
              <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-literal-is-xml-structure">rdfms-literal-is-xml-structure</a>

         1530 break

         1545 Short Presentations - 10 mins each on interesting stuff we are
              doing

         1615 Model Issues continued

         1700 break

         1800 close

         1930 Dinner</pre>

<h3>Thurs, August 2st (all day)</h3>
<pre>         0900 RDF/XML Syntax - Dave Beckett
              <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-formal-grammar">rdfms-formal-grammar</a>
         1000 short presentations

         1030 break

         1045 RDF Schema - Dan Brickley
              <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfs-domain-and-range">rdfs-domain-and-range</a>
              <a>rdfs-domain-unconstrained</a>

         1230 Lunch

         1330 Future Plans - Deliverables, roadmap

         1500 break

         1515 Open Mike

         1600 close</pre>

<h2><a name="reading" id="reading">Reading</a></h2>

<h3><a name="reading1" id="reading1">Required</a></h3>
<ul>
  <li><a href="http://www.w3.org/2001/sw/RDFCoreWGCharter">RDFCore WG
    charter</a></li>
  <li><a href="http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/">Model and
    Syntax Specification</a></li>
  <li><a href="http://www.w3.org/2000/03/rdf-tracking/#active-issues">Active
    Issues</a> and those listed in the agenda as listed in the <a
    href="http://www.w3.org/2000/03/rdf-tracking/#active-issues">Issues
    List</a>, and discussion of them in the <a
    href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/">mail
    archive</a></li>
  <li><a
    href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2001Jul/0399.html">Revised
    Model Theory</a></li>
  <li><a href="http://www.w3.org/TR/2000/CR-rdf-schema-20000327/">RDF Schema
    Specification 1.0</a></li>
  <li><a href="http://ilrt.org/discovery/2001/07/rdf-syntax-grammar/">RDF/XML
    Syntax Grammar Experiments</a></li>
</ul>

<h3><a name="recommended-readings"
id="recommended-readings">Recommended</a></h3>
<ul>
  <li><a href="http://users.bestweb.net/~sowa/misc/mathw.htm#Model">Sowa's
    Section on Model Theory</a></li>
  <li>An introductory text on logic e.g. Metalogic, An Introduction to the
    Metatheory of Standard First Order Logic Geoffrey Hunter University of
    California Press 1971 (6th printing 1996) ISBN 0-520-02356-0</li>
  <li><a
    href="http://www.daml.org/2001/03/model-theoretic-semantics.html">DAML
    Model Theoretic Semantics</a></li>
  <li><a href="http://www.cis.upenn.edu/~hahosoya/xduce/">XDuce Regular
    Expressions</a></li>
  <li><a href="http://www.openhealth.org/RDF/RDFSyntaxFormal">XDuce Grammar
    for RDF</a> by Jonathon Borden</li>
</ul>

<h3>Suggested (Late Addition)</h3>
<ul>
  <li><a
    href="http://www.w3.org/DesignIssues/InterpretationProperties.html">Interpretation
    Properties</a></li>
  <li><a href="http://www.w3.org/DesignIssues/Axioms.html">Universal Resource
    Identifiers -- Axioms of Web Architecture</a></li>
</ul>

<h2><a name="recommended-materials" id="recommended-materials">Recommended
Materials</a></h2>

<p>It is recommended that participants have access to the paragraph numbered
<a
href="http://lists.w3.org/Archives/Public/www-archive/2001Jun/att-0021/00-part">Model
and Syntax</a> and the <a
href="http://lists.w3.org/Archives/Public/www-archive/2001Jun/att-0022/00-part">RDF
Schema</a> specs.</p>
<hr />
<address class="contact">
  <a href="http://www.w3.org/People/EM/">Eric Miller</a> &lt;em@w3.org&gt;,
  (W3C) Semantic Web Activity Lead
</address>

<p><small>$Id: Overview.html,v 1.29 2001/07/27 16:00:21 bmcbride Exp
$</small></p>
</body>
</html>