Posts in the Web Category

Structural Naming

Published 20 years, 9 months past

After I threw out my two cents on ID naming conventions, Andy Clarke revisited the subject and made some more detailed proposals.  As I said before, I think this is a good conversation to be having.  However, the reactions of some people make me think that I wasn’t entirely clear about why.

A standard nomenclature offers the ability to restyle sites, sure.  That’s kind of cool in an übergeek kind of way, like making jokes involving TCP/IP terminology or wearing a T-shirt that says SELECT * FROM users WHERE clue > 0.  That isn’t really the primary reason why I support the exploration of ID naming conventions.  I’d like to see those conventions emerge because they will serve as a useful starting point for beginners in the standards-oriented design field.  It would help reinforce the idea of structural naming, as opposed to presentational naming.

We’re all familiar with presentational naming.  It’s things like id="leftbar" and id="pagetop".  In terms of layout, it’s the equivalent of <b> and <font>.  Structural naming, on the other hand, encourages the author to ask “what role does this piece of the document play?”  Rather than obsess over the visual placement of the navigation links, structural naming gets authors to consider the document structure.  This can’t be anything but good, at least for those of us who want to promote improved structures.  To pick one set of examples from Andy’s recent post:

#branding
Used for a header or banner to brand the site.
#branding-logo
Used for a site logo
#branding-tagline
Used for a strapline or tagline to define the site’s purpose

While #branding is described as “Used for a header or banner…” you may note that the actual ID name has nothing to do with visual placement.  It’s all about identifying the (dare we say it?) semantic role of that bit of the document.  By encouraging that thinking, a structural-naming convention keeps the author in that frame of mind when he has to go outside the common set of names.

I see this as being much like the often-promoted ‘rule’ that link-state styles should go in the order link-visited-hover-active.  I even wrote an article explaining why that order is important.  Here’s the thing: once you understand why the order is important, you can break the ‘rule’ in creative ways.  For example, suppose you want your hover effect to apply only to unvisited links, whereas visited links should get no hover.  No problem!  Just put them in the order link-hover-visited-active, or even link-hover-active-visited if you want visited links to get no active styles, either.

(Side note: if you chain pseudo-classes, such as with a:visited:hover, then the ordering problem goes away.  If Explorer supported that syntax, we could all move on from the LVHA rule.  Too bad it doesn’t.)

Conventions and ground rules exist for a reason: to provide a lower barrier to entry, and to help guide those new to the field.  Once you become experienced, you can break the rules in creative ways.  It’s been said that the key to good jazz improvisation is a thorough understanding of the rules of music.  In other words, once you really know those rules, then you know how to break them.  In order to know the rules, though, there have to be rules.

That’s why I’m glad to see them starting to emerge in blog postings and the public thinking of people in the field.  The development of these rules is not a barrier to creativity, but an enabler of it.


Edged Out Of Contention

Published 20 years, 10 months past

Andrei fired off round two of “Gurus vs. Bloggers”, and good news!  I played on the guru team by proxy, and was defeated by Dave Shea‘s proxy, more or less as I’d hoped I’d have the chance to do after round one was played.  Andrei was nice enough to hem and haw about which one ought to win, but honestly, there wasn’t much contest.  The Zen Garden won two SXSW Web awards including Best In Show, after all, not to mention the awe and respect of Web design folks the world over.  css/edge, at best, earned awe and respect.  In any case, I am honored to have been so thoroughly owned by the man Andrei calls “one of [my] best students.”  Mr. Shea, I bow to you.

In his tongue-in-cheek commentary, Andrei said:

Maybe if Meyer had used orange for CSS Edge, because orange is after all the new black, I would be able to swing the vote the other way.

I don’t know—low-contrast orange doesn’t really seem much better than low-contrast blue, does it?


Self-Referential

Published 20 years, 10 months past

A week ago, I published an entry that was two parts exploration and one part experimentation.  The experiment was to see how readers commented on a post of that nature, one that was potentially very inflammatory even though was not at all its intent.  The commenting ability is still new for me, and I’m working out how open I want to be about comments.  When I was writing the entry, I had in mind to not permit comments, realizing that it could easily draw a metric ton of flames, accusations, and other sundry ickiness.  At the last minute, I decided that it would be better to open comments and see what happened.  I’m well satisfied with the results, but have now closed comments on the entry (you can still ping it if you want).

