Categories
Social Media Specs W3C

HTML5 status and when not to tweet

I’m in the process of rolling out some change proposals and bug reports for HTML5. I had volunteered to help with reviewing MathML during Last Call, and submitting comments for the HTML WG. Unfortunately, the process did not go smoothly.

In the meantime, this week was the W3C’s TPAC meeting, where all the boys and girls from all the W3C working groups get together for a face to face. Interesting stuff happened, including the TAG (TAG is the overall W3C architecture group) recommendation that HTML WG split Microdata from HTML5. We’ll see where that goes.

Twitter was very useful for those of us who were not at TAG. Those at TAG pointed out the IRC channels associated with each meeting, and where links to reports and presentations could be found. It was an example of good Twitter use.

What was not an example of good Twitter use last week were the “live” Twitter messages that came from a soldier in a hospital within Fort Hood during the recent tragic events. The inappropriate and less than helpful use of Twitter was detailed in an exceptionally good post at Techcrunch, written by Paul Carr.

In the writing, Paul makes the point that rather than help, or at least get out of the way, during a crises, we grab our cellphones and become mini-journalists—macabrely excited about being “live” at the event. We post photos of people hurt in accidents, or shot by a crazy man, regardless of who we might harm, including family members or the victims themselves. We exaggerate the event until one gunman becomes three, and an act of insanity becomes one of terrorism.

More importantly, we jam necessary cellphone lines in order to get that last tweet out, cause confusion, and aid and abet chaos.

Even outside a crises, we don’t seem to know when to turn off the spigot. How many of us woke up this morning to be met with the ultimate of absurdities: hundreds of messages from folks “live tweeting” a Congressional vote. My god, it’s just a bloody vote. There is nothing exciting about a vote until the vote is finished and the tabulation made.

Frankly, I would rather hear what people had for breakfast.

Anyway, more on HTML5 later, and do read Paul Carr’s writing.

update Suw Charman-Anderson has a detailed rebuttal. She has some good points, especially about the Iranians feeling reassured that people were listening.

What she misses, though, is the past tense: people were listening. People listened during the Iranian election, dyed their avatars green, and filled Twitter trends with the topic. And then…it all just went away. And that’s the point I think that Paul was making: social media’s ability to influence events is directly proportional to the attention of the participants, and the participants are being subjected to a continuous barrage of new events, and new outrages.

The green avatars are gone. Do the Iranian people still feel assured that people are listening?

Categories
Standards

November is HTML5 Month

I’m not particularly good about compartmentalizing my interests. They say we women are good at multi-tasking, but I must be an exception to the rule.

I have sent off my first half of JavaScript Cookbook to my editor, and I hope to try to salvage an article I was doing for A List Apart, though I’ve run into some bandwidth issues that may be related to the technology covered. But my hope is to spend all of November working on HTML5: writing bugs, escalating bugs to issues, writing comments or change proposals, and, ultimately, going over every last bit of the HTML5 specification.

I can always sell my car to pay my bills.

Categories
W3C

No, HTML5 is NOT at Last Call

It’s unfortunate that the WhatWG made a unilateral decision to go Last Call with HTML5 at WhatWG, as HTML5 is far from ready for Last Call at the W3C.

Supposedly the reason it went to Last Call at the WhatWG is no bugs in the WhatWG database. Considering that there are significant bugs and issues at the W3C, one can only assume that concern about quality is not as strong at the WhatWG as it is at the W3C.

There are also more people questioning decisions, issuing proposals for change, and submitting bugs at the W3C. If one were suspicious, one could imagine the HTML5 editor made this move to assert some form of control.

Categories
HTML5 Social Media

Google Wave, Twitter, and HTML WG

I rejoined the HTML WG. Again. The group has come up with a change procedure/process that I can support. There was confusion before about whether HTML WG members could issue formal objections, since supposedly we’re part of the group making the original decisions. The new procedure, though, reserves us the right to submit a Formal Objection if all other avenues are blocked. I’m more comfortable being part of the group, now. I even have a first change proposal assignment, due after the book deadline.

