Talking with Natasha Noy about possible improvements around dataset description. Some things to look into:

• coverageStart and coverageEnd (currently, the datasetTimeInterval has DateTime, not interval, as its expected time, which I think is not correct, or at least doesn't allow us to specify the coverage interval)
  timestep (dct:accrualPeriodicity)
• bibliographic reference: many of the dataset refer to the paper that describes it
• Main variables measured -- without necessarily knowing the distinction of which ones are dimensions and which ones are measures qb:dimensionProperty and qb:MeasureProperty)

Related work

This all starts to get into the business of looking inside the dataset, which was discussed at schema.org previously - e.g. see Looking inside tables thread from Omar. Subsequently in W3C CSVW some of these ideas went standards track, in particular a templating mechanism to map tabular data into RDF.

• See also the (SDMX-oriented) W3C Data cube specification.
• W3C DCAT final specification (earlier drafts inspired the schema.org Dataset design)
• More recently: DCAT Application Profile for data portals in Europe (DCAT-AP) - @danbri discussed briefly w/ DCAT-AP team the possibility of using a JSON-LD-based @context for DCAT-AP as an 'external extension'.
• CSVW RDF examples using data cube vocabulary from @6a6d74