Re: TriG and default graphs

On 10/24/12 12:29 PM, Yves Raimond wrote:
> Hello!
>
> Just jumping on the last point that was mentioned in today's telecon, about possibly not providing any statements about what to do with a TriG default graph. I have the feeling that not doing that actually defeats the point of having a default graph at all.
>
> If we can't get to an agreement on that first point, I'd really like to understand what the rationale is behind supporting default graphs in TriG, apart from backward-compatibility. When used at the BBC, default graphs have proven to be a very confusing feature, and not having any statement on what do with them would only add to the confusion.
>
> All the dataset metadata that is supposed to go in that default graph could perfectly go in another named graph, e.g. identified by the URI of the sd:Dataset in the SPARQL end-point you're generating a TriG dump from, or the URI of the TriG file itself. Personally, I'd favour a 'flat' version of TriG, where everything is a named graph.
>
> Best,
> Yves

For the record.

+1

Every useful thing needs to have a Name.

Kingsley
>
>
> -----------------------------
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and
> may contain personal views which are not the views of the BBC unless specifically stated.
> If you have received it in
> error, please delete it from your system.
> Do not use, copy or disclose the
> information in any way nor act in reliance on it and notify the sender
> immediately.
> Please note that the BBC monitors e-mails
> sent or received.
> Further communication will signify your consent to
> this.
> -----------------------------
>
>


-- 

Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen