ftf1 23.9 KB

Raw Blame History Permalink

<?xml version="1.0" encoding="UTF-8"?>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  <title>RDF Data Access Working Group Meeting, April 2004 in
  Amsterdam</title>
</head>

<body>

<div class="nav">
<a href="../../../">W3C</a> * <a href="./">RDF Data Access WG</a></div>

<h1>RDF Data Access Working Group Meeting, April 2004</h1>

<h2>hosted near Amsterdam by <a
href="http://www.asemantics.com/">@semantics</a></h2>

<div style="text-align: center">
on this page: <a href="#where">Venue</a> *
<a href="#who">Participants</a> * <a href="#agenda">Agenda</a> * <a href="#min">Minutes</a> * <a href="#rdl">Reading List</a><br />
nearby: <a href="http://www.w3.org/2003/12/swa/dawg-charter">charter</a> * <a
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/">public-rdf-dawg
archive</a> * <a href="http://dawg.asemantics.com/">logistics details</a> *
<a href="UseCases">Use Cases draft</a> * IRC logs: <a
href="http://www.w3.org/2004/04/22-dawg-irc">Thu</a>, <a
href="http://www.w3.org/2004/04/23-dawg-irc">Fri</a></div>

<p>The goals of this meeting are to:</p>
<ul>
  <li>Meet and greet, build trust that facilitates collaboration</li>
  <li>Flesh out use cases and requirements; establish a plan to publish it as
    our <a
    href="http://www.w3.org/2004/02/Process-20040205/tr.html#first-wd">first
    public working draft</a></li>
  <li>Explore the existing technologies a bit</li>
</ul>
<address>
  by Dan Connolly, chair <br />
  <small>$Revision: 1.51 $ of $Date: 2004/05/03 15:35:26 $ by $Author:
  connolly $</small><br />
  <a href="#chlog">changes</a> since v1.36 from <a
  href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0132.html">15
  Apr announcement</a>
</address>

<div>
<h2 id="where">Venue</h2>

<p><img align="right" src="amsTravel-img.png" alt="" />The meeting is
near the Amsterdam Schipol (AMS) international airport. See <a
href="http://dawg.asemantics.com/">logistics details from the host</a>
for exact location, hotel accomodations etc. The local contact is
Dirk-Willem van Gulik <a href="tel:+31-71-514-9564">+31 (0) 71 514
9564</a>.</p>

<ul>
  <li>
<a href="http://photos.dajobe.org/gallery/dawg-leiden-april2004/IMG_3504"><img align="right" src="http://photos.dajobe.org/albums/dawg-leiden-april2004/IMG_3504.thumb.jpg" alt="door to DAWG meeting" /></a>
<a href="http://photos.dajobe.org/gallery/dawg-leiden-april2004">photos by DaveB</a></li>
  <li><a href="http://dawg.asemantics.com/pics/">photos by Dirk</a></li>
</ul>

<p><em>image details: <a href="amsTravel.n3">amsTravel.n3</a>, <a
href="Makefile">Makefile</a></em></p>
</div>

<div>
<h2 id="who">Participants</h2>

<p>
<a href="http://dawg.asemantics.com/pics/images/1.html"><img src="http://dawg.asemantics.com/pics/thumbnails/dscf3200.jpg" alt="meeting participants"  align="right" /></a>
<a href="http://dawg.asemantics.com/pics/images/3.html"><img src="http://dawg.asemantics.com/pics/thumbnails/dscf3202.jpg" alt="meeting participants" align="right"/></a>

