Re: DBpedia - Usage Example

Hi, Eric,

I think DUV could be a vocabulary to semantically describe all this
conversations and feedbacks about the usage of a specific Dataset.

Some of these conversations could be captured, for example, by a form of
contact (a channel) provided by the publisher. Other conversations and
feedbacks will be spread in a lot of other channels like tweets, forums,
papers, journals, magazines, etc., and could be collected by specialized
crawlers, and other services.

All of these forms of collecting data, I think, are out of scope of the
group (maybe a BP for providing feedback channels by publishers). But DUV
could be the vocabulary for describing all these world of data around the
Dataset usage.

It is very important and valuable to know the usage. Tools will be
naturally developed to collect these data (IMHO).

Cheers,
Laufer

2015-04-27 13:20 GMT-03:00 Eric Stephan <ericphb@gmail.com>:

> 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
>>>
>>>
>>>
>>> --
>>> .  .  .  .. .  .
>>> .        .   . ..
>>> .     ..       .
>>>
>>
>>
>


-- 
.  .  .  .. .  .
.        .   . ..
.     ..       .