- From: Holger Knublauch <holger@topquadrant.com>
- Date: Thu, 07 May 2015 22:09:51 +1000
- To: RDF Data Shapes Working Group <public-data-shapes-wg@w3.org>
On 5/7/2015 21:46, Eric Prud'hommeaux wrote: > It's got SPIN templates, SPIN calling conventions (embedding arguments > in lists) and SPIN variable conventions (?this). None of these things > exist in SPARQL. To call them SPARQL is quite misleading. Templates are an RDF vocabulary that is used by a SHACL engine. Of course SPARQL cannot know anything about SHACL templates or variable naming conventions or arguments, neither does it need to. SHACL still operates on SPARQL engines. > We could invent a new name for SPARQL templates but SPIN seems pretty > accurate. What about "SHACL templates"? >> unfortunately a completely inconsistent and incomplete set of >> unrelated documents. Where did the content of chapters 1 - 6 end up? >> Does your Core Semantics document even have the same semantics? How > Not yet. The core semantics is more complex and will require some work > to express in templates. Can we make this a bit more concrete rather than asserting that insurmountable differences exist? We need to make some real decisions in the next two weeks. Could you give me some specific pointers about which features of your language could not be expressed in templates, and where your definition of the core language differs from mine? Ideally can we look at some specific use cases, e.g. expressed as test cases with input and expected output? > Note that the ShEx semantics started out > quite simple (basically Resource Shapes) and grew in response to user > feedback (e.g. multi-occurance). Where are those requirements written down and approved? What do you mean with multi-occurance? > David Booth's proposal is to profile > out the intersection but I think we may be able to offer a more useful > language if we extend the templates to meet more of these use cases. For complex use cases we propose SPARQL instead of reinventing a new variation of it. A huge amount of cases can be covered quite elegantly with user-defined functions. Thanks, Holger
Received on Thursday, 7 May 2015 12:11:38 UTC