Re: ISSUE-23: Dropped sh:ShapeClass, elaborated on sh:scopeClass rule

Holger,

Note that I changed it to a SELECT. I am OK leaving it in. It may help
people understand the prose.

-- Arthur

On Tue, Jan 19, 2016 at 7:52 PM, Holger Knublauch
<holger@topquadrant.com> wrote:
> Thanks, Arthur. Looks good to me. Now that we have the detailed paragraph
> about how to recognize shapes and classes, I don't think we need the SPARQL
> query anymore?
>
> Holger
>
>
> On 20/01/2016 5:31 AM, Arthur Ryman wrote:
>>
>> Holger,
>>
>> I've edited the spec, phrasing this as part of how class-based scopes
>> are computed. No mention of inferencing.
>>
>> -- Arthur
>>
>> On Sun, Jan 10, 2016 at 7:26 PM, Holger Knublauch
>> <holger@topquadrant.com> wrote:
>>>
>>> As resolved recently, I have dropped sh:ShapeClass from the spec (and the
>>> test cases).
>>>
>>> To clarify the compromise that I am supporting, I have rewritten parts of
>>> section 2.1.2
>>>
>>>      http://w3c.github.io/data-shapes/shacl/#scopeClass
>>>
>>> This now includes a SPARQL query that shows how the implicit
>>> sh:scopeClass
>>> triples can be inferred prior to running the validation, on the shapes
>>> graph.
>>>
>>> I welcome further discussion on that.
>>>
>>> Thanks,
>>> Holger
>>>
>>>
>
>

Received on Wednesday, 20 January 2016 03:48:57 UTC