These slides appear to have been used for a course in Database Management Systems at the University of Toronto, but contain material which the creator attributes to other authors. Part 1 outlines a six-step process for "Publishing Linked Data on the Web". Part 2, "How to Publish Relational Databases as Linked Data", covers the following subjects: Mapping relational databases to RDF; following Linked Data Principles and guidelines; mapping and publication tools; the D2R Server.
URL: http://www.cs.toronto.edu/~oktie/slides/publishing-relational-databases-as-linked-data.pdf
Keywords: RBD2RDF, HTTP URIs, Query rewriting, Link discovery
Author: Heath, Tom
Publisher: Herman, Ivan
Date created: 2011-03-01 05:00:00.000
Language: http://id.loc.gov/vocabulary/iso639-2/eng
Time required: P30M
Educational use: instruction
Educational audience: professional
Interactivity type: expositive
- Chooses "hash"- or "slash"-based URI patterns based on requirements.
- Knows methods such as Direct Mapping of Relational Data to RDF (2012) for transforming data from the relational model (keys, values, rows, columns, tables) into RDF graphs.
- Knows the "five stars" of Open Data: put data on the Web, preferably in a structured and preferably non-proprietary format, using URIs to name things, and link to other data.
- Recognizes that owl:sameAs, while popular as a mapping property, has strong formal semantics that can entail unintended inferences.
- Reuses published properties and classes where available.
- Understands the purpose of publishing RDF vocabularies in multiple formats using content negotiation.
- Understands trade-offs between "opaque" URIs and URIs using version numbers, server names, dates, application-specific file extensions, query strings or other obsoletable context.