Backend error when we change geolocalisation ontologie

**Décrivez le bug**
I want to use Geonames/schema.org ontologies in spite of PAIR ontology.
So I've modified containers.js (back) and LocationInput.js (front).
When I open an organization, backend crash with error "Invalid character in statusMessage".

**Etapes pour reproduire**
1. Modify deference line in onrganization container, changing ontology like this :
```
dereference: ['sec:publicKey', 'heco:hasLocation/heco:hasPostalAddress'],
```
3. Restart middleware
4. Open an organization

**Comportement attendu**
Show organization data.

**Captures d'écran**

Start by comparing the ontology changes in containers.js and LocationInput.js, then reproduce the crash by changing the organization dereference and opening an organization after restarting the middleware. Trace the "Invalid character in statusMessage" error; the fix is complete when the organization data is displayed with the Geonames/schema.org ontology.

Written by the indexing model from the issue text.