I do want to follow up just a bit on some of the comments that were posted.  A few people said or implied that I should have picked a less volatile subject than intimate partner violence (IPV).  That’s just it, though: I didn’t pick the subject with an intent to post.  I was doing my own research, for my own information, and at the end of the process decided I’d share the results rather than just sit on what I’d learned.  Why?  I’ll quote myself:

…I was able to do some in-depth fact checking of my own in less than an hour, using nothing but Google and some well-chosen search terms, and obtain a more accurate picture of the world than I’d had before. I believe that this ability to self-inform is one of the most important and often underappreciated benefits of the Web. If nothing else, I’m glad I went on this particular search because it reminded me that the Web really is something worth fighting for, and that improving the Web is always an effort worth undertaking.

It was an aspect of the Web I’d rediscovered, and thought it was also important to share.  I’ve been doing this stuff for more than a decade now, and when I started my whole goal was to help put information online.  That’s why I wrote the HTML tutorials at CWRU—to make it easier for people to share information about whatever they knew best.  I’ve seen a resurgence of that impulse recently, with people blogging obscure fixes or problems they’ve encountered so Google will pick it up, and it will be there for the next person who needs it.  (See, for example,”Writing For Google” over at Daring Fireball.)  So if I can forget that the Web is an astonishing source of information, and need a reminder, maybe others could use the same reminder.

And why did I share so much detailed information on such a potentially sensitive subject?  I don’t think my points would have had the impact without the details.  That probably sounds like I was trying to use a touchy subject to raise my exposure, but that’s not it at all.  If I’d just posted to say, “I was curious about something and dug up a lot of information about it, and that’s what’s cool about the Web” it wouldn’t have had the same resonance.  Walking through the process and pointing to the sources I quoted established a context for my final points.  It was also the case that I believe I found some useful information about a very important subject, and was able to disseminate it further.

My thanks to everyone who contributed comments, especially those of you who pushed back a bit.  I’ll close with a favorite David Byrne lyric; make of it what you will.

Facts are simple and facts are straight
Facts are lazy and facts are late
Facts all come with points of view
Facts don’t do what I want them to
—”Crosseyed and Painless”

My Dinner With Brian

Published 20 years, 10 months past

I was back in the training groove this week, and on Monday morning one of the attendees had to duck out at one of the breaks.  “I have to talk with Brian, who’s consulting for us.”  I must’ve looked blank, because he said, “Brian Foy.  Do you know him?  Works with Randall Schwartz.”

I’ve been reading Brian‘s missives from Iraq on the O’Reilly Network for a year now, and was really psyched to meet him.  As it turned out, we both were planless on Monday night, so I picked him up at his hotel and blundered around the neighborhood until we found a Thai restuarant.  Over appetizers, Brian told me his wife (an opera singer) has been doing her own Web design for a while now, and was getting into CSS.  Then he mentioned buying the O’Reilly CSS book for her, and as he talked about why he’d bought it, I quickly realized that he’d picked it up because it was an O’Reilly book, and recommended.  He literally didn’t know he was having dinner with its author.

After a couple of minutes, I finally told him who’d written the book.  I should probably feel bad about not admitting it right away.  I wasn’t going to say anything here either, but he already blogged it, so… what the heck.

It was very interesting to talk about Iraq with someone who’d been there.  I was able to ask him the question I’ve wanted to have answered for a while: “How does the news coverage compare to what’s really going on over there?”

“It’s horrible,” he said.  “We got CNN and Fox on the Armed Forces Network and they were both just terrible.”  He said that he’d literally been present for things that were being covered on TV by the time he got back to the barracks, and nobody ever accurately represented what had happened.  Not even close, apparently.  Brian made the observation that images are so overwhelming, so powerful, that the story was always driven by whatever footage had been shot.  Not by the actual event in its totality, nor the context.  Just the visual.

It wasn’t surprising to hear that, but it left me saddened and frustrated.


Earning A Spot

Published 20 years, 10 months past