The following <a href="./#who">members of the WG</a> attended:
</p>
</div>
<ol>
  <li><a href="http://www.agfa.com/">Agfa-Gevaert N. V.</a>
    <ul>
      <li>Jos <b>De Roo</b></li>
    </ul>
  </li>
  <li><a href="http://www.asemantics.com/">Asemantics S.R.L.</a>
    <ul>
      <li>Alberto <b>Reggiori</b></li>
      <li>Dirk-Willem <b>van Gulik</b></li>
    </ul>
  </li>
  <li><a href="http://www.hicksandassociates.com/">Hicks &amp; Associates,
    Inc.</a>
    <ul>
      <li>Bryan <b>Thompson</b> (in part, remote)</li>
    </ul>
  </li>
  <li><a href="http://www.hp.com/">HP</a>
    <ul>
      <li>Andy <b>Seaborne</b></li>
    </ul>
  </li>
  <li><a href="http://www.inria.fr/">Institut National de Recherche en
    Informatique et en Automatique (INRIA)</a>
    <ul>
      <li>Jean-François <b>Baget</b> (<a
        href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JanMar/0019.html">intro</a>.
        near <em>Grenoble, France</em>)</li>
    </ul>
  </li>
  <li><a href="http://www.mindlab.umd.edu/index.html">Maryland Information
    and Network Dynamics Lab at the University of Maryland</a>
    <ul>
      <li>Kendall <b>Clark</b></li>
    </ul>
  </li>
  <li><a href="http://www.panasonic.co.jp/global/">Matsushita Electric
    Industrial Co., Ltd. (MEI)</a>
    <ul>
      <li>Yoshio <b>Fukushige</b> (<a
        href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0138.html">intro</a>;
        near <em>Tokyo, Japan</em>)</li>
    </ul>
  </li>
  <li><a href="http://www.networkinference.com/">Network Inference</a>
    <ul>
      <li>Rob <b>Shearer</b></li>
    </ul>
  </li>
  <li><a href="http://www.profium.com/">Profium Ltd.</a>
    <ul>
      <li>Janne <b>Saarela</b></li>
    </ul>
  </li>
  <li><a href="http://www.ilrt.bris.ac.uk/rdu/w3">University of Bristol</a>
    <ul>
      <li>Dave <b>Beckett</b></li>
    </ul>
  </li>
  <li><a href="http://www.ecs.soton.ac.uk/">University of Southampton</a>
    <ul>
      <li>Stephen <b>Harris</b></li>
    </ul>
  </li>
  <li>Invited Experts
    <ul>
      <li>Howard <b>Katz</b></li>
    </ul>
  </li>
  <li><a href="/">W3C</a>
    <ul>
      <li>Dan <b>Connolly</b>, chair (<a
        href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JanMar/0002.html">intro</a>.
        near <tt>MCI</tt>)</li>
      <li>Eric <b>Prud'hommeaux</b>, team contact (<a
        href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JanMar/0001.html">intro</a>.
        near <tt>NRT</tt>)</li>
    </ul>
  </li>
</ol>

<p>Mr. Hiroyuki Sato of Information Sharing Platform Laboratories
NIPPON TELEGRAPH AND TELEPHONE CORPORATION (NTT) attended the meeting
as an observer; he has not yet joined the WG.</p>

<p>See also: <a
href="http://www.w3.org/2002/09/wbs/35463/AmsterdamDAWGF2F/">registration
form</a></p>

<div>
<h2 id="agenda">Agenda</h2>

<h3 id="apr22">Thu, 22 Apr</h3>

<ul>
  <li><a href="#convene">Convene (9am)</a>
  </li>
  <li><a href="#ucr">Use Cases and Requirements</a>, part 1
  </li>
  <li>break (10:15-10:30)</li>
  <li><a href="#ucr">Use Cases and Requirements</a>, part 2 (10:30-12:30)</li>
  <li>lunch (12:30-2)</li>
  <li><a href="#webarch">webarch</a></li>
  <li><a href="#ucr">Use Cases Requirements</a>, part 3</li>
  <li>break (3:30-3:45)</li>
  <li>Use Cases and Requirements, part 4</li>
  <li>stop (5pm)</li>
</ul>

<h3 id="apr23">Fri, 23 Apr</h3>

<ul>
  <li><a href="#mtg-sched">WG meeting schedule</a> (9am to 10:30)</li>
  <li>break (10:30-10:45)</li>
  <li><a href="#ucr">Use Cases and Requirements</a>, part 5
  </li>
  <li>lunch (12:30-2)</li>
  <li><a href="#tech-survey">Survey of existing technologies</a>, part 1 (<a href="#phone">*PHONE</a>;
    <a
    href="http://www.timeanddate.com/worldclock/fixedtime.html?day=23&amp;month=4&amp;year=2004&amp;hour=14&amp;min=0&amp;sec=0&amp;p1=16">time
    near you</a>)
  </li>
  <li>break (3:30-3:45)</li>
  <li><a href="#tech-survey">Survey of existing technologies</a>, part 2 (<a href="#phone">*PHONE</a>)
  </li>
  <li>5pm stop</li>
</ul>

<p><a name="phone" id="phone">*PHONE</a>: We intend to offer remote
participation by telephone during these sessions</p>

<h3>Presentation Materials and Meeting Records</h3>

<p>Presentation materials are part of the meeting record, and accessible
meeting records are important.</p>

