Can we freeze the Tracker for while?

I believe we have a sufficient number of open tickets right now that 
require our attention. The process should resemble a queue in which the 
most urgent tickets are handled with priority. The flood of recently 
raised issues (and non-issues) is IMHO a distraction that turns our 
workflow into a LIFO stack. None of ISSUES-105 onwards are urgent.

While the tracker is good to record suggestions, I believe we should 
refrain from handling them until next year, say, until we had another 
F2F and the next draft has been published.

What is urgently missing is practical experience and real-world 
feedback. While we have a reasonably good draft now, I don't believe 
many people have actually tried to use SHACL. To bootstrap this, we need 
easy to use tools, and to provide those, we need a stable syntax so that 
tool builders are willing to create polished environments with support 
for common use cases, and to write tutorials.

Holger

Received on Saturday, 7 November 2015 05:12:28 UTC