{"id":1593,"date":"2011-10-11T18:53:38","date_gmt":"2011-10-11T22:53:38","guid":{"rendered":"http:\/\/fgiasson.com\/blog\/?p=1593"},"modified":"2011-10-11T21:03:41","modified_gmt":"2011-10-12T01:03:41","slug":"volkswagens-rdf-data-management-workflow","status":"publish","type":"post","link":"https:\/\/fgiasson.com\/blog\/index.php\/2011\/10\/11\/volkswagens-rdf-data-management-workflow\/","title":{"rendered":"Volkswagen’s RDF Data Management Workflow"},"content":{"rendered":"\n\n\n
TribalDDB UK’s team just published a new case study to the W3C: Case Study: Contextual Search for Volkswagen and the Automotive Industry<\/a>. They discuss the benefits of some of the semantic web technologies, techniques and concepts that they use to help them managing their data. They describe their approach and outline their design. It covers the technical aspects of their new Semantic Web Platform that I wrote about a few weeks ago<\/a>.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

In this blog post, I want to further explain their data management workflow, and how their data get exposed to different kind of users.<\/p>\n

Two Classes of Users<\/h3>\n

Let’s take a look at their data ingest\/management\/publishing workflow:<\/p>\n

\"\"<\/a><\/center>As you can see, all their data get collected, transformed and imported into structWSF<\/a>. As I explained in my previous blog post<\/a>, they are using structWSF to manage all their RDF data and access all the functionalities from the different web service endpoints.<\/p>\n

However, how the data get exposed to the users is not that clear. In fact, it depends on the classes of users. A user can be multiple different things: it may be a person, it may be a computer software, it may be an organization, etc. However, there are two general classes of users:<\/p>\n

    \n
  1. Public users, and<\/li>\n
  2. Private users<\/li>\n<\/ol>\n

    Public users are users that have no direct relation with Volkswagen and that have no access to their internal network. Private users are generally internal departments or some internal software applications that have direct access to the structWSF instance.<\/p>\n

    Private Users<\/h3>\n

    Private users generally have access to all structWSF web service endpoints. This means that all structWSF functionalities are accessible to them by querying the endpoints.<\/p>\n

    Two different kind of private users are specified in the use case’s schema:<\/p>\n

      \n
    1. Volkswagen Site Search<\/li>\n
    2. Other \/ External Applications<\/li>\n<\/ol>\n

      The Volkswagen site search is a software application that uses the structWSF Search endpoint<\/a> to search, filter and expose their data to their users (the people who perform searches on the Volkswagen UK website).<\/p>\n

      \"\"<\/a><\/center>The other\/external applications are software applications that have access to the structWSF instance. These are generally internal applications that run in the same network. One of these applications is an internal software that exports all the RDF data from the structWSF SPARQL endpoint<\/a>, and import it into Kasabi<\/a>.<\/p>\n

      These are two examples of software applications that Volkswagen created around the structWSF web services to re-purpose, re-contextualize and re-publish their RDF data.<\/p>\n

      Public Users<\/h3>\n

      There is currently two kinds of public users of this new Volkswagen Semantic Platform:<\/p>\n