W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > January 2015

Re: The Data Portal use cases

From: Holger Knublauch <holger@topquadrant.com>
Date: Tue, 27 Jan 2015 09:42:06 +1000
Message-ID: <54C6D0CE.8030300@topquadrant.com>
To: RDF Data Shapes Working Group <public-data-shapes-wg@w3.org>

On 1/26/15, 6:32 PM, Jose Emilio Labra Gayo wrote:
> You can say that this is hypothetical, but that can occur in practice 
> and we should handle it.
...

> Yes, this is hypothetical. The use case was inspired by this story, 
> but once we published the data portals, our work was done.

I would really prefer to have real examples, how else can I provide 
examples to illustrate how LDOM would be used. There seem to be many 
misunderstandings floating around that I'd like to resolve.

> However, one of the main reasons to publish a data portal, is that the 
> data can be easily reused and consumed by third parts.

Yep, that's why ontologies were invented.

>
> And I think that is one of the missing pieces of linked data in 
> general, that it is not easy for third parties to know what data is 
> available behind data portals and sparql endpoints. One motivating 
> scenarios and probably another user story is when a third party wants 
> to consume data from other data portals.

Well, for SPARQL endpoints there is VOID for example, which uses class 
definitions and rdf:types:

http://www.w3.org/TR/void/#class-property-partitions

>
> In this case, the idea that both portals contain statistical data from 
> a very similar domain following the same RDF Data cube vocabulary 
> could easily lead to some company to create a visualization tool 
> aggregating the data from those data portals...that tool could take 
> the shapes descriptions and adapt its behavior according to them.

Yes of course, having a generic engine to display information so that it 
automatically adjusts to the relevant properties and their 
characteristics is a well-known and well-understood problem, that has 
been solved based on RDFS classes for 10 years now.

>
> I proposed this as a user story because it covers an important aspect 
> of linked data applications which is inspired by a real example. You 
> may say that it is hypothetical, but I think user stories are 
> hypothetical by nature...they can be inspired by practical examples, 
> like this one, but they offer some hypothetical scenario, which this 
> one does, and it also offers some challenges that I think will benefit 
> the WG.

So far there is not a single convincing story why "shapes" are really 
needed.

Holger
Received on Monday, 26 January 2015 23:42:38 UTC

This archive was generated by hypermail 2.3.1 : Monday, 26 January 2015 23:42:38 UTC