Through a winding chain of links—it was, of all things, the result of an extended surf on the Web, and who does that any more?—I came across Cameron Moll‘s “80/20 and the design blogosphere“, where he listed the 20 people from whom he feels 80% of vital new media design information flows.  I was deeply flattered to be on the list, although I again feel weird about it.  I don’t give out design information, and meyerweb is certainly nowhere near as well-designed as many sites (including Cameron’s).  Heck, I don’t even talk about CSS all that much any more, despite numerous vows (public and personal) to do otherwise.  I suppose all the books and other writings allow me to coast into these lists, and that’s a nice feeling, but I’m starting to seriously ask myself what I’ve done for everyone else lately.

So I’ll throw it open to the crowd: what kind of information, new media design or otherwise, would you like to see from me?  What do you feel would earn me the right to stay in Cameron’s 80/20 list?  Post and ping, or contribute a comment.  Your choice!

(I have to shoot down one potential request now: I’m not going back to browser support charting.  Westciv does a decent job already, and as I wrote a while back on www-style, going any further is a massive undertaking.  And, to be honest, it’s mind-shatteringly dull and incredibly time-consuming.)


We Need Some References, STATS!

Published 20 years, 11 months past

During a recent (somewhat contentious) debate, a friend tossed out the statistic that every nine seconds, a woman is beaten in the United States.  Later on, I did some math, and determined even if we assume that every one of those beatings is suffered by a different woman—that is, no woman is beaten more than once in a given year, which is most certainly not the case, but we’ll take it as a premise anyway—that means just over 3.5 million women are beaten every year.  That’s fairly shocking, if it’s true, since that’s about 2.5% of all females in the country (of all ages; there were approximately 144 million females in the U.S. as of March 2002, according to the Census Bureau document Women and Men in the United States: March 2002).

But is it true; or more appropriately, is it an accurate reflection of what’s really happening?  I started to wonder about this, because I have a tendency to question premises pretty closely.  What’s meant by “beaten”—does it include incidents where a single punch is thrown in anger, and instantly regretted?  Does it refer only to reported incidents, or is it based on both reported and estimates of unreported incidents?  Does medical attention have to be sought?  Does it include beatings of women by women, or is it only concerned with times when a man beats a woman?

So I turned to Google to do a little basic research.  The search “woman beaten every seconds” immediately turned up claims that varied from every nine seconds to every fifteen seconds.  That latter interval would mean that about 2.1 million women are beaten every year, again assuming every incident involves a newly beaten woman, which is quite a drop from 3.5 million.  I also found STATS.org, a site that claims to “check out the facts and figures behind the news.”  They claim, in a list of what they term “commonly accepted fallacious statistics,” that the actual interval is every two minutes twenty seconds, based on a figure of “220,000 serious violent incidents” for calendar year 1999.  Which works out to every two minutes 23.34 seconds—if it’s true.

But is it?  Our friends at STATS aren’t much help, because they provide no direct reference for the figure, so there’s no easy way to check up on their methodology either.  Further obscuring the picture is that they don’t define a “serious violent incident.”  To reiterate some earlier questions, does it refer only to reported incidents, or is it based on both reported and estimates of unreported incidents?  Does medical attention have to be sought in order to count as a “serious” incident?  They aren’t saying, nor do they provide any links to more detailed information.

So I started digging a little more deeply, again through Google.  Eventually I found a document on “Intimate Partner Violence” (and more on that in a moment) at the Department of Justice that reports:

  • The number of female victims of intimate violence declined from 1993 to 1998.  In 1998 women experienced about 900,000 violent offenses at the hands of an intimate, down from 1.1 million in 1993.
  • In both 1993 and 1998, men were victims of about 160,000 violent crimes by an intimate partner.
  • Considered by age category, 1993-98, women ages 16 to 24 experienced the highest per capita rates of intimate violence (19.6 per 1,000 women).
  • About half the intimate partner violence against women, 1993-98, was reported to the police; black women were more likely than other women to report such violence.
  • About 4 of 10 female victims of intimate partner violence lived in households with children under age 12.  Population estimates suggest that 27% of U.S. households were home to children under 12.
  • Half of female victims of intimate partner violence reported a physical injury.  About 4 in 10 of these victims sought professional medical treatment.

