You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1706 lines
77 KiB
1706 lines
77 KiB
<?xml version="1.0" encoding="utf-8"?><!--*- nxml -*-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
|
"http://www.w3.org/TR/2002/REC-xhtml1-20020801/DTD/xhtml1-transitional.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<head profile="http://www.w3.org/2003/g/data-view">
|
|
<title>Issues List: RDF Data Access Working Group</title>
|
|
<link href="../../../StyleSheets/base.css" rel="stylesheet" type="text/css"
|
|
/>
|
|
<link rel="transformation"
|
|
href="http://www.w3.org/2001/sw/DataAccess/grokIssues.xsl" />
|
|
<link rel="transformation"
|
|
href="http://www.w3.org/2001/sw/DataAccess/pgdata.xsl" />
|
|
<link rel="base" href="http://www.w3.org/2001/sw/DataAccess/issues" />
|
|
<style type="text/css">
|
|
blockquote { border-left: double; padding-left: 1em; font-style: italic; text-align: justify }
|
|
address { text-align: right }
|
|
h3 { border-bottom: solid; padding-bottom: 0.5em }
|
|
.proposal { background: yellow }
|
|
.resolve { background: green; color: white }
|
|
</style>
|
|
</head>
|
|
|
|
<body>
|
|
|
|
<div class="nav">
|
|
<a href="/"><img style="border: 0" src="/Icons/WWW/w3c_home" alt="W3C"
|
|
/></a> *
|
|
<a rel="group" href="./">RDF Data Access Working Group</a>
|
|
</div>
|
|
|
|
<h1>Issues List</h1>
|
|
|
|
<div style="text-align: center">
|
|
nearby: <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/">public-rdf-dawg
|
|
archive</a> * <a
|
|
href="http://lists.w3.org/Archives/Public/www-rdf-rules/">www-rdf-rules</a></div>
|
|
|
|
<p>Issues are accepted by the chair and disposed of by WG decision. An
|
|
issue owner owes the WG a proposal to close the issue (preferably
|
|
including discussion of alternatives).</p>
|
|
|
|
<p>In preparation for <a href="ftf4.html">the Helsinki meeting</a>,
|
|
there is a <a
|
|
href="http://www.w3.org/2002/09/wbs/35463/issues-ftf4/">survey on
|
|
these issues</a>. <span class="proposal">Proposals are marked up in
|
|
this style.</span> <span class="resolve">decisions to close issues are marked up in this style.</span></p>
|
|
|
|
<p><em>in progress: formalized issue list using <a
|
|
href="http://www.w3.org/2003/g/data-view">GRDDL</a>: <a
|
|
href="http://www.w3.org/2000/06/webdata/xslt?xslfile=http%3A%2F%2Fwww.w3.org%2F2003%2F11%2Frdf-in-xhtml-processor&xmlfile=http%3A%2F%2Fwww.w3.org%2F2001%2Fsw%2FDataAccess%2Fissues">live
|
|
GRDDL output</a></em></p>
|
|
|
|
<h2>Open Issues</h2>
|
|
|
|
|
|
|
|
|
|
|
|
<h2>Postponed Issues</h2>
|
|
|
|
<ol>
|
|
<li>
|
|
<a href="#cascadedQueries">cascadedQueries</a> <b>postponed</b>
|
|
</li>
|
|
<li>
|
|
<a href="#accessingCollections">accessingCollections</a> <b>postponed</b>
|
|
</li>
|
|
<li><a href="#serviceDescription">serviceDescription</a> <b>postponed</b></li>
|
|
<li><a href="#xmlAbstractSyntax">xmlAbstractSyntax</a> <b>postponed</b></li>
|
|
<li><a href="#countAggregate">countAggregate</a> <b>postponed</b></li>
|
|
|
|
<li><a href="#update">update</a> <b>postponed</b></li>
|
|
<li><a href="#queryByReference">queryByReference</a> <b>postponed</b></li>
|
|
<li><a href="#owlDisjunction">owlDisjunction</a> <b>postponed</b></li>
|
|
<li><a href="#nameValueForms">nameValueForms</a> <b>postponed</b></li>
|
|
<li><a href="#bnodeRef">bnodeRef</a> <b>postponed</b></li>
|
|
<li><a href="#unescapedXml">unescapedXml</a> <b>postponed</b></li>
|
|
<li><a href="#simplificationAmbiguity">simplificationAmbiguity</a> <b>postponed</b></li>
|
|
</ol>
|
|
|
|
<h2>Closed Issues</h2>
|
|
|
|
<ol>
|
|
<li>
|
|
<a href="#languageProtocolName">languageProtocolName</a> <b>closed</b>
|
|
</li>
|
|
<li>
|
|
<a href="#DESCRIBE">DESCRIBE</a> <b>closed</b>
|
|
</li>
|
|
<li>
|
|
<a href="#consUnboundVars">consUnboundVars</a> <b>closed</b>
|
|
</li>
|
|
<li>
|
|
<a href="#consWithBnodes">consWithBnodes</a> <b>closed</b>
|
|
</li>
|
|
<li>
|
|
<a href="#SOURCE">SOURCE</a> <b>closed *</b>
|
|
</li>
|
|
<li>
|
|
<a href="#unsaid">unsaid</a> <b>closed</b>
|
|
</li>
|
|
<li>
|
|
<a href="#yesNoQueries">yesNoQueries</a> <b>closed</b>
|
|
</li>
|
|
<li>
|
|
<a href="#prefixSyntax">prefixSyntax</a> <b>closed</b>
|
|
</li>
|
|
<li>
|
|
<a href="#disjunction">disjunction</a> <b>closed</b>
|
|
</li>
|
|
<li>
|
|
<a href="#graphSolutionMapping">graphSolutionMapping</a> <b>closed</b>
|
|
</li>
|
|
<li><a href="#useMentionOp">useMentionOp</a> <b>closed</b></li>
|
|
|
|
<li>
|
|
<a href="#protocolRootReferent">protocolRootReferent</a> <b>closed</b>
|
|
</li>
|
|
<li><a href="#fromUnionQuery">fromUnionQuery</a> <b>closed</b></li>
|
|
<li><a href="#resultsMimeType">resultsMimeType</a> <b>closed</b></li>
|
|
<li><a href="#queryMimeType">queryMimeType</a> <b>closed</b></li>
|
|
<!-- <li><a href="#punctuationSyntax">punctuationSyntax</a> <b>closed*</b></li> -->
|
|
<li><a href="#sort">sort</a> <b>closed</b></li>
|
|
<li><a href="#badIRIRef">badIRIRef</a> <b>closed</b></li>
|
|
<li><a href="#valueTesting">valueTesting</a> <b>closed</b></li>
|
|
<li><a href="#wsdlAbstractProtocol">wsdlAbstractProtocol</a> <b>closed</b></li>
|
|
<li><a href="#rdfSemantics">rdfSemantics</a> <b>closed</b></li>
|
|
<li><a href="#syntaxExtensionProtocol">syntaxExtensionProtocol</a> <b>closed</b></li>
|
|
<li><a href="#contradictoryKB">contradictoryKB</a> <b>closed</b></li>
|
|
<li><a href="#punctuationSyntax">punctuationSyntax</a> <b>closed</b></li>
|
|
<li><a href="#formsOfDistinct">formsOfDistinct</a> <b>closed</b></li>
|
|
<li><a href="#nonliteralValueTesting">nonliteralValueTesting</a> <b>closed</b></li>
|
|
<li><a href="#nestedOptionals">nestedOptionals</a> <b>closed</b></li>
|
|
<li><a href="#openWorldValueTesting">openWorldValueTesting</a> <b>closed</b></li>
|
|
<li><a href="#entailmentFramework">entailmentFramework</a> <b>closed</b></li>
|
|
</ol>
|
|
|
|
<p>* indicates outstanding <a href=
|
|
"http://www.w3.org/2004/02/Process-20040205/policies.html#WGArchiveMinorityViews"
|
|
>formal objections</a> regarding the decision to close the issue or to
|
|
adopt relevant requirements or objectives.</p>
|
|
|
|
<p>There is also outstanding dissent not specific to any of the issues above:</p>
|
|
<ul>
|
|
<li>the WG RESOLVED <a href="http://www.w3.org/2001/sw/DataAccess/ftf2#initdn3">2004-07-15</a> to adopt BRQL v1.11 as its strawman query language design,
|
|
over the <b><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0101.html">objection of RobS and JeffP of Network Inference</a></b>.</li>
|
|
<li>Requirement <a href="http://www.w3.org/TR/rdf-dawg-uc/#r3.6">3.6 Optional Match</a> was accepted <a href="http://www.w3.org/2001/sw/DataAccess/ftf2">2004-07-15</a> over the objection of RobS of Network Inference</li>
|
|
</ul>
|
|
|
|
<div>
|
|
<h3 id="languageProtocolName">languageProtocolName</h3>
|
|
<ul>
|
|
<li class="accept">accepted <a href="ftf2#brqlw">2004-07-15 in Carslbad</a></li>
|
|
<li class="resolve">resolved in <a href="http://www.w3.org/2004/12/21-dawg-irc">2004-12-21 meeting</a>: SPARQL Protocol and RDF Query Language</li>
|
|
</ul>
|
|
|
|
<p>earlier working draft was published as SPARQL, without expansion. (other candidates: DARQ, DART, BRIQL, TRIQL, RAQL/RAQP
|
|
SWQL, BRQL, RQL, BARQ,...)</p>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=languageProtocolName&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...languageProtocolName...</a></p>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="cascadedQueries">cascadedQueries</h3>
|
|
|
|
<p>Capability for multiple queries in the same request, cascading the
|
|
bindings (or graph) returned from one query into another... ala
|
|
SELECT-WHERE, SELECT-WHERE; aka composition.</p>
|
|
|
|
<ul>
|
|
<li class="raise">raised <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0037.html">7
|
|
Jul 2004 by JosD</a></li>
|
|
<li class="accept">accepted <a href="ftf2#brqlw">2004-07-15 in Carslbad</a></li>
|
|
<li class="proposal">proposal:
|
|
<a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/0030.html">Successive Bindings, cascaded queries in Algae2</a> Eric Prud'hommeaux 18 Jan 2005 23:28:46</li>
|
|
<li class="postponed">postponed <a href="ftf4.html#itemCascadedQueries">2005-01-20 in Helsinki meeting</a>:
|
|
<blockquote>
|
|
RESOLVED: to postpone cascadedQueries; while federation use cases are
|
|
interesting, the designs don't seem mature and the use cases are not
|
|
urgent; with KendallC abstaining.
|
|
</blockquote>
|
|
</li>
|
|
</ul>
|
|
|
|
<p>Note also: <a rel="comment" href="http://www.w3.org/mid/43C6CD47.7000100@oracle.com">major technical: no subqueries</a></p>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=cascadedQueries&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...cascadedQueries...</a></p>
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="DESCRIBE">DESCRIBE</h3>
|
|
<ul>
|
|
<li class="accept">accepted <a href="ftf2#brqlw">2004-07-15 in Carslbad</a></li>
|
|
<li><a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0144.html">About
|
|
DESCRIBE</a> 20 Jul 2004 by AndyS</li>
|
|
<li>AlbertoR owner as of <a href="ftf3-brs#issues-other">2004-09-16</a></li>
|
|
<li class="proposal"><a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0343.html">DESCRIBE
|
|
- description of a resource</a> proposal of 23 Nov 2004 discharged
|
|
his action as of <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0434.html">2004-12-07</a>;
|
|
drafted in section <a href="http://www.w3.org/2001/sw/DataAccess/rq23/#describe">10.3 Descriptions of Resources</a> of SPARQL QL</li>
|
|
<li class="proposal">
|
|
<blockquote>
|
|
I like this sort of design where this feature as a completely separate
|
|
query language.
|
|
|
|
<address>
|
|
<a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0146.html">Connolly 20 Jul 2004 </a>
|
|
</address>
|
|
</blockquote>
|
|
<p><em>@@listed out of order in order to keep WBS identifiers stable</em></p>
|
|
</li>
|
|
<li class="proposal"><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2005Jan/0014.html">proposal to drop DESCRIBE from SPARQL</a> Dan Brickley Mon, 17 Jan 2005.
|
|
<p>Also:</p>
|
|
<blockquote>
|
|
<p>I think the desired effect could be achieved using standard SPARQL queries
|
|
with some special RDF vocabulary, or maybe ... .</p>
|
|
<p>I think it has NO PLACE
|
|
in the base SPARQL specification</p>
|
|
<address><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2005Apr/0010.html">Klyne, 08 Apr 2005</a>
|
|
</address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="resolve">closed <a href="ftf4.html#item14">2005-01-20 in Helsinki meeting</a> over DanC's objection</li>
|
|
<li><blockquote>
|
|
<p>It all boils down to this: I think that although the functionality of
|
|
DESCRIBE is useful, it does not belong the core functionality of the
|
|
first version of the first W3C RDF Query Language.</p>
|
|
|
|
<a href="http://www.w3.org/mid/43C2BE91.4010408@cwi.nl">2006-01-09T19:50:41Z from Jacco.van.Ossenbruggen</a>
|
|
</blockquote>
|
|
</li>
|
|
<li>in support of DESCRIBE: <a rel="comment" href="http://www.w3.org/mid/EC03DB45-0CF8-4568-93A4-606C980FA794@rauschma.de">Use Case for DESCRIBE</a></li>
|
|
<li>DanC withdrew his objection in a <a href="http://lists.w3.org/Archives/Public/www-archive/2007May/0029.html">4 May 2007</a> message.</li>
|
|
</ul>
|
|
<p>DESCRIBE: What is it?</p>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=DESCRIBE&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...DESCRIBE...</a></p>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="consUnboundVars">consUnboundVars</h3>
|
|
<p>what if construct graph includes unbound variables?</p>
|
|
<ul>
|
|
<li class="accept">issue acknowledged <a href="ftf2#brqlw">2004-07-15 in Carslbad</a></li>
|
|
<li class="proposal">
|
|
<blockquote>
|
|
If a triple template has a variable, and in a query solution, the variable is unbound, then the substitution of this triple template is skipped but other triple templates are still processed for the same solution and any triples from other solutions are included in the result graph. An error or warning may be generated.
|
|
<address>
|
|
section <a href="http://www.w3.org/2001/sw/DataAccess/rq23/#construct">10.2 Constructing an Output Graph</a><br />
|
|
1.162 (aseaborn 06-Jan-05)
|
|
</address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="resolve">closed <a href="ftf4.html#item22">2005-01-20 in Helsinki meeting</a></li>
|
|
|
|
</ul>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="consWithBnodes">consWithBnodes</h3>
|
|
<ul>
|
|
<li>accepted @@when?</li>
|
|
<li>note public comment:
|
|
<blockquote>
|
|
Are bnodes allowed in the Construct clause? If so, that's a lot like
|
|
existentially quantified terms in the consequent of a rule, and we're in
|
|
Horn logic instead of the more conventional datalog.
|
|
<address>
|
|
<a rel="comment" href="http://www.w3.org/mid/E1CVEJ6-0004J0-VR@localhost.localdomain">Sandro Hawke 19 Nov 2004</a></address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="proposal">
|
|
<blockquote>
|
|
<p><em>To be discussed ...</em></p>
|
|
<p>A template can create an RDF graph containing bNodes, indicated by the syntax of a prefixed name with prefix _ and some label for the local name. The labels are scoped to the template for each solution. ...</p>
|
|
<address>
|
|
section <a href="http://www.w3.org/2001/sw/DataAccess/rq23/#construct">10.2 Constructing an Output Graph</a><br />
|
|
1.133 (aseaborn 17-Nov-04)
|
|
</address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="resolve">closed <a href="ftf4.html#item23">2005-01-20 in Helsinki meeting</a></li>
|
|
</ul>
|
|
<p>Need to allow bNodes in constructed graph</p>
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="SOURCE">SOURCE</h3>
|
|
|
|
<p>Allowing query expressions to refer to the source of a triple.</p>
|
|
|
|
<ul>
|
|
<li class="accept">accepted <a href="ftf2#brqlw">2004-07-15 in Carslbad</a></li>
|
|
<li>cf objective <a href="http://www.w3.org/TR/rdf-dawg-uc/#d4.2">4.2 Data Integration and Aggregation</a> accepted <a href="http://www.w3.org/2001/sw/DataAccess/ftf3-brs#obj564">2004-09-16</a> over the <b>objection of Network Inference/Rob Shearer</b>. Also:
|
|
<blockquote>
|
|
<p>I think these should be removed from the basic SPARQL core, since I feel
|
|
they add a fair deal of implementation complexity and an application can
|
|
achieve the same result by submitting multiple queries, possibly to
|
|
different query processors.</p>
|
|
|
|
<p>I also feel it would be premature to standardize an approach to multi-graph
|
|
querying ahead of there being a consensus/standard for something like RDF
|
|
named graphs.</p>
|
|
<address><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2005Apr/0010.html">Klyne 08 Apr 2005</a></address>
|
|
</blockquote>
|
|
</li>
|
|
<li>DaveB accepted ownership in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0224.html">2004-07-29 telcon</a></li>
|
|
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0309.html">a story of log:semantics and log:includes</a> action DanC done 24 Aug 2004</li>
|
|
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0541.html">SOURCE - simple test cases</a> action AndyS done 27 Sep 2004</li>
|
|
<li class="proposal"><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0241.html">SOURCE - Choosing what to query and querying the origin of statements</a> proposal 8 Nov 2004 from Dave Beckett</li>
|
|
<li class="proposal"><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0421.html">Untrusted graphs - examples</a> 07 Dec 2004 Seaborne, Andy and <a href="http://www.w3.org/2001/sw/DataAccess/tests/data/source-named/">tests designed to match</a> and section <a href="http://www.w3.org/2001/sw/DataAccess/rq23/#source">9 Querying the Origin of Statements</a> of v1.66 2005/01/10 17:59:34 intended to match</li>
|
|
<li class="proposal"><blockquote>
|
|
the URI used to identify the triples (ie. bound by
|
|
the SOURCE keyword) is not neccesarily the URI that was resolve to
|
|
retreive the grpah, that may be got by following some predicate from the
|
|
SOURCE URI to the actual URI resolved
|
|
<address>
|
|
<a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/0022.html">Steve Harris 15 Jan 2005</a>
|
|
</address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="resolve">closed <a href="ftf4.html#item06">2005-01-19 in Helsinki meeting</a></li>
|
|
</ul>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=consUnboundVars&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...consUnboundVars...</a></p>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="nestedOptionals">nestedOptionals</h3>
|
|
|
|
<ul>
|
|
<li class="accept">accepted <a href="ftf2#brqlw">2004-07-15 in Carslbad</a></li>
|
|
<li>SteveH owner as of <a href="ftf3-brs#issues-other">2004-09-16 discussion in Bristol</a></li>
|
|
<li class="proposal">section <a href="http://www.w3.org/2001/sw/DataAccess/rq23/#OptionalMatchingNested">5.5 Nested Optional Blocks</a> v 1.165 of 10-Jan-05 gives a design</li>
|
|
<li><p>Nested OPTIONALS; Subqueries? Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=nestedOptionals&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...nestedOptionals...</a></p></li>
|
|
<li class="resolve">closed <a href="ftf5-bos.html#item_02">2005-03-01 in Boston</a></li>
|
|
<li>re-opened <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006AprJun/0185">20 June 2006</a>, as a result of <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006AprJun/0174">comments from FredZ</a> and <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006AprJun/0175.html">subsequent discussion with AndyS</a> and the WG during the 20 June telcon:
|
|
<blockquote>
|
|
I posed the question of how to interpret queries of the form
|
|
{ P1 } UNION {P2} OPTIONAL {P3}.
|
|
I maintained that the first operand of OPTIONAL must be an
|
|
empty pattern, based on BNF rule [20] GraphPattern, which
|
|
shows that an OptionalGraphPattern is necessarily preceded by
|
|
a FilteredBasicGraphPattern, which I took to be the first operand.
|
|
</blockquote>
|
|
</li>
|
|
<li>Search the archives for <a href="http://www.w3.org/Search/Mail/Public/search?keywords=%7B+P1+%7D+UNION+%7B+P2+%7D+OPTIONAL+%7B+P3+%7D&hdr-1-name=subject&hdr-1-query=&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">{ P1 } UNION { P2 } OPTIONAL { P3 }</a>...</li>
|
|
<li class="resolve">closed <a href="http://www.w3.org/2007/03/13-dawg-minutes.html#item03">2006-03-13</a> with reoslution:
|
|
<blockquote>
|
|
PROPOSED that the current algebra of rq25 addresses http://www.w3.org/2001/sw/DataAccess/issues#nestedOptionals
|
|
</blockquote></li>
|
|
</ul>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="unsaid">unsaid</h3>
|
|
|
|
<ul>
|
|
<li class="accept">accepted <a href="ftf2#brqlw">2004-07-15 in Carslbad</a></li>
|
|
<li class="proposal"><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0447.html">UNSAID drafted and mapped to SQL</a> Eric Prud'hommeaux (Friday, 10 December) ... section <a href="http://www.w3.org/2001/sw/DataAccess/rq23/#unsaid">7 More Pattern Matching – Unsaid</a></li>
|
|
<li class="proposal"><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0534.html">Re: UNSAID drafted and mapped to SQL</a> Pat Hayes 18 Dec 2004:
|
|
<blockquote>
|
|
Let me strongly suggest that we do not include UNSAID in SPARQL. ...
|
|
</blockquote>
|
|
|
|
<p>Note a relevant objective:</p>
|
|
|
|
<blockquote>It must be possible to query for the non-existence of one or more triples or triple patterns in the queried graph.
|
|
<address>
|
|
objective <a href="http://www.w3.org/TR/2004/WD-rdf-dawg-uc-20041012/#d4.3">4.3 Non-existent Triples</a> accepted 2004-07-15
|
|
</address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="resolve">closed <a href="ftf4.html#item04">2005-01-19 in Helsinki meeting</a></li>
|
|
</ul>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=unsaid&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...unsaid...</a></p>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="fromUnionQuery">fromUnionQuery</h3>
|
|
|
|
<p>How to refer, in the protocol and/or query language, to data over which to query?</p>
|
|
|
|
<ul>
|
|
<li class="accept">accepted <a href="ftf2#brqlw">2004-07-15 in Carslbad</a> when walking thru <a href="http://www.w3.org/2004/07/08-BRQL/#grammar-table">BRQL syntax</a>, in particular multiple FROM keywords</li>
|
|
<li class="proposal">
|
|
<blockquote>
|
|
Some processors may choose to allow multiple URIs in the FROM clause. These are used to create a single graph by RDF merge. ...
|
|
<address>
|
|
<a href="http://www.w3.org/2001/sw/DataAccess/rq23/#unnamedGraph">8.1 Specifying the Unnamed Graph</a>
|
|
</address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="resolve">in <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0411.html">2005-06-07 meeting</a>:
|
|
<blockquote>
|
|
<p>RESOLVED: to go option (a) without FROM/FROM_NAMED, dataset is
|
|
unconstrained; with FROM/FROM_NAMED, dataset is bounded from below
|
|
by given references.</p>
|
|
<p>SH objects. abstaing: EricP, DaveB</p>
|
|
</blockquote>
|
|
</li>
|
|
<li>In a <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2007AprJun/0038.html">mailing list message on 3 May 2007</a>, SteveH withdrew his objection.</li>
|
|
</ul>
|
|
|
|
<p>Multiple FROM in a request => union query; Scaling issues
|
|
here?</p>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=fromUnionQuery&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...fromUnionQuery...</a></p>
|
|
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="yesNoQueries">yesNoQueries</h3>
|
|
|
|
<ul>
|
|
<li class="accept">accepted <a href="ftf2#brqlw">2004-07-15 in Carslbad</a></li>
|
|
<li>DanC owner as of <a href="ftf3-brs#issues-other">2004-09-16 discussion in Bristol</a></li>
|
|
<li class="proposal">BooleanQueryResult in <a href="http://www.w3.org/2001/sw/DataAccess/proto-wd/">SPARQL protocol</a> v 1.1 2004/12/17.
|
|
<blockquote>
|
|
<pre>
|
|
PREFIX foaf: <http://xmlns.com/foaf/0.1/>
|
|
ASK (?x foaf:name "Alice" )
|
|
</pre>
|
|
<address>
|
|
section <a href="http://www.w3.org/2001/sw/DataAccess/rq23/#ask">10.4 Asking "yes or no" questions</a>
|
|
v1.133 17-Nov-04
|
|
</address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="proposal">
|
|
use SELECT/LIMIT instead (gleaned from WBS comments 19Jan2005)
|
|
</li>
|
|
<li class="resolve">closed <a href="ftf4.html#item11">2005-01-20 in Helsinki meeting</a></li>
|
|
</ul>
|
|
<p>yes or no questions</p>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=yesNoQueries&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...fromUnionQuery...</a></p>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="prefixSyntax">prefixSyntax</h3>
|
|
|
|
<ul>
|
|
<li>accepted @@when?</li>
|
|
<li>KendallC took an action... @@when?</li>
|
|
<li class="proposal">
|
|
<blockquote>
|
|
[1] Query ::= PrefixDecl* ReportFormat PrefixDecl* FromClause? WhereClause?
|
|
<address>
|
|
<a href="http://www.w3.org/2001/sw/DataAccess/rq23/#grammar">A. SPARQL Grammar</a>
|
|
1.140 28-Nov-04
|
|
</address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="proposal">PrefixDecl allowed in only one place (gleaned from WBS comments 29Jan2005)</li>
|
|
<li class="resolve">closed <a href="ftf4.html#item03">2005-01-19 in Helsinki meeting</a></li>
|
|
</ul>
|
|
<p>prefixFirst: <q>Better would be to have the prefixes first, and to
|
|
have the ':' in the prefix to allow the default prefix to be
|
|
defined.</q></p>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=prefixSyntax&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...prefixSyntax...</a></p>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="disjunction">disjunction</h3>
|
|
|
|
<p>Disjunction designs, balancing user needs with
|
|
implementation difficulties (OPTIONAL, etc.)</p>
|
|
|
|
<ol>
|
|
<li class="accept">accepted <a href="ftf3-brs#issues-other">2004-09-16 in Bristol</a></li>
|
|
<li>SteveH owner as of <a href="ftf3-brs#issues-disj">2004-09-17 in Bristol</a></li>
|
|
<li class="proposal"><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0604.html">Proposal to drop disjunction requirement</a> Steve Harris (Thursday, 30 September 2004)
|
|
<p>To wit: <a href="http://www.w3.org/TR/2004/WD-rdf-dawg-uc-20041012/#r3.13">3.13 RDF Graph Pattern Matching - Disjunction</a></p>
|
|
</li>
|
|
<li class="proposal">section <a href="http://www.w3.org/TR/rdf-sparql-query/#alternatives">6 More Pattern Matching – Alternatives</a> is a sketch as of the 12 Oct 2004 WD; <a href="http://www.w3.org/2001/sw/DataAccess/rq23/#alternatives">section 6 of editor's draft</a> has more detail as of ~ Nov 2004</li>
|
|
<li class="resolve">closed <a href="ftf4.html#item24">2005-01-20 in Helsinki meeting</a> over the objection of Dave Beckett, which was that it did not merit
|
|
the implementation cost. Becket later wrote <q>I'd withdraw my personal objection to it</q> in a <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2006Feb/0021">message of 20 Feb 2006</a>, and the University of Bristol withdrew their objection 27 March 2006.</li>
|
|
</ol>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=disjunction&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...disjunction...</a></p>
|
|
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="graphSolutionMapping">graphSolutionMapping</h3>
|
|
|
|
<ul>
|
|
<li class="accept">accepted <a href="ftf3-brs#issues-other">2004-09-16 in Bristol</a></li>
|
|
<li>relevant comment: <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2004Nov/0019">bnodes/existentials in Construct</a> Hawke 19 Nov 2004</li>
|
|
<li class="proposal">
|
|
<blockquote>
|
|
If a graph template is supplied, then the RDF graph is formed by taking each query solution and substituting the variables into the graph template and merging the triples into a single RDF graph.
|
|
|
|
<address>
|
|
section <a href="http://www.w3.org/2001/sw/DataAccess/rq23/#construct">10.2 Constructing an Output Graph</a><br />
|
|
1.162 (aseaborn 06-Jan-05)
|
|
</address>
|
|
</blockquote>
|
|
</li>
|
|
<li class="resolve">closed <a href="ftf4.html#item20">2005-01-20 in Helsinki meeting</a></li>
|
|
</ul>
|
|
<p>number of bindings vs. number of graphs</p>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=graphSolutionMapping&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...graphSolutionMapping...</a></p>
|
|
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="accessingCollections">accessingCollections</h3>
|
|
|
|
<p>Support for collections/containers? or trees? or path regular
|
|
expressions?</p>
|
|
|
|
<ul>
|
|
<li class="accept">accepted in <a href="ftf3-brs#uc-di">2004-09-16
|
|
discussion of content selection based on client profile in
|
|
Bristol</a></li>
|
|
<li>Note that accessing collections can be done by combining SPARQL
|
|
with inference rules, which, by charter, is orthogonal:
|
|
<blockquote>
|
|
<p>The protocol will allow access to a notional RDF graph. This
|
|
may in practice be the virtual graph which would follow from some
|
|
form of inference from a stored graph.</p>
|
|
<cite>section <a
|
|
href="http://www.w3.org/2003/12/swa/dawg-charter#rdfs-owl-queries">2.1
|
|
Specification of RDF Schema/OWL semantics</a> of the
|
|
charter</cite>
|
|
</blockquote>
|
|
</li>
|
|
<li class="postponed">postponed <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/att-0202/22-dawg-minutes.htm#item07">22
|
|
Feb</a>:
|
|
<blockquote>
|
|
RESOLVED: to postpone accessingCollections because
|
|
<ul>
|
|
<li>our not standardizing it doesn't stop anybody from playing</li>
|
|
<li>none of the extant designs seems sufficiently mature</li>
|
|
</ul>
|
|
<p>Clark/UMD, Fukushige/MEI, <em>and 2 others</em> abstaining</p>
|
|
</blockquote>
|
|
</li>
|
|
|
|
<li>see also comments <a rel="comment"
|
|
href="http://www.w3.org/mid/01CF21867FABC44EBFAC57024D472BEB0189261D@XCH-NW-2V2.nw.nos.boeing.com">Traversing
|
|
trees with sparql?</a>, <a rel="comment"
|
|
href="http://www.w3.org/mid/EF72EBD03EAED74C91670141D409ACBB942D1D@bsebe101.NOE.Nokia.com">Barstow/Nokia, esp point 2 on transitive closure</a></li>
|
|
|
|
<li>WG discussion on using inference rules to supplement SPARQL: <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005OctDec/0190.html">Re:
|
|
summary of some cwm/euler implementation experience w.r.t. accessing
|
|
RDF collections</a> 8 Nov 2005</li>
|
|
|
|
<li>WG discussion considering extending SPARQL with graph regular
|
|
expressions: <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005OctDec/0191.html">Transitive
|
|
properties</a> 08 Nov 2005</li>
|
|
|
|
<li>note <a href="http://www.w3.org/News/2005#item155">W3C Launches
|
|
Rule Interchange Format Working Group</a></li>
|
|
|
|
<li>see comments to WG <a rel="comment"
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2007Jan/0001.html">from
|
|
Alkhateeb (Inria)</a> on their research/implementation into <a
|
|
href="http://psparql.inrialpes.fr/">Path SPARQL</a></li>
|
|
|
|
|
|
</ul>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=accessingCollections&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...accessingCollections...</a></p>
|
|
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="protocolRootReferent">protocolRootReferent</h3>
|
|
<ul>
|
|
<li class="accept">accepted in <a href="ftf3-brs#prot43">2004-09-17 meeting in Bristol</a></li>
|
|
<li class="resolve">closed <a href="ftf5-bos.html#item_05">2005-03-01 in Boston</a></li>
|
|
</ul>
|
|
<p>protocol URIs are for services or for document/graph/models?</p>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=protocolRootReferent&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...protocolRootReferent...</a></p>
|
|
|
|
|
|
</div>
|
|
|
|
<div><h3 id="useMentionOp">useMentionOp</h3>
|
|
<p>use/mention issues in regex operators, test result format</p>
|
|
<ul>
|
|
<li class="accept">accepted in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0434.html">2004-12-07 telcon</a>
|
|
</li>
|
|
<li class="resolve">closed <a href="ftf4.html#itemumop">2005-01-19 in Helsinki meeting</a></li>
|
|
</ul>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=useMentionOp&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...useMentionOp...</a></p>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="valueTesting">valueTesting</h3>
|
|
|
|
<p>What functions and operators on integers, strings, values
|
|
and terms to include, and how?</p>
|
|
|
|
<ul>
|
|
<li>requirement <a href="http://www.w3.org/TR/rdf-dawg-uc/#r3.3">3.3 Extensible Value Testing</a> accepted <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0330.html">2004-05-04</a> <!-- brianT's objection was non-technical --></li>
|
|
<li class="accept">issue acknowledged <a href="ftf4.html#itemumop">2005-01-19 in Helsinki meeting</a></li>
|
|
<li>closed <a href="ftf4.html#item26">2005-01-20 in Helsinki meeting</a></li>
|
|
<li>re-opened <a href="ftf5-bos.html#item05">28 Feb in Boston</a>, with EricP as owner</li>
|
|
<li>closed <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0411.html">2005-06-07</a></li>
|
|
<li>re-opened <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0102.html">2005-07-25</a> following
|
|
<a href="http://www.w3.org/mid/431438b0.225536812@smtp.bjoern.hoehrmann.de" rel="comment">Error handling</a> and <a rel="comment" href="http://www.w3.org/mid/431338a1.225522296@smtp.bjoern.hoehrmann.de">language tag issues</a> comments from Bjoern Hoehrmann
|
|
</li>
|
|
<li>see also comment <a rel="comment" href="http://www.w3.org/mid/B27E3100-A366-496F-AC9A-A0E5257C3F80@w3.org">Bug: "A value disjunction that encounters a type error on only one branch will return the result of evaluating the other branch."</a>,
|
|
<a rel="comment" href="http://www.w3.org/mid/F602F938-4DA2-4466-A149-5EFE224BE16D@w3.org">Roman Numeral test</a>, <a rel="comment" href="http://www.w3.org/mid/97C9F8341808C244BFF39DCB6EDD5AD71116EA@server.home.ryan.levering.name">Example Errors 2005-09-02T23:17:29Z from RRLevering</a>
|
|
</li>
|
|
|
|
<li class="resolve">closed in <a href="http://www.w3.org/2005/10/25-dawg-minutes.html#item07">2005-10-25 meeting</a></li>
|
|
|
|
<li class="resolve">ammended in <a href="http://www.w3.org/2006/01/24-dawg-irc#T15-27-46">2006-01-24 teleconference</a> to deal with casing details,
|
|
<a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JanMar/att-0360/07-dawg-minutes.html#item05">2006-02-07 to include comparison of xsd:string</a></li>
|
|
</ul>
|
|
|
|
</div>
|
|
<div>
|
|
<h3 id="punctuationSyntax">punctuationSyntax</h3>
|
|
|
|
<p>What punctuation-level syntax to use in SPARQL queries?</p>
|
|
|
|
<ul>
|
|
<li>c.f. objective <a href="UseCases#d4.1">4.1 Human-friendly Syntax</a></li>
|
|
<li>Accepted 2004-09-16</li>
|
|
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0160">Draft: open issues around '?' use.</a> Dirk-Willem van Gulik 25 Oct 2004</li>
|
|
<li>issue acknowledged <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/0228.html">2005-03-03</a>, following <a href="ftf5-bos.html#item07">discusion in Boston</a>. See also
|
|
<a href="ftf4.html#item18">discussion and decision in Helsinki</a>
|
|
</li>
|
|
<li class="resolve">resolved in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/0287.html">2005-03-08 meeting</a>:
|
|
<blockquote>
|
|
PROPOSED: adopt the <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/thread.html#227">turtle+variables syntax</a>
|
|
<p>ABSTENTIONS: SteveH, AlbertoR</p>
|
|
</blockquote>
|
|
</li>
|
|
<li>re-opened 5 Apr to consider comments requesting reification syntax</li>
|
|
<li class="resolve">resolved in <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0095.html">2005-04-14 meeting</a>
|
|
to not have reification syntax; some details about
|
|
terminating/separating ;s and .s-in-qnames remain.</li>
|
|
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0156.html">Connolly 21 Apr:</a>
|
|
<blockquote>We should probably be more clear about whether this
|
|
is a sparql query or not:
|
|
|
|
<pre>
|
|
SELECT ?x WHERE { <foo###bar> dc:title ?x }.
|
|
</pre>
|
|
<p><strong>REQUEST FOR TESTCASE.</strong></p>
|
|
|
|
<p>I suggest that yes, it's a SPARQL query as defined by the
|
|
grammar, but it's erroneous; i.e. it's in the same category
|
|
as queries that don't obey the limitations on where variables
|
|
can go when using OPTIONAL.</p>
|
|
|
|
<p>So we probably need a new kinda of test case.</p>
|
|
</blockquote>
|
|
<p>See also: <a href="#badIRIRef">issue badIRIRef</a>.</p>
|
|
</li>
|
|
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0169.html">Fine tuning the rq23 grammar</a> 26 Apr 2005</li>
|
|
<li><a href="tests/data/SyntaxFull/manifest.ttl">SyntaxFull tests</a>
|
|
revision 1.2 date: 2005/04/26 19:44:08</li>
|
|
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0239.html">Comments on SPARQL</a> Ashok Malhotra 16 May 2005 suggests a test case for use of reification vocabulary using ordinary SPARQL graph patterns</li>
|
|
|
|
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0262.html">Re: punctuationSyntax</a> Seaborne 27 May 2005</li>
|
|
<li class="resolve">in <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0411.html">2005-06-07 meeting</a>:
|
|
<blockquote>
|
|
<p>RESOLVED: to address punctuationSyntax ala the 70-ish tests in
|
|
<a href="http://www.w3.org/2001/sw/DataAccess/tests/data/SyntaxFull/">SyntaxFull</a></p>
|
|
<p>PatH and EricP abstaining</p>
|
|
</blockquote>
|
|
</li>
|
|
<li>re-opened 26 Sep in light of comments:
|
|
<a rel="comment" href="http://www.w3.org/mid/5D97B907-ADAE-4F78-9168-AD655D5D3887@reading.ac.uk">twinql Retrospective</a>,
|
|
<a href="http://www.w3.org/mid/4890DFFF-426D-4A80-9C03-8B219FE0E0C7@w3.org" rel="comment">Please make sure the grammar is directly machine consumable.</a>
|
|
<a href="http://www.w3.org/mid/43036ab6.399120375@smtp.bjoern.hoehrmann.de" rel="comment">SPARQL: Backslashes in string literals</a>,
|
|
<a rel="comment" href="http://www.w3.org/mid/20050802193708.4AE45CF@mail.informatik.tu-muenchen.de">SPARQL variable names syntax</a>
|
|
</li>
|
|
|
|
<li class="resolve">resolved in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005OctDec/att-0055/11-dawg-minutes.html#item04">2005-10-11 meeting</a></li>
|
|
<li class="resolve">resolved in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005OctDec/att-0229/Nov15.html#item02">2005-11-15 meeting</a> that 0.2 is a decimal rather than a float; also fixed lack of negative numeric literals.</li>
|
|
|
|
<li class="resolve">amended in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JanMar/att-0298/26-dawg-minutes.html#item04">2006-01-26 discussion of issues rdfSemantics, owlDisjunction</a> to exclude bnodes from the predicate position</li>
|
|
|
|
<li>objection: <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2006Mar/0006.html">don't
|
|
use ? and $. Pick one.</a> Harold, 5 March</li>
|
|
|
|
<li>re-opened <a href="http://www.w3.org/2006/08/08-dawg-minutes.html#action02">8 Aug 2006</a> to consider <strong>commas in the SELECT clause</strong>, due to <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006AprJun/0117.html">comments from FredZ</a> and <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006AprJun/0145">AndyS</a>.</li>
|
|
|
|
<li>WG discussion about commas in the SELECT list: <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006OctDec/0077.html">18
|
|
Oct 2006</a></li>
|
|
|
|
<li class="resolve">resolved in <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/att-0005/simon-RDF_DAWG_Weekly_--_2_Jan_2007.html#ActionSummary">2 Jan 2007
|
|
meeting</a> to close this issue with no change</li>
|
|
|
|
</ul>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h3 id="sort">sort</h3>
|
|
|
|
<p>How to express sort orderings on query results?</p>
|
|
<ul>
|
|
<li>design objective <a href="UseCases#d4.11">4.11 Sorting Results</a> accepted 2004-03-15</li>
|
|
<li class="accept">issue acknowledged <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/0358.html">2005-03-18 in a teleconference</a>; AndyS took an action
|
|
</li>
|
|
<li class="resolve">closed in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0248.html">2005-05-19 meeting</a>
|
|
<blockquote>
|
|
RESOLVED: that <a href="http://www.w3.org/2001/sw/DataAccess/rq23/">draft</a> v 1.328 and
|
|
<a href="http://www.w3.org/2001/sw/DataAccess/tests/data/sort/query-sort-1.rq">tests/data/sort/query-sort-1.rq</a>
|
|
address the sort issue
|
|
</blockquote>
|
|
</li>
|
|
<li>re-opened 2005-08-03 following comment <a rel="comment" href="http://www.w3.org/mid/431b3915.225638015@smtp.bjoern.hoehrmann.de">ORDER with IRIs</a>. <em>needs test case</em></li>
|
|
<li class="resolve">resolved in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005OctDec/att-0055/11-dawg-minutes.html#item05">2005-10-11 meeting</a></li>
|
|
|
|
</ul>
|
|
|
|
</div>
|
|
|
|
<div><h3 id="serviceDescription">serviceDescription</h3>
|
|
|
|
<ul>
|
|
<li class="accept">acknowledged <a href="http://www.w3.org/2001/sw/DataAccess/ftf5-bos.html#item_03">2005-03-01 Boston</a>; see also <a href="http://www.w3.org/2001/sw/DataAccess/ftf4.html#item10">Jan discussion in Helsinki</a>
|
|
</li>
|
|
<li class="postponed">postponed
|
|
<a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0248.html">2005-05-19</a>:
|
|
<blockquote>
|
|
whereas the serviceDescription designs aren't maturing in the
|
|
timescale of the current schedule, and implementation experience is
|
|
somewhat thin, RESOLVED to postpone serviceDescriptions
|
|
</blockquote>
|
|
</li>
|
|
</ul>
|
|
|
|
</div>
|
|
<div><h3 id="wsdlAbstractProtocol">wsdlAbstractProtocol</h3>
|
|
|
|
<ul>
|
|
<li class="accept">acknowledged <a href="http://www.w3.org/2001/sw/DataAccess/ftf5-bos.html#item_03">2005-03-01 Boston</a> after adopting a requirement
|
|
</li>
|
|
<li>progress: <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/0382.html">sparql-protocol.wsdl updated</a> Kendall Clark (Monday, 21 March)</li>
|
|
<li>proposal: <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0228.html">protocol draft updated, open issue proposals</a> Kendall Clark (Sat, 14 May 2005)</li>
|
|
<li>closed <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0411.html">2005-06-07</a></li>
|
|
<li>reopened in <a href="http://www.w3.org/2005/10/18-dawg-minutes#item04">18 Oct discussion</a> of WSDL 2.0 spec progress. Note relevant comments:
|
|
<a rel="comment" href="http://www.w3.org/mid/B3E9154E-B4CA-4A7E-863E-4DA33D4F1B0D@w3.org">Note about WSDL2 Binding</a>,
|
|
<a rel="comment" href="http://www.w3.org/mid/1127750143.6446.55.camel@dirk">Protocol Review and Comments</a>, <a rel="comment" href="http://www.w3.org/mid/1127750143.6446.55.camel@dirk">David Wood's comment</a>, <a rel="comment" href="http://www.w3.org/mid/4367C4C7.90803@ldodds.com">HTTP Status Codes for QueryRequestRefused</a>, <a rel="comment" href="http://www.w3.org/mid/4367C67C.6000904@ldodds.com">Query By Reference in SPARQL Protocol</a>
|
|
</li>
|
|
<li class="resolve">closed again in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JanMar/att-0113/12-dawg-minutes.html#item02">2006-01-12 teleconference discussion</a></li>
|
|
</ul>
|
|
|
|
</div>
|
|
<div><h3 id="xmlAbstractSyntax">xmlAbstractSyntax</h3>
|
|
|
|
<ul>
|
|
<li class="accept">acknowledged 2005-03-04 after <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/0330.html">XML serialization of SPARQL</a> and <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JanMar/0414.html">sparqlx</a> threads</li>
|
|
<li>KendallC owner as of <a href="http://www.w3.org/2005/03/29-dawg-minutes.html#item08">29 Mar</a></li>
|
|
<li class="postponed">postponed
|
|
<a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0248.html">2005-05-19</a>:
|
|
<blockquote>
|
|
RESOLVED to postpone xmlAbstractSyntax on the grounds that it seems
|
|
more straightforward to do in a later version</blockquote>
|
|
</li>
|
|
</ul>
|
|
|
|
</div>
|
|
|
|
<div><h3 id="countAggregate">countAggregate</h3>
|
|
|
|
<p>other query languages have counting and other aggregate functions;
|
|
these are complicated in RDF due to open world notions of equality and
|
|
inequality.</p>
|
|
|
|
<ul>
|
|
<li class="accept">accepted in <a href="http://www.w3.org/2005/06/28-dawg-minutes#item10">2005-06-28 telconference discussion</a>, following <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0435.html">comment from Das</a></li>
|
|
|
|
<li class="postponed">postponed in <a href="http://www.w3.org/2005/06/28-dawg-minutes#item10">2005-06-28 telconference discussion</a></li>
|
|
</ul>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=countAggregate&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...countAggregate...</a></p>
|
|
|
|
</div>
|
|
|
|
<div><h3 id="bnodeRef">bnodeRef</h3>
|
|
|
|
<p>Users seem to find it useful to refer to bnodes given by the
|
|
server, though the scope of a bnode is usually one lexical graph.</p>
|
|
|
|
<ul>
|
|
<li class="accept">accepted in <a href="http://www.w3.org/2005/07/12-dawg-minutes#item02">2005-07-12 telconference discussion</a>, following <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2005Jun/0039.html">comment from Alford</a></li>
|
|
|
|
<li class="postponed">postponed in <a href="http://www.w3.org/2005/07/12-dawg-minutes#item02">2005-07-12 telconference discussion</a></li>
|
|
|
|
<li>reopened on 30 August, based on <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0191.html">comments raised by BijanP</a>:
|
|
|
|
<p>What is the scope of bnodes through UNION and other algebraic options?</p>
|
|
|
|
<blockquote>I suspect that the current "understanding" is query scoped BNodes.
|
|
But I don't see where it's specified. (Pointer welcome.) It's worht
|
|
considering table scoping. While less expressive (misses some
|
|
coreferences) it is arguably simpler.</blockquote>
|
|
</li>
|
|
|
|
<li class="resolve">The re-opened issue was closed with a decision in the <a href="http://www.w3.org/2007/03/13-dawg-minutes.html#item03">2007-03-13 teleconference</a>:
|
|
<blockquote>
|
|
PROPOSED that the current treatment of bnode labels in rq25 addresses http://www.w3.org/2001/sw/DataAccess/issues#bnodeRef
|
|
</blockquote>
|
|
</li>
|
|
<li class="postponed">However, the original bnodeRef issue involving reusing blank nodes from results to subsequent queries remains <em>postponed</em>.</li>
|
|
</ul>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=bnodeRef&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...bnodeRef...</a></p>
|
|
|
|
</div>
|
|
|
|
<div><h3 id="unescapedXml">unescapedXml</h3>
|
|
|
|
<p>Should the SPARQL Query Results XML Format allow XML literals to be returned unescaped
|
|
within a <tt><binding></tt> element?</p>
|
|
|
|
<ul>
|
|
<li>raised by commenter Stu Baurmann in a <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2007Aug/0005.html">message on 2 Aug 2007</a>.</li>
|
|
<li>discussed on the working group list in a <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JulSep/0160.html">Sep 2007 thread</a>, where the issue received some support and some technical concerns.</li>
|
|
<li class="accept">accepted in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JulSep/0172.html">2007-09-25 teleconference</a>, where it was immediately
|
|
<li class="postponed">postponed</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div><h3 id="simplificationAmbiguity">simplificationAmbiguity</h3>
|
|
|
|
<ul>
|
|
<li>raised by Working Group member Andy Seaborne in a <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JulSep/0178.html">26 Sep 2007 message</a> on the
|
|
Working Group mailing list</li>
|
|
<li>the Chair sought advice from implementors that indicated that implementators were split both in current behavior
|
|
and desired behavior</li>
|
|
<li class="postponed">in lieu of schedule concerns, the corner-case nature of the ambiguity, and the lack of consensus, noted as an acknowledged ambiguity and
|
|
postponed in a <a href="http://www.w3.org/2007/10/09-dawg-minutes.html#item04">09 Oct 2007 teleconference</a></li>
|
|
<li>added the following text to the specification:
|
|
<blockquote>
|
|
<div class="wgNote">
|
|
|
|
<p >The working group notes that the point at the simplification step is applied leads to ambiguous transformation
|
|
of queries involving a doubly nested filter and pattern in an optional:</p>
|
|
|
|
<pre><code>OPTIONAL { { ... FILTER ( ... ?x ... ) } }.</code>.</pre>
|
|
<p>This is illustrated by two non-normative test cases:</p>
|
|
<ul>
|
|
<li><p><a href="http://www.w3.org/2001/sw/DataAccess/tests/data-r2/optional-filter/manifest#dawg-optional-filter-005-not-simplified">
|
|
Simplification applied at the end</a> or not at all.</p></li>
|
|
|
|
<li><p><a href="http://www.w3.org/2001/sw/DataAccess/tests/data-r2/optional-filter/manifest#dawg-optional-filter-005-simplified">
|
|
Simplification applied during step 4</a>.</p>
|
|
</li>
|
|
|
|
</ul>
|
|
|
|
|
|
</div>
|
|
|
|
</blockquote>
|
|
</ul>
|
|
|
|
|
|
<div><h3 id="queryMimeType">queryMimeType</h3>
|
|
|
|
<p>A <a href="http://www.w3.org/2001/tag/2002/0129-mime">TAG
|
|
finding</a> says <q>W3C Working Groups engaged in defining a language
|
|
SHOULD arrange for the registration of an Internet Media Type for that
|
|
language.</q> DAWG should choose an Internet Media Type for SPARQL
|
|
queries or explain why not.</p>
|
|
|
|
<ul>
|
|
<li>raised in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2004Jul/0001.html">13 Jul 2004 msg from Bjoern Hoehrmann</a></li>
|
|
<li class="accept">acknowledged 2005-07-25, following <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2005Jul/0035.html">22 Jul 2005 last call comment</a></li>
|
|
<li>EricP took an action <a
|
|
href="http://www.w3.org/2005/07/26-dawg-minutes">26 July</a> to
|
|
integrate <a
|
|
href="http://www.w3.org/2001/sw/DataAccess/rq23/mime.txt">a
|
|
proposal</a> </li>
|
|
<li class="resolve">closed in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/att-0320/Aug30.html#item08">2005-08-30 meeting</a></li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div><h3 id="resultsMimeType">resultsMimeType</h3>
|
|
|
|
<p>A <a href="http://www.w3.org/2001/tag/2002/0129-mime">TAG
|
|
finding</a> says <q>W3C Working Groups engaged in defining a language
|
|
SHOULD arrange for the registration of an Internet Media Type for that
|
|
language.</q> DAWG should choose an Internet Media Type for SPARQL
|
|
results or explain why not.</p>
|
|
|
|
<ul>
|
|
<li class="accept">acknowledged 2005-07-25 following
|
|
<a rel="comment" href="http://www.w3.org/mid/431738d8.225577640@smtp.bjoern.hoehrmann.de">External storage of queries</a> comment</li>
|
|
<li class="resolve">resolved in <a href="http://www.w3.org/2005/07/26-dawg-minutes#item02">2005-07-26 telcon discussion</a></li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div><h3 id="badIRIRef">badIRIRef</h3>
|
|
|
|
<p>What to say about queries like <tt>SELECT ?x WHERE { <foo###bar> dc:title ?x }</tt>?</p>
|
|
|
|
<ul>
|
|
<li class="accept">acknowledged 2005-07-25 after comment <a rel="comment"
|
|
href="http://www.w3.org/mid/431838ee.225599421@smtp.bjoern.hoehrmann.de">QuotedIRIref
|
|
too lax</a> and <a rel="comment"
|
|
href="http://www.w3.org/mid/431638d0.225569265@smtp.bjoern.hoehrmann.de">IRIs
|
|
vs RDF URI References</a>; see also earlier discussion <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0156">URI/IRI
|
|
concrete and abstract syntax</a></li>
|
|
<li class="resolve">resolved in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005OctDec/att-0055/11-dawg-minutes.html#item03">2005-10-11 meeting</a></li></ul>
|
|
</div>
|
|
|
|
<div><h3 id="rdfSemantics">rdfSemantics</h3>
|
|
|
|
<p>should queries of non-<a
|
|
href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210/#deflean">lean</a>
|
|
and lean graphs that entail each other give the same answers? Any
|
|
practical advice about queries over infinite graph such as all the RDF
|
|
axiomatic triples?</p>
|
|
|
|
<ul>
|
|
<li>cf <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0330.html">2 Sep 2005 from Enrico Franconi</a>, with reference to <a href="http://www.inf.unibz.it/krdb/w3c/sparql-notes-fub.html">Notes on SPARQL Query Language for RDF</a></li>
|
|
|
|
<li>see comments <a
|
|
href="http://www.w3.org/mid/1126298371.4430.308.camel@dirk"
|
|
rel="comment">[Fwd: Comments on SPARQL] (entailment, soundness,
|
|
completeness)</a>, <a href=
|
|
"http://www.w3.org/mid/20050907.212659.48908953.pfps@research.bell-labs.com"
|
|
rel="comment">2005-09-08T01:26:59Z from pfps</a>
|
|
<a rel="comment" href="http://www.w3.org/mid/20050918.110248.43269866.pfps@research.bell-labs.com">2005-09-18T15:02:48Z from pfps</a>
|
|
, <a href=
|
|
"http://www.w3.org/mid/EF72EBD03EAED74C91670141D409ACBB942D1D@bsebe101.NOE.Nokia.com" rel="comment">2005-09-01T17:12:32Z
|
|
from Art.Barstow</a>, <a rel="comment" href="http://www.w3.org/mid/19A11794-047B-4AFF-93B6-1E4ED98C1F10@softwarememetics.com">2005-11-05T12:27:19Z from dwood</a>,
|
|
<a rel="comment" href='http://www.w3.org/mid/OFC99B9CA9.34EA98A2-ONC12570A8.003B7029-C12570A8.0040C484@philips.com'>2005-10-28T11:45:37Z from herman.ter.horst</a></li>
|
|
|
|
<li class="resolve">closed in <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JanMar/att-0298/26-dawg-minutes.html#item04">2006-01-26
|
|
meeting</a> over the objection of PatH, which was clarified <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JanMar/att-0400/14-dawg-minutes.html">14
|
|
Feb</a>: <q>I can see that the definition of BGP' works as stated, but
|
|
I think it's too complex.</q></li>
|
|
<li>outstanding formal objection: <a href="http://www.w3.org/mid/20060222.185654.133907622.pfps@research.bell-labs.com">comments on Section 1 and Section 2 of SPARQL Query Language for RDF</a> Peter F. Patel-Schneider 22 Feb. marked [needstest]</li>
|
|
<li>PatH withdrew his objection to this issue in a <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2007AprJun/0020.html">17 Apr 2007 mailing list message</a>.</li>
|
|
</ul>
|
|
|
|
<blockquote style="text-align: left">
|
|
<p><em>some notes by DanC in preparation for 18 Oct telcon, based on <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005OctDec/0017.html">4 Oct discussion</a>:</em>
|
|
</p>
|
|
|
|
<table border="1">
|
|
<tr><th>proposal:</th><th>LC design</th><th>redundancy optional</th><th>parameterized entailment</th></tr>
|
|
|
|
<tr><th>query options</th>
|
|
<td>dataset</td><td>dataset</td><td>dataset</td>
|
|
</tr>
|
|
<tr><th>service options</th>
|
|
<td>service may support any dataset(s) it chooses,
|
|
by loading from the web, by inference, etc;
|
|
must fail if a sepecific dataset is requested
|
|
and not supported</td>
|
|
<td>(same as LC)</td>
|
|
<td>service may support any dataset it chooses,
|
|
and in any entailment mode it chooses.
|
|
Entailment modes include rdf simple entailment,
|
|
abstract syntax entailment, RDFS entailment,
|
|
etc. (e.g. OWL DL entailment, OWL full entailment)
|
|
</td>
|
|
</tr>
|
|
|
|
<tr><th>use case: results of
|
|
querying equivalent graph should be equivalent (<a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0430.html">14 Sep</a>)</th>
|
|
<td>No</td>
|
|
<td>yes, though clients need to be prepared to ignore redundancy in answers</td>
|
|
<td>yes, though clients need to be sure they're talking to a SPARQL service that does the right kind of entailment</td>
|
|
</tr>
|
|
<tr>
|
|
<th>use case: Building a Graph
|
|
(<a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0430.html">14 Sep</a>)</th>
|
|
<td>yes</td>
|
|
<td>no; a service is never obliged to return redundant solutions</td>
|
|
<td>yes; a service that advertises "abstract syntax" entailment gives the desired answer</td>
|
|
</tr>
|
|
|
|
<tr><th>spec impact</th>
|
|
<td>none</td>
|
|
<td>change "subgraph" to "rdf simple entailment";
|
|
allow redundant bnode answers (not clear how this
|
|
interacts with optional etc. though the fact that
|
|
the tests already work this way suggests
|
|
it doesn't)</td>
|
|
<td>change "subgraph" to "appropriate entailment";
|
|
define abstract syntax entailment and choose a URI
|
|
for it; chose a URI to rdf simple entailment;
|
|
perhaps standardize URIs for RDFS, OWL-DL, OWL-Full
|
|
entailment</td>
|
|
</tr>
|
|
|
|
<tr><th>test impact</th>
|
|
<td>tests with sorted results are OK; test
|
|
with unsorted results also need indexes or other
|
|
nonces that distinguish otherwise-redundant results</td>
|
|
<td>none; the tests already work this way</td>
|
|
<td>add entailment parameter to manifests;
|
|
add tests for rdf simple entailment vs
|
|
abstract syntax entailment vs RDFS entailment
|
|
(plus tests for interactions with optional etc.?)</td>
|
|
</tr>
|
|
|
|
<tr><th>implementation experience</th>
|
|
<td>several service implementations (ARQ, librdf, 3store, ...)</td>
|
|
<td>all service implementations of LC spec (ARQ, librdf, 2store, ...) plus any implementations that use lean graphs (e.g. cwm)
|
|
</td>
|
|
<td>librdf, ARQ support "abstract syntax" entailment;
|
|
cwm supports rdf-simple entailment. I gather 3store
|
|
supports RDFS entailment, or something close (hmm... how
|
|
does this interact with the GRAPH stuff?)</td>
|
|
</tr>
|
|
<tr><td>support</td>
|
|
<td>WG, as of <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0412.html">14 Jun</a></td>
|
|
<td>?</td>
|
|
<td>bparsia@isr.umd.edu, franconi@inf.unibz.it, ...?</td>
|
|
</tr>
|
|
<tr><td>opposition</td>
|
|
<td><a href="http://www.w3.org/mid/20050907.212659.48908953.pfps@research.bell-labs.com">pfps</a>, ...?</td>
|
|
<td>?</td>
|
|
<td>?</td>
|
|
</tr>
|
|
|
|
</table>
|
|
|
|
|
|
</blockquote>
|
|
</div>
|
|
|
|
<div><h3 id="owlDisjunction">owlDisjunction</h3>
|
|
|
|
<p>The worker example in <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0069">Enrico's
|
|
msg from July 2004</a> evidently doesn't work well with SPARQL as of
|
|
the 21 July 2005 LCWD. Are there mature designs that work better? At a
|
|
minimum, we should be explicit that we don't handle this. Note that
|
|
this issue seems to interact with <a
|
|
href="http://www.w3.org/2003/12/swa/dawg-charter#rdfs-owl-queries">section
|
|
2.1 Specification of RDF Schema/OWL semantics of the DAWG charter</a>.
|
|
</p>
|
|
<ul>
|
|
<li>acknowledged 9 Sep 2005. see comments <a href=
|
|
"http://www.w3.org/mid/EF72EBD03EAED74C91670141D409ACBB942D1D@bsebe101.NOE.Nokia.com" rel="comment">2005-09-01T17:12:32Z
|
|
from Art.Barstow</a>, <a
|
|
href="http://www.w3.org/mid/1126298371.4430.308.camel@dirk"
|
|
rel="comment">[Fwd: Comments on SPARQL] (entailment, soundness,
|
|
completeness)</a>
|
|
</li>
|
|
<li>postponed in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JanMar/att-0298/26-dawg-minutes.html#item04">2006-01-26 meeting</a></li>
|
|
</ul>
|
|
|
|
</div>
|
|
|
|
<div><h2 id="update">update</h2>
|
|
<p>Add update/write/insert operations to SPARQL protocol?</p>
|
|
|
|
<ul>
|
|
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2005Mar/0031.html">comment 19 Mar 2005 from Ayers</a></li>
|
|
<li>see <a href="http://www.w3.org/2001/sw/DataAccess/ftf5-bos.html#item_09">discussion 1 Mar 2005 in Boston</a></li>
|
|
<li>postponed <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2005OctDec/att-0384/20-dawg-minutes.html">2005-12-20</a></li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div><h3 id="nameValueForms">nameValueForms</h3>
|
|
<p>Connect/adapts SPARQL protocol to ?name=value HTML form syntax/protocol?</p>
|
|
|
|
<ul>
|
|
<li>See <a href="http://swig.xmlhack.com/2005/10/05/2005-10-05.html#1128524113.602537">SemWeb IG discussion 2005-10-05</a></li>
|
|
<li>postponed <a href="http://www.w3.org/2006/03/28-dawg-minutes.html#item03">2006-03-28</a></li>
|
|
</ul>
|
|
|
|
</div>
|
|
|
|
<div><h3 id="queryByReference">queryByReference</h3>
|
|
|
|
|
|
<ul>
|
|
<li class="accept">accepted in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JanMar/att-0042/05-01-minutes.html#item02">2005-01-06 teleconference discussion</a> of <a href="#wsdlAbstractProtocol">wsdlAbstractProtocol</a>, following <a rel="comment" href="http://www.w3.org/mid/4367C67C.6000904@ldodds.com">comment from Dodds</a></li>
|
|
|
|
<li class="postponed">postponed 2005-01-06</li>
|
|
</ul>
|
|
|
|
<p>Search WG mail archives for <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=queryByReference&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&resultsperpage=20&sortby=date&index-grp=Public__FULL&index-type=t&type-index=public-rdf-dawg">Subject: ...queryByReference...</a></p>
|
|
|
|
</div>
|
|
|
|
<div><h3 id="syntaxExtensionProtocol">syntaxExtensionProtocol</h3>
|
|
|
|
<p>How does the protocol handle syntax extensions?</p>
|
|
|
|
<ul>
|
|
<li class="accept">acknowledged 2006-02-14
|
|
noting <a href="http://www.w3.org/mid/431438b0.225536812@smtp.bjoern.hoehrmann.de">comment from BH</a> and noting <a href="http://www.w3.org/2005/08/16-dawg-minutes#item04">2005-08-16 decision</a></li>
|
|
<li class="resolve">resolved in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JanMar/att-0400/14-dawg-minutes.html#item04">2006-02-14 meeting</a></li></ul>
|
|
</div>
|
|
|
|
<div><h3 id="contradictoryKB">contradictoryKB</h3>
|
|
|
|
<p>What are the answers to a contradictory KB?</p>
|
|
|
|
<p>Resolved:</p>
|
|
|
|
<blockquote>PROPOSED: [[Logical entailment may result in inconsistent RDF graphs. For example, "-1"^^xsd:positiveInteger is inconsistent with respect to D-entailment [INFORMATIVE]. The result of queries on an inconsistent graph is outside this specification.]] With the proviso that this ought not be interpreted as precluding the possibility of returning errors.</blockquote>
|
|
|
|
<ul>
|
|
<li><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006OctDec/att-0012/19-dawg-minutes.html">resolved on 19 Sept 2006</a></li>
|
|
<li>opened 30 August, based on <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0119.html">comments raised by BijanP</a></li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div><h3 id="formsOfDistinct">formsOfDistinct</h3>
|
|
|
|
<p><strike>What form of distinct do we want to support and which syntax to signal them?</strike> What is the notion of distinctness for RDF literals?</p>
|
|
|
|
<ul>
|
|
<li>opened 30 August, based on <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0092.html">comments raised by BijanP</a></li>
|
|
<li>See a thread that contains <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0151.html">some explorations of the design space</a></li>
|
|
<li class="resolve"><a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006OctDec/att-0012/19-dawg-minutes.html">resolved 19 September</a> (with University of Manchester abstaining) to support term distinctness for URIs and bnodes</li>
|
|
<li class="resolve">resolved <a
|
|
href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006OctDec/att-0018/03-dawg-minutes.html#item07">3
|
|
Oct 2006</a> with BijanP/UManchester abstaining
|
|
<blockquote>
|
|
RESOLUTION: DISTINCTness depends of the surface form of the literal (term distinct)
|
|
</blockquote>
|
|
</li>
|
|
</ul>
|
|
|
|
</div>
|
|
|
|
<div><h3 id="nonliteralValueTesting">nonliteralValueTesting</h3>
|
|
|
|
<p>Do we want to support non-literal data value testing?</p>
|
|
|
|
<ul>
|
|
<li>opened 30 August, based on <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0121.html">comments raised by BijanP</a></li>
|
|
<li class="resolve">closed <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006OctDec/att-0018/03-dawg-minutes.html#item01">3 Oct 2006</a>, based on resolution in <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/att-0241/01-part">12 Sep 2006 telecon decision</a>:
|
|
<blockquote>
|
|
PROPOSAL: To restrict value testing to literals.
|
|
</blockquote>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div><h3 id="openWorldValueTesting">openWorldValueTesting</h3>
|
|
<p>How does open world assumption interact with value testing?</p>
|
|
<ul>
|
|
<li>opened 30 August, based on <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0180.html">test cases from AndyS</a></li>
|
|
<li class="resolve">closed <a href="http://www.w3.org/2007/03/13-dawg-minutes.html#item03">2007-03-13</a> with AndyS and patH abstaining with resolution:
|
|
<blockquote>
|
|
PROPOSED that the text in 11.3.1 Operator Extensibility in rq25 addresses http://www.w3.org/2001/sw/DataAccess/issues#openWorldValueTesting
|
|
</blockquote>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div><h3 id="entailmentFramework">entailmentFramework</h3>
|
|
<p>I'm collecting all the issues related to entailment and SPARQL here till either a theme emerges or they get broken into separate issues.</p>
|
|
<ul>
|
|
<li>Neatly summarized by FredZ <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0264.html">here</a><br />
|
|
<a href="http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0048.html">FredZ's request</a> re: entailment framework and bnode scope</li>
|
|
<li>others that are related here but lumped under separate heads above...</li>
|
|
<li class="resolve">closed <a href="http://www.w3.org/2007/03/20-dawg-minutes.html">2007-03-20</a> with resolution:
|
|
<blockquote>
|
|
PROPOSED: that version 1.59 of rq25 addresses and closes http://www.w3.org/2001/sw/DataAccess/issues#entailmentFramework
|
|
</blockquote>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
|
|
|
|
<h2 id="changes">Change Log</h2>
|
|
<pre><!-- log goes on the next line -->
|
|
$Log: issues.html,v $
|
|
Revision 1.156 2007/10/23 15:28:27 lfeigenb
|
|
typo fix
|
|
|
|
Revision 1.155 2007/10/13 08:26:37 lfeigenb
|
|
slight update to simplificationAmbiguity
|
|
|
|
Revision 1.154 2007/10/13 08:23:57 lfeigenb
|
|
updated issues list with simplificationAmbiguity
|
|
|
|
Revision 1.153 2007/10/01 00:36:54 lfeigenb
|
|
added and postponed unescapedXml issue
|
|
|
|
Revision 1.152 2007/05/05 17:30:04 lfeigenb
|
|
DanC withdraws DESCRIBE objection
|
|
|
|
Revision 1.151 2007/05/03 13:34:06 lfeigenb
|
|
SteveH withdraws objection to fromUnionQuery
|
|
|
|
Revision 1.150 2007/04/17 20:04:05 lfeigenb
|
|
PatH withdraws objection to rdfSemantics resolution
|
|
|
|
Revision 1.149 2007/04/10 15:17:05 eric
|
|
~ validated
|
|
|
|
Revision 1.148 2007/03/20 23:06:55 lfeigenb
|
|
closed entailmentFramework issue
|
|
|
|
Revision 1.147 2007/03/13 22:51:08 lfeigenb
|
|
Closed nestedOptionals and openWorldValueTesting.
|
|
|
|
Closed re-opened bnodeRef issue and marked original bnodeRef issue as postponed.
|
|
|
|
Revision 1.146 2007/02/26 00:16:59 lfeigenb
|
|
closed nonliteralValueTesting
|
|
|
|
Revision 1.145 2007/01/07 19:59:12 lfeigenb
|
|
|
|
Closed punctuationSyntax issue (also notes on additional discussion).
|
|
Closed formsOfDistinct issue.
|
|
Noted comments regarding accessingCollections issue.
|
|
|
|
Revision 1.144 2006/10/02 16:53:46 eric
|
|
commited per KendallC's request
|
|
- closed <a href="#contradictoryKB">contradictoryKB</a>
|
|
+ opend <a href="#entailmentFramework">entailmentFramework</a>
|
|
|
|
Revision 1.143 2006/08/29 14:28:10 kclark
|
|
Reopened: bnodeRef, punctuationSyntax, nestedOptionals
|
|
Opened: formsOfDistinct, contradictoryKB, nonliteralValueTesting, openWorldValueTesting
|
|
|
|
Revision 1.142 2006/05/11 14:54:58 connolly
|
|
note that 26 Jan decision on rdfSemantics impacts punctuationSyntax too
|
|
(per my action from 9 May)
|
|
|
|
Revision 1.141 2006/04/06 20:12:11 connolly
|
|
note PFPS's comments of 22 Feb and formal objection
|
|
|
|
Revision 1.140 2006/04/04 16:03:33 connolly
|
|
Network Inference withdraws objection on result limits
|
|
in a message of Fri, 31 Mar 2006 18:04:07 -0800
|
|
|
|
Revision 1.139 2006/03/29 17:26:30 connolly
|
|
h3, not h2, for nameValueForms
|
|
|
|
Revision 1.138 2006/03/29 17:25:07 connolly
|
|
nameValueForms postponed markup fix
|
|
|
|
Revision 1.137 2006/03/29 17:21:45 connolly
|
|
nameValueForms is postponed
|
|
|
|
Revision 1.136 2006/03/27 14:08:37 connolly
|
|
objection to disjuction withdrawn
|
|
|
|
Revision 1.135 2006/03/21 23:58:18 connolly
|
|
Hays's objection clarified
|
|
|
|
Revision 1.134 2006/03/20 23:09:12 connolly
|
|
note Beckett on disjunction
|
|
|
|
Revision 1.133 2006/03/20 21:44:50 connolly
|
|
note Harold's dissent on punctuationSyntax
|
|
|
|
Revision 1.132 2006/02/20 15:21:46 connolly
|
|
syntaxExtensionProtocol closed
|
|
|
|
Revision 1.131 2006/02/18 04:40:30 connolly
|
|
lifted more of DaveB's objection on disjunction from minutes to issues list
|
|
|
|
Revision 1.130 2006/02/17 22:15:19 connolly
|
|
fill in valueTesting decision record
|
|
|
|
Revision 1.129 2006/02/13 22:33:59 connolly
|
|
re-reading records, I see RobS didn't object to subgraph results; he abstained
|
|
|
|
Revision 1.128 2006/02/13 14:38:07 connolly
|
|
cite record of postponing owlDisjunction
|
|
|
|
Revision 1.127 2006/02/10 21:25:04 connolly
|
|
connect ter Horst's comments to rdfSemantics
|
|
|
|
Revision 1.126 2006/02/07 03:31:24 connolly
|
|
issue closure date markup
|
|
|
|
Revision 1.125 2006/02/06 23:59:21 connolly
|
|
rel for link to group for foaf:homepage connection
|
|
|
|
Revision 1.124 2006/02/06 22:40:12 connolly
|
|
rdfSemantics was closed 26 Jan
|
|
|
|
Revision 1.123 2006/01/25 23:46:43 connolly
|
|
wsdlAbstractProtocol, valueTesting closed
|
|
|
|
Revision 1.122 2006/01/25 16:17:02 connolly
|
|
note "no subqueries" comment under a postponed issue
|
|
|
|
Revision 1.121 2006/01/25 15:31:21 connolly
|
|
markup fix
|
|
|
|
Revision 1.120 2006/01/25 15:29:38 connolly
|
|
note comment in support of describe
|
|
|
|
Revision 1.119 2006/01/11 18:08:25 connolly
|
|
note Jacco's objection to issue DESCRIBE
|
|
|
|
Revision 1.118 2006/01/09 19:17:42 connolly
|
|
added queryByReference postponed issue
|
|
|
|
Revision 1.117 2006/01/04 16:15:54 connolly
|
|
update is postponed
|
|
connected more comments to issues
|
|
|
|
Revision 1.116 2005/12/12 21:16:47 connolly
|
|
make a couple issues explicit: update, nameValueForms
|
|
|
|
Revision 1.115 2005/12/12 21:09:31 connolly
|
|
valueTesting is open again
|
|
|
|
Revision 1.114 2005/12/12 20:55:14 connolly
|
|
note punctuationSyntax ammended
|
|
|
|
Revision 1.113 2005/11/09 15:30:05 connolly
|
|
updated/expanded accessingCollections
|
|
|
|
Revision 1.112 2005/11/05 21:07:43 connolly
|
|
put closed markers in the right place
|
|
|
|
Revision 1.111 2005/11/05 21:05:32 connolly
|
|
wsdl is open; valueTesting is closed
|
|
|
|
Revision 1.110 2005/10/18 13:38:57 connolly
|
|
s/steve's system/3store/g
|
|
|
|
Revision 1.109 2005/10/17 19:10:54 connolly
|
|
badIRIRef closed
|
|
|
|
Revision 1.108 2005/10/17 19:09:32 connolly
|
|
sort closed
|
|
|
|
Revision 1.107 2005/10/17 19:06:52 connolly
|
|
punctuationSyntax is closed
|
|
|
|
Revision 1.106 2005/10/17 18:45:18 connolly
|
|
text align
|
|
|
|
Revision 1.105 2005/10/17 18:44:41 connolly
|
|
don't suggest there's no other opposition to LC design
|
|
|
|
Revision 1.104 2005/10/17 18:43:51 connolly
|
|
more on implementation experience
|
|
|
|
Revision 1.103 2005/10/17 18:34:54 connolly
|
|
table border
|
|
|
|
Revision 1.102 2005/10/17 18:31:28 connolly
|
|
collecting thoughts on rdfSemantics
|
|
|
|
Revision 1.101 2005/09/27 14:13:11 connolly
|
|
connected issues#punctuationSyntax to some comments; added some implicit refs
|
|
|
|
Revision 1.100 2005/09/22 12:36:26 connolly
|
|
added doctype
|
|
|
|
Revision 1.99 2005/09/09 23:07:19 connolly
|
|
added issues rdfSemantics and owlDisjunction in light of recent comments
|
|
|
|
Revision 1.98 2005/09/05 14:45:11 connolly
|
|
issue queryMimeType closed last week
|
|
|
|
Revision 1.97 2005/08/03 23:04:25 connolly
|
|
- reopened sort; needs IRI sort test
|
|
- added rel="comment" to connect issues to comments
|
|
- connected a few more comments to issues
|
|
|
|
Revision 1.96 2005/08/01 17:56:09 connolly
|
|
resultsMimeType is closed
|
|
|
|
Revision 1.95 2005/08/01 17:21:24 connolly
|
|
connect language tag comment to valueTesting
|
|
|
|
Revision 1.94 2005/08/01 17:13:22 connolly
|
|
IRIs vs RDF URI References is also relevant to badIRIRef
|
|
|
|
Revision 1.93 2005/08/01 16:21:10 connolly
|
|
progress on queryMimeType
|
|
|
|
Revision 1.92 2005/07/25 15:38:26 connolly
|
|
re-opened valueTesting
|
|
added badIRIRef
|
|
|
|
Revision 1.91 2005/07/25 14:49:20 connolly
|
|
fixed resultsMimeType id
|
|
|
|
Revision 1.90 2005/07/25 14:07:00 connolly
|
|
new issues queryMimeType and resultsMimeType
|
|
|
|
Revision 1.89 2005/07/25 13:26:24 connolly
|
|
fg color of resolved
|
|
|
|
Revision 1.88 2005/07/19 15:10:40 connolly
|
|
search bnodeRef
|
|
|
|
Revision 1.87 2005/07/12 16:24:04 connolly
|
|
oops... bnodeRef in the TOC too
|
|
|
|
Revision 1.86 2005/07/12 16:23:33 connolly
|
|
added, postponed countAggregate and bnodeRef issues
|
|
|
|
Revision 1.85 2005/06/24 18:34:46 connolly
|
|
- noted resolutions to fromUnionQuery, punctuationSyntax,
|
|
valueTesting, and wsdlAbstractProtocol from 7 Jun;
|
|
- elaborated fromUnionQuery resolution a bit, including SH's objection
|
|
- removed class="owner" where the relevant actions are done
|
|
- added missing class="accept" a few times
|
|
|
|
Revision 1.84 2005/06/07 19:32:30 connolly
|
|
amp/lt
|
|
|
|
Revision 1.83 2005/06/07 19:31:55 connolly
|
|
excerpt more re ## testcase
|
|
|
|
Revision 1.82 2005/06/07 19:31:19 connolly
|
|
note request for ## testcase under punctuationSyntax
|
|
|
|
Revision 1.81 2005/05/31 14:12:01 connolly
|
|
more background on punctuationSyntax
|
|
|
|
Revision 1.80 2005/05/30 02:12:05 connolly
|
|
minutes 19 May provide details for closing serviceDescription,
|
|
xmlAbstractSyntax, sort
|
|
noted a test idea for punctuationSyntax from Ashok's comment
|
|
|
|
Revision 1.79 2005/05/24 10:21:17 connolly
|
|
punctuationSyntax tests
|
|
|
|
Revision 1.78 2005/05/24 09:51:20 connolly
|
|
a sort of proposal re punctuationSyntax
|
|
|
|
Revision 1.77 2005/05/17 16:22:38 connolly
|
|
closed three issues! minutes pending...
|
|
|
|
Revision 1.76 2005/04/19 22:37:13 connolly
|
|
decided against reification syntax
|
|
|
|
Revision 1.75 2005/04/19 22:34:51 connolly
|
|
beefed up fromUnionQuery, valueTesting, and sort a bit; mostly
|
|
by adding short descriptions
|
|
|
|
Revision 1.74 2005/04/12 13:52:31 connolly
|
|
note bnodes/existentials comment re graphSolutionsMapping
|
|
|
|
Revision 1.73 2005/04/08 19:39:21 connolly
|
|
moved GK's comment on DESCRIBE closer to other public comments
|
|
|
|
Revision 1.72 2005/04/08 19:10:43 connolly
|
|
noted GK's position on DESCRIBE
|
|
|
|
Revision 1.71 2005/04/08 19:00:00 connolly
|
|
note Klyne's position on SOURCE
|
|
|
|
Revision 1.70 2005/04/08 18:43:08 connolly
|
|
noted outstanding dissent on issues:
|
|
- valueTesting, 3.3 Extensible Value Testing
|
|
- SOURCE, objective 4.2 Data Integration and Aggregation
|
|
and requirements
|
|
- subgraph results
|
|
- result limits
|
|
- optional match
|
|
and overall approach
|
|
- BRQL straw-man
|
|
|
|
Revision 1.69 2005/04/05 20:53:26 connolly
|
|
noted I have the ball on punctuationSyntax
|
|
|
|
Revision 1.68 2005/04/05 20:33:05 connolly
|
|
re-opened punctuationSyntax
|
|
|
|
Revision 1.67 2005/03/29 16:47:29 connolly
|
|
owner of xmlAbstractSyntax
|
|
|
|
Revision 1.66 2005/03/25 23:50:21 connolly
|
|
cleaned up punctuationSyntax; quoted resolution
|
|
|
|
Revision 1.65 2005/03/25 23:47:05 connolly
|
|
cleaned up accessingCollections: quoted resolution
|
|
|
|
Revision 1.64 2005/03/25 23:42:42 connolly
|
|
cleaned up cascadedQueries: quoted resolution, revised summary
|
|
|
|
Revision 1.63 2005/03/24 18:53:19 connolly
|
|
- added serviceDescription, wsdlAbstractProtocol, xmlAbstractSyntax
|
|
|
|
Revision 1.62 2005/03/21 22:33:42 connolly
|
|
noted owners of sort, valueTesting issues
|
|
|
|
Revision 1.61 2005/03/21 17:13:56 connolly
|
|
- added sort issue
|
|
- moved punctuationSyntax to closed
|
|
|
|
Revision 1.60 2005/03/04 00:35:08 connolly
|
|
update from 22Feb, ftf5
|
|
|
|
Revision 1.59 2005/03/03 22:45:29 connolly
|
|
ack punctuationSyntax
|
|
|
|
Revision 1.58 2005/02/04 20:16:13 connolly
|
|
document class="resolve"
|
|
|
|
Revision 1.57 2005/02/04 20:14:48 connolly
|
|
class="resolve" vs "resolved"
|
|
|
|
Revision 1.56 2005/02/04 20:13:23 connolly
|
|
markup fix
|
|
|
|
Revision 1.55 2005/02/04 20:13:08 connolly
|
|
- linked issues to decisions from helsinki
|
|
- grouped issues by status (open/postsponed/closed)
|
|
|
|
Revision 1.54 2005/01/19 05:02:01 connolly
|
|
proposal markup
|
|
|
|
Revision 1.53 2005/01/19 05:01:34 connolly
|
|
proposal markup. again. sigh.
|
|
|
|
Revision 1.52 2005/01/19 04:50:30 connolly
|
|
proposal markup on separate DESCRIBE ql
|
|
|
|
Revision 1.51 2005/01/19 04:44:25 connolly
|
|
- cascadedQueries proposal from eric
|
|
- DESCRIBE proposals from DanC, DanBri
|
|
- note sandro's input to consWithBnodes
|
|
- SOURCE option from SteveH
|
|
- yesNo SELECT/LIMIT option
|
|
- prefixDecl only in one place option
|
|
|
|
Revision 1.50 2005/01/14 22:33:49 connolly
|
|
DESCRIBE link to spec fixed
|
|
|
|
Revision 1.49 2005/01/14 22:28:27 connolly
|
|
absolutized links for portability to WBS
|
|
|
|
Revision 1.48 2005/01/14 21:44:44 connolly
|
|
change issue names constructWithBnodes and constructUnboundVars
|
|
to be distinct in the 1st 8 chars. (sigh)
|
|
|
|
Revision 1.47 2005/01/14 21:19:58 connolly
|
|
spurious wbs URI
|
|
|
|
Revision 1.46 2005/01/14 21:19:19 connolly
|
|
prefix syntax proposal class markup
|
|
|
|
Revision 1.45 2005/01/14 21:17:54 connolly
|
|
nest requirements/objectives under relevant proposals
|
|
|
|
Revision 1.44 2005/01/14 21:13:32 connolly
|
|
link to WBS; explain proposal style
|
|
|
|
Revision 1.43 2005/01/14 21:10:52 connolly
|
|
proposals yellow
|
|
|
|
Revision 1.42 2005/01/14 21:08:48 connolly
|
|
quote bug
|
|
|
|
Revision 1.41 2005/01/14 21:08:20 connolly
|
|
relevant part of the spec on prefixDecl
|
|
|
|
Revision 1.40 2005/01/14 21:05:47 connolly
|
|
spec section relevant to yes/no
|
|
|
|
Revision 1.39 2005/01/14 21:01:09 connolly
|
|
border-bottom
|
|
|
|
Revision 1.38 2005/01/14 20:59:17 connolly
|
|
found more proposals from the rq23 spec
|
|
|
|
Revision 1.37 2005/01/14 20:50:16 connolly
|
|
rq23 position on constructUnbound
|
|
|
|
Revision 1.36 2005/01/14 14:49:02 connolly
|
|
grddling issues list
|
|
|
|
Revision 1.35 2005/01/13 19:27:42 connolly
|
|
blockquote/address style
|
|
|
|
Revision 1.34 2005/01/13 19:26:50 connolly
|
|
beefing up unsaid
|
|
|
|
Revision 1.33 2005/01/11 16:35:21 connolly
|
|
removed obsolete notes on SOURCE
|
|
|
|
Revision 1.32 2005/01/11 16:34:23 connolly
|
|
elaborated source issue
|
|
|
|
Revision 1.31 2005/01/11 16:22:02 connolly
|
|
made search links more readable
|
|
|
|
Revision 1.30 2005/01/11 16:19:08 connolly
|
|
fleshed out disjunction issue
|
|
|
|
Revision 1.29 2005/01/05 23:05:38 connolly
|
|
note name issue closed
|
|
|
|
Revision 1.28 2004/12/13 16:19:36 connolly
|
|
new issue in TOC
|
|
|
|
Revision 1.27 2004/12/13 14:31:54 connolly
|
|
fixed bullet
|
|
|
|
Revision 1.26 2004/12/13 14:31:13 connolly
|
|
archive search for each issue
|
|
|
|
Revision 1.25 2004/12/13 14:21:42 connolly
|
|
- relieved Alberto of owning DESCRIBE
|
|
- added useMentionOp
|
|
|
|
Revision 1.24 2004/11/15 14:44:11 connolly
|
|
cite DaveB's SOURCE proposal
|
|
|
|
Revision 1.23 2004/11/01 17:16:31 connolly
|
|
fixing broken links
|
|
|
|
Revision 1.22 2004/09/30 13:30:13 connolly
|
|
dropped unack'd issues
|
|
|
|
Revision 1.21 2004/09/28 19:16:44 connolly
|
|
shortened h1, moved DAWG from nearby to context
|
|
|
|
Revision 1.20 2004/09/28 19:15:07 connolly
|
|
indexed owners
|
|
|
|
Revision 1.19 2004/09/28 19:12:01 connolly
|
|
cited actions relevant to SOURCE issue
|
|
|
|
Revision 1.18 2004/09/28 18:57:33 connolly
|
|
named all the issues
|
|
merged "queries and a merge rule" into cascadedQueries
|
|
merged 2 not/unsaid issues
|
|
merged 2 source issues
|
|
|
|
20 rows - 2 unacked issues - 3 merged = 15 issues
|
|
|
|
Revision 1.17 2004/09/20 23:41:45 connolly
|
|
collections, service/document
|
|
|
|
Revision 1.16 2004/09/20 18:52:58 connolly
|
|
ftf3 issues: owners, disjunction, ...
|
|
|
|
Revision 1.15 2004/09/17 13:13:49 connolly
|
|
(connolly) Changed through Jigsaw.
|
|
|
|
Revision 1.14 2004/09/17 08:41:02 dbeckett2
|
|
+disjunction
|
|
|
|
Revision 1.13 2004/09/09 15:29:55 connolly
|
|
removed dup: construct unbound vars
|
|
|
|
Revision 1.12 2004/09/09 11:46:12 connolly
|
|
SOURCE description
|
|
|
|
Revision 1.11 2004/09/08 18:14:58 connolly
|
|
use lists for all (normal) issue histories
|
|
|
|
Revision 1.10 2004/09/08 18:13:18 connolly
|
|
table border, changelog</pre>
|
|
<hr />
|
|
<address>
|
|
Dan Connolly for <a href="/People/Eric/">Eric Prud'hommeaux</a> and the <a
|
|
href=".">RDF Data Access Working Group</a><br />
|
|
<small>$Id: issues.html,v 1.156 2007/10/23 15:28:27 lfeigenb Exp $</small>
|
|
</address>
|
|
</body>
|
|
</html>
|