kburger

Hi @KarolisCremers. Without any experience running this on windows, this seems to be a higher level issue. For reference, can you post the `docker-compose.yml` file you are using? And can...

Hi @vemonet, I'm sorry to hear about these issues. Unfortunately, I don't see the same behaviour for the demo instances we are running. The underlying systems are a bit different...

Hi @markwilkinson, thanks for the report. I'll pass this bug along, in the mean time could you check if an offset would fix this? Either something like `+1` or `+01:00`.

Hi @hvdsomp, the current approach is to describe the service within the data return from the root, using (among others) [LDP](https://www.w3.org/TR/ldp). Do you have use cases where this would not...

Hi @markwilkinson, there's a pending issue that the index does not behave correctly as an FDP at this point. In practice this means the root metadata is there, but the...

The FDP specs allow for any way you prefer to generate the identifiers. Currently the reference implementation will generate unique identifiers for you. In case of a migration, I think...

> @kburger there is some issue resulting in `org.eclipse.rdf4j.sail.shacl.ast.ShaclUnsupportedException` for the `shacl-shacl.ttl` (based on #95), any idea why that happends? 😕 I'm guessing certain features in the shacl-shacl are not...

> > shacl-shacl contains a lot of those, so maybe that causes the exception to be thrown instead of a shacl violation report. One option is to postpone this feature...

Hi @PderyckeSciensano, for SHACL the correct syntax would be `sh:datatype xsd:float` (which could be combined with `sh:nodeKind sh:Literal`, but that's probably not required). This would at least solve the validation...

Hi @vemonet, I'll pass this request to the UI team. If you have any experience on the client stack (vue.js mostly), you are more than welcome to submit PR for...