On 3/28/12 1:29 PM, Hugh Glaser wrote:
Thanks Kingsley. On 28 Mar 2012, at 17:43, Kingsley Idehen wrote:On 3/28/12 12:10 PM, Hugh Glaser wrote:Now that Dam (sic*) Brickley has told me his Facebook ID, and I sameAs'ed it to one of his others, such as his foaf, RKBExplorer can happily tell you all about the Facebook person: http://www.rkbexplorer.com/explorer/#display=person-{http://graph.facebook.com/danbri} or http://www.rkbexplorer.com/network/?uri=http://graph.facebook.com/danbri&type=person-person&format=foafknowsn31. http://linkeddata.uriburner.com/about/html/http/acm.rkbexplorer.com/id/person-451271-2b39d8f576cc59e4495e9f18a9ff5f5b -- works fine because your page exposes @danbri's URI to my user agent 2. http://linkeddata.uriburner.com/describe/?url=http%3A%2F%2Facm.rkbexplorer.com%2Fid%2Fperson-451271-2b39d8f576cc59e4495e9f18a9ff5f5b -- faceted browsing and follow-your-nose friendly report 3. http://linkeddata.uriburner.com/c/IIOLYW -- some other folks from your data space via faceted navigation scoped to a specific class.To be brutally honest, I am not really interested in going and looking at yet more geeky renderings of RDF and related data. As I said, I am well aware of the benefits of Linked Data. What I want to see is stuff I can possible show non-LD people as useful things.Ideally, I would like to grap the subject URI from: http://www.rkbexplorer.com/explorer/#display=person-%7Bhttp%3A//acm.rkbexplorer.com/id/person-451271-2b39d8f576cc59e4495e9f18a9ff5f5b%7D, but I can't for obvious reasons. Thus, I have to click the icon beside "Dan Brickley" as you haven't anchored the text using: http://acm.rkbexplorer.com/id/person-451271-2b39d8f576cc59e4495e9f18a9ff5f5b via @href. Wondering if you could tweak this?Neither Ian or I have touched that code in 3 or 4 years, so I will need to dig into it. But I don't know what you are asking for.
I want to be able to use CTRL+RightMouse (browser context menu pattern) to start exploring the graph exposed via the URI in @href.
Do I need to add something to the fresnel generation (the Details pane) such what produces http://www.rkbexplorer.com/detail/?uri=http://southampton.rkbexplorer.com/id/person-2f876940347fe251382724b34c27346f-cb9c89b02b078212e440a8016915856a or http://www.rkbexplorer.com/detail/?uri=http://southampton.rkbexplorer.com/id/eprints-12614 Or do you want something in the main page? You probably need to explain to me off-list.
Preference: http://southampton.rkbexplorer.com/id/person-2f876940347fe251382724b34c27346f-cb9c89b02b078212e440a8016915856a -- subject URI
or in the data accessible from the following addresses, just add <link rel="related" ../> relations in <head/> which enables user agents discover associations between the following pages and the named entities they 'mention' :
1. http://www.rkbexplorer.com/detail/?uri=http://southampton.rkbexplorer.com/id/person-2f876940347fe251382724b34c27346f-cb9c89b02b078212e440a8016915856a
2. http://www.rkbexplorer.com/detail/?uri=http://southampton.rkbexplorer.com/id/eprints-12614.
Once we get past this, and subject to your server access privileges, you can replicate the <link/> relations via "Link:" header responses thereby opening up a discovery path for user agents that process HTTP response metadata.
Kingsley
Best HughMy workflow pattern (using our ODE browser extensions and bookmarklets) is outlined here, follow any of the example links: http://ode.openlinksw.com/example.html . -- 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
-- 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
smime.p7s
Description: S/MIME Cryptographic Signature
