[resolver] format for catalog entries

[mromanello]

Hi @hcayless

I've been thinking a bit about a JSON-based format to allow people to "register" a text service for later resolution (assuming one day this resolver will exist ;-) ).

As we discussed at Duke, we can foresee a Github-based workflow as easy as fork-push-PR. A folder services (even hosted in this repo) would allow people to add a JSON minimal description for the service they wish to register (where "register" means telling a future resolver, "hey my text service lives here etc.").

Here a fictional entry for Pietro'd current DTS implementation, just as a way of starting a discussion about a possible format.

(content of services/betamasaheft.json)

{
        "endpoint": "http://betamasaheft.eu/api/dts",
        "protocol": "dts",
        "name": "Beta maṣāḥǝft",
        "contact": "mailto:pietro.liuzzo@uni-hamburg.de",
        "status": "beta"
    }

where status could take values: alpha, beta, demo, experimental and protocol either cts or dts.