Hi,
I noticed that your ETL modules are not designed to use a dimensional model
(facts and dimensions), so it may be better to have your own namespace
instead of using DataWarehouse namespace.
Since it is more generic than a DataWarehouse, I would say Data::ETL is a
reasonable option. In fact, the Data namespace is already used by other
modules that deal with some kind of ETL, for instance:
Data::CTable
Read, write, manipulate tabular data
On Wed, May 4, 2016 at 4:46 AM, Robert Wohlfarth <rbwohlfa...@gmail.com>
wrote:
> This is all very helpful. I'm weighing 3 ideas...
> 1. Take Nelson up on his offer and name it something like
> Datawarehouse::ETL::Script.
> 2. Create a top-level namespace for ETL.
> 3. Make a new namespace like StructuredDataConverter.
>
--
Nelson Ferraz
