charter-20080304
12.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><meta name="generator" content="HTML Tidy for Linux/x86 (vers 1 September 2005), see www.w3.org"/><meta http-equiv="content-type" content="text/html; charset=utf-8"/><title>RDB2RDF XG Charter</title><meta name="author" content="Karl Dubost"/><meta name="keywords" content="charter, checker, test assertions, W3C Process Document, W3C"/><link rel="stylesheet" href="http://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen"/><link rel="stylesheet" type="text/css" href="http://www.w3.org/Guide/pubrules-style.css"/><link rel="stylesheet" type="text/css" href="http://www.w3.org/2006/02/charter-style.css"/></head><body>
<div id="template"><ul id="navbar" style="font-size: small"><li><a href="#scope">Scope</a></li><li><a href="#deliverables">Deliverables</a></li><li><a href="#coordination">Dependencies</a></li><li><a href="#participation">Participation</a></li><li><a href="#communication">Communication</a></li><li><a href="#decisions">Decision Policy</a></li><li><a href="#patentpolicy">Patent
Policy</a></li><li><a href="#additional">Additional Information</a></li><li><a href="#about">About this Charter</a></li></ul>
<p><a href="http://www.w3.org/" shape="rect"><img alt="W3C" height="48" src="/Icons/w3c_home" width="72"/></a> <a class="domainlogo" href="/2005/Incubator/" shape="rect"><img src="http://www.w3.org/2005/Incubator/images/incubator" alt="Incubator Activity"/></a></p>
<h1 id="title">RDB2RDF Incubator Group Charter</h1>
<p class="mission">The
<strong>mission</strong> of the <a href="http://www.w3.org/2005/Incubator//">RDB2RDF Incubator Group</a>, part of
the <a href="http://www.w3.org/2005/Incubator/">Incubator Activity</a>, has two initiatives.</p>
<p> The first is to
examine and classify existing approaches to mapping relational data into RDF and decide whether standardization is possible and/or necessary in this area and, if so, the direction such standardization could take. The goal is to specify how to generate RDF triples from one or more Relational tables without loss of information. Furher, a default mapping should not be used, but, instead, it should be possible for the the mapping to be customized by the user.</p>
<p>The second initiative is to examine and classify existing approaches to mapping OWL classes to Relational data, or, more accurately, SQL queries, moving towards the goal of defining a standard in this area. Each OWL class would be associated with one or more SQL queries which may be run on separate databases. The results from these queries would then be integrated into a single Relational table. This would be transformed into RDF using the approach defined as a result of the first initiative.
</p>
<p>An important problem to be solved as part of this work is the mapping of RDB names to RDF/XML names.</p>
<div class="noprint">
<p class="join"><a href="/2004/01/pp-impl/42232/join">Join the RDB2RDF Incubator Group</a>.</p>
</div>
<table class="summary-table"><tr id="Duration"><th rowspan="1" colspan="1">End date</th><td rowspan="1" colspan="1">14 February, 2009</td></tr><tr><th rowspan="1" colspan="1">Confidentiality</th><td rowspan="1" colspan="1">Proceedings are <a href="/2005/10/Process-20051014/comm.html#confidentiality-levels" shape="rect">
public
</a></td></tr><tr><th rowspan="1" colspan="1">Initial Chairs</th><td rowspan="1" colspan="1">Ashok Malhotra, Oracle -- ashok.malhotra@oracle.com</td></tr>
<tr><th rowspan="1" colspan="1">Initiating Members</th>
<td rowspan="1" colspan="1">Oracle, HP, PartnersHealthcare, OpenLink Software</td>
</tr>
<tr><th rowspan="1" colspan="1">Usual Meeting Schedule</th><td rowspan="1" colspan="1">Teleconferences: Weekly
<br/>
Face-to-face meetings:
2-3 per year </td></tr></table>
<div class="scope">
<h2 id="scope">Scope</h2>
<div class="may">
<h3>Plan of Work</h3>
<ul><li>Development of use cases and requirements.</li>
<li>Development of general approach to the problem.</li>
<li>(Optional) Selection of technology for sample implementation(s).</li>
<li>Generation of deliverables.</li>
</ul>
</div>
<div class="may">
<h3>Success Criteria</h3>
<p>The XG will be deemed successful if and when it produces the deliverables listed below.</p>
</div>
<div class="may">
<h3>Out of Scope</h3>
<p>Mapping from other data sources such as spreadsheets and PDF documents to RDF is out of scope. Anything not explicitly listed as being in scope is out of scope.</p>
</div>
</div>
<div>
<h2 id="deliverables">Deliverables</h2>
<ul>
<li>A report describing an approach to how Relational data can be transformed into RDF triples in a customized manner.</li>
<li>A report describing an approach to mapping OWL classes to SQL queries.</li>
<li>(optional) Sample implementation(s) of the technology described in the above reports.</li>
</ul>
</div>
<div class="dependencies">
<h2 id="coordination">Contacts and Dependencies</h2>
<div class="may">
<h3>W3C Groups</h3>
<dl><dt>
<a href="http://www.w3.org/2001/sw/DataAccess/">RDF Data Access Working Group -- contact</a><br/>
<a href="http://www.w3.org/2005/10/swap3/swig-charter.html">Semantic Web Interest Group -- contact</a><br/>
<a href="http://www.w3.org/2005/rules/wg">Rule Interchange Format (RIF) Working Group -- contact</a><br/>
<a href="http://www.w3.org/2007/OWL/">OWL Working Group -- contact</a>
</dt></dl>
</div>
</div>
<div class="participation">
<h2 id="participation">Participation</h2>
<p>It is envisioned that the XG will have begin with 60-minute telecons every week at a time that provides an adequate compromise over the various time zones of the interested participants. This can be modified as the work proceeds. During the telecons, the participants will review work done by individuals and sub-groups, and new work items will be defined and assigned. Additionally, it may be useful to have periodic face-to-face meeting at a venue for which a significant number of XG participants are likely to attend.</p>
<p>
Expected participation follows the <a href="http://www.w3.org/2005/10/Process-20051014/process.html#good-standing">W3C Process Document discussion of Good Standing</a></p>
</div>
<div class="communication">
<h2 id="communication">Communication</h2>
<p>This group primarily conducts its work on the public
mailing list
public-xg-rdb2rdf@w3.org
(<a href="http://lists.w3.org/Archives/Public/public-xg-rdb2rdf/">archive</a>).
The group's Member-only list is
member-xg-rdb2rdf@w3.org
(<a href="http://lists.w3.org/Archives/Member/member-xg-rdb2rdf/">archive</a>).
</p>
<p>Information about the group (deliverables, participants,
face-to-face
meetings, teleconferences, etc.) is
available from the <a href="http://www.w3.org/2005/Incubator//">RDB2RDF Incubator Group home
page</a>.</p>
</div>
<div class="decisions">
<h2 id="decisions">Decision Policy</h2>
<p>As explained in the Process Document (<a href="/Consortium/Process/policies#Consensus" shape="rect">section
3.3</a>), this group will seek to make decisions when there
is consensus. When the Chair puts a question and observes
dissent, after due consideration of different opinions, the
Chair should record a decision (possibly after a formal vote)
and any objections, and move on.</p>
<ul><li>When deciding a substantive technical issue, the Chair
may put a question before the group. The Chair must only do
so during a <a href="/Consortium/Process/policies.html#GeneralMeetings" shape="rect">
group meeting</a>, and at least two-thirds of participants
in <a href="/Consortium/Process/groups.html#good-standing" shape="rect">
Good Standing</a> must be in attendance. When the Chair
conducts a <a href="/Consortium/Process/policies#Votes" shape="rect">formal
vote</a> to reach a decision on a substantive technical
issue, eligible voters may vote on a proposal one of three
ways: for a proposal, against a proposal, or abstain. For
the proposal to pass there must be more votes for the
proposal than against. In case of a tie, the Chair will
decide the outcome of the proposal.</li><li>This charter is written in accordance with <a href="/Consortium/Process/policies#Votes" shape="rect">Section
3.4, Votes</a> of the W3C Process Document and includes no
voting procedures beyond what the Process Document
requires.</li></ul>
</div>
<div class="patent">
<h2 id="patentpolicy">Patent
Policy</h2>
<p>This Incubator Group provides an opportunity to share
perspectives on the topic addressed by this charter. W3C
reminds Incubator Group participants of their obligation to
comply with patent disclosure obligations as set out in
<a href="/Consortium/Patent-Policy/#sec-Disclosure" shape="rect">Section
6</a> of the W3C Patent Policy. While the Incubator Group
does not produce Recommendation-track documents, when
Incubator Group participants review Recommendation-track
specifications from Working Groups, the patent disclosure
obligations do apply.</p>
<p>Incubator Groups have as a goal to produce work that can
be implemented on a Royalty Free basis, as defined in the
<a href="/Consortium/Patent-Policy/" shape="rect">W3C
Patent Policy</a>.</p>
<p>Participants in this Incubator Group wishing to exclude <a href="/Consortium/Patent-Policy-20040205/#def-essential" shape="rect">essential patent
claims</a> from the licensing commitment must join the Working Group created
to work on the XG Report and follow the normal exclusion procedures defined
by the Patent Policy. The W3C Team is responsible for notifying all
Participants in this Incubator Group in the event that a new Working Group is
proposed to develop a Recommendation that takes the XG Report as an input.
</p>
<p>For more information about disclosure obligations for
this group, please see the <a href="/2004/01/pp-impl/" shape="rect">W3C
Patent Policy Implementation</a>.</p>
</div>
<h2 id="additional">Additional Information</h2>
<p>There is existing work in this area, for example: Virtuoso, D2RQ, SquirrelRDF and investigations at the Univ. of Texas. See <a href="http://www.w3.org/2007/03/RdfRDB/accepted">Accepted Papers</a> from the <a href="http://www.w3.org/2007/03/RdfRDB/">W3C Workshop on RDF Access to Relational Databases</a>. This work can be used as a starting point for the Incubator Group.</p>
<h2 id="about">About this Charter</h2>
<p>This charter for the RDB2RDF Incubator Group has been created according to
the <a href="/2005/Incubator/procedures" shape="rect">Incubator
Group Procedures documentation</a>. In the event of a
conflict between this document or the provisions of any charter
and the W3C Process, the W3C Process shall take precedence.</p>
<hr/>
<address>
Ashok Malhotra
</address>
<p class="copyright"><a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright" shape="rect">Copyright</a>©
2008 <a href="/" shape="rect"><acronym title="World Wide Web Consortium">W3C</acronym></a>
<sup>®</sup> (<a href="http://www.csail.mit.edu/" shape="rect"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a> ,
<a href="http://www.ercim.org/" shape="rect"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>
, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>), All Rights
Reserved.</p>
<p>$Date: 2008/03/04 22:26:45 $</p>
</div>
</body>
</html>