Re: ISSUE-23 implicit scopeClass text updated

Peter,

On Fri, Jan 22, 2016 at 9:58 AM, Peter F. Patel-Schneider
<pfpschneider@gmail.com> wrote:

> Quite a mouthful, but this appears to do the trick.

Thanks for the review. My goal was to be precise. If we are all in
agreement, then we can work on improving the readability.

>
> This may, however, upset some of the "implicit typing" simplifications
> elsewhere in the document, such as
>
> 11. Validation of shapes graphs and the sh:defaultValueType property
> Example 8
> Example 27
> Example 28
>
> The first mention of what is a shape is right at the beginning of Section 2.
> The relevant text above is quite a bit later, which should be remedied.

I think we should do some editorial work to explain the shapes graph,
the data graph, and how typing works, probably nearer where we discuss
the relation to RDFS. Then go through the whole spec and much sure we
are consistent.

A couple of issues occur to me, e.g, we were giving rdfs:Resource
special treatment in the definition of sh:class (all classes are
subclasses of rdfs:Resource). Also, we do not require the presences of
an explicit sh:Shape type triple in some cases, i.e. we are in effect
inferring the type from the context.

> The comment
>
> Issue 23: Use of shapes graph versus data graph for metadata
> We should be consistent here. We put shape information in the shapes graph.
> Class information should also be in the shapes graph, especially for designers
> who couple shapes and classes. Both shapes and classes are kinds of metadata
> so they should be in the same graph.
>
> should probably be removed, but I do agree that the early examples should not
> use a combined data and shapes graph.

Removed.

-- Arthur

Received on Monday, 25 January 2016 17:00:10 UTC