Namespace specifications

[XavierChanth]

On stand we discussed how apps might reuse / share information.

Right now, several apps look into in the wavi namespace to pull public or basic profile information such as name, profile pic, etc.

This should really be renamed to something more generic such as profile or public.

### Action items
- [ ] Migration code for apps using the .wavi namespace to move data to .profile (or whatever it ends up being called)
- [ ] Specification document for generic namespaces - .wavi/.profile, .contacts, etc.
- [ ] Open source the specification and make it readily available for contributions - could be part of at_protocol, could be it's own repo

[XavierChanth]

This is a tracker & discussion item

[XavierChanth]

I thought of a cool way to do this, the atSign that owns the namespace could publish a spec (of some yet to be determined format) to the .namespace namespace:

For example the wavi namespace could be found at:
public:spec.namespace@wavi

Accessible by anyone who wishes to use it in their app.