<p>A few WG members have requested that presentation materials be available a
couple days ahead of time. An easy way to submit them to the record without
clogging up everybody's mailbox is to mail them to
<tt>www-archive@w3.org</tt> as attachments, then find them in the <a
href="http://lists.w3.org/Archives/Public/www-archive/">archive</a>, and send
a pointer to <tt>public-rdf-dawg@w3.org</tt>.</p>

<p>The <a
href="http://www.w3.org/2002/03/email_attachment_formats.html">guidelines for
email attachments</a> are relevant:</p>

<blockquote>
  <p>...avoid formats that are virus prone, proprietary or platform
  dependent. For example, whenever possible you should use HTML instead of MS
  Word, PowerPoint or PDF. (Ideally, use XHTML or HTML4.)</p>

  <p>If you must use a proprietary or platform-dependent format, please also
  include an alternate version in a universally readable format, such as HTML
  or plain text, if possible. If you cannot, then at least include a format
  that has widely available free viewers, if possible.</p>
</blockquote>

<p>If you use powerpoint, please give us the powerpoint sources plus a PDF
export plus some sort of text dump (RTF?).</p>
</div>

<div><h2 id="min">Minutes</h2>

<p><em>See also: <a href="http://www.w3.org/2004/04/22-dawg-irc">IRC log from
Thu</a>,
<a href="http://www.w3.org/2004/04/23-dawg-irc">IRC log from
Fri</a>.</em></p>

<h3 id="convene">Convene, review charter and W3C process</h3>

<p>Roll call: see <a href="#who">attendance</a> above.</p>

<p>Connolly briefly reviewed <a href="/Consortium/Process/">W3C
process</a>, emphasizing that its purpose is to build community
consensus to deploy new technologies.  Connolly noted that changes to
the <a href="http://www.w3.org/2003/12/swa/dawg-charter">charter</a>
are possible, but they involve negotation with parties outside the
WG.</p>

<p><em>(not presented:</em><a href="../../02pd/rec54-img"><em>formal
process model diagram</em></a><em>, with versions in</em><a
href="../../02pd/rec54-img.ps"><em>.ps</em></a><em>,</em><a
href="../../02pd/rec54-img.png"><em>.png</em></a><em>, and</em><a
href="../../02pd/rec54-img.svg"><em>.svg</em></a><em>)</em></p>

<h3 id="ucr">Use Cases</h3>

<p>Connolly noted that outreach is an important function of the use
cases and requirements document; for example, it would be nice to note
a few use cases in a short summary of our work for the WWW2004
conference.</p>

<p>Each member of the WG was invited to speak briefly to their most
valued use cases and the connection to their work and their
constituency. <em>see <a
href="http://www.w3.org/2004/04/22-dawg-irc">IRC log</a> for some
details</em>.</p>

<p><b>ACTION DaveB:</b> write up this educational metadata UC</p>

<p>Clark reported on the current (1.24) use cases draft: some
struggles with the "benefits" heading and such.</p>

<p>The group discussed the balance between quality and quantity of use
cases: how many do we have time to write up well? Opinions varied from
5 to 10 to 15. Some sentiment favored a small number of elaborated use
cases and a larger number of short sketches. External feedback might
prompt us to reconsider which use cases to elaborate.</p>

<p>The group discussed wasy to improve the document, including promoting the "problem description" material in the introduction.</p>

<p><b>ACTION RobS:</b> to generate some RDF (in some form) for 5.1.1.</p>

<p><b>ACTION EricP:</b> to generate a diagram of a query discussed in
the use cases document.</p>

<p><b>ACTION Kendall:</b> to work with Alberto on 5.1.3.</p>

<p><b>ACTION Yoshio:</b> to write up "Kate finds an article and wants
to find related programs..."</p>

<p>ACTION Kendall: to recast this (5.2.1. Saying things about web
resources) in terms of some tool for annotating photos. (<b>DONE</b>
in 1.25)</p>

<p>ACTION Kendall: to add negotiation of query lang to
candidate requirements. (<b>DONE</b> in 1.25)</p>


<p>The group discussed requirements, especially their
relationship to use cases that motivate them.</p>

<p>The discussion got into some design details about styles of query
result bindings.</p>

<p>The group discussed requirements for support of various
forms of datatyping in some depth. We began collecting
<a href="ftfreq">straw poll data about support for
various requirements</a>.</p>

<p>Connolly constructed straw polls:</p>
<ul>
<li>if we were to keep only 5 use cases, would this be one of them?</li>
<li>if we were to keep only 10 use cases, would this be one of them? <em>this second question was abandoned part way thru.</em></li>
</ul>

