I couldn't find any existing CPAN modules with a Nike-related namespace. On the other hand the WWW precedence is a convincing argument already made.

The only thing I would add is that it would make sense for WWW namespaces to follow the URL they support as closely as possible to prevent conflict of naming conventions. It is too late to do that exactly right because ambiguity of .com versus .net or .co.uk etc has already taken precedence in these namespaces.

It is legally possible for two companies to have different APIs with the same name in which case the second field of the URL would be the only distinguishing feature.

The only way I can see to follow the strongest existing precedents and respect the need for close-to-unique URL mapping is to take the second field of the URL first and follow it with the '/'-delimited path after that, separateing each field with '::'.

In this case, such analysis produces WWW::Nike::NikePlus, so that if some other API appears on www.nike.com/Foo it could take the namespace WWW::Nike::Foo.

__________________________________________________________________________________

^M Free your mind!

In reply to Re: CPAN module name for Nike+ API by Moron
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.