Milton Reder

On the dependency, I do not believe that Clojure's deps.edn can currently support "POM-only" artifacts which this [lib uses post 2.4.0](https://kohlschutter.github.io/junixsocket/changelog.html#2021-07-30-junixsocket-2-4-0) > Maven Dependency: junixsocket-core is now a POM-only artifact...

@florianrusso I've confirmed that `junixsocket` doesn't require any modules outside of `java.base`, so that is likely OK. I've pushed a docker image with the dep included, [yetanalytics/lrsql:junixsocket-test](https://hub.docker.com/layers/lrsql/yetanalytics/lrsql/junixsocket-test/images/sha256-f1acabf7b22c0a06b3ef0dcb5af9453910a047c5e0206ef6005b2187dee8e48a?context=explore), please try that...

@florianrusso sorry, this got lost in the shuffle. I'll try out that compose and see what I can find.

Looks like you need to provide the full path to the socket for it to work like `jdbc:postgresql://localhost/test-postgres-db?socketFactory=org.newsclub.net.unix.AFUNIXSocketFactory%24FactoryArg&socketFactoryArg=/var/run/postgresql/.s.PGSQL.5432&sslMode=disable&user=test-postgres-db`. When I tried it with that locally it worked. I'll go ahead...

Additionally, it looks like there was a typo in your port for SQL LRS, here is a full working template: ```yaml version: '3' services: postgres: image: postgres:13 ports: - '5432:5432'...

junixsocket landed in main a while ago, so the instructions above should work fine with the `latest` tag. Closing

Linking the version header issue here so it doesn't get lost: https://github.com/adlnet/lrs-conformance-test-suite/pull/252#issuecomment-1508742585 Essentially the `1.0.3` tests (as they are on the `2.0.0` branch) prevent an LRS from being compatible with...

Hey all, I'm late to the party on this one. It's not ready for a PR yet, but I generated a new ontology based on the triple destructuring we've done...

@fugu13 I tried my hand at a context to go along with the ontology I posted on #7. It's mostly complete (I don't think I've done extensions yet), but would...