Hi,
Yes, that's a good idea. We might also want to take this discussion
over to the dataincubator list (again! :) rather than continue here.
Cheers,
L.
On 8 June 2010 18:23, Kurt J wrote:
>> As pointed out earlier in the thread, the code for the conversion can
>> be found here:
>>
>> http://co
> As pointed out earlier in the thread, the code for the conversion can
> be found here:
>
> http://code.google.com/p/dataincubator/source/browse/#svn/trunk/discogs/scripts
>
Hi Leigh - should we go ahead and start using the issue cue associated
with that project to document the Unicode problems
Hi,
On 7 June 2010 13:51, zazi wrote:
> Hi Leigh,
>
> I contacted you a while ago re. the Discogs dataset. It would be glad,
> if you could send me the mapping code you wrote for the Discogs RDFizer.
> I plan to include such a RDFizer also in my Master-like project, so I
> would be very happy to
Hi Leigh,
I contacted you a while ago re. the Discogs dataset. It would be glad,
if you could send me the mapping code you wrote for the Discogs RDFizer.
I plan to include such a RDFizer also in my Master-like project, so I
would be very happy to have a nice starting project, where I can conti
Hi,
As already noted the discogs data is still live, but I failed to load
the void description hence the home page not resolving properly.
I'll aim to get that fixed ASAP.
As Kurt pointed out the code for the conversion is available if anyone
needs it. I was intending to try and hack up a fix fo
Kurts, Mats, Kingsley
Thanks for the info. So to clarify, there is access to a Discogs
dataset but it has the issues which you raised.
I would be interested in working on the interlinking aspect to get
resources correctly synched with dbtunes and maybe dbpedia concepts
also. Who was worki
>
> this is a data set i really want too somebody know a way around
> the unicode problem???
>
> Maybe find stuff like these "ï" with a regexp and then replace
them with the correct unicode chars.
In Python something like this looped through each line of the files should
work I think:
impor
Hellos
> The main major thing lacking now I think is links[1] to MusicBrainz, and I
> don't think that can be done without a dump. Apart from that, the mappings
> are also incomplete. The ruby code can be found at dataincubator[2].
but plz note the UTF-8 problems in the underlying dump as discuss
The main major thing lacking now I think is links[1] to MusicBrainz, and I
don't think that can be done without a dump. Apart from that, the mappings
are also incomplete. The ruby code can be found at dataincubator[2].
1.
http://blog.dbtune.org/post/2007/06/11/Linking-open-data%3A-interlinking-the
Hello,
>> Does anyone know the state of play wrt a linked dataset describing Discogs
>> (the music/record site)?
I've spent some time w/ Discogs stuff - it needs some work. The links
to DBpedia are broken b/c of some capitalization errors, and the
artist URIs and foaf:names are a bit borked b/c
On 6/3/10 7:07 AM, Matthew Rowe wrote:
Does anyone know the state of play wrt a linked dataset describing
Discogs (the music/record site)?
There have always been Virtuoso Sponger [1] Cartridges (Basic and Meta)
for Discogs.
Examples:
1.
http://linkeddata.uriburner.com/about/id/entity/http
Does anyone know the state of play wrt a linked dataset describing
Discogs (the music/record site)?
I know that Leigh Dodds did some work about a year ago [1] but it
appears that the data incubator page for the dataset is not active.
There is also a SPARQL endpoint to the data at [2] but no
12 matches
Mail list logo