So that gives us some actual numbers into which we can sink our calculators.  I’ll take one million as an average for the period 1993-1998, which is a crude but convenient measure.  That works out to a beating every 31.536 seconds; we’ll round down to every 31 seconds.

There are three things to note here.  One, this is “intimate partner violence,” which includes spouses, ex-spouses, boy/girlfriends, and ex-boy/-girlfriends.  It therefore doesn’t count random attacks like violent muggings, rapes by strangers, and so on.  Two, there were a million violent offenses, which does not necessarily mean a million different women, but there’s no way to measure that so we’ll continue to assume that every incident involves a different woman.  Three, it’s stated that about half of such violent incidents are actually reported to the police, which means there’s potential uncertainty in the data set.  The description of methodology restores some confidence; in the period 1993-1998, they interviewed “approximately 293,400 households.”  That’s a pretty good data set.

The report also states:

Women were more likely to be victimized by a nonstranger, which includes a friend, family member, or intimate partner, while men were more likely to be victimized by a stranger.

“More likely” doesn’t give us much of a handle on the proportion of intimate-to-stranger violence, unfortunately.  If intimate partner violence constitutes 55% of all violent crimes against women, that’s a much different story than if it’s 90%.  Furthermore:

Sixty-five percent of all intimate partner violence against women and 68% of intimate partner violence against men involved a simple assault, the least serious form of violence studied.

“Least serious” is a bit of a misnomer, in my opinion, since “simple assault” is later defined as:

Simple assault is an attack without a weapon resulting either in no injury, minor injury (such as bruises, black eyes, cuts, scratches, or swelling) or an undetermined injury requiring less than 2 days of hospitalization.  Simple assaults also include attempted assaults without a weapon. 

So a slap in the face is lumped in with a beating that leaves marks or requires up to two days in the hospital.  We’re also including incidents where a person (male or female) tried to attack a woman without making use of a weapon, but failed.  Or succeeded.  That’s a very, very wide range of incidents and types of violence.

Since the next step up in assault severity is aggravated assault, which includes incidents in which “the victim is seriously injured,” we could decide to count all non-simple assaults as serious violent incidents.  That would mean around 350,000 such incidents in a year, which is obviously higher than STATS’ figure of 220,000 for 1999.  Now, I suppose it’s possible that the figure dropped that much between 1998 and 1999, but I give such an occurence a probability somewhere around that of my being made the first astronaut to Mars.  So we’re still left wondering what “actual figure as estimated by the Justice Department” they’re using, since the actual figures I got from the Justice Department seem to have nothing to do with their figures.  (But at least I pointed you to my source, so you can check up on my assertions; see the Bureau of Justice Statistics’ main page on Intimate Partner Violence to get links to PDFs, Excel spreadsheets, the document I’ve been referencing, and more.)

At the end of all this, we seem to have arrived at an answer between the commonly-repeated figure of “every nine seconds” and STATS’ claim of every two-and-a-third minutes (which in turn leads me to harbor deep skepticism about their other claims, since their domestic violence number seems to be, well, fallacious).  As noted, the numbers I’ve been using all cover intimate partner violence.  I didn’t find similar information on other kinds of violence, although I’m sure it exists somewhere.  Once those incidents were added in, they would lower the average interval between beatings, although they couldn’t lower the interval all the way to nine seconds, or even fifteen.  To do that, there would have to be more stranger-perpetrated violence than intimate partner violence, which the report says isn’t the case.

So what’s my point?  I have three, as it happens.

My first point is that obtaining an accurate picture of the world is a messy, complicated business, and simple unattributed figures don’t help at all.  I’m not trying to say that violence against women isn’t a big deal: it is.  I personally think violence of any kind, no matter who is the victim and whom the attacker, is a big deal, and we should work to lessen such incidents.  I am saying that it may or may not be as bad as we think—and, in fact, the document I used states that intimate partner violence and homicides dropped over the covered period, despite the fact the national population was rising.  That says to me that we should work harder to figure out the causes driving that decrease, and exert more efforts along the same lines.  I’m not so naïve as to think we can ever totally eliminate violence, but we can and should do our best to get as close to that goal as we can.

