Gregg Kellogg

Some grammar comments: * `shapeMap` ends with a ';' which is not quoted; does this have some significance? * The `triplePattern` production has a First/First conflict on '{' (a concern...

WebIDL is somewhat restricted in the datatypes available. URL parameters are commonly DOMString or USVString in other W3C Specs. Mime Types come in when interpreting the dereferenced result.

The [Promises Guide](https://www.w3.org/2001/tag/doc/promises-guide#reasons-should-be-errors) says to use the ECMAScript `Error` type (or `DOMException`), where the code is a string passed to the error, such as: ``` const oldPromise = windowA.Promise; windowA.Promise...

USVString handles both URI and text; WebIDL has not datatype for URI, and this is not commonly used in other specs I've seen. The distinction between text and URI is...

I'm not against this, but I don't see what may actually happen. Anything that has the form of a URI couldn't possibly be either a schema or a graph and...

Two interfaces? Standard for WebIDL lately has been to use promises. If you did want to define a synchronous interface, perhaps simply use a different method? The method could be...

Okay, I can see the value in this. Not sure that in WebIDL a call can return an interface, as it's not really object-oriented. Perhaps both methods are in the...

Looks like it's a synchronous, rather than asynchronous API.

This could be done by making `ShapeResults` be serializable as JSON-LD, something like the following: ```json { "@context": "http://w3.org/ns/shex.jsonld", "@type": "ShapeResults", "results": { "http://example.com/node1": { "@type": "ShapeResult", "shape": "http://example.org/S", "result":...

This was discussed during today's call: https://json-ld.org/minutes/2022-06-22/.