Jos De Roo
Jos De Roo
To put it in a wider historical perspective, see https://lists.w3.org/Archives/Public/www-archive/2022Apr/0001.html
Not yet like that but see https://github.com/MellonScholarlyCommunication/POrchestrator/issues/3 and one day it will work out ;-)
For the moment I think that the best solution is mentioned in https://github.com/MellonScholarlyCommunication/POrchestrator/issues/3#issuecomment-960831148 > In the browser, we could also host a Prolog engine via WebAssembly if we wanted to....
I tried my *nix skills and was able to run EYE on my Android phone 🙂  Having a reasoner in your hand feels good and thanks to the [UserLAnd](https://play.google.com/store/apps/details?id=tech.ula&hl=nl&gl=US)...
I was also surprised and it was working out quite well and all tests in the 81 subprojects at https://github.com/josd/eye/tree/master/reasoning work perfectly. The speed is a bit slower than in...
It is about the same difficulty/effort @JanWielemaker 🙂 I tried it as described in https://github.com/josd/josd.github.io/blob/master/temp/termux.txt I was also trying to build swipl wasm following https://github.com/SWI-Prolog/swipl-devel/blob/master/CMAKE.md#wasm-emscripten and `~/github.com/SWI-Prolog/swipl-devel/build.wasm/build.ninja` was nicely generated...
Today @JanWielemaker and @RubenVerborgh we were able to run eye on swipl.wasm by doing ``` sudo apt install cmake sudo apt install ninja-build cd ~ git clone https://github.com/emscripten-core/emsdk.git cd emsdk...
Maybe yes @jeswr once the OOM is resolved. If not we remain with @RubenVerborgh 's excellent https://www.npmjs.com/package/eyeserver
> Have tried playing with the Node.js command-line flags for memory? Very good suggestion @RubenVerborgh and when building with `-s ALLOW_MEMORY_GROWTH=1` it now works much better! Still the 100000 deep...
Could you elaborate on what is `wrong or broken` in the output of EYE ``` $ eye --quiet --nope card.n3 --pass 2>/dev/null @prefix xsd: . @prefix foaf: . @prefix rdfs:...