- From: Jose Emilio Labra Gayo <jelabra@gmail.com>
- Date: Mon, 2 Feb 2015 10:26:47 +0100
- To: RDF Data Shapes Working Group <public-data-shapes-wg@w3.org>
- Message-ID: <CAJadXX+Y5UUumqgh2fhDhz24Gbv-4Js3Xx_=rEV1dbqZWRSjRg@mail.gmail.com>
Following Peter's question in last meeting, I have edited the User story adding a paragraph where I indicate the possible constraints that can be represented in this example. The result is: https://www.w3.org/2014/data-shapes/wiki/User_Stories#S38_Describing_and_Validating_Linked_Data_portals Regards, Jose Labra On Fri, Jan 23, 2015 at 6:40 PM, Jose Emilio Labra Gayo <jelabra@gmail.com> wrote: > Although I know that it is a bit late, I would like to add a new user > story that is based in a real life experience and that I think is not > completely covered by the other user stories. > > The reason that I didn't add it before is that I could not be part of the > WG until two weeks ago. > > The User Story could be: > > Describing and Validating Linked Data portals > by Jose Labra > > A small company is specialized in the development of linked data portals. > The contents of those portals are usually from statistical data that comes > from Excel sheets and can easily be mapped to RDF Data Cube observations. > > The company needs a way to describe the model of the RDF graphs that need > to be generated from the Excel sheets which will also be published as an > SPARQL endpoint. Notice that those linked data portals could contain > observations which will usually be instances of qb:Observation but can > contain different properties. > > In this context, the company is looking for a solution that can be easily > understood by the team of developers which are familiar work with OO > programming languages, relational databases, XML technologies and some > basic RDF knowledge, but they are not familiar with other semantic web > technologies like SPARQL, OWL, etc. > > The company also wants some solution that can be published and understood > by external semantic web developers so they can easily know how to query > the SPARQL endpoint. > > There is also a need that the solution can be machine processable, so the > contents of the linked data portal can automatically be validated. > > Finally, the company would like to compare the schemas employed so they > can check which are the differences between the RDF nodes in those portals > and they can even create new applications on top of the data aggregated by > those portals. > > --------- end of User Story > > The user story is based on my own experience in the development of two > real life linked data portals (the WebIndex and the LandPortal). > > In both cases, we employed ShEx documents to describe the RDF contents > that had to be generated to the development team (which were no semantic > web experts). The experience is also described in [1]. > > [1] Validating and Describing Linked Data Portals using RDF Shape > Expressions, Jose Emilio Labra Gayo, Eric Prud'hommeaux, Harold Solbrig, > 1st Workshop on Linked Data Quality, Sept. 2014, Leipzig, Germany > PDF: http://labra.github.io/ShExcala/papers/ldq2014.pdf > Slides: http://www.slideshare.net/jelabra/linked-dataquality-2014 > > -- > Best regards, Labra > -- Saludos, Labra
Received on Monday, 2 February 2015 09:27:34 UTC