Re: Moving forward with ISSUE-30 (IRI template expansion)

On 8/19/14 2:24 PM, Ruben Verborgh wrote:
>> That's true and one of the reasons I would actually prefer to get rid of
>> those Turtle artifacts.. Anyway I asked a while ago to add those angle
>> brackets to make it compatible with Turtle. Unfortunately no one commented that.
> For all IRIs? I don't see the point in that.
> It makes things more complicated without adding value.

+1000

>
>> We seem to get stuck here. Any suggestions how we could move forward? (this
>> is a question for everyone)
> Let me try to help by rephrasing the problem.
>
> a) We need to distinguish between IRIs and literals.
> i.e., the text “http://www.hydra-cg.com/” is different from
> the IRI  http://www.hydra-cg.com/.
>
> b) For literals, we should be able to add a type or a language.
>
> Nothing more is necessary; delimiting and escaping already happens.
> This contrasts with Turtle, where delimiting of multiple fields is needed,
> and where IRIs also need to be distinguished from prefixed names.
>
>
> The syntax we currently have is:
> - surround literals in double quotes
> - signify data types with @ and types with ^^
>
> This seems to be a minimal solution,
> with the added benefit that the '@' and '^^' symbols look familiar.
> There is, however, no other resemblance with N-Triples / Turtle.
>
> Do we agree or disagree on this syntax?
>
> (Perhaps it's best to talk about names after this.)

You guys should talk, and <{IRI}> shouldn't be tampered with.

>
> Best,
>
> Ruben
>


-- 
Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this