[ckan-dev] CKAN-specific considerations for DCAT-AP

Florian.Brucker at mb.karlsruhe.de Florian.Brucker at mb.karlsruhe.de
Mon Dec 19 09:03:43 UTC 2016


Dear Tim,

your profile would definitely be a great help! Since others may be in the 
same situation as me you could also think about posting the files on 
GitHub or something similar.


Regards,
Florian


"ckan-dev" <ckan-dev-bounces at lists.okfn.org> schrieb am 16.12.2016 
14:58:05:

> Von: Timothy Giles <timothy.giles at slu.se>
> An: CKAN Development Discussions <ckan-dev at lists.okfn.org>, 
> Datum: 16.12.2016 14:58
> Betreff: Re: [ckan-dev] CKAN-specific considerations for DCAT-AP
> Gesendet von: "ckan-dev" <ckan-dev-bounces at lists.okfn.org>
> 
> I can send you are profile, but they are specific to our metadata 
schema.
> 
> I cant say I am an expert on DCAT AP ? the most confusing issue is 
> the various examples I find around the web that don?t work with 
> validators! We want to connect to oppna data .se and they have 
> examples but these don?t validate fully in their sandbox system? 
> But, it is still pretty easy to change. I will send you our schema 
> document, json and the profile early next week.
> 
> Regards Tim
> 
> From: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org] On Behalf Of 
> Florian.Brucker at mb.karlsruhe.de
> Sent: den 16 december 2016 13:29
> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
> Subject: Re: [ckan-dev] CKAN-specific considerations for DCAT-AP
> 
> Dear Timothy, 
> 
> thanks for the feedback! Nice to hear that things are working well. 
> Is there anything that worked particularly well or not? Anything to 
> watch out for when defining the profile? 
> 
> Are your adaptions to ckanext-dcat available somewhere? 
> 
> 
> Regards, 
> Florian 
> 
> 
> 
> 
> "ckan-dev" <ckan-dev-bounces at lists.okfn.org> schrieb am 16.12.2016 
11:17:28:
> 
> > Von: Timothy Giles <timothy.giles at slu.se> 
> > An: CKAN Development Discussions <ckan-dev at lists.okfn.org>, 
> > Datum: 16.12.2016 11:17 
> > Betreff: Re: [ckan-dev] CKAN-specific considerations for DCAT-AP 
> > Gesendet von: "ckan-dev" <ckan-dev-bounces at lists.okfn.org> 
> > 
> > Hi Florian, 
> > 
> > We use CKANEXT-DCAT as a base and have a custom DCAT AP 1.1 profile 
> > defined. It is easy to do, using the current profile as a base. If 
> > you know DCAT and have the profile mapped out already, it is a few 
> > hours work to implement. 
> > 
> > Regards Timothy 
> > 
> > From: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org] On Behalf Of 
> > Florian.Brucker at mb.karlsruhe.de
> > Sent: den 16 december 2016 11:10
> > To: ckan-dev at lists.okfn.org
> > Subject: [ckan-dev] CKAN-specific considerations for DCAT-AP 
> > 
> > Hi! 
> > 
> > The German council responsible for the metadata standard for open 
> > government data  has recently decided to develop a custom DCAT-AP 
> > profile "DCAT-AP.DE". That profile will be used for collecting and 
> > exchanging meta data in the open data portals of the German 
> > administration (on federal, state and municipal level). Many of the 
> > German open data portals are CKAN-based, so I'm wondering if there's
> > anything CKAN-specific that we should keep in mind while developing 
> > DCAT-AP.DE. I'm aware of ckanext-dcat but have never used it myself. 
> > 
> > Does anybody have experiences with using CKAN for DCAT-AP and 
> > profiles derived from it? 
> > 
> > Thanks for any input! 
> > 
> > 
> > Regards, 
> > Florian_______________________________________________
> > ckan-dev mailing list
> > ckan-dev at lists.okfn.org
> > https://lists.okfn.org/mailman/listinfo/ckan-dev
> > Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20161219/1cc311d2/attachment-0003.html>


More information about the ckan-dev mailing list