<p>The <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0175.html">results as reported by Beckett</a> include:</p>

<pre>
    5  T
1.  8 10 5.1.1.  Finding an email address
2.  9  - 5.6.1.  Finding information about motorcycle parts
3.  8  - 5.5.1.  Finding unknown titles (media)
4.  7 12 5.1.3.  Monitoring news events
5.  7  - 5.8.1.  Avoiding traffic jams
    7  - 5.2.2.  Discovering what people say about news stories

    6  - 5.4.1.  Exploring my neighborhood

    4  7 5.2.1.  Saying things about web resources
    4  - 5.7.1.  Finding input and output documents for test cases

    2  7 5.9.1.  Ordering an x-ray
    2  - 5.8.2.  Finding the cheapest flight from Boston to Chicago
    2  - 5.3.1.  Tracking accounts and customers
    2  - 5.10.1. Find employees by group
    1  4 5.1.2.  Regularly executing a query
    1  - 5.7.2.  Describing software configurations
</pre>

<p>The straw polls do not take into account the following use cases,
which had not been digested into the use cases document or, in some
cases, not been written:</p>

<ul>
<li>Browsing Example - tell me about X, <b>ACTION Steve Harris</b></li>
<li>Bandwidth Efficiency - bytesize of resultset, <b>ACTION SteveH</b></li>
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0096.html">Chunking" - limit and offset, Steve Harris</a></li>
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0130.html">OWL Ontology Browser</a>, Pat Hayes</li>
</ul>

<p><b>ACTION Kendall:</b> to look at Yoshio's use cases.</p>

<p><b>ACTION Janne:</b> write a use case to motivate the requirement
of having queries written in RDF. (WITHDRAWN?)</p>

<p>The group only briefly discussed a plan for publishing the use
cases and requirements document as a W3C <a
href="http://www.w3.org/2004/02/Process-20040205/tr.html#first-wd">first
public working draft</a>. The 3 month "heartbeat" requirement means we
need to publish in May; May 17, the start of the WWW2004 web
conference, is an interesting, if challenging, target.</p>

<p>On Friday morning, the editor reported some progress
on updating the document (Revision 1.25 2004/04/23 08:13:40).
The WG <b>RESOLVED:</b> kendall has done a great job.
</p>

<p><b>ACTION: AndyS, EricP</b> to review kendallC draft by 4 May telcon</p>

<p>As discussion of datatype constraints brought up some
implementation experience with specific cases, the chair
asked for a volunteer to start collecting test cases.</p>

<p><b>ACTION SteveH:</b> to draft and maintain a list of test sketch
cases, including x &lt; y, x &lt; 18.</p>

<p>As recorded in <a href="ftfreq">requirements straw polls</a>,
various members of the WG supported or opposed various requirements:</p>

<blockquote>
<ul>
 <li> Queries with optional triples (straw poll on required: yes 9, no 1)
 </li>
<li> Queries with disjunction (straw poll on required: yes 4, no 3, chat more 2-3)
   UC: 5.3.1

 </li><li> Queries expressing arbitrary RDF data types (straw poll on required: yes 6, no: 3)

 </li><li> Queries supporting datatypes xsd:integer and xsd:float with operations: less than,
   equal, greater than [DATATYPES-IF]

 </li><li> Queries supporting date and time datatypes with operations equal, before and
   after. [DATATYPE-DT]  (straw poll, yes: 9, no: 3)

 </li><li> Queries expressible as URLs. (straw poll: yes 9, no: 1)

 </li><li> Queries serializable as text. (straw poll: yes everyone)

 </li><li> Query results in user-selectable result template. (straw poll: yes: 0, no: 10)

 </li><li> Query results in user-selectable Internet Media Types. (straw poll: yes: 5, no: 4)

 </li><li> Query results as a sub-graph of the queried RDF graph (straw poll: yes 10, no: 2)

 </li><li> Query results as multiple solution graphs (straw poll: yes 4, no 5)

 </li><li> Queries for the non-existence of one or more triples in a graph.
   (straw poll: yes 6, no 1)

 </li><li> Queries expressible in a syntax that is easily read and written by people.
   (straw poll: yes 10, no 1)

 </li><li> Queries shall allow execution against a local RDF storage service without network support
   (i.e., queries independent of any network protocol).
   (straw poll: yes 10, no 0)

 </li><li> The protocol shall allow the negotiation of query languages (straw poll: yes 4, no 8)

 </li><li> Query results can be returned as 0 or more variable bindings (tuples)
   (straw poll: yes 12, no 1)

 </li><li> Query results must return source/provenance (straw poll: yes 2, no 10)

 </li><li> Query results may return source/provenance (straw poll: yes 8, no 3)

 </li><li> Query results can be interpreted without knowledge of RDF. (straw poll: yes 2, no 6)

 </li><li> Queries written in an RDF syntax (straw poll: 0, no: 8)

 </li><li> The graph of the query looks like the graph of the result (straw poll: yes 1, no 8)

 </li><li> The query language shall be extendable
   (such as via function calls or namespace mechanism) (straw poll: yes 11, no 1)

 </li><li> The query protocol shall address bandwidth issues of result formats.
   (straw poll: yes 9, no 1)

 </li><li> The query language/protocol supports limit, offset and ordering of results.
   (straw poll: yes 5, no 3)

 </li><li> The query language/protocol supports limiting of the number of results.
   (straw poll: yes 9, no 2)</li>
