forked from bsletten/db2triples
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGES.txt
185 lines (115 loc) · 5.91 KB
/
CHANGES.txt
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
Release Notes db2triples v0.9.9
Released on 08/04/2012
1. New features
1.1 R2RML, implementation of new W3C Candidate Recommendation of 23
February 2012
(see http://www.w3.org/TR/r2rml/ for more information)
which includes among others:
* New R2RML data model
* New R2RML vocabulary
* Datatypes treatments are now normalized (in a generic SQL formalism)
* Any DBMS that conform to Core SQL 2008 can now be mapped with
its specific driver (tested only on PostGreSQL, which conforms
to at least 160 mandatory features required for full Core
conformance of 179)
* Support for MySQL
* Support for binary types conversion
* Support for predicate rr:inverseExpression (optimize term maps
processing that reference derived columns in R2RML views)
* Support for limited and regular SQL identifiers : allows to
execute SQL query with case-sensitive/case-insensitive SQL
identifier syntax rules
* Support for canonical RDF lexical forms and transformation
1.2 Direct Mapping, implementation of new Candidate Recommendation of
23 February 2012 (see http://www.w3.org/TR/rdb-direct-mapping/ for
more information) which includes among others:
* Support for binary types conversion
* Support for canonical RDF lexical forms and transformations (that
uses the same common rules as R2RML)
2. Improvements
2.1 Syntax of URI
* URI syntax of generated RDF terms strictly complies with the W3C
standard: IRI-safe version of string, percent-encoding and other
encoding process in the two Candidate Recommendations are
implemented.
2.2 XMLSchema Types Management
* Rules for canonical RDF lexical forms and transformations
3. Known Issues
3.1 R2R2ML
* Use of litterals with bad types does not yet raise "Data error"
_____________________________________________________________________
Release Notes db2triples v0.9.5
Released on 14/02/2012
1. New features
1.1 Direct Mapping: Cursor mode
- New database extraction method based on JDBC cursor mode
* Rows of databases tables are processed one by one. It considerably reduces memory usage.
* Big database can now be processed (ex: a MySQL database of
1.5 Go generates 30M triples in 3 hours with native
triplestore method on a commodity PC).
1.2 Direct Mapping: Implementation of new W3C Working Draft (of 20 September 2011)
* Syntax of URIs is now normalized
* Datatypes treatments are now normalized (in a generic SQL formalism)
* Any DBMS can now be mapped with its specific driver
(tested only on MySQL and PostGreSQL at this time)
* "XMLSchema base64 encoding" mentioned in literal map
definition of W3C Working Draft of 20 September 2011 is not
yet supported.
2. Improvements
2.1 Direct Mapping
- Implementation Version to be used can now be selected (between the
Working Draft of 23 March 2011 and the Working Draft of 20 September
2011)
* New parameter "version" can be specified
- Add support for PostGreSQL (for W3C Working Draft 23 March 2011)
* Use value "org.postgresql.Driver" in "driver" parameter
2.2 SQL Database Model
- Model completed with new generic interfaces
* Allow compatibility with cursor mode and several Direct Mapping implementations
2.3 SQL Types Management
- SQL types are distinguished in two categories "generic types" and "specific types"
* Open Direct Mapping implementations to all DBMS
* Includes compatibility with version of 23 March 2011
* Includes compatibility with new Working Draft of R2RML (of 20 September 2011)
2.4 XMLSchema Types Management
- XMLSchema datatype conversions are adapted for generic SQL datatypes.
2.5 Miscellaneous
- Direct Mapping console interface Improvement
* Normalization of parameters name
- "@author" tags have been removed
3. Bug fixes
- Fixes an issue where blank nodes links for empty (non-existent) primary key were broken
* References to section 2.4.4 in "A Direct Mapping of Relational Data to RDF"
(W3C Working Draft 24 March 2011)
* References to section 2.5 in "A Direct Mapping of Relational Data to RDF"
(W3C Working Draft 20 September 2011)
* References to tables rows with no primary key are expressed
as RDF triples with blank nodes for objects, where this
blank node is the same node used for the subject in the
referenced row.
Appendix: New parameters of Direct Mapping
-b,--database <database_name> database name
-d,--driver <driver> Driver to use (default:
com.mysql.jdbc.Driver )
-f Force loading of existing repository
(without remove data)
-i,--base_uri <base_uri> Base URI (default:
http://foo.example/DB/)
-l,--url <url> Database URL (default:
jdbc:mysql://localhost/)
-m,--format <format> RDF syntax output format ('RDFXML',
'N3', 'NTRIPLES' or 'TURTLE')
-n,--native_output <nativeOutput> Native store output directory
-o,--output <output> Output RDF filename (default:
output)
-p,--pass <password> Database password
-q,--sparql_output <sparql_output> Transformed graph output file
(optional if sparql option is not
specified, default: sparql_output
otherwise)
-s,--sparql <sparql> Sparql transform request file
(optional)
-u,--user <user_name> Database user name
-v,--version <version> Version of norm to use (1 = Working
Draft 20 September 2011 (default), 2
= Working Draft 23 March 2011)