[ckan-dev] CKAN info

[Mark Wainwright]

Hi Bert,

> I have now: (technical format for displaying it on the lod2stack overview)
>     <owl:NamedIndividual rdf:about="&localhost;CKAN">

Not sure what this bit means but I assume it's ok ...

>         <tool_description>CKAN is a registry or catalogue system for
> datasets or other "knowledge" resources. CKAN aims to make it easy
> to find, share and reuse open content and data, especially in ways that are
> machine automatable.</tool_description>

The first sentence of this description is a bit out of date. I suggest:

<tool_description>CKAN is a system for storing, cataloguing and
visualising data or other "knowledge" resources. CKAN aims
to make it easy to find, share and re-use open content and data,
especially in ways that are machine automatable.</tool_description>

> I need url license and contact details.

URL: http://ckan.org
Licence: CC BY 3.0
Contact: info at ckan.org

> Eventually, some acknowledgements to the software components that are
> embedded in the software.
> The last is I believe the right way for open-source software: namely the
> acknowledge in your high level description about the work you reuse.
> It also aids to trace some license issues if the software is going to be
> used in a commercial setting.

I don't know much about this - cc'ing to the dev list, where perhaps
someone can shed some light on what components should be mentioned.

Regards,

Mark


On 18 July 2012 09:25, Bert Van Nuffelen <bert.van.nuffelen at tenforce.com> wrote:
> Hi Darwin and Mark,
>
> can you provide me info about CKAN? For the LOD2 stack.
>
> I have now: (technical format for displaying it on the lod2stack overview)
>     <owl:NamedIndividual rdf:about="&localhost;CKAN">
>         <rdf:type rdf:resource="&lod2;Tool"/>
>         <rdfs:label xml:lang="en">CKAN</rdfs:label>
>         <tool_description>CKAN is a registry or catalogue system for
> datasets or other "knowledge" resources. CKAN aims to make it easy
> to find, share and reuse open content and data, especially in ways that are
> machine automatable.</tool_description>
>         <contributed_by_partner rdf:resource="&Partner;okfn"/>
>     </owl:NamedIndividual>
>
> I need url license and contact details.
> Eventually, some acknowledgements to the software components that are
> embedded in the software.
> The last is I believe the right way for open-source software: namely the
> acknowledge in your high level description about the work you reuse.
> It also aids to trace some license issues if the software is going to be
> used in a commercial setting.
>
> kind regards,
>
> Bert
>
>
>
>
>
> --
> Bert Van Nuffelen
>
> Semantic Technologies Software Architect at TenForce
> www.tenforce.be
>
> Bert.Van.Nuffelen at tenforce.com
> Office: +32 (0)16 31 48 60
> Mobile:+32 479 06 24 26
> skype: bert.van.nuffelen



-- 
Mark Wainwright, CKAN Community Co-ordinator
Open Knowledge Foundation http://okfn.org/
CKAN on Twitter: @CKANproject