</ul>

<p>Obvious:</p>
<ul>
<li> Queries with paths of two or more edges </li>
</ul>

<p>Insufficient Support:</p>
<ul>
<li> Query results using 1) graph entailment *OR*</li>
<li> Query results (not using entailment) but 2) treating the graph as a fixed object</li>
<li>Query results can be returned as triple bindings </li>
<li> The query protocol should be cognizant of network access.</li>
</ul>
</blockquote>


<h3 id="webarch">Web Architecture in Brief</h3>

<p>Connolly presented <a
href="http://www.w3.org/2004/Talks/0121-ij-xmlgov/all.htm">some
slides</a> on the Web Architecture document and the TAG. Blah blah
blah.</p>

<h3 id="mtg-sched">Meeting Schedule</h3>

<p>As recorded in <a
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0177.html"
>DAWG telcon and F2F meeting decisions</a>, after discussing various
constraints, we made the following decisions:</p>

<ul>
  <li><strong>Resolved</strong> to have telcons: 14:30Z Tuesday (10:30
  Boston / 11:30pm tokyo / 16:30 Paris / 07:30am SF) starting 4th May
  2004 <p>Abstained: RS</p>
  </li>
  <li><strong>Resolved</strong> to meet 2004-07-14/15 Network
  Inference place: California<br />
  tentative regrets: JS, DB</li>
  <li><strong>Resolved</strong> to meet 2004-09-16/17 HP AndyS place:
  bristol <br />
  RS abstaining</li>
  <li><strong>Resolved</strong> to meet 2004-12-01/02 Network
  Inference place: Las Vegas<br />
  JdR abstaining</li>
</ul>

<h3 id="tech-survey">Survey of existing technologies</h3>

<p>The first session consistend of three 10-minute talks followed by
an hour of discussion.</p>

<ol>
  <li><cite><a
  href="http://lists.w3.org/Archives/Public/www-archive/2004Apr/0087.html">on
  the use of XPointer and the HT TP "Range " header as a possible
  scalable and extensible RDF data access protocol</a></cite> by Bryan
  Thompson (remote)</li>
  <li><cite><a
  href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0180.html">XQuery:
  a whirlwind tour</a></cite> by HowardK</li>
  <li><cite>Using XQuery for RDF: costs and benefits of one
  approach</cite> by RobS
  <p>@@materials</p>
  </li>
</ol>

<p><em>see the <a href="http://www.w3.org/2004/04/23-dawg-irc">IRC log
from Fri</a> for some notes on discussion.</em></p>

<p><b>ACTION DanC:</b> inform the TAG of the conflict between <a
href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.9">sec13.9
of the HTTP spec</a> and TAG's recommendation on issue 7</p>

<p>In the second session, Kendall's Versa talk was preempted by more
work on the usecases document, and Pat Hayes's DAML QL talk was
posponed until Pat is available, so we had 2 short talks on
implementation experience with RDQL:</p>

<ol>
  <li><cite><a
  href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/att-0181/all.html">Implementing
  RDQL in Rasqal</a></cite> by DaveB</li>
  <li><a name="RDQL" id="RDQL"
  href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0178.html"><cite>RDQL:
  an implementation experience</cite></a> by Alberto</li>
</ol>

<p>After a short discussion, the WG <b>resolved</b> to thank the
hosts, with applause, and the meeting was adjourned.</p>

</div>

<div>
<h2 id="rdl">Reading List</h2>

