No subject


Thu Oct 25 19:26:07 UTC 2012


.rdf)
so its lifespan is probably only as long as they are still available.
 Sorry it lack of documentation caused you to do more work than necessary
:( You can override that template if you'd like to tweak the DCAT though.

I think deprecating ckanext-rdf was, at the time, the correct thing to do,
but perhaps with a bit of polish and optimisation it could be useful again?
 Would definitely be the right place to add VoID support I think if the
deps for the package could be reduced.  I know the templating of the format
probably isn't ideal, but it *is* fast.

I'm not sure of what the CKAN team's plans are for linked-data, but I'll
see if I can find out what our plans are at data.gov.uk when I'm back at
work next week.  Failing that, I'm happy to help anyone in the community
who might want some help on the CKAN side in implementing this stuff.

Ross








On Fri, Feb 15, 2013 at 5:32 PM, Timothy Lebo <lebot at rpi.edu> wrote:

> Ross,
>
> I'd love if CKAN used VoID (or, DCAT) natively.
>
> It certainly would help me access the listings in an arbitrary CKAN.
>
> For example, it was a bit more difficult than we would have hoped for us
> to get the entries from http://hub.healthdata.gov/dataset (some notes
> at [1]).
>
> It would have been great to just grab  http://hub.healthdata.gov<http://h=
ub.healthdata.gov/dataset>/void.ttl
> and run with the RDF descriptions of all the datasets (some notes at [2])=
.
> Or -- even better -- just conneg http://hub.healthdata.gov/dataset with
> an Accept: application/rdf+xml=85 (several other ways are mentioned in [2=
]).
>
> Please note that W3C's DCAT [3] can be used to describe _any_ kind of
> dataset, not just RDF datasets.
> We ended up crawling CKAN to produce DCAT entries for all of its datasets
> (notes at [4];  an example at [5] which includes W3C's PROV-O assertions =
at
> two levels).
>
> I think VoID should be seen as a special case of DCAT, in the case where
> one has RDF datasets.
>
> There are some nice features that VoID offers that DCAT does not (such as
> the "top level" http://hub.healthdata.gov<http://hub.healthdata.gov/datas=
et>/void.ttl file
> to "just get the listing"), and CKAN's needs could inspire the W3C GLD te=
am
> to get them into DCAT, which is still in development.
>
> Regards,
> Tim Lebo
>
> [1]
> https://github.com/jimmccusker/twc-healthdata/wiki/Accessing-CKAN-listing=
s
> [2]
> https://github.com/jimmccusker/twc-healthdata/wiki/Using-VoID-for-Accessi=
bility
> [3] http://www.w3.org/2011/gld/wiki/Data_Catalog_Vocabulary
> [4]
> https://github.com/jimmccusker/twc-healthdata/wiki/Retrieving-CKAN%27s-Da=
taset-Distribution-Files<https://github.com/jimmccusker/twc-healthdata/wiki=
/Retrieving-CKAN's-Dataset-Distribution-Files>
> [5]
> https://github.com/jimmccusker/melagrid/blob/master/data/source/data-mela=
grid-org/e-geod-11584/access.ttl
>
>
> On Feb 15, 2013, at 12:01 PM, Ross Jones <ross at servercode.co.uk> wrote:
>
> I've been looking at http://www.w3.org/TR/void/ and thought it might be
> worth taking a look at implementing it for CKAN as it has been asked for
> more than once, and seems like a useful way of finding the datasets that
> are available as RDF.
>
> As CKAN doesn't really model the relationships between datasets, other
> than membership of groups, I wondered whether it would be enough for the
> void file to simply be a collection of void:Datasets so that at least it
> would aid in discovery via void.(rdf|ttl) even if it didn't attempt to
> describe the relationships between them?
>
> Any suggestions, or general guidance appreciated.
>
> Ross
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
>

