Re: Data Package RFCs coming up ...

On 2 July 2015 at 18:36, Dan Brickley <danbri@google.com> wrote:

> Hi Rufus,
>
> On 2 July 2015 at 13:02, Rufus Pollock <rufus.pollock@okfn.org> wrote:
> > Hi All,
> >
> > I wanted to flag that the Data Package suite of "proposals" which
> includes:
> >
> > - Data Package - http://dataprotocols.org/data-package/
> > - JSON Table Schema - http://dataprotocols.org/json-table-schema/
> > - Tabular Data Package - http://dataprotocols.org/tabular-data-package/
> >
> > Are being readied for submission as IETF RFC's.
> >
> > Folks on this list are no doubt very familiar with these as they formed a
> > basis for the initial CSV spec here (especially tabular data package).
> >
> > We have long planned to do this and have been waiting for the specs to
> > mature - especially actual implementations to exist - to submit as proper
> > RFCs and over the last year or so we've felt we're nearing that point
> and so
> > this should happen very soon.
> >
> > I wanted to flag now especially if there were any specific alignment that
> > could be done that would be great to do now - i know I have flagged some
> > issues on the dataprotocols tracker over the last year on this.
>
> Thanks for letting us know. It is rather likely that many on this WG
> are not tracking your tracker. As an author on both sets of specs,
> you're ideally positioned to give us an overview of how the two
> approaches diverge. Can you perhaps outline the key differences
> between the Data Package proposals and W3C CSVW specs?
>

Good suggestion, obviously CSVW was heavily based on Tabular Data Package
so they were very close initially but some changes in the CSVW spec have
developed over time. Structurally the specs are very similar but many
keywords have now changed and there have been several substantive changes
and additions. I won't list all but give some examples:

- CSVW renamed "fields" to "columns", "schema" became "tableSchema",
"title" (for a field/column) became "titles", column "type" became
"datatype" etc etc
- you can have prefixes in property names (dc:title) in CSVW but not
Tabular Data Package
- CSVW defaults to one "table" (CSV) whilst (Tabular) Data Packages
defaults to always having a list of "resources" (and "resources" is called
"tables" in CSVW)
- CSVW includes some degree of mandatory or recommended JSON-LD (e.g.
@type) - this optional or absent in Tabular Data Package
- The type list for column types in CSVW is substantially different
- foreignKeys are implemented somewhat different (but similarly
conceptually)
- Transformation Definitions: this was new concept introduced into CSVW and
absent in tabular data package
- ...

Rufus


>
> cheers,
>
> Dan
>
>
> > Regards,
> >
> > Rufus
> > --
> >
> > Rufus Pollock
> >
> > Founder and President | skype: rufuspollock | @rufuspollock
> >
> > Open Knowledge - see how data can change the world
> >
> > http://okfn.org/ | @okfn | Open Knowledge on Facebook |  Blog
>



-- 

*Rufus PollockFounder and President | skype: rufuspollock | @rufuspollock
<https://twitter.com/rufuspollock>Open Knowledge <http://okfn.org/> - see
how data can change the world**http://okfn.org/ <http://okfn.org/> | @okfn
<http://twitter.com/OKFN> | Open Knowledge on Facebook
<https://www.facebook.com/OKFNetwork> |  Blog <http://blog.okfn.org/>*