Executive summary

Our methodology to convert tabular literals to a Resource Description Framework representation enables answers to novel questions that could not previously be answered because it explicitly connects previously disconnected datasets that can and have been queried in a uniform fashion.

(todo :-)

• Provenance-inspired naming of datasets and the entities they describe (using "the essential three": version, dataset, and version).
• Minimal effort to obtain initial RDF from tabular formats. Get what you need and quickly move on to the rest of your application.
• Declarative interpretation parameters control resulting RDF structure.
• Parallels RDFS and OWL axioms, but applies to tabular literals instead of existing RDF.
• Provides backwards-compatible enhancements to initial verbatim RDF interpretation (usig layered predicate design).
• Leverages previous enhancement parameters via an include mechanism.
• Leverages RDF output of previous conversions as enhancement parameters for subsequent conversions.
• Abbreviated description of resulting structure (no need to dig into custom code).
• Uniform treatment and results across dataset application .