spec.json should identify concepts and concept values by URI

[dret]

currently spec.json "identifies" concepts and values by string value only:

{"ietf-httpbis-encryption-encoding": {
  "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-encryption-encoding",
  "title": "Encrypted Content-Encoding for HTTP",
  "name": "Internet Draft ietf-httpbis-encryption-encoding",
  "URI": "urn:ietf:id:ietf-httpbis-encryption-encoding",
  "URL": "http://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding",
  "abstract": "This memo introduces a content coding for HTTP that allows message payloads to be encrypted.",
  "concepts": [
    {"http-content-coding": "aesgcm"},
    {"http-header": "Crypto-Key"},
    {"http-header": "Encryption"}]}}

this seems wrong because both concept and concept value should be identified by their ID (their URIs) as documented at http://webconcepts.info/JSON. i am inclined to just fix this, but wanted to see if anybody is using these values, and what they think about switching from plain strings to proper URIs.

[dret]

pinging @kinlane @arno-di-loreto @pmhsfelix @mitraman because you might be using this?

[arno-di-loreto]

I'm not using webconcepts yet (on my Christmas holidays todo list! ), so no problem for me.

[dret]

this issue is related to #24 which is about how to identify concepts (and values).

[dret]

On 2016-12-21 12:39, Arnaud Lauret wrote: I'm not using webconcepts yet (on my Christmas holidays todo list! ), so no problem for me.

happy holidays, and if there's any wish you have for web concepts, this is the time of the year to get them fulfilled!

[dret]

ffb2afc should fix this.