Extend the 'our-journey' JSON format to support meta-data

[nfreear]

Hi @timcoughlan,

Can I suggest that you/we nest the journey data deeper in the saved JSON, to allow arbitrary meta-data to be recorded?

So instead of ... :

[
  {
    "eID": "place0",
    "description": "test description 0",
    "emoticon": "happy",
    "icon": "timelost",
    "postit": "post it text"
  },
  {
    "eID": "place1",
    "description": "test description 1",
    "emoticon": "happy",
    "icon": "timelost",
    "postit": "post it text"
  }

  ...
]

... We have, for example:

{
  "schema-version": "1.0",
  "#": "Save date ~ 2017-06-23T22:17:00",
  "summary": "My first journey",
  "url": "https://iet-ou.github.io/our-journey/#!id=ab12cd34ef",
  "generator": "our-journey/v1.2.3",

  ...

  "journey": [
    {
      "eID": "place0",
      "description": "test description 0",
      "emoticon": "happy",
      "icon": "timelost",
      "postit": "post it text"
    },
    {
      "eID": "place1",
      "description": "test description 1",
      "emoticon": "happy",
      "icon": "timelost",
      "postit": "post it text"
    }

    ...
  ]
}

No rush !! ;)

Ta,

Nick

[nfreear]

Note, I've created a draft JSON schema -- with quite tight constraints!

(A useful document about JSON schema.)

To discuss ...

N.