Allowing bnodes would always fail validation when the data graph and the shapes graph are not the same but I do not see any other problem. Since it does not affect the language I suggest we allow it for both, someone might find a use case for this On Mon, Dec 12, 2016 at 2:06 AM, Holger Knublauch <holger@topquadrant.com> wrote: > What would you suggest: > a) disallow bnodes for both > b) allow bnodes for both. > > I have no strong opinion on this. Does anyone have use cases for bnodes in > sh:hasValue? > > Holger > > > > On 12/12/2016 7:34, Peter F. Patel-Schneider wrote: > >> sh:hasValue allows blank nodes but sh:in does not. >> >> >> This difference does not seem to have any rationale. If blank nodes are >> allowed for sh:hasValue then they should be allowed for sh:in. >> >> >> >> Peter F. Patel-Schneider >> Nuance Communications >> >> > > -- 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
Received on Monday, 12 December 2016 18:01:08 UTC