index.html 22.9 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>25-26 February 2002 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></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="#where">venue</a>] [<a
href="#objectives">objectives</a>] [<a href="#agenda">agenda</a>] [<a
href="#reading">reading</a>]</p>


<h1 align="center">25th-26th February 2002 Meeting of the W3C RDFCore WG</h1>

<p style="text-align: center"><span style="font-weight: bold"><a
href="http://www.w3.org/2001/07/allgroupoverview.html">Technical Plenary and
WG Meeting Event Hotel Royal Casino - Cannes Mandelieu FRANCE</a></span></p>

<h2><a id="who" name="who">Participants</a><br />
</h2>
<ul>
  <li>Dave Beckett, ILRT</li>
  <li>Jeremy Carroll, (hplabs)</li>
  <li>Dan Connoly, W3C</li>
  <li>Mike Dean, BBN <span style="font-style: italic"></span></li>
  <li>Jos De Roo, AGFA</li>
  <li>Martyn Horner, Profium Sarl</li>
  <li>Graham Klyne, Baltimore Technologies</li>
  <li>Brian McBride, Hewlett Packard <i>(co-chair)</i></li>
  <li>Eric Miller, W3C</li>
  <li>Patrick Stickler, Nokia</li>
</ul>

<h3>Telecon Participants</h3>

<p>Telecon partipants attended the two telecon's at 4pm each day.</p>
<ul>
  <li>Pat Hayes, IHMC</li>
  <li>Frank Manola, MITRE</li>
  <li>Aaron Swartz, HWG</li>
</ul>

<h3>Regrets</h3>
<ul>
  <li>Dan Brickley, University of Bristol (co-chair)</li>
  <li>Ron Daniel, Interwoven</li>
  <li>Jan Grant, ILRT, University of Bristol</li>
  <li>Sergey Melnik, Stanford University</li>
  <li>Steve Petschulat, IBM</li>
</ul>

<h3>Absent</h3>
<ul>
  <li>Frank Boumphrey</li>
  <li>Bill dehOra, InterX</li>
  <li>Rael Dornfest</li>
  <li>R. V. Guha</li>
  <li>Yoshiyuki Kitahara</li>
  <li>Michael Kopchenov</li>
  <li>KWON, Hyung-Jin</li>
  <li>Ora Lassila</li>
  <li>Satoshi Nakamura</li>
  <li>Pierre G. Richard</li>
</ul>

<h2><a id="objectives" name="objectives">Objectives</a></h2>
<ul>
  <li>to resolve as many outstanding issues as possible</li>
  <li>to plan for getting to last call and beyond</li>
</ul>

<h2><a id="agenda1" name="agenda1">Agenda</a></h2>

<p>irc channel: irc.openprojects.net #rdfcore</p>

<h3>Monday, 25th Feb 2002 (all day)</h3>
<pre>         0830 Welcome, Introductions, meeting objectives, agenda review
         0845 The current state of play (bwm)
         0900 Issues session 1
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-not-id-and-resource-attr">rdfms-not-id-and-resource-attr</a>
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-nested-bagIDs">rdfms-nested-bagIDs</a>
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-rdf-names-use">rdfms-rdf-names-use</a>
         1030 Coffee
         1045 short presentation
         1100 issues session 2
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-replace-value">rdfms-replace-value</a>
                rdfms-editorial
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-xml-base">rdfms-xml-base</a>
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-fragments">rdfms-fragments</a>
         1230 lunch
         1330 issues session 3
              preparing for I18N meeting
              Datatypes
         1515 coffee
         1545 short presentation
         1600 telecon
                review of the day
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-identity-of-statements">rdfms-identity-of-statements</a>
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-fragments">rdfms-fragments</a>
                datatypes
         1730 plans for next day
         1745 close

              Dinner
              Homework - read Pat's latest <a href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Feb/0646.html">datatyping proposal</a></pre>

