Improve data structure for pathway relationships

[timothyfcook]

So that parents can have multiple children and children can have multiple parents.

This is sort of currently possible, but it's messy.

One child can have two parents (if they both list the child in their comes_before property) but one child can only reference one parent (because the child's comes_after property only contains a single reference).

[timothyfcook]

might be something like this:

{
  "on_pathways": [
    {
      "name": "Cooking and Eating",
      "name-slug": "cooking-and-eating",
      "before_this": ["resource-example-a", "resource-example-b", "resource-example-c"],
      "after_this": ["resource-example-e"]
    }

    {
      "name": "Composting",
      "name-slug": "composting",
      "before_this": ["resource-example-u", "resource-example-v"],
      "after_this": ["resource-example-y", "resource-example-z"]
    }
  ],
}

[timothyfcook]

This could possibly be addressed by the work be done to define a standard pathways data spec: 1EdTech/openbadges-discussion#24