I was going to make a joke that "X-Subliminal" from <a href="http://tuxgames.com" rel="nofollow">http://tuxgames.com</a> should become "com.tuxgames.subliminal", but I see they already made it for me...<p>> <i>In some situations, segregating the parameter name space used in a
given application protocol can be justified:</i><p>> <i>1. When it is extremely unlikely that some parameters will ever be
standardized. In this case, implementation-specific and private-
use parameters could at least incorporate the organization's name
(e.g., "ExampleInc-foo" or, consistent with [RFC4288],
"VND.ExampleInc.foo") or primary domain name (e.g.,
"com.example.foo" or a Uniform Resource Identifier [RFC3986] such
as "<a href="http://example.com/foo" rel="nofollow">http://example.com/foo</a>). In rare cases, truly experimental
parameters could be given meaningless names such as nonsense
words, the output of a hash function, or Universally Unique
Identifiers (UUIDs) [RFC4122].</i>