Oops, resend... there was a wrong address there someplace. On Sun, Sep 16, 2001 at 11:48:34PM -0500, [EMAIL PROTECTED] wrote: | Hi Kirrily, good to hear from you as well... hope you're having fun in Canada. Well, apart from being N thousand kilometres closer to the WTC than I'd like to be... :-/ | I actually started off calling it XML::NewsML, but then I read this post from Ken |McLeod in the archives of the perl modules list... | | http://www.xray.mpe.mpg.de/mailing-lists/modules/2000-07/msg00191.html | | "...the XML:: namespace should only be used for modules that work with | XML generically. Modules that just use XML should go in a namespace | or category more appropriate for what the module is doing." | | Which seems to make sense. So it does. *sigh* | So does anyone have any ideas about what I should call these modules? Perhaps |Text::News::NewsML, or XML::App:NewsML...??? *NOT* Text:: ... talk about an overused, too-general namespace! I think this comes down to making a decision on XML:: and where specific applications of XML should go. I imagine the modules list will have some more opinions on it. | The above quoted post was actually about a module called XML::OCS, which I can't |find anywhere. It and XML::RSS are probably NewsML's closest relatives, but I do like |Ken's reasoning that the XML:: space should be reserved for modules working with XML, |not modules based on XML applications. But what about the stuff under HTML? There's a precedent for a namespace with both generic parsers etc, and applications. K.
