- From: Hugh Glaser <hg@ecs.soton.ac.uk>
- Date: Sun, 21 Mar 2010 18:20:21 +0000
- To: Kingsley Idehen <kidehen@openlinksw.com>
- CC: Linked Data community <public-lod@w3.org>
On 21/03/2010 18:10, "Kingsley Idehen" <kidehen@openlinksw.com> wrote: > Hugh Glaser wrote: >> Hi Kingsley, I am right with you - finding stuff is hard. >> But I do think we could make it easier for all of us. >> Just the esw wiki alone requires me to put every set I create into a bunch of >> place, for example, at least: >> * [[http://esw.w3.org/TaskForces/CommunityProjects/LinkingOpenData/DataSets >> DataSets]] >> * [[http://esw.w3.org/DataSetRDFDumps RDF Dumps]] >> * [[http://esw.w3.org/SparqlEndpoints SPARQL endpoints]] >> * >> [[http://esw.w3.org/TaskForces/CommunityProjects/LinkingOpenData/DataSets/Lin >> kStatistics Link Statistics]] >> >> >> In the end, I just donšt manage it, partially because it entails editing a >> large wiki page for most (although the move to MW must be an great >> improvement). >> >> So if I find the whole thing laborious. >> Telling people to go and edit multiple pages is not really customer oriented >> (I view the publishers as our customers in the Linked Data world). >> > I agree, so what about del.icio.us bookmarks? True, it's a "bit", however it only gives a URI and some tags, but providing the metadata is more complicated. And it would be yet another place to put and find dataset metadata. >> Does anyone want to step up to the plate and do a swish repository for this >> data, with easy entry (including RESTful) and publishing as html, Linked >> Data, json etc. using voiD, etc? >> > Even better, I am sure this can be assembled in bits, as Melvin has > already demonstrated :-) Actually, what Melvin demonstrated was neat, but only about re-publishing and consuming. The trouble with "bits" is that there are usually quite a few of them, and so they (such as delicious) will only increase the number of places with which a dataset publisher needs to interact. The esw pages are exactly the sort of structured data that we claim to be able to deal with - surely someone has the tools and the time to deploy them (!) to do a proper data management of this metadata around RDF? Maybe a PG wants to use it as a use case for Linked Data research? I'm sure the Sindice team has much of the data already in RDF? Best Hugh > > Kingsley >> Best >> Hugh >> >> On 20/03/2010 20:18, "Kingsley Idehen" <kidehen@openlinksw.com> wrote: >> >> >>> All, >>> >>> I continue to struggle with easy discovery of Government oriented Linked >>> Data (UK and U.S. are examples). Basically, a long time ago, we >>> established some core principles for Linked Open Data published to the >>> Web. The components where broken down as follows: >>> >>> 1. Publish RDF Data Set archive URLs to a well known location -- >>> http://esw.w3.org/DataSetRDFDumps >>> 2. Publish SPARQL Endpoints -- e.g., <http://esw.w3.org/SparqlEndpoints> >>> 3. Publish Linked Data -- an home page or deeply linked URI will do. >>> >>> DBpedia still provides a very nice template for the above. >>> >>> Unfortunately, most of the Govt oriented Linked Data projects haven't >>> quite adopted the scheme above thereby making the process of discovering >>> items 1-3 quite tedious. >>> >>> Suggestions: >>> >>> I think we can tackle this problem by doing the following: >>> >>> 1. Use the moniker Linked Open Govt Data (LOGD) for all Govt. oriented >>> Linked Data projects >>> 2. Use #hashtag #logd on Twitter and "logd" for tagging on del.cio.us -- >>> one data is on del.icio.us or Twitter, its basically part of LOD via >>> RDFizers etc.. >>> >>> So Far I have: >>> >>> 1. http://delicious.com/kidehen/logd -- del.icio.us tag >>> >>> >> >> >
Received on Sunday, 21 March 2010 18:25:22 UTC