Re: shapes-ISSUE-164 (mutable graphs): [EDITORIAL] Section 1.4 (and maybe other places) looks as if graphs are mutable [SHACL Spec]

Right, I was hoping we get rid of defaultValueType completely with my
syntax change suggestion.
If we plan to vote on that in the next telco we can close these together.
Let's leave it open a little longer then


On Tue, May 24, 2016 at 5:45 PM, Peter F. Patel-Schneider <
pfpschneider@gmail.com> wrote:

> I think that something has to be done with default value type as well.
> This
> may also require changes to the terminology section.
>
> The point is that it is not sufficient to just look at one part of the
> document but that the entire document needs to be examined to look for
> places
> where it may appear that SHACL validation changes the data or shapes graph.
>
> peter
>
>
> On 05/24/2016 06:19 AM, Dimitris Kontokostas wrote:
> > Peter,
> >
> > Could you please check if the following commit resolves this issue?
> >
> https://github.com/w3c/data-shapes/commit/3ed0a4dda0f6d1804c49d175bdb52ec12171e8c8
> >
> > Best,
> > Dimitris
> >
> > On Thu, May 19, 2016 at 11:35 PM, RDF Data Shapes Working Group Issue
> Tracker
> > <sysbot+tracker@w3.org <mailto:sysbot+tracker@w3.org>> wrote:
> >
> >     shapes-ISSUE-164 (mutable graphs): [EDITORIAL] Section 1.4 (and maybe
> >     other places) looks as if graphs are mutable [SHACL Spec]
> >
> >     http://www.w3.org/2014/data-shapes/track/issues/164
> >
> >     Raised by: Peter Patel-Schneider
> >     On product: SHACL Spec
> >
> >     The spec should be much clearer that SHACL works on immutable shape
> and
> >     data graphs.  Section 1.4 gives a false impression, but the various
> >     discussions of default value type might also need to be revised.
> >
> >
> >     1.4 Relationship between SHACL and RDFS inferencing
> >
> >     SHACL uses the RDF and RDFS vocabularies. SHACL processors MUST
> perform
> >     inferencing when needed to identify SHACL instances of a class both
> in the
> >     data graph and the shapes graph but full RDFS inferencing is not
> required.
> >     However, SHACL processors may operate on RDF graphs that include
> >     entailments - either pre-computed before being submitted to a SHACL
> >     processor or performed on the fly as part of SHACL processing. To
> support
> >     on the fly processing of entailments, SHACL includes the property
> >     sh:entailment to indicate what inferencing is required by a given
> shapes
> >     graph. SHACL implementations may, but are not required to, support
> >     entailment regimes.
> >
> >
> >
> >
> >
> >
> >
> > --
> > Dimitris Kontokostas
> > Department of Computer Science, University of Leipzig & DBpedia
> Association
> > Projects: http://dbpedia.org, http://rdfunit.aksw.org,
> http://aligned-project.eu
> > Homepage: http://aksw.org/DimitrisKontokostas
> > Research Group: AKSW/KILT http://aksw.org/Groups/KILT
> >
>
>


-- 
Dimitris Kontokostas
Department of Computer Science, University of Leipzig & DBpedia Association
Projects: http://dbpedia.org, http://rdfunit.aksw.org,
http://aligned-project.eu
Homepage: http://aksw.org/DimitrisKontokostas
Research Group: AKSW/KILT http://aksw.org/Groups/KILT