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

Re: social recasting and webid - an asde on of RE: Mandatory client supported serializations

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Sat, 31 Dec 2011 13:27:01 -0500
Message-ID: <4EFF53F5.7060404@openlinksw.com>
To: Peter Williams <home_pw@msn.com>
CC: "public-xg-webid@w3.org" <public-xg-webid@w3.org>
On 12/31/11 1:03 PM, Peter Williams wrote:
> I going to edit my little validator agent experiment today, to make further use of the linkburner sparl-protocol endpoint, doing remote query execution in the course of enforcing the SSL handshake protocol.

You mean: URIBurner, a Linked Data service that we offer to the public :-)

> I assume its owl-enabled, with reasoner.

You add this pragma to your SPARQL:
DEFINE input:same-as "yes"

Example from prior queries:

## owl:sameAs pragma. Comment out if you don't seek owl:sameAs reasoning 
applied to the SPARQL query .

DEFINE input:same-as "yes"
## pragma use end

## HTTP GET (sponging) pragma, use "add" for progressive named graph 
population, so you can add relations to the source without overwriting
## the local graph used by the Virtuoso server. Note, this is also a 
default  cache invalidation scheme override

DEFINE get:soft "add"

## pragam use end.

PREFIX : <http://www.w3.org/ns/auth/cert#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>

?s  :key [
:exponent ?exp ;
] .

>   I will need help formulating working queries that exercise some query ...working over 2 profiles, named using 2 SAN URIs from 1 cert, with 1 key.

You idp space simply needs to have owl:sameAs relations in place and the 
reasoner will handle the query solution.
> Your linkburner sparql server has an option to auto-pull owl:sameAs data from the triples*received*  from the securely-named endpoint, when its "useful" to do so, in the course of preparing data for local querying.

The pragma: define get:soft "{add | replace | soft}" handles resource 
retrieval modalities.
The pragma: define input:same-as "yes" handles enabling or disabling of 
the OWL reasoner.

>   I want to see the utility of  what we have been discussing. I want (as the worlds worst programmer) to be able to do it, so we know its real fo all the class (not just those who get As) .


Also note you could also test the inversefunctional property relation 
option by declaring cert:key as being an IFP and then making a custom 
inference rule that's invoked by a pragma. For the URIBurner instance, 
I'll have to set up that rule once you are ready to test that scenario. 
All you have to do is associate two URIs with the same public key in 
your idp space modulo owl:sameAs relation.

>   Then the rest of the world can copy it. Using a remote sparql protocol server for this seems ideal, since its now acting as a trust resolver (leveraging equivalence relations). using a sparql server guarded by webid validation is even better, as a "system" of trusted agents start to come into being.

Yes, we can WebID protect the sparql endpoint. Basically, that's what 
we'll soon enact re. id.myopenlink.net, we've been waiting for an 
external QA tester like you for a few years now!

> I want to be able to test for membership of two profiles in a given equivalence class. The class itself will be distinguishsed using a data URI with certain integrity properties that detect tampering, and webid validation agents (and the SSL handshake) will prove that the profiles do participate in that particular equivalency class. Since the class apparatus is based on the  canonical nature of the public key in the data URI, it obviously scales to any size of equivalencies we want, suit the million person world of (wholly de-centralized) realty trust networks based on the individual (and her 20 local friends, neighbors, and business associates).

This is the game, right here!



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 Saturday, 31 December 2011 18:27:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:28 UTC