Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[Compat Data] Various compatibility tables
6 views
Skip to first unread message
Jeremie Patonnier
Feb 3, 2014, 1:41:05 PM2/3/14
to dev-mdc, dev...@lists.mozilla.org, Holly Habstritt
Hi!
Among the various point that have been raised regarding compatibility data,
there is the form that can take a compatibility table.
It exists various ways to display compatibility data. One of the most used
on MDN or elsewhere are compatibility tables. The way caniuse.com display
its data seams to have some traction. However there is other data table
layout to consider based on various needs.
I try to summarized what could be done if we would be able to have our data
available in a more structured way.
Please, take a look at those first rough schema and tell me if you see
other use cases that need to be addressed or if you have opinions about
those ones:
- caniuse style layout:
https://wiki.mozilla.org/images/e/ee/Compat-tables-mockups.png
This an operational view for people working on a given feature.
- Current MDN style layout:
https://wiki.mozilla.org/images/6/63/MDN-compat-table.png
This also an operational view for people working on a set of feature and
need a detailed overview.
- mobilehtml5 style layout:
https://wiki.mozilla.org/images/f/fe/Mobilehtml5-compat-table.png
This is a more decisional view that provide a global overview. It's very
useful for project managers or web architects who want to know what can be
used on their projects.
- Filtered layout:
https://wiki.mozilla.org/images/4/4e/Filter-compat-tables.png
Those are other possible layouts, extends with filtering features. They
are mainly decisional view more browser centric. As soon as we have
structured data, it become easy to build such things. So the question is:
How far should we go, for whom and why?
NOTE: Those schema are not formal UX mockups and are mainly a way to make
things clearer regarding data to display (it's still a bit early to move
very fare on the UX side). However, Holly, as you are copy of this e-mail,
please, feel free to share your thought :)
Best,
--
Jeremie
.............................
Web : http://jeremie.patonnier.net
Twitter : @JeremiePa <http://twitter.com/JeremiePat>
Among the various point that have been raised regarding compatibility data,
there is the form that can take a compatibility table.
It exists various ways to display compatibility data. One of the most used
on MDN or elsewhere are compatibility tables. The way caniuse.com display
its data seams to have some traction. However there is other data table
layout to consider based on various needs.
I try to summarized what could be done if we would be able to have our data
available in a more structured way.
Please, take a look at those first rough schema and tell me if you see
other use cases that need to be addressed or if you have opinions about
those ones:
- caniuse style layout:
https://wiki.mozilla.org/images/e/ee/Compat-tables-mockups.png
This an operational view for people working on a given feature.
- Current MDN style layout:
https://wiki.mozilla.org/images/6/63/MDN-compat-table.png
This also an operational view for people working on a set of feature and
need a detailed overview.
- mobilehtml5 style layout:
https://wiki.mozilla.org/images/f/fe/Mobilehtml5-compat-table.png
This is a more decisional view that provide a global overview. It's very
useful for project managers or web architects who want to know what can be
used on their projects.
- Filtered layout:
https://wiki.mozilla.org/images/4/4e/Filter-compat-tables.png
Those are other possible layouts, extends with filtering features. They
are mainly decisional view more browser centric. As soon as we have
structured data, it become easy to build such things. So the question is:
How far should we go, for whom and why?
NOTE: Those schema are not formal UX mockups and are mainly a way to make
things clearer regarding data to display (it's still a bit early to move
very fare on the UX side). However, Holly, as you are copy of this e-mail,
please, feel free to share your thought :)
Best,
--
Jeremie
.............................
Web : http://jeremie.patonnier.net
Twitter : @JeremiePa <http://twitter.com/JeremiePat>
0 new messages