*Moderator: Please feel free to move this post.

This is my first post, so I hope you'll bear with me.

My boss has started his first Techinical Support Wiki and wants to discuss naming conventions with me. There are a couple methods available and I'd like to know if anyone has experience with?

1) Name the wiki after a product we support as a third party software developer.
CONS: The owner of the product could ask us to take it down or re-name it.
EXAMPLE: http://microsoft.company.com

2) Name the wiki after our product
CONS: No one knows about our product, which is why we are turning to interesting naming conventions.
EXAMPLE: http://product.company.com

3) Name each Technical Support Wiki for each product we support (Microsoft, Palm, etc).
CONS: Multiple wikis, each which has the potential to being stopped by its trademarked owner.
EXAMPLE: http://microsoft.company.com
EXAMPLE: http://palm.company.com

4) Name each Technical Support Wiki with BOTH our product name and the product it supports.
CONS: Same trademark problem, less so.
EXAMPLE: http://microsoft_product.company.com
EXAMPLE: http://microsoft_another_product.company.com

5) Use keywords in the Wiki name instead
EXAMPLE: http://email.company.com

And to throw more problems into the mix, is it better to format the wiki:

EXAMPLE: http://wiki.company.com
EXAMPLE: http://company.com/wiki

Thoughts?

Any and all discussions or opinions welcome.

Thank you in advance-

two thumbs

I would use the subdomian wiki.company as it will get recognized separately by the search engines

Thank you for the response. Any thoughts on the other questions?