Spec: Multiple Filters / Flexible Meta Details (advanced extra notation)

[jaruba]

Proposing changes:

manifest {
    catalogs: [
        {
            filters: [
                {
                    name: 'genre',
                    values: [...]
                }, {
                    name: 'platform',
                    values: [...]
                }, {
                    name: 'year',
                    values: [...]
                }
            ],
            extraSupported: [ 'skip', 'genre', 'platform', 'year' ]
        }
     ]
}

We use select boxes for the filters on the Discovery Page instead of one vertical list.

meta {
    details: {
        year: 1997,
        genre: ['Action', 'Shooter'],
        platform: ['PC', 'Mac'],
        description: 'something'
    }
}

We generate the Detail Page based on meta.details.

If a meta.details property is also in extraSupported of the current catalogue, we link it back to the Discovery Page with the filter set.

[Ivshti]

Alternative proposal:

Do this as an extension (verbose syntax) for extraRequired/extraSupported

Rather than extraSupported: ['genre'], we would use extra: [{ name: 'genre', isRequired: false, values: ['Action', 'Comedy'...] }]

Some things to be decided:

1. is a human friendly name needed
2. should we have a defaultValue for extraRequired or just assume the first

Then, we only load "complete" (better name: defined/defaultable?) catalogs, which means that they have no extraRequired properties without a default value

[Ivshti]

closing in favour of #49