- From: Holger Knublauch <holger@topquadrant.com>
- Date: Tue, 11 Oct 2016 10:20:25 +1000
- To: "public-data-shapes-wg@w3.org" <public-data-shapes-wg@w3.org>
I have switched these uses of "error" to "SPARQL error" wrapped with a hyperlink to a place in the SPARQL spec: https://github.com/w3c/data-shapes/commit/b367dcd030c652bcb7f7818bb01177dbb7f1d50b This should make clear what we are talking about. The other uses of the term "error" are about errors in shapes graphs. Holger On 11/10/2016 7:55, Karen Coyle wrote: > This substitutes "error" for "undefined" and refers to an error as a > failure. I believe that both error and failure will therefore need to > be defined in the terminology: > > "<li><span class="term">error</span> if during the execution a > <a>failure</a> has been reported. This result indicates a > <a>failure</a>. Implementations MAY for example use this to report > infinite recursion.</li>" > > kc > > On 10/2/16 5:32 AM, RDF Data Shapes Working Group Issue Tracker wrote: >> shapes-ISSUE-183 (undefined term): Eliminating the term "Undefined" >> [SHACL - SPARQL] >> >> http://www.w3.org/2014/data-shapes/track/issues/183 >> >> Raised by: Dimitris Kontokostas >> On product: SHACL - SPARQL >> >> While addressing some public comments the SHACL editors made edits >> in the spec that should have been approved by the WG. >> One of these cases is the effort to eliminate the term undefined from >> the spec as described in the following link and affect the SPARQL >> extension mechanism: >> https://lists.w3.org/Archives/Public/public-rdf-shapes/2016Sep/0062.html >> >> Proposal: accept the edits made by the editors to eliminate the term >> undefined which alters the definition of the sh:hasShape SPARQL function >> >> >> >> >
Received on Tuesday, 11 October 2016 00:21:01 UTC