[ckan-discuss] Fwd: CKAN feature roadmap. Support VOID files and SPARQL service description

[Mark Wainwright]

This is interesting, though I'm not sure how it would work in
practice. E.g. would it be sufficient for you to have a tool you could
run (by invoking something like "voidckanupdate void.rdf
http://datahub.io") which automatically extracted the information you
wanted to record from the VoID file, and updated the Datahub via the
API?

Mark


On 04/07/2013, Jerven Bolleman <me at jerven.eu> wrote:
> The number of triples. number of links to other datasets, last update
> etc...
>
> Mainly we need one point for maintaining this kind of data that is pulled.
> Instead of the current approach of
> visit datahub.io make changes manually
> visit identifiers.org make changes manually
> visit biodbcore make changes manually
> etc...
>
> i.e. currently as a large data provider we need to visit quite a lot of
> this kind of site to fill in and maintain all dataset meta data.
> This is not sustainable which is why I am happy that the other sites are
> looking into parsing VoID files.
> I hope that the datahub.io can do so as well.
>
> Regards,
> Jerven
>
>
>
> On Thu, Jul 4, 2013 at 3:32 PM, Mark Wainwright
> <mark.wainwright at okfn.org>wrote:
>
>> Hmm, I guess the common use case is for metadata that doesn't change
>> every month (address, type, description, licence, etc). What is it
>> you're updating monthly? What specific functionality on the Datahub
>> are you suggesting?
>>
>> Mark
>>
>> On 04/07/2013, Jerven Bolleman <me at jerven.eu> wrote:
>> > Hi All,
>> >
>> > This is a desired feature to remove manual overhead of maintaining the
>> same
>> > dataset information in many different databases of databases.
>> >
>> > For example the UniProt sparql endpoint has meta data in its service
>> > description. That you can retrieve here
>> >
>> > wget --header="Accept:application/rdf+xml"
>> > "http://beta.sparql.uniprot.org/"
>> > (Expect major improvements to this output in the coming months)
>> >
>> > Or the attached void file.
>> >
>> > Instead of us updating all this information manually everymonth we
>> > would
>> > rather generate a single void file. That other tools and list than
>> datahub
>> > could use as well.
>> >
>> > Regards,
>> > Jerven
>> >
>> > PS. now with gzipped void file.
>> >
>> >
>> > --
>> > Jerven Bolleman
>> > me at jerven.eu
>> >
>>
>>
>> --
>> Business development and user engagement manager
>> The Open Knowledge Foundation
>> Empowering through Open Knowledge
>> http://okfn.org/  |  @okfn  |  http://ckan.org  |  @CKANproject
>>
>
>
>
> --
> Jerven Bolleman
> me at jerven.eu
>


-- 
Business development and user engagement manager
The Open Knowledge Foundation
Empowering through Open Knowledge
http://okfn.org/  |  @okfn  |  http://ckan.org  |  @CKANproject