- From: Aaron Gustafson <notifications@github.com>
- Date: Mon, 01 May 2017 17:38:00 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 2 May 2017 00:38:35 UTC
I think this makes a lot of sense and I’m inclined to have the spec define the canonical list. Then it would be up to the individual app stores to map those standard categories to their specific ones internally (rather than putting the onus on the developer to track all of the various categories run by each app store—and any new ones that crop up). So, for simplicity: * Business * Books * Education * Entertainment * Food * Health * Lifestyle * Maps * Medical * Music * News * Productivity * Shopping * Sports I’m also fine with authors being able to define additional sub-categories if they want. Direction doesn’t really matter to me much. Font families go one way (cascading backwards until a match is made), the original concept of `class`-ification started general and grew more specific (BEM and similar classification schemes echo this as well). I don’t really have a preference, but I do think the order should be defined rather than random. From a processing standpoint, its 6-of-one: `shift()` or `pop()`. I also think non-English categories provide a nice option as long as the canonical category is included in the appropriate position. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/569#issuecomment-298468874
Received on Tuesday, 2 May 2017 00:38:35 UTC