- From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
- Date: Fri, 6 Nov 2015 21:52:25 -0800
- To: Holger Knublauch <holger@topquadrant.com>, public-data-shapes-wg <public-data-shapes-wg@w3.org>
Opening an issue is largely independent of how or when it is to handled. If any working group member feels that certain issues need to be addressed now they are welcome to advocate that more attention be paid to these issues. If any working group member feels that certain proposed issues should not be opened they they are also welcome to so advocate. I would be against a general moratorium on opening issues, or even a slowdown on opening issues. Restricting the opening and resolution of issues is not going to result in more practical experience with and real-world feedback on SHACL. I do believe that the working group should be spending more time on fundamental issues. Making progress on fundamental issues can require considerable time, and I know that I have been spending time on what I consider to be less important issues, but these have been coming up for consideration mostly independently of any actions on my part. peter On 11/06/2015 09:11 PM, Holger Knublauch wrote: > 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:52:55 UTC