My second point is that the news media don’t help at all in clarifying this stuff—no great shock there, I suppose, but it’s something that been bothering me more and more of late (as I wrote yesterday).  I previously linked to an article about the gross inaccuracies in reporting about the cost of the proposed missions to the Moon and Mars, and this is another example of how convenient, unexamined “facts” become common conversational currency.  I know I’ve heard the “every nine seconds” figure on the news, or at least a figure very much like it.

The third and perhaps most important point, and the one I found most personally fascinating, is that I was able to do some in-depth fact checking of my own in less than an hour, using nothing but Google and some well-chosen search terms, and obtain a more accurate picture of the world than I’d had before.  I believe that this ability to self-inform is one of the most important and often underappreciated benefits of the Web.  If nothing else, I’m glad I went on this particular search because it reminded me that the Web really is something worth fighting for, and that improving the Web is always an effort worth undertaking.


Under The Influences

Published 20 years, 11 months past

When I pointed to Nick Finck‘s mention of me as an influence, I somehow missed the fact that he was doing it in response to a post by D. Keith Robinson about his Web design influences.  Keith listed me as well.  And before I move on, I’ll join everyone else in congratulating Nick on the Digital Web redesign.

So—I’m still grappling somewhat with the idea that I’ve been a Web design influence to anyone, let alone for people like Nick and Keith.  A quick glance around will tell you I’m no designer.  If I wanted to pretend that I had an aesthetic, I could claim to be a Minimalist, but let’s be frank: my design skills are just not very sharp.  But that’s okay.  I’m content to help spread information about CSS and how to use it, thus allowing designers to get into using it more effectively and intelligently.

It’s an odd feeling to think of myself as An Influence (and that’s how the words sound in my head, at least in this context).  It’s much easier to think about the people who have influenced me.  So here’s my list of the people who have most influenced my activities, outlook, and career path over the past decade.  I expect this will read a bit like Message To The Messengers, but hey, I’ve been around for a while.  There are two things I’d like to make clear up front.  First, these are professional influences, not personal ones (although there is some overlap, of course).  So there are folks out there who have meant a great deal to me, just in other ways.  Second, these are more or less in the order they occurred to me.  No overt attempt at ranking should be inferred.

Jim Nauer

We were college roommates for a year, and not too much later on I worked for him at the University Microcomputer Labs (wall to wall Macintosh SE’s, baby!).  Shortly after that, I graduated from college and was hired by Library Information Technologies, so that made us co-workers.  All along, he’s been a friend.  In fact, he was over at our house yesterday afternoon to spend some time playing with Carolyn.  The Web-centric point of all this is that it was Jim who first dragged me in front of a Mosaic beta, getting me instantly hooked.  He pointed me to the HTML specification, and it was he who convinced me that well-formed markup was important when I tackled my first Web pages in late 1993.  Without that critical early guidance, I might easily have become a table-and-spacer hack, and never seen CSS for what it was.

Tantek Çelik

I’ve said before that Tantek is one of the sharpest thinkers I know, and that’s no less true today.  Furthermore, he’s someone who genuinely cares about doing the right thing and supporting the common good.  I always take his opinions and thoughts on the Web and its technologies seriously.  I may not always agree with him, but even in disagreement I find his insights to be invaluable.  In a way, it’s a pity that his name has come to be associated with the CSS hack he published, because that’s a tiny dot compared to the totality of his efforts on behalf of Web standards and Web design.  I wrote about some of that back when IE/Mac was discontinued.  If you’re a Web designer today, you owe Tantek more than you realize.

Todd Fahrner

Remember Agitprop?  If not, go read it; Todd’s observations on font sizing and styling are still relevant, and help explain a lot about how we got to where we are with font styling on the Web.  Remember the Box Acid Test, which eventually found its way into the CSS1 Test Suite?  That was him too.  You know DOCTYPE switching?  Todd’s idea.  When Todd retired from the Web, it was a sad day for us all, although I’m happy that he’s found activities that are more enjoyable for him.  If you’re a Web designer today, odds are you owe Todd far more than you realize.

David Baron and Ian Hickson

