On 4/23/13 5:04 PM, Hugh Glaser wrote:
Ah POWDER - of course. It all comes together :-) (Sorry if this is boring and obvious to others - and thanks Kingsley.) So last (?!) 2 things, if I may. Any proposal to attach types to the objects of the wdrs:desribedby triples?
So as in <http://ns.nature.com/docs/terms/datatypes/anyURI___279277607.html> you seek the xsd:anyURI type qualification, for objects of said relation, right? If yes, then fine, it can be added quickly.
Any proposal so that I can infer the available types for the whole dataset, rather than inferring from a particular resource resolution?
You mean for RDF resources such as the one denoted by <http://dbpedia.org/data/Luton.ttl> ? If yes, then we can just add the missing resource metadata relations which would basically come from VoID [1].
Links: 1. http://www.w3.org/TR/void/#class-property-partitions Kingsley
Cheers On 23 Apr 2013, at 21:48, Kingsley Idehen <[email protected]> wrote:On 4/23/13 4:23 PM, Hugh Glaser wrote:Ah, thanks for the Web101 course.:-) Sorry, I usually live in a Linked Data world, so I don't think about html stuff such as <link rel="alternate" … because (like the header) it doesn't appear in the RDF. On 23 Apr 2013, at 20:54, Kingsley Idehen<[email protected]> wrote:On 4/23/13 3:39 PM, Hugh Glaser wrote:Ah of course - thanks Mark, silly me. So I look at the Link: header for something like curl -L -ihttp://dbpedia.org/resource/Luton Which gives me the information I want. Anyone got any offers for how I would use Linked Data to get this into my RDF store?Assuming I understand your question, the answer would depend on the capabilities of your RDF store. If it can injest RDF resource URLs you can request the formats exposed on the "Link:" responses. If it handles SPARQL 1.1 INSERT and/or LOAD just use SPARQL.I don't think I can use the SPARQL INSERT, etc, because it isn't RDF. Is the <link rel="alternate" available anywhere as RDF? It could be returned with the RDF forhttp://dbpedia.org/resource/Luton Better still, it could be available in the voiD description (so that it is site-oriented, not resource-oriented)? Or somewhere else? CheersOkay, now that <link/>, "Link:", and SPARQL aren't options, of course you can get it from the RDF that describes <http://dbpedia.org/resource/Luton>, see: http://dbpedia.org/describe/?url=http%3A%2F%2Fdbpedia.org%2Fresource%2FLuton&gp=8&go= We use the wdrs:desribedby relation for that :-) -- 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
