Organization of catalog.json

This is a proposed structure for catalog.json, based on cdorn’s tusk-catalog fork http://github.com/cadorn/narwhal/tree/tusk-catalog/

It roughly follows the schema

catalog_name, type, origin, packages[ 
    package_name : [ 
       [ installation_info_if_installed ],
       [ source_package_info ],
       [ package_metadata]  # this is the entire contents of the package's package.json file
     ],
     another_package_name : [ ......
  ]

Here is an example from http://github.com/cadorn/narwhal/blob/tusk-catalog/docs/tusk.md

 
{
    "name": "com.github.tlrobinson.narwhal",       
    "type": "sea",
    "origin": {
        "locate": "http://github.com/cadorn/narwhal/raw/master/catalog.json"
    },
    "packages": {
        "narwhal": [
            ["source", {
                "locate": "file://./",
                "package": "narwhal",
                "revision": "latest"
            }],
            ["latest", {
                "locate": "http://github.com/tlrobinson/narwhal/zipball/master/",
                "package": "narwhal",
                "revision": "master"
            }]
        ],
        "template": [
            ["source", {
                "locate": "git://github.com/gmosx/template.git",
                "package": "template",
                "revision": "master"
            }],
            ["latest", {
                "locate": "http://github.com/gmosx/template/zipball/master/",
                "package": "template",
                "revision": "master"
            }]
        ]
    }
}