W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > October 2016

Re: shapes-ISSUE-183 (undefined term): Eliminating the term "Undefined" [SHACL - SPARQL]

From: Karen Coyle <kcoyle@kcoyle.net>
Date: Mon, 10 Oct 2016 14:55:17 -0700
To: public-data-shapes-wg@w3.org
Message-ID: <b1445154-577c-adf8-84d3-f700ddf28ea8@kcoyle.net>
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>"


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

Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet/+1-510-984-3600
Received on Monday, 10 October 2016 21:55:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:37 UTC