Re: Comment on module name Data::ETL
[email protected] (James E Keenan)
| Newsgroups | perl.module-authors |
|---|---|
| Message-ID | <[email protected]> |
On 05/04/2016 09:27 AM, Smylers wrote: > Robert Wohlfarth writes: > >> I'm weighing 3 ideas... >> 2. Create a top-level namespace for ETL. >> >> Idea 2 looks like so... >> * ETL >> * ETL::Extract >> * ETL::Extract::Excel >> * ETL::Extract::DelimitedText >> * ETL::Extract::XML >> * ETL::Load >> * ETL::Load::MSAccess > > Not necessarily. That would be effectively claiming the ETL:: namespace > is for your suite of modules. > > An alternative would be to create the ETL:: top-level namespace and then > put your framework under another level of hierarchy there, leaving space > for other ETL modules to share ETL::. As in: > > • ETL::$Brand > • ETL::$Brand::Extract > • ETL::$Brand::Extract::Excel > • ETL::$Brand::Extract::DelimitedText > • ETL::$Brand::Extract::XML > • ETL::$Brand::Load > • ETL::$Brand::Load::MSAccess > > — where $Brand is a word/phrase of your choice (either just a fanciful > name you like, or one you think sums up your particular ETL module suite > over other (potentially yet to be written) options. > This is what I would recommend as well.