Every jid is a node that can be interacted with for messages, presence, and special purpose iq namespaces. We need a far better way to structure and manage this culture of jid stew. The following is a first-pass at a list of the possible categories and subtypes. The elements within this namespace are identified by the categories listed above, with a few generic attributes. The required jid attribute is the full Jabber ID of the entity described.
Type is the subtype for the category as defined above, and is required.
Name is a friendly name that may be used in a GUI, and is optional. Any element may contain any other element as a child, describing the relationship between the two. When a jid is browsed to, the result may contain children or be empty. An empty child does not mean anything, and to determine if there are more children of it it must be browsed to directly. This allows any entity to advertise which features they support, based on namespaces.