- From: Steven Adler <adler1@us.ibm.com>
- Date: Mon, 27 Apr 2015 15:16:17 -0400
- To: "yaso@nic.br" <yaso@nic.br>
- Cc: public-dwbp-wg@w3.org
- Message-ID: <OF473FE289.7CC36162-ON85257E34.0069B359-85257E34.0069DC77@us.ibm.com>
This kind of iterative interaction on improving DQ makes a fantastic BP
recommendation. It enhances trust between publishers and consumers, builds
a feedback loop on DQ, and augments publisher resources.
We should flesh this out and look for more use cases to validate and test
it.
Best Regards,
Steve
Motto: "Do First, Think, Do it Again"
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|"yaso@nic.br" <yaso@nic.br> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|public-dwbp-wg@w3.org |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|04/27/2015 03:08 PM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: DBpedia - Usage Example |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Hi Eric!
Interesting thread. In 2013 we held a hackathon with the Ministry of
Justice and the datasets were terrible, full of errors and missing
semantic. When the ministry released the datasets the teams organized the
issues on github [1] (here comes yaso with github again, lol) and we keep
the interactions upon the dataset improvements at a conversation in a mail
list [2].
To the extent that the dataset was being "repaired" the ministry improved
other datasets that was in "the line" for opening. But only because we had
use cases (the apps) to where improvements were important.
I imagine that this kind of interaction upon a dataset is not yet a
widespread method of working with data, at least in governamental sphere. I
like the idea of cycles of improvements based on usage of data, provoked by
standardized feedback and other ways of conversations and also like the
idea of tracking usage of data. I can imagine that it would be really
useful, but still have not imagined a way to implement it without taking
advantage of usage of 2 or more tools at the same time :-)
yaso
[1] https://github.com/W3CBrasil/PerguntasMJ/issues?q=is%3Aissue
+is%3Aclosed
[2] https://groups.google.com/forum/#!topic/dadosabertosmj
On 04/27/2015 01:20 PM, Eric Stephan wrote:
Hi Laufer,
I’ve been thinking about the DBpedia dataset example over the
weekend. This may not be what you are looking for, but thinking
about the DBpedia example generated many ideas that may be useful as
we discuss how we implement Dataset Usage Vocabulary concepts in the
real world.
DBpedia is one of the premier off the chart rock stars of datasets I
find it the very opposite of many obscure scientific datasets that I
am more accustomed. My first reaction when you provided the links to
DBpedia applications I thought this example was much to trivial
depicting associations between the dataset and the application links.
However the more I thought about this rockstar dataset, the more I
got to thinking about “who” was talking about usage of the dataset,
“who” was talking about applications and experiences with the
dataset. Was I ever wrong to think your posed example problem was
trival.
Here’s what I found:
Twitter feeds, Reddit, Tumblr, Youtube, Github, scholar.google.com
are all talking about DBpedia data usage in blogs, forums, code
repositories etc. The dataset usage discussions are happening in
multiple natural languages. These discussions involved experts and
novices.
The problem is that all of these wonderful knowledge exchanges are
happening in a variety of forms and there is no composite way to
complete my understanding about DBpedia dataset application usage.
One possible application from a consumer perspective of the dataset
usage vocabulary is that I have a service that can periodically
search these services and maintain a database composite picture of
dataset usage using the Dataset Usage Vocabulary as a common
representation that may describe experiences using the SPARQL API and
tools and example queries that are refinements of what is provided by
DBpedia. >From the dataset publisher perspective this same
application could help aid in discovering what people are discussing
that aren’t directly reported to the website.
Sumit and I are meeting with a group of scientists tomorrow to
explore how scientists can explore the deep web more effectively for
climate research.
I don't know if this is useful to you, but I'm curious as to what you
and others in the group think of the "usage" of the Dataset Usage
Vocab.
Cheers,
Eric S
On Fri, Apr 24, 2015 at 5:18 PM, Eric Stephan <ericphb@gmail.com>
wrote:
Laufer,
Great idea, perhaps this would be another example I could work
through...keep these ideas coming :-)
Eric
On Fri, Apr 24, 2015 at 4:52 PM, Laufer <laufer@globo.com> wrote:
Hi Eric,
Maybe would be interesting to see how DUV could be used with
DBpedia.
There is a web page with a list of applications that use the
Dataset:
http://wiki.dbpedia.org/Applications
There is another web page that explain the online access to the
Dataset:
http://wiki.dbpedia.org/OnlineAccess
Cheers,
Laufer
--
. . . .. . .
. . . ..
. .. .
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: ecblank.gif
Received on Monday, 27 April 2015 19:17:02 UTC