--089e01182b263d72bf04d5c78de4
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Tim,<div><br></div><div><div style>Content negotiation =
or adding .rdf to the dataset URL should get you the RDF repr of the meta-d=
ata, even on 2.x (see=A0<a href=3D"http://hub.healthdata.gov/dataset/adopti=
on-foster-care-analysis.rdf">http://hub.healthdata.gov/dataset/adoption-fos=
ter-care-analysis.rdf</a>). =A0</div>
<div style><br></div><div style>From a quick glance it is still using the l=
egacy_templates (<a href=3D"https://github.com/okfn/ckan/blob/master/ckan/t=
emplates_legacy/package/read.rdf">https://github.com/okfn/ckan/blob/master/=
ckan/templates_legacy/package/read.rdf</a>) so its lifespan is probably onl=
y as long as they are still available. =A0Sorry it lack of documentation ca=
used you to do more work than necessary :( You can override that template i=
f you&#39;d like to tweak the DCAT though.</div>
<div style><br></div><div style>I think deprecating ckanext-rdf was, at the=
 time, the correct thing to do, but perhaps with a bit of polish and optimi=
sation it could be useful again? =A0Would definitely be the right place to =
add VoID support I think if the deps for the package could be reduced. =A0I=
 know the templating of the format probably isn&#39;t ideal, but it *is* fa=
st.</div>
<div style><br></div><div style>I&#39;m not sure of what the CKAN team&#39;=
s plans are for linked-data, but I&#39;ll see if I can find out what our pl=
ans are at <a href=3D"http://data.gov.uk">data.gov.uk</a> when I&#39;m back=
 at work next week. =A0Failing that, I&#39;m happy to help anyone in the co=
mmunity who might want some help on the CKAN side in implementing this stuf=
f.</div>
<div style><br></div><div style>Ross</div><div style><br></div><div style><=
br></div><div style><br></div><div style><br></div><div style><br></div><di=
v><br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Fri, Feb 15, 2013 at 5:32 PM, Timothy Lebo <span dir=3D"ltr">&lt;<a href=
=3D"mailto:lebot at rpi.edu" target=3D"_blank">lebot at rpi.edu</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div style=3D"word-wrap:break-word">Ross,<div><br></div><d=
iv>
I&#39;d love if CKAN used VoID (or, DCAT) natively.</div><div><br></div><di=
v>It certainly would help me access the listings in an arbitrary CKAN.</div=
><div><br></div><div>For example, it was a bit more difficult than we would=
 have hoped for us to get the entries from=A0<a href=3D"http://hub.healthda=
ta.gov/dataset" target=3D"_blank">http://hub.healthdata.gov/dataset</a>=A0(=
some notes at=A0[1]).</div>
<div><br></div><div>It would have been great to just grab=A0=A0<a href=3D"h=
ttp://hub.healthdata.gov/dataset" target=3D"_blank">http://hub.healthdata.g=
ov</a>/void.ttl and run with the RDF descriptions of all the datasets (some=
 notes at [2]).</div>
