make specification JSON more self-contained

[dret]

the current way how specifications list concepts is by URIs (as fixed in #36). this is correct, but means that there no easy way to get concept information from the JSON.

{ "concepts": [
  { "http://webconcepts.info/concepts/urn-namespace": "http://webconcepts.info/concepts/urn-namespace/ietf" }]}

the proposal is to make this a bit more self-contained by adding the concept name and value, resulting in something like this:

{ "concepts": [
    { "id": "http://webconcepts.info/concepts/urn-namespace",
      "name": "URN Namespace",
      "value-id": "http://webconcepts.info/concepts/urn-namespace/ietf",
      "value": "ietf" }]}

this would be a breaking change. @kinlane @mogsie @tpluscode @mitraman @BigBlueHat @pmhsfelix, anybody using this and disliking this proposal?

[tpluscode]

@pmhsfelix can also have something to say

[dret]

while documenting the JSON structure it just occurred to me that the current design is really bad, because it creates repeated member names when a specification defines more than one value for a concept. this means that the current design creates correct but rather questionable JSON. this will have to change better sooner than later.

[BigBlueHat]

Changing the structure isn't going to throw me off (currently) and the new layout does seem considerably more informative. 😃