Project Plan
From LDTables Wiki
This is a general to-do list for the project, organized by deliverables. The overall goal is make Linked Data Tables be a practical and accepted way to share data on the web, rivaling RDF/XML, RDFa, SPARQL, CSV, XML, etc, etc., with hopefully most of the best features of each.
Contents |
[edit] Community
Okay, maybe this isn't a deliverable, but surely a community of developers and supporters is required to make this thing work. At some point, on-line support will be useful. A mailing list? Google group? Hashtag? Phone calls? irc channel?
A key question here is whether to piggyback on the semantic web / linked data communities, or start a new one, which could be more welcoming to folks who know nothing of RDF.
[edit] Specification
Start on the wiki. At some point, probably, move it along through W3C, if there's enough community support.
[edit] Library of Formats
Keep evolving http://www.ldtables.org/wiki/Category:Format
At some point, figure out which ones are required for "level 1", or something like that.
[edit] Library of Properties
Keep evolving http://www.ldtables.org/wiki/Category:Property
This is closely related to the RDF vocabulary ecosystem; it's unclear the best way to support the evolution of healthy system.
[edit] Open Source Client Library
python tablegate library
[edit] Gateway Site
gateway to/from RDF/XML; maybe RDFa, SPARQL, ...
maybe gateway to/from CSV, ODBC, ...
[edit] Example Scenarios
[edit] Event Listing
Several people post tables on their blogs/sites with information about about upcoming and recent events. People can search on various criteria, perhaps bringing in various RDF databases.
Ties in to music reviews if it's a musical event.
[edit] Bike Shopping
Semantic craigslist. Can do kinds of searching craigslist doesn't yet support.
[edit] Food Poisoning
People post tables about getting sick and what/where they ate recently. A search pretty quickly shows the source. Works better if you can feed it directly from existing (private) databases.
[edit] Test Cases
- Design test case framework: tables->rdf and/or tables->tables
- Different layouts of the same data
- Tricky RDF data
- Different formats
