Re: Important Question re. WebID Verifiers & Linked Data

On 22 Dec 2011, at 16:23, Kingsley Idehen wrote:

> 
> Turtle is missing from the list. Contemporary Linked Data tools prefer Turtle over RDF/XML. By this I mean: there are far more tools today that process Turtle than there are those that process RDF/XML.

citation?

There are lots of tools which support Turtle, and some people find it easier to read and write by hand than RDF/XML.

No software which supports Turtle is meant to be supporting that and *not* RDF/XML, given RDF/XML's position in the specs…

>> Similarly, there needs to be working somewhere which makes HTTP and HTTPS a MUST with other schemes a MAY, but reading the spec I couldn't figure out entirely where to insert it -- I think the first couple of paras of §2.1 may need rewording to make clear the relationship between the SAN URI and the document.
> 
> URI abstraction is scheme agnostic. HTTP should be a suggestion. In reality, nobody is going to make an HTTP alternative as part of their WebID implementation. At the same time, implementers will support other schemes and bridge to HTTP. A mailto: or acct: scheme URI will always be a more intuitive WebID than an http: scheme URI.

No. In reality, do this, and somebody will come along with their “WebID verification agent” which only supports their pet scheme, and claim it's perfectly in line with the specs, and the only people who will suffer will be end-users.

Whether the scheme is intuitive or not to write down and remember is slightly besides the point when the only time you see it is when you're publishing it and generating your certificate.


> Turtle has to be there right now. Keeping it out is also kinda contradictory. Remember, SPARQL query patterns used in WebID examples are based on Turtle. Without Turtle we wouldn't have SPARQL. Without SPARQL (albeit an implementation detail) you wouldn't have the exponentially growing Linked Open Data Cloud of today.

It’s not 'keeping it out', but it’s not mandated.

With each that you mandate, though, you’re increasing the burden on implementors, and DECREASING the likelihood that people who build ordinary websites will actually bother with any of it.

M.

-- 
Mo McRoberts - Technical Lead - The Space,
0141 422 6036 (Internal: 01-26036) - PGP key CEBCF03E,
Project Office: Room 7083, BBC Television Centre, London W12 7RJ



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.
					

Received on Thursday, 22 December 2011 16:33:33 UTC