- From: Harold Solbrig via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Nov 2020 09:47:50 +0000
- To: public-shex-dev@w3.org
hsolbrig has just created a new issue for https://github.com/shexSpec/shex: == Blank node behavior when using SPARQL == At the moment, different ShEx implementations exhibit different behaviors when crossing BNodes in SPARQL. PyShEx has three options: 1) Throw an error when attempting to submit a SPARQL query with a BNode subject or object 2) Assume that the SPARQL endpoint maintains persistent BNodes (which may cause a hang / timeout if not true) 3) Take advantage of the GraphDB specific solution Shex.js only implements option 2) Not sure on other implementations Do we want to specify a consistent behavior across interpreters? If so, what should that be? Please view or discuss this issue at https://github.com/shexSpec/shex/issues/109 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 November 2020 09:47:51 UTC