asami

Asami, the graph database https://github.com/threatgrid/asami
2021-05-11T21:22:40.340300Z

Yeah, you can have : in prolog atoms and predicates too. At least it’s supported in SWI prolog, I suspect most other prologs too.

2021-05-11T21:24:00.340600Z

I tried finding a canonical reference for you, but most descriptions of the syntax are informally specified. Unfortunately the ISO standard is paywalled.

2021-05-11T21:25:20.340800Z

ISO prolog was I believe largely derived from Edinburgh prolog… but I can’t find any good references their either. I think most implementers don’t care much for ISO prolog tbh

quoll 2021-05-11T21:54:43.341200Z

It looks like adding an extra tag would be appropriate

quoll 2021-05-11T21:56:14.341400Z

A familiar syntax would be to add a tag like this to the comments:

@prefix rdf: &lt;<http://www.w3.org/1999/02/22-rdf-syntax-ns#>&gt; .

2021-05-11T22:13:31.341600Z

Do you mean literally that? Or putting it in a pabu comment? e.g.

%@prefix rdf: &lt;<http://www.w3.org/1999/02/22-rdf-syntax-ns#>&gt; .

quoll 2021-05-11T22:15:29.341900Z

in a comment

quoll 2021-05-11T22:15:50.342100Z

That way it would look like a SWI-Prolog structured comment

quoll 2021-05-11T22:16:39.342300Z

It would just be a new tag https://www.swi-prolog.org/pldoc/man?section=tags

2021-05-11T22:19:04.342500Z

Incidentally the standards body added to turtle 1.1 SPARQL like prefix support in addition to @prefix So arguably because of SPARQL PREFIX rdf: &lt;<http://www.w3.org/1999/02/22-rdf-syntax-ns#>&gt; is more well known. Obviously that won’t align with a swipl comment tag

2021-05-11T22:22:27.342700Z

Incidentally I think those tagged comments might only be expected inside /** comment blocks */

quoll 2021-05-11T22:22:40.342900Z

honestly, I always forgot which syntax did which. I copy/pasted and focused either on data or on queries.

2021-05-11T22:23:36.343100Z

Yeah me too… it’s just frustrating when you copy/paste a turtle @style one into a SPARQL query 😩 or you skip the @ but leave the .

quoll 2021-05-11T22:25:41.343400Z

Go to the SPARQL query doc, and the first appearance of a prefix syntax is section https://www.w3.org/TR/sparql11-query/#docDataDesc: > This document uses the http://www.w3.org/TR/turtle/ [https://www.w3.org/TR/sparql11-query/#TURTLE] data format to show each triple explicitly. Turtle allows IRIs to be abbreviated with prefixes:

@prefix dc:   &lt;<http://purl.org/dc/elements/1.1/>&gt; .
@prefix :     &lt;<http://example.org/book/>&gt; .
:book1  dc:title  "SPARQL Tutorial" .

quoll 2021-05-11T22:26:45.343600Z

The query form is almost identical except: • no @ • no trailing .

2021-05-11T22:27:08.343800Z

IKR 😩

quoll 2021-05-11T22:27:12.344Z

I do like SPARQL, but some parts of it frustrate me no end

2021-05-11T22:27:16.344200Z

yeah

quoll 2021-05-11T22:27:55.344400Z

I’m hoping to put a SPARQL front-end over Asami. If I ever get the time

2021-05-11T22:29:00.344600Z

TBH I might mention that on the SPARQL 1.2 issues…. they should really axe that @prefix dc: .... stuff from the document and use the turtle 1.1 style to help prevent confusion.

quoll 2021-05-11T22:32:17.344900Z

If you recall the https://youtu.be/oyLBGkS5ICk?list=PLZdCLR02grLofiMKo0bCeLHZC0_2rpqsz from the 2016 Conj, he said that you shouldn’t axe anything 🙂

quoll 2021-05-11T22:32:28.345100Z

But I’d be all for accepting both forms

2021-05-11T22:35:55.345300Z

Yeah I’m definitely not suggesting axing support for it all, it should remain standardised in turtle. I’m just suggesting that the SPARQL 1.2 sample data should be updated to use the turtle 1.1 feature (of SPARQL style PREFIX: blocks; i.e. a small step to preventing the confusion.

2021-05-11T22:37:47.345600Z

Granted it might further add to that confusion; but it will at least mean people copy/pasting example data in that document into sparql etc won’t trip up.

2021-05-11T22:38:14.345800Z

Anyway this is an irrelevance 🙂