<h3>Tuesday, 26th Feb 2002 (all day)</h3>
<pre>         0900 Split Session
                  Meeting with I18N irc #rdfcore-i18n
                  breakout group - test cases
                     DaveB's detailed test case for rdfms-nested-bagID
                     Jeremy's XML base test cases (+ve test cases for error2 and error3)
                     generate test cases for illegal names use e.g. &lt;rdf:foo&gt;
                     Discuss RDF 2396 - rdf:ID="foo" is equiv to rdf:about=".#foo"
         1030 Coffee
         1045 issues session 4
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdf-charmod-literals">rdf-charmod-literals</a>
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdf-charmod-uris">rdf-charmod-uris</a>
                <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-xmllang">rdfms-xmllang</a>
                rdfms-literal-is-xml-structure
                rdfms-xml-literal-namespaces
                Test cases from morning session
                RFC 2396 - rdf:ID="foo" is equiv to rdf:about=".#foo"
                rdfms-assertion
                rdfms-not-id-and-resource-attr
         1230 lunch
         1330 Issues session 5
                rdfms-assertion
                rdfms-not-id-and-resource-attr
                datatyping
         1515 short presentation - Patrick
         1530 coffee
         1600 Telecon
              Getting to Rec
              Goals and Next Steps
         1800 close</pre>

<h2><a id="actions" name="actions">Actions</a></h2>

