Add Namespace Mapping Models and Manager about pybel

[NandithaMallesh]

@cthoyt : i can work on this. But define "this" :) We can discuss it later today and maybe you can explain what you are thinking when you say this :)

[cebel]

In general we have a problem with ...

1. missing names in namespaces
2. wrong classification of names in namespace leads to parser error logs. example: Inflammation classified with O in MESHD namespace as _path_ and not correctly with B as _biological process_

Solution: own repository of namespaces?

[cthoyt]

Missing names: I don't need to be convinced. My thoughts are in the design choices section of the docs... definitely an issue for another day

I think the line between biological processes and pathologies are often very blurred, and definitely subjective. This is definitely true for the case for whether inflammation is a pathology or biological process, and maybe also true in general.

Can you give an example where there is a substantial difference in the way analyses are performed that's affected by this difference?

[cthoyt]

nanditha why don't you give this a try while waiting for the data manager and pybel-API prerequisites

[cebel]

@cthoyt : What you mean with this in the comment to nanditha?

[cthoyt]

@cebel Nanditha's task for the flask-restless API on top of the data manager is dependent on @LeKono's work. @NandithaMallesh if you're feeling motivated, you could work on this while you're waiting and that would be really helpful! Otherwise, Andrej could get to it later, or I'll do it when I need it.

[cthoyt]

Completed with efbda0d