- From: Holger Knublauch <holger@topquadrant.com>
- Date: Fri, 18 Nov 2016 16:18:47 +1000
- To: public-data-shapes-wg@w3.org
As I said in the meeting, I believe it is premature to remove pre-binding from the core. Peter's argument is that we should not rely on it because it's a non-standard concept. However, we will hopefully have a proper definition of pre-binding soon - if not then we would need to remove it completely and rewrite also the extension mechanism, not just the core. The specific mechanism suggested by Peter, to project the pre-bound variables to the outside with a SELECT is very counter-intuitive, inefficient, does not align with how the extension mechanism works, and does not generally work for all cases (as he noted himself), requiring an inconsistent secondary approach. He would also need to provide details of how all the other cases work: it's too late to do hand-waving on such a fundamental change. I see no need to do anything at this stage. PROPOSAL: Close ISSUE-202 as explained in this email. If pre-binding (ISSUE-68) cannot be resolved, then we need to replace all queries anyway, and then we could revisit his suggestions. Holger On 18/11/2016 9:28, RDF Data Shapes Working Group Issue Tracker wrote: > shapes-ISSUE-202 (Remove pre-binding from core): Suggestion to remove pre-binding from core [SHACL - Core] > > http://www.w3.org/2014/data-shapes/track/issues/202 > > Raised by: Karen Coyle > On product: SHACL - Core > > See Peter's emails: > > https://lists.w3.org/Archives/Public/public-rdf-shapes/2016Nov/0001.html > https://lists.w3.org/Archives/Public/public-rdf-shapes/2016Nov/0002.html > > >
Received on Friday, 18 November 2016 06:19:24 UTC