Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Tomasz Pluskiewicz
@tpluscode
@angelo-v what do I need to do?
Angelo Veltens
@angelo-v
@tpluscode you need to support this PR :)
Tomasz Pluskiewicz
@tpluscode
really. anything we can do on our end @bergos ?
Thomas Bergwinkl
@bergos
@tpluscode i'm not an webpack expert, but maybe it could be solved somehow via the resolve logic/config: https://webpack.js.org/configuration/resolve/
Angelo Veltens
@angelo-v
I do not think so. Even if we manage to enforce readable.js instead of readable-browser.js, it will fail in the browser, because there is no process.env
Thomas Bergwinkl
@bergos
maybe if you configure resolve to use a file in your own codebase, use @angelo-v version of https://github.com/angelo-v/readable-stream/blob/master/readable-browser.js and replace ./lib/ with readable-stream/lib/?
Angelo Veltens
@angelo-v
might work, but I would prefer when they just merge the **%# PR
Thomas Bergwinkl
@bergos
sure, my proposal is just a workaround
Angelo Veltens
@angelo-v
after I took the effort and migrated some tests they finally merged it nodejs/readable-stream#409
let's hope for a quick release....
Tomasz Pluskiewicz
@tpluscode
woo hoo
elf Pavlik
@elf-pavlik
:clap:
Angelo Veltens
@angelo-v
here we go, please update your dependencies :) https://github.com/nodejs/readable-stream/releases/tag/v3.4.0
Adrian Gschwend
@ktk
Am I right that there is currently no RDFa parser that implements the new RDFJS stream interface?
Ruben Taelman
@rubensworks
It already passes all spec tests, just need to cleanup some things, optimize, and document.
Adrian Gschwend
@ktk
yay!
@rubensworks we will use it in the same issue in rdf-vocabularies, some only return RDFa :)
Ruben Taelman
@rubensworks
Great :-) I hope to release it later this week or early next week.
Pieter Colpaert
@pietercolpaert
Is there already a rdfjs compliant SHACL validator around?
Ruben Taelman
@rubensworks
@ktk FYI, I just released the RDFa parser: https://github.com/rubensworks/rdfa-streaming-parser.js
Sarven Capadisli
@csarven
^ @bergos Could you give a rough pointers on what needs to happen to get SimpleRDF up to date with the recent RDFJS based parsers/serialisers...? https://gitter.im/linkeddata/dokieli?at=5d23774326a152537e4bf01e
Adrian Gschwend
@ktk
@rubensworks saw it great, thanks!
Thomas Bergwinkl
@bergos
@csarven as far as i remember, the way you used simplerdf it would be better for your to use the dataset directly or clownface
Thomas Bergwinkl
@bergos
i will move the packages i started in the rdfjs github organization to rdfjs-base. i will handle them like rdf-ext packages. so not to much should change, but i can avoid asking in the big round if there are bigger decisions to make, which cost me a lot of time in the past.
Tomasz Pluskiewicz
@tpluscode
hey. is there a JS in-memory triple store with SPARQL Update support?
Martynas Jusevicius
@namedgraph_twitter
@tpluscode i've asked more or less the same some time ago
you mean in-browser i assume?
check https://gitter.im/rdfjs/Representation-Task-Force, people are talking about quadstore there
Tomasz Pluskiewicz
@tpluscode
nope. I only need node. for in-memory tests which operate on a store
Martynas Jusevicius
@namedgraph_twitter
can't you package the whole thing into Docker and then run whatever, like Jena/Fuseki?
Tomasz Pluskiewicz
@tpluscode
oh boy that would be such an overkill for tests running jest/jasmine/etc
Martynas Jusevicius
@namedgraph_twitter
might help you in the long run more than you know ;)
Tomasz Pluskiewicz
@tpluscode
I don't know ;)
what you say, I do with end-to-end tests running over actual API
Martynas Jusevicius
@namedgraph_twitter
check the Beautiful Interactions stuff. i haven't looked deeply myself
Tomasz Pluskiewicz
@tpluscode
will do thanks
Martynas Jusevicius
@namedgraph_twitter
i'm also running an HTTP test suite but it's just shell scripts and Docker ;)
Chris Wilkinson
@thewilkybarkid
Hi all :wave: We're starting to build Hydra-based APIs so are adopting linked data. We've started with plain JSON-LD, but are looking at making use of RDF/JS in libero/article-store#64. Would be interested in any feedback, comments or suggestions. Would also be interested to find out about best practices on mixing static (eg Hydra collection) and dynamic (eg items in the collection) statements, as well as access control (eg not exposing parts of the Hydra API doc when you don’t have permission for an operation, or only exposing some statements that make up an item (eg article stored in a database) if you don't have permission to see all of it). Also, advice on persistence would be great, especially in using Postgres rather than a triple store (more details on libero/publisher#292).
(There's background on our project at https://httpapis.slack.com/archives/C1JP575EX/p1572362193080200 in case it's useful.)
Tomasz Pluskiewicz
@tpluscode
not everything strictly related to rdfjs but I can give some of my advice:
Tomasz Pluskiewicz
@tpluscode
  1. avoid URI manipulation at all cost.

for example if you have a /book/foo resource and its chapters, do not mint a /book/foo/chapters URI for a hydra:Collection. this practice will spread like wildfire across resources which are not strictly your domain and also pollute the domain identifiers too.

instead simply create the collection identifier once and persist it somewhere along your data, with a link (reference) to the book it belongs to.

I store RDF so I have </book/foo/chapters> ex:book </book/foo> and use that relation in the queries, thus avoiding the need to explicitly name any resources

an additional benefit is that if you ever change the naming scheme, nothing should break. for example when you migrate from hierarchical URIs like <book/{id}/chapter/{chapter}> to a flat structure </book/{id}> and </chapter/{id}>. the old identifiers should continue to work while the new data has a different naming space

Chris Wilkinson
@thewilkybarkid
Makes sense; so you store a minimal representation of some resources and populate the rest at runtime? (Literally just the ID/link?)
Tomasz Pluskiewicz
@tpluscode
stuff which is dynamic anyway. for a collection I guess you could also store its @type and some constant metadata
Chris Wilkinson
@thewilkybarkid
:+1:
Chris Wilkinson
@thewilkybarkid
Got a couple of RDF/JS-specific questions.
Is the Stream interface not meant to extend NodeJS.ReadableStream on object mode (in @types/rdfjs)? (Refs https://github.com/libero/article-store/pull/64#discussion_r352029306)