W3C home > Mailing lists > Public > public-xg-webid@w3.org > December 2011

Re: Another Translator for RDF

From: Mo McRoberts <mo.mcroberts@bbc.co.uk>
Date: Fri, 30 Dec 2011 11:48:00 +0000
Cc: "public-xg-webid@w3.org" <public-xg-webid@w3.org>
Message-Id: <9BCEAB3C-0EEF-43FE-A5D4-397D07F253C8@bbc.co.uk>
To: Peter Williams <home_pw@msn.com>

On 30 Dec 2011, at 09:31, Peter Williams wrote:

> his #this is NOT attached to my yorkporc URI. There is no entity with such name in my card. His #this is not even attached to the (URI=typed) parameter in the translating services invocation URI.


> Onto the end of that he stuck a #this. He could have stuck a #that, but was alluding to the semantics we all know from C++'s this. We all learned #this, in moving from C to C++! (If you use extension methods in C#, its gets even more fun.)

Ahhh, okay, I see what's happening -- 


So you want to use an automated translation service to get N3 (and instead of republishing that N3, just point things at the dynamically-generated version -- certainly fine for testing).

Now, your URI (which when dereferenced results in some RDFa describing you, amongst other things)  is <http://yorkporc2.blogspot.com/#me>. Whether you're meant to include the fragment in the 'url' parameter to the translation service or not is a matter for that translation service (the fact it's a "URL" parameter suggests not, as it's a resource translation facility, but it might accept it and strip it anyway, doesnít really matter).

BUT, because it's a resource translation facility, what you feed into it ó a resource which *includes* a description of <http://yorkporc2.blogspot.com/#me> ó you get back out again, subject URIs and all. A consumer of that translated resource won't know to look at the statements with <http://yorkporc2.blogspot.com/#me> as the URI because that isn't the URI you handed the consumer for yourself.

You can add assertions, though, so you add an assertion to your source document stating that <http://yorkporc2.blogspot.com/#me> is the same as <http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3#this>. Then, you tell consumers to use that URI (complete with the #this) and they do so and find a owl:sameAs relation pointing them at <http://yorkporc2.blogspot.com/#me>, which in theory they donít need to bother fetching because it's already described in the resource they've got.

What threw me was that you hadnít got as far as adding the owl:sameAs relation to your source document, so it doesn't appear in the translated output either, and so '#this' doesn't appear anywhere.

It's a neat trick, but I can think of a couple of awkward reasons why you might not want to rely on the behaviour. Tends to be easier to use the translator to generate the format you want and the republish it with conneg switched on!

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 Friday, 30 December 2011 11:48:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 30 December 2011 11:48:48 GMT