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

Re: Another Translator for RDF

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Thu, 29 Dec 2011 22:28:54 -0500
Message-ID: <4EFD2FF6.1040600@openlinksw.com>
To: public-xg-webid@w3.org
CC: Mitko Iliev <imitko@openlinksw.com>
On 12/29/11 9:12 PM, Kingsley Idehen wrote:
> On 12/29/11 12:32 PM, Kingsley Idehen wrote:
>> On 12/29/11 12:26 PM, Kingsley Idehen wrote:
>>> I meant:
>>>
>>> <http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3#this> 
>>>
>>> wdrs:describedby
>>> <http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3> 
>>> .
>>>
>>>
>>> Put this in your browser for implicit indirection effect:
>>> http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3#this 
>>> .
>> Peter,
>>
>> seeAlso:
>>
>> 1.  
>> http://linkeddata.informatik.hu-berlin.de/uridbg/index.php?url=http%3A%2F%2Frdf-translator.appspot.com%2Fparse%3Furl%3Dhttp%253A%252F%252Fyorkporc2.blogspot.com%252F%26of%3Dn3%23this&useragentheader=&acceptheader= 
>> -- URI Debugger output
>>
>> 2. 
>> http://validator.linkeddata.org/vapour?vocabUri=http%3A%2F%2Frdf-translator.appspot.com%2Fparse%3Furl%3Dhttp%253A%252F%252Fyorkporc2.blogspot.com%252F%26of%3Dn3%23this&classUri=http%3A%2F%2F&propertyUri=http%3A%2F%2F&instanceUri=http%3A%2F%2F&defaultResponse=dontmind&userAgent=vapour.sourceforge.net 
>> -- another Debugger (but it suffers from RDF/XML specificity so jump 
>> to its conclusion re. Object/Entity Name / Descriptor Resource 
>> Address disambiguation) .
>>
> Peter,
>
> A correction to the above.
>
> URI in SAN: 
> http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3&html=1 
> <http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3&html=1>#this 
>
>
> Means that in your (X)HTML you need to add the relation:
>
> <http://yorkporc2.blogspot.com/#me> owl:sameAs 
> <http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3&html=1 
> <http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3&html=1>#this>  
> .

First off, cut and past fix for the relation. It should be:

<http://yorkporc2.blogspot.com/#me> owl:sameAs 
<http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3&html=1#this> 


>
> Please add that to your posts and repeat your tests with our 
> validator. The relation above is crucial, I completely forget to 
> mention that :-(
>

In addition to the above, if you have two HTTP URIs in SAN:

1. http://yorkporc2.blogspot.com/#me
2. 
http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3&html=1#this 
.

A WebID verifier should really assume that you are claiming that:
<http://yorkporc2.blogspot.com/#me> and 
<http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3&html=1#this> 
are co-references for the certificate's subject .

Basically, that claim is signed and verifiable. One could go the extra 
mile on the IdP side and also sign the claim. But that's for another 
time, once we are beyond the basics :-)


Hopefully, no cut and paste craziness this time around .


Kingsley


-- 

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








Received on Friday, 30 December 2011 03:29:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 30 December 2011 03:29:33 GMT