I can only make a wild guess based on your short description since I can't enter the site due to lack of newest flash player. The WWW namespace is filled with modules provide interfaces to various web services, including the very tool WWW::Mechanize. So, IMO, this is enough justification to put your module under that namespace. Since the + part seems to be very attached to the Nike part as a web service, combining the parts is more appropriate so NikePlus is what comes to mind.

However, it might be better if you can narrow a category under WWW itself. Beside this can avoid cluttering the namespace further, it will give an instant hint about what can be done with Nike+, especially for people who have no idea what Nike+ is. Examples are WWW::Search or WWW::Scraper. Similiarly, WWW::Blog::WordPress would be more appropriate instead of WWW::WordPress.

You can make new category to put under WWW if no existing ones matching your modules to form WWW::NewCategory::NikePlus. Or, if you think the service can be extented in the future with distinct set of features, feel free to just use WWW::NikePlus. The precedence for this are WWW::Google and WWW:Yahoo.

The very last, I think you still need to talk to modules@cpan.org before making your final decision. Good luck, puploki :-)

Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!

In reply to Re: CPAN module name for Nike+ API by naikonta
in thread CPAN module name for Nike+ API by puploki

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.