<table>
  <caption></caption>
  <tbody>
    <tr>
      <td>2002-02-25#1</td>
      <td>jjc</td>
      <td>Formalize test case for &lt;eg:prop rdf:ID="issue" eg:p1="foo"
      /&gt;</td>
    </tr>
    <tr>
      <td>2002-02-25#2</td>
      <td>JanG</td>
      <td>Add test case for &lt;eg:prop rdf:ID="issue" eg:p1="foo" /&gt; to
        test cases draft</td>
    </tr>
    <tr>
      <td>2002-02-25#3</td>
      <td>JanG</td>
      <td>Review test cases in case changed by &lt;eg:prop rdf:ID="issue"
        eg:p1="foo" /&gt; decision</td>
    </tr>
    <tr>
      <td>2002-02-25#4</td>
      <td>DaveB</td>
      <td>rdfms-nested-bagID: update syntax WD to reflect decision</td>
    </tr>
    <tr>
      <td>2002-02-25#5</td>
      <td>bwm</td>
      <td>review test case for rdfms-nested-bagID</td>
    </tr>
    <tr>
      <td>2002-02-25#6</td>
      <td>jjc</td>
      <td>generate more test cases for rdfms-nested-bagID</td>
    </tr>
    <tr>
      <td>2002-02-25#7</td>
      <td>DaveB</td>
      <td>Emphasise in syntax WD that rdf:li is not allowed as an
      attribute</td>
    </tr>
    <tr>
      <td>2002-02-25#8</td>
      <td>DaveB</td>
      <td>Update syntax doc to reflect</td>
    </tr>
    <tr>
      <td>2002-02-25#9</td>
      <td>JanG</td>
      <td>Ensure test cases for rdf:foo added to test cases WD</td>
    </tr>
    <tr>
      <td>2002-02-25#10</td>
      <td>DaveB</td>
      <td>Update syntax doc to reflect xml:base same doc ref decision</td>
    </tr>
    <tr>
      <td>2002-02-25#11</td>
      <td>JanG</td>
      <td>Add test case for xml:base same doc reference to test cases WD</td>
    </tr>
    <tr>
      <td>2002-02-25#12</td>
      <td>DanC</td>
      <td>Contact RFC 2396 editors to confirm that RDF will use a different
        algorithm for xml:base</td>
    </tr>
    <tr>
      <td>2002-02-25#13</td>
      <td>DaveB</td>
      <td>Update syntax WD to reflect xml:base="http://example.org"&gt;
        decision</td>
    </tr>
    <tr>
      <td>2002-02-25#14</td>
      <td>JanG</td>
      <td>update test cases to reflect xml:base="http://example.org"&gt;
        decision</td>
    </tr>
    <tr>
      <td>2002-02-25#15</td>
      <td>DanC</td>
      <td>Confirm with RDF 2396 that xml:base="http://example.org"&gt;
        decision is correct</td>
    </tr>
    <tr>
      <td>2002-02-25#16</td>
      <td>jjc</td>
      <td>replace xml:base error cases 1 and 2 with +ve test cases</td>
    </tr>
    <tr>
      <td>2002-02-25#17</td>
      <td>EricM</td>
      <td>Ensure primer has appropriate description of use of rdf:value</td>
    </tr>
    <tr>
      <td>2002-02-25#18</td>
      <td>bwm</td>
      <td>ensure model theory updated to reflect semantics of rdf:value</td>
    </tr>
    <tr>
      <td>2002-02-25#19</td>
      <td>Graham</td>
      <td>Draft text for the primer on use of frag id's with appropriate
        warnings re mime types</td>
    </tr>
    <tr>
      <td>2002-02-25#20</td>
      <td>DanC</td>
      <td>Highlight frag id semantics issue with the TAG</td>
    </tr>
    <tr>
      <td>2002-02-25#21</td>
      <td>EricM</td>
      <td>Ensure M&amp;S has an erratum to say the M&amp;S will be superceded
          by new documents</td>
    </tr>
    <tr>
      <td>2002-02-26#1</td>
      <td>bwm</td>
      <td>Add to postponed issues list, URI's to represent languages in
        literals</td>
    </tr>
    <tr>
      <td>2002-02-26#2</td>
      <td>DanC</td>
      <td>Create test case for daml:collection behaves like Literal</td>
    </tr>
    <tr>
      <td>2002-02-26#3</td>
      <td>DaveB</td>
      <td>Update syntax doc to reflect decsision about structure of
      literals</td>
    </tr>
    <tr>
      <td>2002-02-26#4</td>
      <td>bwm</td>
      <td>Contact Pat re effects of literals decision on model theory</td>
    </tr>
    <tr>
      <td>2002-02-26#5</td>
      <td>jjc</td>
      <td>Produce proposal for use of canonicalization for parseType
      literals</td>
    </tr>
    <tr>
      <td>2002-02-26#6</td>
      <td>bwm</td>
      <td>send draft text for #rdfms-assertion issue to TimBL for comment</td>
    </tr>
    <tr>
      <td>2002-02-26#7</td>
      <td>DaveB</td>
      <td>Update test cases to reflect not-id-and-resource decision</td>
    </tr>
    <tr>
      <td>2002-02-26#8</td>
      <td>PatrickS</td>
      <td>Create XML examples for datatypes doc</td>
    </tr>
    <tr>
      <td>2002-02-26#9</td>
      <td>FrankM</td>
      <td>Primer WD ready for review by 8th Mar</td>
    </tr>
    <tr>
      <td>2002-02-26#10</td>
      <td>bwm</td>
      <td>Organise f2f around Sardinia timescales in Bristol</td>
    </tr>
    <tr>
      <td>2002-02-26#11</td>
      <td>bwm</td>
      <td>Consider arrangements for RDF 2 workshop</td>
    </tr>
    <tr>
      <td>2002-02-26#12</td>
      <td>DaveB</td>
      <td>Propose n-triples changes to represent the new form of rdf literals.</td>
    </tr>
    <tr>
      <td></td>
      <td></td>
      <td></td>
    </tr>
  </tbody>
</table>

<h2><a id="decisions" name="decisions">Decisions</a></h2>

<h4><a id="d-2002-02-25-1" name="d-2002-02-25-1">d-2002-02-25-1</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-not-id-and-resource-attr">rdfms-not-id-and-resource-attr</a></p>

<pre>
  &lt;rdf:RDF>
    &lt;rdf:Description>
    &lt;eg:prop rdf:ID="issue" eg:p1="foo" />
    &lt;/rdf:Description>
  &lt;/rdf:RDF>
</pre>

<p>should generate</p>

