Thomas Bergwinkl

Two weeks is what we agreed on for the specs, but I see that for code it could be a long time. If it doesn't make the process too complicated,...

I don't use TypeScript in my projects, which is why there are currently no Type Definitions. But adding Type Definitions is part of the planned work funded via the [RDF-Ext...

You can pass a list of shapes to the `.validate()` method. If you use `grapoi`, you can directly pass the pointer: ```javascript await validator.validate({ dataset }, ptr) ``` Otherwise, the...

I will have a closer look. I'm not sure yet if it should be ignored when the shapes are explicitly given and don't exist.

I added support for SPARQL targets to the [experimental branch](https://github.com/rdf-ext/shacl-engine/tree/experimental). It looks a bit different from the SPARQL target defined in the SHACL-AF specification. It's based on Node expressions. See...

Works fine here. Will close this issue. If the problem recurs, please provide further details such as request/response headers and your location, so others can try to reproduce the problem.

I only had a brief look as I am on vacation and traveling, so forgive me if I missed something. It looks like you are adding arguments to the factory...

@RubenVerborgh > That's the main reason why I am proposing an object as an optional second argument, so { token } rather than directly token or even a string. This...

@faubulous @RubenVerborgh I expected `source` to be a property with an object value that contains all other properties like this: ``` { source: { tokenType, token, prefix, line, start, end...

@RubenVerborgh All of them are source attributes, as a different serialization may generate different tokens, and prefixes are also defined as part of the serialization. Maybe a short overview of...