Or, as I sometimes think of them, The Wonder Twins of Mozilla.  Not that they look or act anything alike, and of course Ian works for Opera now, but anyway.  They pounded on me (via e-mail) until I finally understood the inline layout model, and were immensely helpful in making the first edition of CSS:TDG as good as it was.  They’ve both taught me a lot over the years.  They both put a lot of work into making Mozilla a great CSS rendering engine and making CSS itself a better specification.  They both care about standards.  It probably isn’t fair to lump them together, but that’s how I think of them.  (Probably because of their joint work on CSS:TDG.)

Jeffrey Zeldman

Jefferey’s a mensch.  I’m tempted to leave it at that, because what else matters?  And yet he’s also been an enormous force for good, helping found the Web Standards Project.  His writing is easy on the eye and ear, and it goes down smoother than silk.  He’s always trying to better himself and his understanding of how to do the right Web thing, sharing both what he knows and what he doesn’t know, and letting the rest of us learn along with him.

Steve Champeon

Anyone who’s subscribed to Webdesign-L for a while knows The Joy Of Steve.  Unless of course you annoy him, in which case he’ll tell you in detail.  That characterizes Steve himself, actually: he’s a man who cares a great deal about the details, and about getting them right.  If you’ve ever enjoyed the Color Blender, you can thank Steve for its existence, as it was his detailed explanation of how to calculate color midpoints that made me realize that, hey, it would be pretty easy create a tool to do that.  Furthermore, css-discuss is modeled in a great many ways on Webdesign-L, so his influence is felt there too.

Håkon Lie and Bert Bos

They were the lead authors of the CSS1 specification.  In the words of Stan Lee, ’nuff sed!

Chris Lilley

Chris passed on my early test suite work to folks at both Microsoft and Netscape, and was the person who extended the Working Group’s invitation to join as an invited expert.  His dry wit and genial outlook in WG meetings served as an example to me, and helped me mesh with the group much more smoothly than I might otherwise have done.  Fun trivia fact: Chris was moderator the session at WWW5 in which Peter Murray and I presented our paper on the Borealis Image Server.  Followup fun fact: Robert Thau, who presented before us about Apache, sat next to a guy in the audience and talked loudly with him throughout our entire presentation.

Doug Bowman

Doug took Wired News in the direction we’d all wanted to see a major site go, converting to standards-oriented design and making it look good.  Then he shared his experiences with the world, and showed us all how easy it could be.  Even I was surprised at how much was possible, and how much benefit it conferred.  It’s a big part of what got the “business case for standards” discussion going, because it served as a concrete example of the benefits.  I sometimes wonder if I’d have had the nerve to launch Complex Spiral Consulting if that hadn’t happened.  Probably not.

Dave Shea

The CSS Zen Garden—you knew that was coming, right?—opened the floodgates and buried, pretty much forever, the myth that CSS design was all the same, too boring, and too limited for anyone to take it seriously.  It’s hard to imagine now, but there was a time that we had to waste energy refuting those claims.  I’ll always be grateful to Dave for ending that debate, and his excellent work on sites like Mozilla.org has been a recent inspiration.

My final, but in no way smallest, person of influence must receive the honor posthumously: my mother.  For a listing of most of the reasons why, I refer you to the eulogy I delivered, but there’s at least one more reason that’s relevant here.

She taught me to believe in myself.


Look Back In Awe

Published 20 years, 11 months past

Just in case you haven’t seen it yet, John Allsopp posted a nostalgic note about the early days of CSS.  If you want to know who I hung out with back in the day, John’s got most of the names right there for you, and links to many of them.  There’s even a link to the CSS Samurai page, which I thought was long dead, and was greatly amused to read.

To John’s recollections, I would add Chris Lilley, who’s since been much more involved in SVG and other things; and Susan Lesch, who’s now at the W3C but back then was at macvirus.com.  (There’s a reason I didn’t link to that address, by the way.  If you go, make sure you can block popups.)

A more recent event of note is that it was a year ago today that the CSS Zen Garden opened its gates to the world.  Congratulations on an incredible first year, Dave.  I’m honored to have been able to contribute to the Garden in that time, and eternally grateful (and a little jealous) that you created such an awesome resource.  It opened a lot of doors, and a lot more eyes and minds.


Browse the Archive

Earlier Entries

Later Entries