<pre>
  _:a &lt;eg:prop> _: b.
  _:b &lt;eg:p1> "foo" .
  &lt;#issue> &lt;rdf:type> &lt;rdf:Statement> .
  &lt;#issue> &lt;rdf:subject> _:a.
  &lt;#issue> &lt;rdf:predicate> &lt;eg:prop>.
  &lt;#issue> &lt;rdf:object> _:b.
</pre>

<p>This is a change to some readings of M&amp;S and is made on the
on the grounds that M&amp;S is confusing and this decision adopts
a consistent interpretation of rdf:ID on property elements.
This issue is now closed.</p>

<h4><a id="d-2002-02-25-2" name="d-2002-02-25-2">d-2002-02-25-2</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-nested-bagID">rdfms-nested-bagID</a></p>

<p>The WG decided that:</p>

<blockquote>
<p>A bagID reifies the property attributes on the same element as the
bagid, the type node and statements immediately arising from property
elements that are immediate children of the element containing the
bagId.  In particular a property element whose statement is part of
the bag, which has property attributes, those statements are not part
of the bag.</p>
</blockquote>

<p>Specifically:</p>
<pre>
  &lt;rdf:Description about="a" bagID="bag1">
    &lt;some:prop rdf:ID="st1">
      &lt;rdf:Description about="b" bagID="bag2">
        &lt;some:otherProp rdf:ID="st2"> A literal &lt;/some:otherProp>
      &lt;/rdf:Description>
    &lt;/some:prop>
  &lt;/rdf:Description>
</pre>

<p>generates two bags.  Bag1 contains st1 only.  Bag2 contains st2
only.  This issue is closed.</p>

<h4><a id="d-2002-02-25-3" name="d-2002-02-25-3">d-2002-02-25-3</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-rdf-names-use">rdfms-rdf-names-use</a></p>

<p>The WG reaffirmed its decision not to restrict names in the RDF
namespaces which are not syntactic.  The WG decided that an RDF
processor SHOULD emit a warning when encountering names in the
RDF namespace which are not defined, but should otherwise behave
normally.</p>

<p>Specifically:</p>

<pre>
  &lt;rdf:Description>
    &lt;rdf:foo>foo&lt;/rdf:foo>
  &lt;/rdf:Description>
</pre>

is equivalent to:

<pre>
  _:a &lt;rdf:foo> "foo" .
</pre>

<p>This issue is closed.</p>

<h4><a id="d-2002-02-25-4" name="d-2002-02-25-4">d-2002-02-25-4</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-xml-base">rdfms-xml-base</a></p>

<p>RFC 2396 states that self document references, such as
rdf:about=&quot;&quot;, are not relative URI&quot;s are thus not
subject to being converted to an absolute URI using xml:base.
It was also noted in section 4.2 of RFC 2396 it states:</p>

<blockquote>
However, if the URI reference occurs in a context that is always
   intended to result in a new request, as in the case of HTML's FORM
   element, then an empty URI reference represents the base URI of the
   current document and should be replaced by that URI when transformed
   into a request.
</blockquote>

<p>It can be argued that this case should cover RDF's use of URI's.</p>

<p>The WG decided that RDF will convert such references to absolute
URI's and will take in scope xml:base attributes into account
in such conversions.</p>

<p>Specifically:</p>

<pre>
  &lt;rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
           xmlns:eg="http://example.org/"
           xml:base="http://example.org/dir/file">
    &lt;eg:type rdf:about="" />
  &lt;/rdf:RDF>
</pre>

<p>is equivalent to:</p>

<pre>
  &lt;http://example.org/dir/file> &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#type> &lt;http://example.org/type> .
</pre>

<h4><a id="d-2002-02-25-5" name="d-2002-02-25-5">d-2002-02-25-5</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-xml-base">rdfms-xml-base</a></p>

<p>The algorithm in RFC 2396 for creating an absolute URI is flawed in
the case where the base consists of a scheme, such as http:, followed
by a domain name with no terminating '/'.</p>

<p>Specifically, the WG decided that:</p>

