Annotation syntax [was: SPARQL* test suite]

On 29/08/2020 20:54, Gregg Kellogg wrote:
> On Aug 29, 2020, at 12:35 PM, Andy Seaborne <andy@apache.org> wrote:
>>>>> On 28 Aug 2020, at 03:06, Holger Knublauch <holger@topquadrant.com> wrote:
>>>>
>> ...
>>
>>>> I, for one, keep being unimpressed by the Turtle syntax, which ends up becoming quite redundant because depending on the interpretation a triple needs to be stated twice (once for the actual assertion and once for the reifications). We are for now using a syntax such as
>>>>
>>>> ex:subject ex:predicate ex:object [[
>>>>      ex:created "2010-10-10"^^xsd:date ;
>>>> ]]
>>
>> Yes, there is room for annotation syntax. Stardog has the annotation after the predicate, before the object (guess: to avoid a problem with TriG). What happens about object lists?
>>
>> ]] can occur in Turtle data.
> 
> [[ can occur in Notation-3, which will eventually want compatibility with RDF*, too.
> 
>> Given that {} is used for grouping in TriG and SPARQL:
>>
>> {%...%}
>> {|...|}
>> {!...!}
>> {{...}}
> 
> Same for {{ in N3., but I do like the other suggestions.

Thanks for the reminder.

Once upon a time, {$...$} was a proposed N3 syntax for sets as literals.

     Andy

> 
> Gregg
> 
>> and some others
>> and the [%...%] (%...%) forms
>>
>> The PLX rule in Turtle is not a problem.
>>
>>     Andy
>>
>>>>
>>>> to state both at the same time, and this seems to work better. But in the absence of any formal starting point (such as a respec spec and a proper development process with regular meetings and bug tracker tickets) I guess many implementations will just go with the original syntax or diverge further. Maybe everyone here is waiting for Olaf to take more control again, but that's not really his job or responsibility and maybe it's time for the implementers to chose a chair, have a couple of meetings and establish productive processes?
>>>>
>>>> Holger
>>>>
>>>>
>>

Received on Sunday, 30 August 2020 09:09:14 UTC