<div>Or -- even better -- just conneg=A0<a href=3D"http://hub.healthdata.go=
v/dataset" target=3D"_blank">http://hub.healthdata.gov/dataset</a>=A0with a=
n Accept: application/rdf+xml=85 (several other ways are mentioned in [2]).=
</div>
<div><br></div><div>Please note that W3C&#39;s DCAT [3] can be used to desc=
ribe _any_ kind of dataset, not just RDF datasets.</div><div>We ended up cr=
awling CKAN to produce DCAT entries for all of its datasets (notes at [4]; =
=A0an example at [5] which includes W3C&#39;s PROV-O assertions at two leve=
ls).</div>
<div><br></div><div>I think VoID should be seen as a special case of DCAT, =
in the case where one has RDF datasets.</div><div><br></div><div>There are =
some nice features that VoID offers that DCAT does not (such as the &quot;t=
op level&quot;=A0<a href=3D"http://hub.healthdata.gov/dataset" target=3D"_b=
lank">http://hub.healthdata.gov</a>/void.ttl=A0file to &quot;just get the l=
isting&quot;), and CKAN&#39;s needs could inspire the W3C GLD team to get t=
hem into DCAT, which is still in development.</div>
<div><br></div><div>Regards,</div><div>Tim Lebo</div><div><br></div><div>[1=
]=A0<a href=3D"https://github.com/jimmccusker/twc-healthdata/wiki/Accessing=
-CKAN-listings" target=3D"_blank">https://github.com/jimmccusker/twc-health=
data/wiki/Accessing-CKAN-listings</a></div>
<div>[2]=A0<a href=3D"https://github.com/jimmccusker/twc-healthdata/wiki/Us=
ing-VoID-for-Accessibility" target=3D"_blank">https://github.com/jimmccuske=
r/twc-healthdata/wiki/Using-VoID-for-Accessibility</a></div><div>[3]=A0<a h=
ref=3D"http://www.w3.org/2011/gld/wiki/Data_Catalog_Vocabulary" target=3D"_=
blank">http://www.w3.org/2011/gld/wiki/Data_Catalog_Vocabulary</a></div>
<div>[4]=A0<a href=3D"https://github.com/jimmccusker/twc-healthdata/wiki/Re=
trieving-CKAN&#39;s-Dataset-Distribution-Files" target=3D"_blank">https://g=
ithub.com/jimmccusker/twc-healthdata/wiki/Retrieving-CKAN%27s-Dataset-Distr=
ibution-Files</a></div>
<div>[5]=A0<a href=3D"https://github.com/jimmccusker/melagrid/blob/master/d=
ata/source/data-melagrid-org/e-geod-11584/access.ttl" target=3D"_blank">htt=
ps://github.com/jimmccusker/melagrid/blob/master/data/source/data-melagrid-=
org/e-geod-11584/access.ttl</a></div>
<div><br></div><div><br><div><div><div class=3D"h5"><div>On Feb 15, 2013, a=
t 12:01 PM, Ross Jones &lt;<a href=3D"mailto:ross at servercode.co.uk" target=
=3D"_blank">ross at servercode.co.uk</a>&gt; wrote:</div><br></div></div><bloc=
kquote type=3D"cite">
<div><div class=3D"h5"><div dir=3D"ltr">I&#39;ve been looking at <a href=3D=
"http://www.w3.org/TR/void/" target=3D"_blank">http://www.w3.org/TR/void/</=
a>=A0and thought it might be worth taking a look at implementing it for CKA=
N as it has been asked for more than once, and seems like a useful way of f=
inding the datasets that are available as RDF.<div>


<br></div><div>As CKAN doesn&#39;t really model the relationships between d=
atasets, other than membership of groups, I wondered whether it would be en=
ough for the void file to simply be a collection of void:Datasets so that a=
t least it would aid in discovery via void.(rdf|ttl) even if it didn&#39;t =
attempt to describe the relationships between them?</div>


<div><br></div><div>Any suggestions, or general guidance appreciated.</div>=
<div><br></div><div>Ross</div><div><br></div></div></div></div>
_______________________________________________<br>ckan-dev mailing list<br=
><a href=3D"mailto:ckan-dev at lists.okfn.org" target=3D"_blank">ckan-dev at list=
s.okfn.org</a><br><a href=3D"http://lists.okfn.org/mailman/listinfo/ckan-de=
v" target=3D"_blank">http://lists.okfn.org/mailman/listinfo/ckan-dev</a><br=
>
Unsubscribe: <a href=3D"http://lists.okfn.org/mailman/options/ckan-dev" tar=
get=3D"_blank">http://lists.okfn.org/mailman/options/ckan-dev</a><br></bloc=
kquote></div><br></div></div><br>__________________________________________=
_____<br>

ckan-dev mailing list<br>
<a href=3D"mailto:ckan-dev at lists.okfn.org">ckan-dev at lists.okfn.org</a><br>
<a href=3D"http://lists.okfn.org/mailman/listinfo/ckan-dev" target=3D"_blan=
k">http://lists.okfn.org/mailman/listinfo/ckan-dev</a><br>
Unsubscribe: <a href=3D"http://lists.okfn.org/mailman/options/ckan-dev" tar=
get=3D"_blank">http://lists.okfn.org/mailman/options/ckan-dev</a><br>
<br></blockquote></div><br></div></div><div class=3D"gmail_extra"><br></div=
></div>

--089e01182b263d72bf04d5c78de4--



More information about the ckan-dev mailing list