<pre>
  &lt;rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
              xmlns:eg="http://example.org/"
              xml:base="http://example.org">
    &lt;eg:type rdf:about="relfile" />
  &lt;/rdf:RDF>
</pre>

<p>is equivalent to:</p>

<pre>
  &lt;http://example.org/relfile> &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#type> &lt;http://example.org/type> .
</pre>


<h4><a id="d-2002-02-25-6" name="d-2002-02-25-6">d-2002-02-25-6</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-xml-base">rdfms-xml-base</a></p>

<p>M&mp;S states that it is not legal to have two rdf:ID attributes in
a document with the same value.  The WG decided that any scope
xml:base attributes should be taken into account in this test.</p>

<p>Specifically, the WG decided that</p>

<pre>
  &lt;rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
              xmlns:eg="http://example.org/" >
    &lt;rdf:Description xml:base="http://example.org/dir/file"
                        rdf:ID="frag" eg:value="v" />
    &lt;rdf:Description rdf:ID="frag" eg:value="v" />
  &lt;/rdf:RDF>
</pre>

<p>is not an error</p>

<p>All outstanding questions on this issue have been resolved.  It will be
closed when all test cases have been approved.</p>


<h4><a id="d-2002-02-25-7" name="d-2002-02-25-7">d-2002-02-25-7</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-replace-value">rdfms-replace-value</a></p>

<p>The WG resolved:</p>

<ul>
  <li>that rdf:value is a property defined in the rdf namespace</li>
  <li>the model theory must state that rdf:value is a property</li>
  <li>that no other model theory semantics is defined specificaly for it</li>
  <li>This issue is closed</li>
</ul>

<h4><a id="d-2002-02-25-8" name="d-2002-02-25-8">d-2002-02-25-8</a></h4>

<p>The WG resolved that the Model and Syntax recommendation would be
replaced by the following documents:</p>

<ul>
  <li>a primer</li>
  <li>an RDF/XML syntax specification</li>
  <li>a model theory specification</li>
  <li>a test cases specification</li>
</ul>

<h4><a id="d-2002-02-25-9" name="d-2002-02-25-9">d-2002-02-25-9</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-editorial">rdfms-editorial</a></p>

<p>The WG resolved, given decision <a
href="d-2002-02-25-8">d-2002-02-25-8</a>, the editorial issues with
M&amp;S are now not relevant to the current document set and this
issue be closed.</p>

<h4><a id="d-2002-02-25-10" name="d-2002-02-25-10">d-2002-02-25-10</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-fragments">rdfms-fragments</a></p>

<p>The WG resolved that RDF uses URI's with fragment ID's to identify
resources.  This issue is now closed.</p>

<h4><a id="d-2002-02-26-1" name="d-2002-02-26-1">d-2002-02-26-1</a></h4>

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

<p>The WG resolved that a literal consists of three components:</p>

<ul>
<li>A representation of the parseType, which is a single bit</li>
<li>A language indicator which is a string as defined in XML.</li>
<li>A fully normalized UNICODE string.</li>
</ul>

<p>Further, the WG resolved that these two issues are closed.</p>

<h4><a id="d-2002-02-26-2" name="d-2002-02-26-2">d-2002-02-26-2</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfms-not-id-and-resource-attr">rdfms-not-id-and-resource-attr</a></p>

<p>The WG resolved that:</p>

<pre>
  &lt;rdf:Description>
    &lt;foo:bar rdf:ID="foo" rdf:resource="bar"/>
  &lt;/rdf:Description>
</pre>

<p>is legal.  This issue is now closed.</p>

<h4><a id="d-2002-02-26-3" name="d-2002-02-26-3">d-2002-02-26-3</a></h4>

<p>Issue: <a href="http://www.w3.org/2000/03/rdf-tracking/#rdfs-xml-schema-datatypes">rdfs-xml-schema-datatypes</a></p>

<p>The WG resolved that:</p>

