Warning:
This wiki has been archived and is now read-only.
Main Page
From RDB2RDF
Contents
RDB2RDF Working Group Space
Candidate Recommendation
Official CR documents:
Additional resources:
Last Call
See Last Call page for details ...
Working Documents
Editor's Drafts
Meetings
See Meetings page for agenda and minutes
On the Wiki
- Use Cases and Requirements
- Implementations
- TestCases (old: R2RML Test Cases v1, even older R2RML Test Cases)
- Invalid R2RML: Examples for things that are not allowed in R2RML and should be checked in implementations or test cases
- SQL to XSD Type Mappings
- Note on Blank Nodes
- RDB2RDF Design Issues:
- Linked Data Aspects
- GeneratedSQL
- PotentialSQLIssues
- Logical Equivalences
- Direct Mapping in RIF
- Database-Instance-Only and Database-Instances-and-Schema Mapping
- Semantics of R2RML
- Default Mapping
- Default Mapping to RDFS/OWL
- All Cases for Default Mapping
- Default Mapping Description
- Mapping SQL datatypes to XML Schema datatypes
- Translation Table Proposal
- Translating Database Values to RDF Terms
- Non-unique Tables
Presentations, Outreach and Tutorials
- RDB2RDF Publicity
- Mapping Relational Data to RDF - status of the W3C RDB2RDF work in November 2010
- Initial Round of Presentations
- Semtech 2011 Proposal
- Media resources
Administrative Stuff
Keeping track of actions and issues
The RDB2RDF WG has an instance of the Tracker running at: RDB2RDF Tracker.
Countdown to Proposed Recommendation
- We have a face-to-face meeting scheduled at TPAC (31 Oct-4 Nov 2011).
- We would like all Last Call issues to be closed by the end of the f2f meeting to start preparing for Proposed Recommendation status. So, working backwards ...
- We need at least three weeks for a Last Call comment period (see W3C Process Document) and, say, a month for resolution of Last Call issues in case we get a lot of comments.
- Thus, we should plan to publish Last Call drafts around September 1, 2011
- We must close all open issues before we can go to Last Call.
- The Process Document says that before announcing a Last Call, the Working Group MUST do all of the following:
- Record the group's decision to request advancement.
- Fulfill the relevant requirements of the Working Group charter and those of any accompanying requirements documents, or report which relevant requirements have not been fulfilled.
- Indicate which dependencies with other groups the Working Group believes it has satisfied, and report which dependencies have not been satisfied.
Meetings
- Scribing (see Zakim and RRSAgent)
- ScribeList
- Participation:
- log into IRC first using the W3C Web IRC client or another Web IRC client such as mibbit
- join the '#RDB2RDF' channel
- dail into the conference using +1-617-761-6200 and the code 7322733# (spells "RDB2RDF#")
- Face to Face 1
- Face to Face 2
Liaisons
As of our charter we shall coordinate our work with other W3C groups but also with external activities, see Liaisons for details.
Old stuff
- RDB2RDF Incubator Group Wiki
- Draft of Use Cases
- Requirements: discussion of DDL statements
- RDB2RDF Mapping: SQL Approach
- Example of SQL-Query based Approach
- Newer versions: Using Turtle Syntax
- Newer versions: Revision 2
- Newer versions: Revision 1
- Prior versions
- R2RML in Turtle: Same approach, but using an RDF surface syntax instead of XML
- R2RML in a custom syntax: Same approach, but using a SPARQL-inspired custom syntax
- SQL View Annotation
- Example of SQL-Query based Approach