<p>The only required reading for the meeting is:</p>
<ul>
  <li><cite><a href="http://lists.w3.org/Archives/Public/www-archive/2004Apr/att-0095/_UseCases-ftf.html">Data Access Working Group User Cases: WORKING
    DRAFT</a></cite> v1.24 2004/04/16 21:44:17</li>
</ul>

<p>The following reading materials are recommended to you by fellow WG
members (e.g. in the <a
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0092.html">10
Apr telcon</a>) and by the chair for meeting preparation. They are reasonably
short, and you will eventually need to know this material in order to
participate effectively in this WG, but since they don't directly relate to
decisions on the meeting agenda, none of them is required.</p>
<ul>
  <li><cite><a
    href="http://www.ilrt.bris.ac.uk/discovery/2004/01/turtle/">Turtle -
    Terse RDF Triple Language</a></cite><br />
    Dave Beckett<br />
    Institute for Learning and Research Technology<br />
    University of Bristol<br />
    Date: 2004/03/25 22:32:27.
    <p><em>That's a precise spec for turtle. For an informal introduction to
    this style of syntax, see...</em></p>
    <ul>
      <li><cite><a href="http://www.w3.org/2000/10/swap/Primer">Primer:
        Getting into RDF &amp; Semantic Web using N3</a></cite><br />
        Tim BL, with his director hat off<br />
        Id: Primer.html,v 1.55 2003/04/15 23:57:30 sandro Exp</li>
    </ul>
  </li>
  <li><cite><a href="http://www.joseki.org/protocol.html">Joseki: RDF
    WebAPI</a></cite><br />
    Date: 2003/09/16 16:30:58 Revision: 1.4 Author: andy_seaborne</li>
  <li><cite><a
    href="http://www.w3.org/Submission/2004/SUBM-RDQL-20040109/">RDQL - A
    Query Language for RDF</a></cite><br />
    W3C Member Submission 9 January 2004
    <p><em>for a less terse treatment of RDQL, see:</em></p>
    <ul>
      <li><cite><a href="http://jena.sourceforge.net/tutorial/RDQL/">A
        Programmer's Introduction to RDQL</a></cite><br />
        Andy Seaborne April 2002</li>
    </ul>
  </li>
  <li><cite><a
    href="http://www.research.ibm.com/journal/sj/414/chamberlin.pdf">XQuery:An
    XML Query Language</a></cite><br />
    Don Chamberlin. IBM Systems Journal Vol 41, No 4. 2002
    <p><em>recommended by HowardK. see also: <a
    href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0128.html">supplement
    15Apr</a></em></p>
  </li>
  <li><cite><a href="http://www.w3.org/2001/11/13-RDF-Query-Rules/">RDF Query
    Survey</a></cite><br />
    Eric Prud'hommeaux and Benjamin Grosof<br />
    Id: Overview.html,v 1.89 2004/04/08 07:59:42 eric Exp</li>
</ul>
</div>

<div>
<h2 id="chlog">Change Log</h2>

<p>These are the changes since v1.36 from the <a
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0132.html">15
Apr announcement</a>:</p>
<pre><!-- log goes on next line, not this one -->
$Log: ftf1.html,v $
Revision 1.51  2004/05/03 15:35:26  connolly
added some photo links

Revision 1.50  2004/04/30 21:37:14  connolly
finished attendance
move venue above participants; moved map to venue section

Revision 1.49  2004/04/30 21:28:56  connolly
done summarizing friday

Revision 1.48  2004/04/30 19:15:16  connolly
markup fixes

Revision 1.47  2004/04/30 19:13:10  connolly
Thu minutes done-ish

Revision 1.46  2004/04/26 13:54:24  connolly
(connolly) Changed through Jigsaw.

Revision 1.45  2004/04/26 13:43:51  connolly
(connolly) Changed through Jigsaw.

Revision 1.44  2004/04/24 10:10:53  connolly
clean up "11 or 12" note

Revision 1.43  2004/04/24 10:09:47  connolly
more updates, rescued from Amaya cache

Revision 1.41  2004/04/23 11:53:05  connolly
some pointers to records so far

Revision 1.40  2004/04/22 11:40:03  connolly
links to hosting offer details

Revision 1.39  2004/04/20 14:35:57  connolly
more changelog tweaks

Revision 1.38  2004/04/20 14:34:59  connolly
changelog

revision 1.37
date: 2004/04/20 14:31:42;  author: connolly;  state: Exp;  lines: +3 -3
note times near WG members for phone sessions</pre>
</div>
</body>
</html>