<ul>
<li>Pat's proposal <a href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Feb/0643.html">simple datatypes 23-02-2002</a> is the basis for our datatypes solution</li>
<li>We will only make changes to fix specific problems, with test cases. A problem is something the WG agrees is problem.</li>
</ul>

<p>Further, the WG agreed that the following issues with the
datatyping proposal were problems:</p>

<ul>
<li>The lack of XML examples (Patrick Stickler to provide)</li>
<li>Jeremy's entailment is a problem</li>
<li>Octal is not an XML Schema datatype</li>
<li>XML Schema datatypes do not support different language
representations.</li>
</ul>

<h4><a id="d-2002-02-26-4" name="d-2002-02-26-4">d-2002-02-26-4</a></h4>

<p>The WG made the following decision with respect to the documents
under development:</p>

<ul>
<li>The primer, syntax spec, model theory, schema spec and test cases documents are all  recommendation track.</li>
<li>Datatypes will be included in the schema document.</li>
<li>The WG will aim for last call 1st May 2002.</li>
<li>Patrick Sticker will assist with editing the Schema document.</li>
</ul>

<h4><a id="d-2002-02-26-5" name="d-2002-02-26-5">d-2002-02-26-5</a></h4>

<p>The WG agreed to continue until six months after the
documents become recommendations, though not necessarily meeting
regularly.</p>

<h4><a id="d-2002-02-26-6" name="d-2002-02-26-6">d-2002-02-26-6</a></h4>

<p>The WG decided to hold a face to face meeting in June to consider
last call comments.</p>

<a id="minutes" name="minutes"></a>

<h2>Minutes</h2>

<h3><a id="i18n" name="i18n">Notes from I18N/RDFCore Meeting</a></h3>

<ul>
<li>I18N recommend that literals (strings) in the RDF graph be fully normalised UNICODE and should not start with a combining character.</li>

<li>I18N suggests that IRI's be used to name resources in the graph and that comparison of IRI's behaves as if they are UNICODE normalised, but not does require that such normalization is performed.</li>

<li>I18N agree that RDFCore requires a transitive string comparison
algorithm and requests that the specs do not mislead application
developers into thinking they are not permitted to implement a
more flexible string matching algorithm, e.g. on queries.</li>

<li>I18N note that the strings defining languages occasionally change and suggests that RDFCore may choose to use URI's to name languages.  RDFCore agree to consider.</li>

<li>I18N found the proposed solution of literals being a pair of a
string and a language tag acceptable.</li>

<li>I18N agree that n-triples is an internal tool for the WG and
developers and is not subject to the same internationization concerns
of more public syntaxes.  I18N request that the specs make this
limited role for n-triples clear.</li>

<li>There was some dicussion of RDFCore concerns that I18N specs would
not be final and of a lack of implementations delaying completion of
RDFCore.</li>
</ul>

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

<p><a href="rdfcore-i18n-irclog.html">rdfcore/i18n breakout session</a></p>

<p><a href="irclog-2002-02-25.html">Monday, 25th February 2002</a></p>

<p><a href="irclog-2002-02-26.html">Tuesday, 26th February 2002</a></p>

<p><a href="20020225-am.html">Monday Morning</a></p>

<p><a href="20020225-pm.html">Monday Afternoon</a></p>

<p><a href="20020226-pm.html">Tuesday Afternoon</a></p>

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

<p><a href="http://www.royal-hotel-casino.com/"><strong>Royal Hotel
Casino</strong></a>, Cannes-Mandelieu, France</p>

<p>605 avenue du G&#35817;ral de Gaulle <br />
06210 Mandelieu la Napoule <br />
T&#35502; : +33 (0)4 92 97 70 00 <br />
Fax : +33 (0)4 93 49 51 50</p>

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

<p>None required.</p>
<hr />

<p><small><span style="font-style: italic"><a
href="mailto:brian_mcbride@hp.com">Brian McBride</a></span>
&lt;brian_mcbride@hp.com&gt; $Id: Overview.html,v 1.21 2002/05/24 09:14:57 bmcbride Exp $</small></p>
</body>
</html>