Warning:
This wiki has been archived and is now read-only.
Requirements/Functional
Contents
Database Connection
The mapping language should allow to specify a database connection, which e.g. can be established using a DSN or connection string.
Relevant for: All usecases
Namespace declaration
The mapping language should enable the declaration and use of namespace prefixes.
Relevant for: All usecases
User defined output processing functions
The mapping language should enable the use of user defined output processing functions in order to transform values from the physical database representation into some domain representation. For example, a database row might contain Wiki text, which should be transformed into HTML - this can be achieved, for example, by using standard or user defined SQL functions or using XQuery/XPath Functions and Operators.
Relevant for: All usecases
Static Metadata
The mapping language should enable the attachment of static metadata (such as licensing information) to all RDF entities or instances of a certain class. This is in particular important, when RDF is published as Linked Data on the Web.
Relevant for: WebApp use case
Attribute-Value Tables
In some cases relational database schema already contain attribute value tables. The mapping language should also allow to map such attribute-value tables to RDF.
Relevant for: All usecases
Named Graphs
The mapping language should enable the creation of multiple Named Graphs within one mapping definition.
Relevant for: All usecases
Update Logs
The mapping language should support the creation of update logs of relational data.
Relevant for: All usecases
Provenance
The mapping language should support the preservation of provenance by generating additional RDF triples according to a provenance vocabulary, e.g. http://sourceforge.net/apps/mediawiki/trdf/index.php?title=Guide_to_the_Provenance_Vocabulary
Relevant for: WebApp use case