Posts in the W3C Category

CSS3 Feedback: Selector Blocks

Published 13 years, 4 months past

(This is part of the Feedback on ‘WaSP Community CSS3 Feedback 2008’ series.)

Out of all the selector feedback, selector blocks was the part that really caught my attention.  I also see the usefulness of a parent selector, but that one has come up many times before, and it’s always died at the doorstep of implementors, who point out that it’s far too difficult to implement without serious performance penalties and even risk of browser lockup.  See, for example, the comment left by David Hyatt on Shaun Inman’s post on the idea.  Similarly, I think constants (or macros or whatever they’re called) are a great idea and would be very helpful, especially if you’re coding up a Jason Special.  Both are loaded with use cases, so I don’t feel like I can add a lot; besides, constants are already in the WG charter, so there’s once more hope in the land.

So anyway, selector blocks.  To pick one recent example, while working on a project that should very soon see the light of day, I had a situation involving the following chunk of rules.

h1, h2, h3, h4, h5, h6, table {
   font: 1em Arial, "Helvetica Neue", Helvetica, sans-serif;}
h1 {font-size: 275%;}
h3:first-child {margin-top: 1em;}
p.tagline {margin: -0.25em 0 1.25em;
   font-size: 125%;
   color: #7B7960;}
h3 {margin: 1.5em 0 0.25em; font-size: 125%;}
h3:before {font-size: 75%; counter-increment: subhead;}
h4 {margin: 2.5em 0 0.75em;
   text-transform: uppercase; font-size: 125%;
   color: #928F59;}
p {margin: 0 0 1em;}
ul {padding-left: 1.5em;}
ul li {list-style: disc; margin: 0.5em 0;}

Nothing unusual about them, of course, unless you count my use of counters.  These rules had been written early on in development, and the design had evolved around that part of the document.  As more page components were added, I realized that I needed to scope all these rules to one section of the document: specifically, a div with a class of main.  So here’s what I had to do.

.main h1, .main h2, .main h3, .main h4, 
.main h5, .main h6, .main table {
   font: 1em Arial, "Helvetica Neue", Helvetica, sans-serif;}
.main h1 {font-size: 275%;}
.main h3:first-child {margin-top: 1em;}
.main p.tagline {margin: -0.25em 0 1.25em;
   font-size: 125%;
   color: #7B7960;}
.main h3 {margin: 1.5em 0 0.25em; font-size: 125%;}
.main h3:before {font-size: 75%; counter-increment: subhead;}
.main h4 {margin: 2.5em 0 0.75em;
   text-transform: uppercase; font-size: 125%;
   color: #928F59;}
.main p {margin: 0 0 1em;}
.main ul {padding-left: 1.5em;}
.main ul li {list-style: disc; margin: 0.5em 0;}

This, on the other hand, is what I really wanted to do:

.main {
   h1, h2, h3, h4, h5, h6, table {
      font: 1em Arial, "Helvetica Neue", Helvetica, sans-serif;}
   h1 {font-size: 275%;}
   h3:first-child {margin-top: 1em;}
   p.tagline {margin: -0.25em 0 1.25em;
      font-size: 125%;
      color: #7B7960;}
   h3 {margin: 1.5em 0 0.25em; font-size: 125%;}
   h3:before {font-size: 75%; counter-increment: subhead;}
   h4 {margin: 2.5em 0 0.75em;
      text-transform: uppercase; font-size: 125%;
      color: #928F59;}
   p {margin: 1em 0;}
   ul {padding-left: 1.5em;}
   ul li {list-style: disc; margin: 0.5em 0;}

Or, if necessary, to put the whole original chunk into its own style sheet and then do one of the following:

div.main {@import url(main-style.css);}

<div class="main" style="@import url(main-style.css);">

Interestingly, the latter is theoretically possible, thanks to the more advanced profiles in the CSS module “Syntax of CSS rules in HTML’s ‘style’ attribute“.  I’m not aware of the former having been seriously considered (despite my best efforts, once upon a time), though it’s always possible I missed something.

But either one of those approaches would be a last resort, in my opinion.  I’d much rather just wrap the whole chunk in .main { }, like I showed previously, and be done with it.  That capability would also simplify certain annoyingly repetitive patterns, like the very first of those rules.  I think it’s pretty obvious which of the following is easier to write and maintain:

body.home #content .entry h2, 
body.home #content .entry h3, 
body.home #content .entry h4, 
body.home #content .entry h5, 
body.home #content .entry h6 {...}

body.home #content .entry {
   h2, h3, h4, h5, h6 {...}

I mean, just look at the former, and imagine what one goes through to write it in the first place.  Copy, paste, paste, paste, paste, paste… maddening.  And that’s just for a small block of CSS like this one.  Imagine the tedium of doing this for a block of 50 rules, or 150.  (Also, this is the the same thing that was requested in the feedback as “Grouped Alternates“, albeit with a different syntax.)

One objection to this sort of pattern is that it increases dependence on descendant selectors, which are computationally inefficient.  But it doesn’t: I had to create a whole bunch of descendant selectors as it was, and did so far more clumsily.  And had I missed a command-V somewhere, I’d have had styles that applied outside their intended subtree.  Introducing a way to nest blocks like this doesn’t change anything except make it easier and more maintainable to do what we already do.  Honestly, it’s pretty much impossible to increase dependence on descendant selectors.  The best we can do now is make them less difficult to write.

I realize that the syntax I depict would cause backwards-compatibility problems, as in older browsers would not behave as intended when exposed to this sort of thing, but I’ve also stopped being concerned about that.  We can’t keep holding ourselves hostage to decisions made a decade or more back.  Provide the capability and authors will use it when they can.  Over time, its use will become more prevalent—kind of the same way authors adopted CSS in the first place.

I also realize that this case has been made time and again by many, many other people.  This isn’t even the first time I’ve made this case, though I think the other times were within the WG and therefore off the public record.  The fact that it keeps being made is a strong indicator that the need exists, and dismissing the idea because the same end effect can be achieved with existing selector syntax (as shown above) isn’t acceptable.  That’s like saying that complex selection effects can be achieved with JavaScript or XPath, so there’s no need for advanced CSS selectors.

So that’s my use case.  I actually have a bunch more, but they all follow the same basic pattern: the desire to group rules together into subsections of a document, or to otherwise simplify the writing of CSS.

Feedback on ‘WaSP Community CSS3 Feedback 2008’

Published 13 years, 4 months past

Back before holiday season hit, Elika Etemad—better known as Fantasai—published WaSP Community CSS3 Feedback 2008.  I gave it a read and came away with a number of things I wanted to say.  So many things, in fact, that I’ll need to split them up into a series of posts.  This here post will serve as introduction and hub, with links to the follow-on entries added as they’re published.  All very Bray-ny, no?  (Go ahead, groan.  It only encourages me.)

Here you go:

  1. Selector blocks
  2. Layout
  3. Wanted: Layout System
  4. Animated Shapes
  5. Graphical Thoughts

I want to make clear up front that I’m not going to address every single point in the feedback document: it’s just too incredibly huge.  I did think about making my own copy and then just filling in my reactions to each point, but that didn’t scale very well.  Not only did it seem really overbearing and maybe just a touch egotistical, but some of my reactions were based on related topics in separate areas of the original.  Besides, I know what it’s like trying to read a really, really long article, so breaking it up and just focusing on the parts that got me fired up made way more sense.

There is one thing I want to address before I start serving up the follow-on installments.  At the end of Fantasai’s post, there’s a link to my 2006 post about the benefit of having a community liaison, someone who bridges the gap between the WG and the public.  She then asks if anyone is interested in volunteering, but personally, I don’t see the need.  The WG already has a community liaison:  it’s you, Fantasai.  It has been for some time now, thanks to your regular and informative CSS WG blog posts and other outreach work such as “WaSP Community CSS3 Feedback 2008”.  The job is being done, and being done very well, I don’t think there’s any doubt that the Working Group is much, much better for it.

W3C Change: Your Turn!

Published 15 years, 8 months past

So recently, I shared a number of ideas for improving the W3C, the last of which (posted a week ago) was to transition from a member-funded organization to a fully independent foundation of sorts, one that was funded by the interest earned by an endowment fund.  Surprisingly, there seemed to be little objection to the idea.  That was the one thing that I figured would get some pushback, mainly due to the magnitude of the change involved.  I’m still interested in hearing any counter-arguments to that one, if somebody’s got ’em (thought they’d be best registered on that particular post, and not here).

The other thing I was expecting to see, but didn’t, was other people’s ideas for improvements to the W3C.  That was probably my fault, given the way I wrote the posts, which now that I look at them were set up more as soliloquies than the beginnings of a discussion.  While I think my ideas are good ones (of course!), I’m only one person, and I very much doubt I’ve thought of everything.

So what are your thoughts for improving the W3C’s effectiveness and standing in the field?

W3C Change: Full Independence

Published 15 years, 9 months past

Apologies for the break in posting just as I was getting to the best part of the W3C Change series, but back-to-back trips to Seattle and Dallas came up before I could finish writing up my thoughts.  This one was, for all the simplicity of the content, the hardest one to write, because I kept revising it to try to be more clear about what I’m proposing and how it would be an improvement.  I could keep revising ’til the end of forever, so I’m just going to take what I have now and go with it.

My third recommendation is simply this: Transform the W3C from a member-funded organization to a financially independent entity.

In order to accomplish this, the W3C would need to embark on a major capital campaign, similar to the efforts mounted by major non-profit organizations and American private universities.  The campaign parameters that come to mind are a ten-year campaign whose goal is to build an endowment of $200 million.  From the interest on this endowment—which at a relatively modest 5% return would be $10 million annually—the W3C could fund its activities.

(Note: I do not have access to the budget of the W3C, but with approximately 70 staff members at an average total cost of $125,000 per year in salary, benefits, and travel expenses, the staffing cost would be $8.75 million.  If I am lowballing the budget, then obviously the capital campaign’s goal would have to be raised.  The general approach remains the same.)

As the campaign progressed, the membership dues would be reduced across the board in proportion to the progress of the campaign.  Once the campaign reached its end and the full endowment had been acquired, the dues would fall to zero and the membership model would be dismantled.

You might wonder where the blinking font the W3C could get that kind of money, even over the course of a decade.  Well, 20 Internet billionaires could each donate $10 million in thanks for the W3C making their fortunes possible, and there you go.  Even if that doesn’t happen, there are many foundations whose goal is to foster better technology and communications, and who might be persuaded to contribute.  Government grants could help.  And, of course, a supporter campaign like that run by the EFF would allow individual developers to add their support.

Frankly, I don’t think the problem would be finding the money, especially over a ten-year period.  By hiring an experienced fund-raiser, I think the funds could be raised a good deal more quickly.  I think this would be especially true if Sir Tim publicly put his weight behind the effort, and made personal appeals to potential major donors.

But why would I even suggest such a thing?

  1. The current membership model creates an apparent wall between the W3C and the rest of us.  Because it costs a minimum of $15,000 over three years to become a W3C Member, individuals will rarely, if ever, be able to justify membership.  The same is true of web design and development shops.

    For primarily this reason, there is the belief that non-paying members of the community cannot join Working Groups, and that the WGs are forever closed to the rest of the world.  This is not really true, since any Working Group can ask people in the community to become Invited Experts.  These are Working Group members who don’t have to pay to get in, and aren’t necessarily held to the same contribution standards as Member representatives.  (Not that contribution standards are always upheld for them either, as I observed in an earlier post.)

    So now imagine a W3C where there are no Members.  That means that every Working Group is comprised entirely of Invited Experts (except for any W3C staff members who might join).  This bridges the perceived gap, and puts community members on a more equal footing with those who would currently be Member representatives.  I’m not saying there wouldn’t be company representatives at all.  The CSS WG is going to have representatives from Microsoft, Mozilla, Apple, and so on.  The alternative is for them to not participate, and thus be at the mercy of what happens in their absence.

    Since someone’s going to bring it up, I’ll address the Microsoft question.  You might think that Microsoft could decide to both abandon, say, the CSS WG and ignore what it produces.  (Anyone could do this, but Microsoft is going to be the company accused of hypothetically plotting such a thing.)  That could well be.  But wouldn’t Microsoft departing the CSS WG be a large red flag that something’s seriously wrong, and that it needs to be addressed before worrying about exactly how the layout module is written?

    Of course, some other player could do this as easily as Microsoft.  The point is really that, if a major player in the space with which the WG is concerned departs that WG, then it identifies a situation that needs to be addressed.  The Member model actually goes some small way toward concealing that, because the dues paid create a certain impetus to put someone on a WG, even if there’s no serious interest.

    The flip side of this is the question, which I’ve heard more than once from people when I talk about this idea, “How would a WG force the players to the table?”  For example, how could a new browser-technology WG force the browser makers to join the group?

    The question itself betrays a fallacious assumption: that players should be forced to work together.  If you propose to form a WG that doesn’t interest one or more of the major players in the field, then the WG may well be flawed from the start.  The point of a WG is to produce an interoperable standard.  If a WG just goes off and does something without buy-in from players, and there’s never an implementation, then the whole effort was wasted.  On the other hand, a specification that was produced with the involvement of all the major players stands a much better chance of being implemented, and thus a much better chance of being used and appreciated by the community.

    The flip side of that flip side is the question, “What if a WG refuses to admit a player in the field?”  In other words, what if the CSS WG barred Microsoft from having a representative on the WG?  Again, that would be an enormous red flag that something had gone awry.  Any WG that refused to involve an important player in their field would need to be scrutinized, and probably reformatted.

    All this does raise the spectre of replacing a centralized model with a consensus model.  Which is just fine with me, for all the reasons I just mentioned.

  2. There is the perception—largely untrue, but no less persistent—that the W3C is controlled by those who fund it.

    It’s actually been my experience that there’s an inverse correlation between the amount of money a company puts into the W3C and the frequency with which their representatives get their way.  During my time in the CSS WG, the Microsoft people faced more resistance and more grief from the rest of the WG than the Netscape reps ever dreamed of getting.  CSS-like things which IE/Win had done faced a serious uphill battle to be incorporated in the specification, even when they were good ideas.  I don’t know how to explain this odd variance from the usual effect of money, but it was there.  Maybe in other WGs, the situation is different, although I kind of doubt it.

    But as I say, the perception is persistent.  A financially independent W3C would remove that perception.  I wouldn’t propose this kind of funding-model change solely to clear up some erroneous perceptions, but it’s an undeniably positive side effect.

  3. Full financial independence allows the W3C to do things that its dues-paying Members likely wouldn’t permit.

    Now what could I be talking about, since I just claimed that dues money doesn’t drive what the W3C does, except in inverse ways?  What I’m talking about is things like launching a program to pay Invited Experts a small stipend.  Currently, Invited Experts receive no financial support, whereas Member representatives are supported by their employers while devoting some of their time to the W3C.  I tried to imagine a world where the dues-paying Members of the W3C approved the idea of paying Experts, and although I managed to do so, it turned out to be entirely populated by talking kawaii unicorns who get joyfully teary about their perpetually rainbow-filled skies and giggle a lot.

    Here’s another W3C effort which probably could never get funded under the current model:  a university scholarship for students who plan to study the web, or uses of the web.  They might fund independent research on the effects of the web in developing countries, or what users want, or any number of other things.  Or hey, how about putting enough money into the WWW conference series that people who present papers are given a complimentary registration?  (I know—radical!)

    These things couldn’t happen if the W3C’s endowment generated only enough interest to cover staffing and overhead, but the endowment doesn’t have to be limited to just that much.  A second capital campaign, or a simple continuation of the first one, could increase the endowment, thus giving the W3C (potentially) quite a bit of discretionary funding.  It would give them the opportunity to spend money on efforts that advance their core mission (“To lead the World Wide Web to its full potential by developing protocols and guidelines that ensure long-term growth for the Web”).

There are various knock-on effects that arise from those points, of course, but I’ve gone on long enough.

As many of you have noticed, I’m effectively proposing that the W3C become a foundation instead of a consortium, albeit a foundation whose primary mission is to act as a consortium would.  I’ve avoided using terms like “non-profit” and “not-for-profit” because they might imply specific things which I don’t fully intend in terms of tax law, or whatever, but I do think of it as a generically non-profit institution; that is, one that does not strive to create a profit, except as can be invested into the endowment.

I’ve tried to explain why I believe this is a good idea, but in the end, I think the most fundamental reason is that one I can’t explain:  it just feels like the right thing to do.  It’s like I can perceive a shape without grasping all its details, but the overall shape looks right, looks better.

I fully expect that some will recoil from this idea, convinced that a foundation is a poor substitute for a consortium.  Obviously, I disagree.  I think the W3C’s future could be made much more stable with this approach, especially in financial terms.  I also believe, as I said before, that it would be no less of a force for the advancement of the web.  In fact, I think it would be a much stronger force, and have a greater positive effect, over the long term.

It is not a small undertaking, but it is an important and worthwhile effort, and I hope it is one the W3C considers seriously.

W3C Change: Working Groups

Published 15 years, 9 months past

The second area where I think the W3C could be improved is in how Working Groups are populated and managed.  To a large extent, what I propose is just a re-commitment to existing rules, and isn’t particularly radical.  That doesn’t make them any less important, of course.  Furthermore, this area of discussion doesn’t boil down to one talking point; rather, it boils down to three.

First is this: participants in a Working Group should be productive, or else leave the group, whether voluntarily or otherwise.

This is really already part of the rules, but it’s not very well enforced, in my experience.  I mean that personally, too: between mid-2003 and mid-2004, I contributed almost nothing to the CSS WG.  I didn’t even phone in for teleconferences, let alone contribute to specifications.  Now, as an Invited Expert, the participation rules aren’t quite the same for me as they are for Member representatives, but by any measure, I was deadweight.  I was only on the WG membership list out of inertia.

When the WG’s charter came up for renewal in 2004, the chair asked me if I wanted to stay in the group and start contributing again.  After some reflection, I said no, because I wasn’t going to magically have more time and energy to give to the WG.  To stay would have been dishonest at best, so I left.

Honestly, though, he should have asked me the same question (and been a little more pointed about it) six months previously.  WG chairs should do the same for any member who falls silent.  The actual reasons for the silence don’t matter, because having a WG member step down isn’t a permanent excommunication.  It’s simply an acknowledgment that the person is too busy to be a contributing member, and so leaves the group, whether temporarily or for good.

Ideally, people would voluntarily do this upon recognizing their lack of participation, but not everyone would.  I didn’t, until I was prompted.  WG chairs should prompt when necessary, and even be empowered to place someone on inactive status if they don’t contribute but refuse to step down.  Again, this isn’t a permanent decision, and it isn’t punishment.  It’s just keeping the WG membership list aligned with those who are actually contributing.

This brings me to the second point, related very closely to the first: Working Groups should have a minimum membership requirement.

If a WG doesn’t have enough members to operate, then it needs to be mothballed.  Simple as that.  If you had ten WG members and eight of them went silent, leaving you with only two active members, then it’s time to close up shop for a while.  No WG would ever be permanently shuttered this way:  it would simply be placed on “inactive” status.  Once enough people committed to being contributing WG members, it could be re-activated.  Granted, this would require a re-chartering and all the other things necessary during that process.

I also have to figure that if a WG was in danger of going inactive, some of the group’s members would get involved again.  If not, word would spread and community members would step up to offer their help.  And if none of that happened, then it would be a pretty strong indication that the WG did need to be shut down, for general lack of interest.

Of course, all this requires a WG chair who is willing to hold people’s feet to the fire, to cut inactive members, and to shut down his own WG if there aren’t enough active participants.  But then WG chairs are already required to do a lot of things, and not all of them get done.  Some are trivial; some are not.

The biggest obstacle a WG can face is its own chair, if said chair is abrasive or obstructionist or just plain out of touch.  As things stand, the only way to lodge a complaint against a chair is by working your way up the chain of command at the W3C.  That’s a pretty flat set of rather short chains, though.  In many cases, it doesn’t take a whole lot of steps to reach Sir Tim himself.  And there are even cases where WG chairs are their own bosses, hierarchically speaking, which makes it hard to effectively lodge complaints.

Thus we come to my third suggestion: there needs to be a “vote of no confidence” mechanism for WG chairs.

This is nothing more than a vote by the members of a Working Group:  do we keep our chair, or should he step down?  In this way, the WG itself can decide when it’s time for a leader to go.  I get a little wobbly over the actual vote threshold: should a chair be removed if half the WG votes against him, or two-thirds?  Tough call.  Probably a majority, on the theory that any WG with that many people opposed to the chair is already in deep trouble.

I’m also unable to decide whether I’d have these votes happen automatically, on a set schedule—say, every year right before the March Technical Plenary—or only when a member of the WG calls for one.  Both approaches have pros and cons.  I think my slight preference is for the set schedule, but on the other hand, requiring a member of the WG to call for a “no confidence” vote would be useful, in that the mere call for a vote would serve as its own indication of trouble in a WG, regardless of the vote’s outcome.

So that’s how I’d reform WG membership and leadership:  participants need to be active; WGs need a minimum membership to continue; and WGs should be able to remove their own chairs when necessary.

W3C Change: Outreach

Published 15 years, 9 months past

My first suggestion for improving the W3C is this:  every Working Group should have one member whose primary (and possibly sole) responsibility is outreach.

To make life a little easier, I’m going to refer to this position as a WGO (for Working Group Outreach).  As an aside, I’m not sure that “outreach” is exactly the right term for what I have in mind, but it’s a decent term that captures most of what I have in mind, so I’ll use it here.  If someone comes up with a better term, I’ll be grateful.

So here’s what I envision for a WGO.

  1. The WGO keeps the public informed about the top issues on the Working Group’s agenda and immediate-future activities.  The easiest, most obvious way to do this is to post a summary of every WG FTF (face-to-face) meeting.  A summary would describe the topics the WG discussed, resolutions that were reached, which problems were not solved, and so forth.  This could be a bullet-point list, but a better summary would be something like a short article.

    Note that I do not say that the WGO should post the FTF minutes, which are often private.  The results of those discussions, though, should be public, even when no results occurred.  A summary can say that the WG discussed a topic at length and reached no resolution without saying why.  It can also say that a topic was discussed and a solution found, and then describe the solution.

    A really good WGO would produce an activity summary more often than every FTF.  I don’t know that I’d insist on a summary for every weekly teleconference, but sending out a summary once a month would be more than reasonable.  These summaries would be posted on the W3C site and to the relevant public mailing lists.  For the CSS WGO, this would always mean posting to www-style.  In cases where WG activity touched on features of XHTML or SVG, summary posts would be made to those public lists as well.

    The purpose here is to draw back some of the curtain surrounding Working Groups.  Too often, interested members of the public don’t know what the WG is up to, and that can be frustrating.  If there are several people agitating for a new feature and the WG stays silent on it, it’s impossible to tell if the WG is blowing the idea off or if it’s something they’ve considered at length but haven’t yet reached a decision.

    Public summaries also have the benefit of allowing some public discussion of work before the public-comment period on a proposed specification.  This would help distribute the WG’s feedback load.

  2. The WGO brings the needs and concerns of the public to the Working Group, and communicates back the WG’s reactions.  This means part of the WGO’s job is to be involved in the wider community surrounding a given activity.  The CSS WGO, for example, would spend time reading web design mailing lists, forums, blogs, and so forth to find out what people in the field want and need (in CSS terms, anyway).  The WGO would present these to the WG as items to consider.  The topics so raised, and the WG’s responses to them, would go into the next summary.

    The goal here, of course, is to have someone on the Working Group who represents the “in the trenches” folks.  If there are other members of the WG who also represent those who work in the field, that’s awesome.  With the WGO position, though, there’s the assurance of at least one person who speaks for those who actually use the products of the Working Group, and who will use any future products.

  3. The presence of a WGO in a Working Group should be a charter condition.  No group should be (re-)chartered without an identified WGO, and the extended lack of a WGO should be cause to question the continued charter of a group.

    Basically, I’m of the opinion that if a WG can’t find someone passionate enough about what they’re doing to be the WGO, then it’s time to ask whether or not they should continue at all.  Similarly, if there’s no real community for the WGO to represent, then it’s time to ask why the WG even exists.

  4. The WGO should have no other major responsibilites within the Working Group.  This means the WGO cannot be the WG’s chair, and should not be a specification editor.  Their primary job should be the two-way representation I’ve described here.

    It’s too easy to get overloaded in a WG, especially if you’re the kind of enthusiast a good WGO should be.  There needs to be a defined limit to the position, so that outreach is always topmost on that person’s agenda within the WG, and it doesn’t get buried under other duties.

In summary, a good WGO would act as a liason between the Working Group and the community surrounding it.  A great WGO would do all that and also produce information that helps expand that community.  They could publish quick how-to’s, for example, concentrating on either current or near-future specifications.

If you could, please allow me to illustrate my points with a few things that a CSS WGO might do in the course of their duties.  I’ll call this CSS WGO “Bob” to make the example less clumsy.

Recently, Bob’s been seeing a lot of calls on blogs for an “ancestor” selector.  This would be something that lets you say, “style this element based on its descendants”, such as styling all links that contain an image without having to class them.  (This idea has come up many times in the past, by the way, but has yet to be added to CSS.)  So Bob brings the “ancestor selector” subject to the WG.  The WG says, “Yes, that’s a very good idea, but it runs aground on the following problems.”  Bob would then put all that into his next summary: “The WG is in favor of adding the ancestor selector, but the following problems prevent its inclusion…”  Bob could certainly also communicate the response directly, through mailing lists or blogs, instead of just putting the response in the summary.  The latter is necessary, of course, but doing both is better.

How is this better?  Because the community knows the WG has considered the idea, where the WG stands on the idea, and the reasons why it hasn’t been accepted.  Everyone knows where the sticking points lie, and can make suggestions to overcome them, instead of just guessing as to why the requested feature hasn’t been adopted.  As for the reasons, they could be anything from “that’s demonstrably impossible in an entropic universe” to “not enough implementors have committed to doing it”.  As long as we know what the roadblock is, we can act accordingly.

Furthermore, Bob might accompany a new version of the Advanced Layout module with a quick how-to article that describes how to do a certain common layout, one that’s very hard to do in current CSS, with the stuff in the new module.  This provides a quick, “wow cool!” introduction to the WG’s efforts, which can energize the community and also draw in new people.

I will readily grant that many WGs have what are effectively unofficial WGOs; in a lot of ways, you could argue that I’ve been a WGO for years, as have several other people, through books and articles and forum participation and blogging and so on.  That’s not enough.  There needs to be someone inside the Working Group who is focused on explaining to the world what the WG is doing and who is explaining to the WG what the world is doing, or at least trying to do.

So that’s the first of my three major suggestions for reforming the W3C: an outreach person for every Working Group.

W3C Change: Introduction

Published 15 years, 9 months past

When I posted about the W3C, a few people responded with, “All right, fine, you’re angry with the W3C.  So what’s your alternative, smart guy?”  A fair enough question.

While I applaud the efforts of the WHAT WG and the microformats community, I’m not advocating a complete dismissal of the W3C.  The basic role filled by the W3C, that of being a central meeting place and coordinating body, is an important one.  It’s also potentially damaging.  Think of it like a central file server at work.  As long as the server is fine, your work can continue.  If it goes offline or, worse, its contents get corrupted, you’re in a very bad position.

When I point to the WHAT WG and microformats, I’m not holding them up as saviors or replacements.  I’m simply drawing attention to effects of the basic problem.  Both communities arose because of the nature and (lack of) speed of the W3C and its work.  We could argue about whether or not they should replace the W3C, but the simple fact is that had the W3C been more responsive and in touch with developer needs, they would never have existed in the first place.  They wouldn’t have had to exist.

If the W3C can get back on track, I wouldn’t want to see it replaced.  If it can’t, then it will be replaced, no matter what I or anyone else has to say.  That doesn’t mean it would cease to exist, of course.  It would simply become less and less relevant.  I have some ideas about how the W3C might avoid such a fate, but they aren’t things that I can cover in a single post.  Instead, I’ll do it in three parts, and the three topic areas I’m going to address are:

No small potatoes, those.  It will be interesting to find out what people think of my proposals for each.

Angry Indeed

Published 15 years, 10 months past

In my head, at any rate, it was Jeffrey‘s angry post that kicked off the latest round of posts about consortium contretemps, even though Jeffrey’s post was triggered (at least in part) by a message posted to the fairly obscure public-qa-dev mailing list by Björn Höhrmann, detailing his reasons for leaving the W3C.

A little over a week later, there came a semi-rebuttal by Molly over at the Web Standards Project, where she talked about a new spirit of “opening up to new things”, like adding “at least one classically trained artist and graphic designer” to the CSS Working Group (a role that’s been more or less vacant ever since Jeff Veen left the WG over half a decade ago).

That’s great to hear, but what’s perversely fascinating to me is that in that very same post, Molly herself lists the reasons why Jeffrey’s anger is in no way misplaced:

Am I defending the W3C’s slow-to-move process or its over-bureaucratized administration? Its lack of attention and sensitivity to gender (count the women, go ahead, dare you) and racial diversity, its frightening disregard for the real needs of the workaday Web world? Oh no, nor would I want to.

It’s that last point that lends the greatest support to Jeffrey’s argument:  “…frightening disregard for the real needs of the workaday Web world”.

What more really needs to be said?  It’s the most concise indictment possible that the first part of the W3C’s mission statement, the fragment they put right on their home page, “Leading the Web to Its Full Potential…”, has been betrayed.

Believe me, I’d prefer things to be otherwise.  I’m still a strong believer in standards, and for seven years (1997 – 2004) put my time and energy into supporting and advancing them as a member of the CSS Working Group.  When I left, it was because I didn’t have the time and energy to contribute any more, and rather than continue to be a deadwood listing on the group’s roster, I left.  But most of the reason I couldn’t come up with the time and energy was precisely what Molly articulated.  I no longer believed in the W3C’s ability to do what it promised, and what I wanted.

But the worst part?  None of this is new.  Look back two years, when David Baron and Brendan Eich walked away from a W3C Workshop in disgust.  To a large degree, both men walked away from the W3C itself at that point—and if you’ve spurred David Baron to turn his back on the web’s central standards body, then boyo, you’ve got some deeply serious problems.

Let’s be frank: a whole lot of people who believe passionately in the web’s potential and want to see it advance fought for years to make that happen through the W3C, and finally decided they’d had enough.  One by one, I saw some of the best minds of my generation soured by the W3C; one by one, the embittered generals marched forward, determined to make some sort of progress.

Perhaps my eyes have become a touch too jaundiced over the last decade, but I’m not sure I could disagree more with what Molly claims near the end of her post:

Jeffrey is wrong in his current assessment of the W3C.

If only that were so.

If the folks at the WaSP believe the Good Ship Consortium is beginning to change course, then I’m happy for them, really; I’ll be even more happy if they’re right.  But when the ship is moving so slowly and has drifted so far out to sea, how much relevance can a change of heading really have?

Browse the Archive

Earlier Entries

Later Entries