- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Wed, 20 Aug 2014 14:40:18 +0200
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: public-hydra@w3.org
> Yep. The question is how similar they will be. Or, in other words, how easy
> is it to distinguish them.
Very easy for machines, who are the main (only?) users.
They just read the variableRepresentation property to find out what they should do.
And maybe that's a point we shouldn't forget:
there's not much opportunity for error, as machines will use the templates, not us.
>>> """Markus"""^^<http://www.w3.org/2001/XMLSchema#string>
>>> """Markus"""^^http://www.w3.org/2001/XMLSchema#string
>>
>> Note that these mean different things anyway!
>> In our template syntax, it would express the string:
>> ""Markus"" In Turtle syntax, It would express the string: Markus
>
> Right, that was the point I was trying to make. Especially if you are used
> to Turtle, it is very easy to miss the fact that the angular brackets are
> missing in the second example.
I'd argue the first case is more confusing then. It has angular brackets,
but still parses to {""Markus""}, not {Markus}.
> Perhaps just using different delimiters?
Yet that still doesn't help literals without language or type. E.g.,:
"Mar\'kus"
parses to {Mark'us} in Turtle, but to {Mark\'us} in templates.
Best,
Ruben
Received on Wednesday, 20 August 2014 12:40:50 UTC