Re: Standardization status

Hi Lea,

I'm new here, at the moment I'm working on documenting the Device APIs with
Chris' help, so I played with the wiki for a while and would like to share
with you my thoughts.

Here are some considerations:

- Since the "title" attribute doesn't work on mobile touch devices, we need
something else: what if the indicator is clickable and opens an in-page
popup with an explanation of the standardization status? Alternatively, it
might simply link to the a mobile-friendly page where the W3C process is
explained. On no-touch devices, laptops and desktops, this might be
achieved including a little question mark icon, as Chris suggested.

- Since the W3C specifications change quite rapidly, at least for Device
APIs, it would be useful for contributors, and maybe also for readers, to
know which version (and on which date) the documentation page refers to.
For example, I'm writing the documentation for Media Capture And Streams,
referring to the W3C Working Draft 16 May 2013. The indicator is set to
"W3C Working Draft", that means I'm not referring to the newer editor's
drafts, but it's not clear I'm referring to that specific version: I'm
keeping track of that in the notes.

Anyway, I think the key word here is simplify, and that's what your
infographics do :)

Regards,

Francesco <http://www.francesco.iovine.name>


On 12 July 2013 03:47, Julee <julee@adobe.com> wrote:

> I think these infographics are great! A few comments:
>
> 1. Should they link to the explanation of the icon or to the specification
> section, below?
>
> 2. What's the value for a proprietary feature?
>
> 3. I thought the original requirement was for an icon that represents a
> combination of spec status and vendor implementation, with the ability to
> link to more detailed information about the specification or compatibility.
>
> In other words, the original idea was to give the visitor a quick
> indication of whether a feature was production-ready (stable and
> implemented across browsers). If this is still the main experience we're
> shooting for, then maybe we can reduce the number of W3C statuses and add
> implementation "statuses"?
>
> J
>
> ----------------------------
> julee@adobe.com
> @adobejulee
>
>
>
>
>
> -----Original Message-----
> From: Lea Verou <lea@w3.org>
> Date: Thursday, July 11, 2013 3:32 AM
> To: Doug Schepers <schepers@w3.org>
> Cc: Chris Mills <cmills@w3.org>, Nic da Costa <njr.dacosta@gmail.com>,
> WebPlatform Community <public-webplatform@w3.org>
> Subject: Re: Standardization status
>
> >Hi Doug,
> >
> >Should I link each status to the appropriate section there?
> >
> >There aren’t any sections for the non W3C Rec track statuses...
> >
> >I will also look into including the icons on each section.
> >
> >Cheers,
> >Lea
> >
> >Lea Verou
> >W3C developer relations
> >http://w3.org/people/all#lea ? http://lea.verou.me ? @leaverou
> >
> >
> >
> >
> >
> >
> >On Jul 11, 2013, at 13:31, Doug Schepers <schepers@w3.org> wrote:
> >
> >> Hi, folks-
> >>
> >> Here's the page explaining the standards statuses for W3C:
> >> http://docs.webplatform.org/wiki/Standards/W3C
> >>
> >> It would be nice if we could transclude each section as appropriate
> >>into the articles.
> >>
> >> Regards-
> >> -Doug
> >>
> >> On 7/11/13 4:38 AM, Chris Mills wrote:
> >>> Love the icons Lea.
> >>>
> >>> To combat the issue about people not knowing what the icons mean, how
> >>> about including a little question mark icon near to where the icon is
> >>> going to go, which when followed goes to a  page showing all the
> >>> icons in sequence, along with a paragraph next to each one explaining
> >>> what each means?
> >>>
> >>> Chris Mills Opera Software, dev.opera.com W3C Fellow, web education
> >>> and webplatform.org Author of "Practical CSS3: Develop and Design"
> >>> (http://goo.gl/AKf9M)
> >>>
> >>> On 11 Jul 2013, at 07:56, Nic da Costa <njr.dacosta@gmail.com>
> >>> wrote:
> >>>
> >>>> The only reason i brought this up as i viewed these on my phone
> >>>> this morning and wasn't sure what they each stood for. And i agree,
> >>>> a legend isn't the solution as having to navigate to another page
> >>>> just to view it won;t work.
> >>>>
> >>>> Just a thought, what about something like wrapping the text around
> >>>> the indicator stating what it stands for, something like this [1]?
> >>>> Having it split up around the top and the bottom? I will try do a
> >>>> quick mock-up later today with the examples you sent to see how it
> >>>> looks.
> >>>>
> >>>> [1] http://codepen.io/chriscoyier/pen/circle-type/
> >>>>
> >>>> // Nic da Costa
> >>>>
> >>>>
> >>>> On 11 July 2013 08:31, Lea Verou <lea@w3.org> wrote: Hi Nic,
> >>>>
> >>>> Glad you like it!
> >>>>
> >>>> You are raising a very good point. Honestly, I don’t know. :(
> >>>> Suggestions welcome.
> >>>>
> >>>> Eventually these statuses will link to pages explaining what they
> >>>> mean, so at least that will be some help. Although, you certainly
> >>>> shouldn't need to load another page just to find out the status.
> >>>>
> >>>> Perhaps we could have a legend somewhere for now? I don’t like this
> >>>> solution because most people won’t look at it, but it’s better than
> >>>> nothing.
> >>>>
> >>>> Doug, since it was your idea, perhaps you’ve thought about this?
> >>>>
> >>>> Cheers, Lea
> >>>>
> >>>> Lea Verou W3C developer relations http://w3.org/people/all#lea ?
> >>>> http://lea.verou.me ? @leaverou
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Jul 11, 2013, at 09:18, Nic da Costa <njr.dacosta@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Hey Lea
> >>>>>
> >>>>> They look awesome! I really like them.
> >>>>>
> >>>>> Is there a key on one of our pages indicating what each indicator
> >>>>> means? As currently to determine what the indicator is ( if you
> >>>>> aren't already familiar with them ) you have to hover over them,
> >>>>> but what if this is mobile or other touch devices? How are new
> >>>>> user's going to know what the indicator stands for?
> >>>>>
> >>>>> Otherwise i think they look great!
> >>>>>
> >>>>> // Nic da Costa
> >>>>>
> >>>>>
> >>>>> On 11 July 2013 06:54, Lea Verou <lea@w3.org> wrote: A few days
> >>>>> ago Doug asked me to redesign the standardization status ribbon,
> >>>>> because it was misleading and too obtrusive. A very good point he
> >>>>> made was that we should indicate what each status means, not just
> >>>>> the name. For example, many people don’t know that Proposed
> >>>>> Recommendations are more mature that Candidate Recommendations or
> >>>>> that an Editor’s Draft comes before a Working Draft. So, we
> >>>>> worked together on a standardization status that looks more like
> >>>>> a progress indicator for W3C statuses. Today I worked a bit on
> >>>>> the other, non-W3C statuses as well, so I wanted some feedback.
> >>>>>
> >>>>> Here’s a dabblet with all statuses:
> >>>>> http://dabblet.com/gist/5922066
> >>>>>
> >>>>> And here are various statuses in context: ED:
> >>>>> http://docs.webplatform.org/wiki/OLD:css/cssom/CSSRegionStyleRule
> >>>>>
> >>>>>
> >> WD: http://docs.webplatform.org/wiki/css/properties/shape-outside
> >>>>> LC: http://docs.webplatform.org/wiki/css/functions/var CR:
> >>>>> http://docs.webplatform.org/wiki/css/properties/border-radius
> >>>>> REC: http://docs.webplatform.org/wiki/css/properties/font-size
> >>>>> Deprecated:
> >>>>> http://docs.webplatform.org/wiki/html/attributes/lowsrc
> >>>>> Experimental:
> >>>>> http://docs.webplatform.org/wiki/css/properties/shape-inside
> >>>>>
> >>>>> Also, I realized W3C Proposed Recommendation is not in the
> >>>>> allowed statuses [1]. Someone should add it. I’d do it myself,
> >>>>> but I’m not sure how.
> >>>>>
> >>>>> [1]:
> >>>>> http://docs.webplatform.org/wiki/Property:Standardization_Status
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> Cheers, Lea
> >>>>>
> >>>>>
> >>>>> Lea Verou W3C developer relations http://w3.org/people/all#lea ?
> >>>>> http://lea.verou.me ? @leaverou
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>
> >
>
>
>
>