Recursion (ISSUE-22)

With this e-mail, I would like to revisit the resolution on issue 22.

With the recent addition of property paths, we can cover a big range of
recursion use cases.
I cannot easily tell what percentage of all recursion use cases we can
actually cover but it definitely covers most of the simple ones.

My proposal is to alter the resolution and say something like
A shape MUSt NOT refer to itself directly or indirectly via shape-based
constraint components (e.g. sh:shape), logical constraint components (e.g.
sh:or) and filter shapes (sh:filterShape)

With this proposal, we close a big hole in the spec without sacrificing the
expressivity of the language

Best,
Dimitris

-- 
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