- From: Samu Láng <langsamu@hotmail.com>
- Date: Wed, 25 Mar 2026 21:47:56 +0000
- To: public-rdfjs@w3.org
- Message-ID: <CAAB8E647OkU09dyPKGKp0jXa8QW_A40voUERKHUrdv6EG7-07w@mail.gmail.com>
Why are none of the methods in RDF/JS asynchronous and could we make them such? In a recent discussion of the Solid Open-source Tools group <https://hackmd.io/_jbi_VaRRP69YjJEBdxeDg#RDFJS-Async> (whose members tend to be heavily invested in both RDF and JavaScript), I had asked whether I was the only one struggling with the lack of asynchronicity in RDF/JS. Specifically I mean asynchronicity in the sense of the `async` and `await` keywords in JavaScript, of methods that return `Promise`s. As an implementer of software that adheres to the RDF/JS: Data model specification and the RDF/JS: Dataset specification, I frequently come up against the problem of using synchronous methods like `DatasetCore.match` in contexts that favor it nowadays like network IO and background processing. My fellow implementers/users of RDF/JS reported that they struggle with the same issue and tend to go through hoops to make RDF/JS work in 'modern' context. My question is generic and open: Was there any thought given to this? Was it discarded? Or have we just come some way since? How would we go on about adding asynchronicity to RDF/JS? Is there history worth reading about the topic? I have searched the mailing list and GitHub for relevant information and haven't found any. I apologize if I'm reopening a long dormant debate and would appreciate pointers to previous discussion.
Received on Wednesday, 25 March 2026 21:55:26 UTC