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.