On Sat, 2011-05-07 at 14:03 +0200, Jeremiah Foster wrote: > Is this the current canonical source for compliance in MeeGo? > > In that document it states "Currently MeeGo supports five different > verticals: Netbooks, Handsets, Connected-TVs, In-Vehicle Infotainment > systems and tablets. Each of these verticals will have a Compliance > Profile." I take that to mean that the In-Vehicle Infotainment (IVI) > will have a separate compliance specification.
Hypothetically, what about a device that doesn't fit into any of these categories? What if it doesn't have a traditional "display"/"touchscreen"/"mouse"/"ivi-scrollwheel"/etc. or what if the human interface is remote, over a network, or implemented entirely over audio? What if the device looks like clothing, a wristwatch, a wall-wart or "black box" or audio component, a video camera, or a portable music player? What is the compliance profile of http://www.cyberstep.com/kdj/ ?? (its based on IVI UX according to gabrbedd in #meego -- and i guess it qualifies as IVI if you're riding the bus or train with one :-) ). -- Niels P. Mayer <[email protected]> _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
