What kind of meta data do you mean? It sounds like there is application-specific functionality that the Miner/Store modules provide, rather than being a general Star/Open Office parser or an HTML parser. The type of meta data you're retrieving from the files would probably hint towards a better name, since (IMHO) "MetaInfo" is too vague to signal what kind of problem could be solved with the module.
--Ade. On Mon, 2002-07-15 at 17:36, Midh Mulpuri wrote: > I am writing an application that collects and stores meta data > from a variety of files (e.g. Star/Open Office files, HTML files) etc. > The application is written as one set of modules that extract this meta > data from a file and another set of modules that store this information. > The information is exchanged between a miner and a store in a hash. > I believe that the miner modules would be useful to every one. I > would like to release to CPAN. At the same time the store modules are a > nice way to store this meta information but they do not implement > anything that is useful separate from the Miner modules. > Would it be a good thing to release both the Miner and Store > modules. At last count I have four of the former and two of the latter. > There is one store Module that write the Metadata to a XML file and > another to a DBI supported database. > Another problem would be the Namespace. MetaInfo sees available. > I could release the modules as MetaInfo::Miner::--------- and > MetaInfo::Store::------ if I wanted to release both sets. On the other > hand I could release just the Miners under the MetaInfo namespace. > Any advice and pointers would be appreciated since this would be > my first release to CPAN. > - Midh Mulpuri
