Gregg Kellogg

IMO, diffs are actually less useful than an appendix summarizing the change with a reference to the associated PR. PR Preciew does a good job of a diff for that...

I think The ReSpec team is working on a way to automate this for spec updates. It’s complicated by the new process document which didn’t consider the need of tooling...

I've always voiced the opinion that it should be illegal to use a blank node as a ShEx starting point, as in RDF, there is no expectation that one used...

Explain the regex bit.

I had some thoughts about how we might go about doing this: If there was some syntax to describe a node as representing a name graph, which we could associate...

This is similar to wanting to use a path to avoid having a BNode target. In the case of a predicate, you might imagine that this could use a similar...

I think it should be part of the main language, not annotations, as it relates to control flow. Anything other than "mandatory" should be treated something like `?` or `*`,...

Why not just use ShapeAnd?: ``` @ AND { a [sx:OneOf] ; } @ AND { a [sx:EachOf] ; } CLOSED { a . ; sx:min xsd:integer? ; sx:max xsd:integer...

If the `datatype` production used `ValueSetValue` would that do it? [55] datatype ::= iri Becomes [55] datatype ::= iri | '(' valueSetValue* ')' This moves it to a NodeConstraint, but...

I've been using `http://www.w3.org/ns/shex#Start` (`shex:Start`), but that might be easy to confuse with `shex:start`, which is a predicate URI. However, it is distinct, and is being used in the subject/object...