Rename this library

Context

Data Packages, and Frictionless Data specifications, are essentially part of the protocol and inner workings of this package, but the package itself does not really require knowledge of these specs. Branding it as “Data Packages” is misleading, and potentially would confuse users into thinking that a knowledge of data packages is required to use this package.

I think we should rename the package to simply pipelines or pipeline.

What are your thoughts @akariv

Any opinion on this @brew @roll @danfowler @vitorbaptista @amercader @rufuspollock ?

[danfowler]

Thinking it over, while it is true that @brew (and anyone else who wants to write their own processors) needs to know how Data Packages work in order to work with this tool, the most common user should be someone who (1) knows where her data is, (2) what it looks like, (3) where she wants to put it, and (4) how to write YAML. Thinking back to the first sentence of the README:

datapackage-pipelines is a framework for declarative stream-processing of tabular data. It is built upon the concepts and tooling of the Frictionless Data project.

Maybe the name should reference the most important type of data it ingests and spews (tables): table-pipelines, tabular-pipelines, tabular-data-pipelines, table-factory, table-streams, tabulator-streams (probably worth emphasizing in the README the connection to tabulator)…

[brew]

I found I needed a passing understanding of data packages to understand how to write pipelines and processors.