Good news from the group: the HTML+RDFa document is now a published draft. However, the work on distributed extensibility is slow going. It’s difficult to split off the technical concerns from the knee jerk reactions.

You may, or may not, have noticed that I don’t post links to my main feed, or this site, for my Just Shelley site. That site is very personal, and a lot of people who read my stuff are more interested in my more impersonal writings, such as tech. Of course, I haven’t been writing at any of my sites lately. Too busy with the book.

I did get a Wave invite–thanks to whoever sent me it. And yes, I’ve given out all of the Wave invitations I have.

What do I think of Google Wave? I think it’s too much for me, though I did have a fun exchange with Marius Coomans, as he was sailing the ideal waters around Australia. We exchange emails and twitter messages, but there’s something different about seeing a message being typed out by someone who is on a boat, and watching them make corrections, as they’re watching you correct your own mistakes. And you’re on opposite sides of the planet, and different hemispheres. It’s not earth shattering, but it is a bit uncanny.

So what else is there to say about Wave. The user interface sucks, but that’s not unusual for a Google application. The performance is sluggish, but it’s alpha. And it performs better than Twitter. Other than that, though, I’m just not sure about the usability of the service. I know that others like the tool, such as Laura Scott who had a nice write-up.

Frankly, though, I’m really getting burned out on the whole social media thing so I may not be a good judge.

There was another instance where I wrote one thing, and it was interpreted as the opposite. I supported what Kurt Cagle wrote on HTML5, but based on a intense Twitter exchange I had with another person, Kurt interpreted my reaction to be opposite of what it is.

Twitter is useless as a tool for doing more than pointing out a link or talking about what you had for breakfast.

Categories
HTML5 Social Media

Google Wave, Twitter, and HTML WG

I rejoined the HTML WG. Again. The group has come up with a change procedure/process that I can support. There was confusion before about whether HTML WG members could issue formal objections, since supposedly we’re part of the group making the original decisions. The new procedure, though, reserves us the right to submit a Formal Objection if all other avenues are blocked. I’m more comfortable being part of the group, now. I even have a first change proposal assignment, due after the book deadline.

Good news from the group: the HTML+RDFa document is now a published draft. However, the work on distributed extensibility is slow going. It’s difficult to split off the technical concerns from the knee jerk reactions.

You may, or may not, have noticed that I don’t post links to my main feed, or this site, for my Just Shelley site. That site is very personal, and a lot of people who read my stuff are more interested in my more impersonal writings, such as tech. Of course, I haven’t been writing at any of my sites lately. Too busy with the book.

I did get a Wave invite–thanks to whoever sent me it. And yes, I’ve given out all of the Wave invitations I have.

What do I think of Google Wave? I think it’s too much for me, though I did have a fun exchange with Marius Coomans, as he was sailing the ideal waters around Australia. We exchange emails and twitter messages, but there’s something different about seeing a message being typed out by someone who is on a boat, and watching them make corrections, as they’re watching you correct your own mistakes. And you’re on opposite sides of the planet, and different hemispheres. It’s not earth shattering, but it is a bit uncanny.

So what else is there to say about Wave. The user interface sucks, but that’s not unusual for a Google application. The performance is sluggish, but it’s alpha. And it performs better than Twitter. Other than that, though, I’m just not sure about the usability of the service. I know that others like the tool, such as Laura Scott who had a nice write-up.

Frankly, though, I’m really getting burned out on the whole social media thing so I may not be a good judge.

There was another instance where I wrote one thing, and it was interpreted as the opposite. I supported what Kurt Cagle wrote on HTML5, but based on a intense Twitter exchange I had with another person, Kurt interpreted my reaction to be opposite of what it is.

Twitter is useless as a tool for doing more than pointing out a link or talking about what you had for breakfast.