Category: web standards

SxSW Panel Online Finally!

You can go get the audio from our panel at SXSW (Convincing Your Company to Embrace Web Standards to get the slides) over on their podcasts page, or get the mp3 directly.\
I just listened to it (Steve listened to it to too, and we traded jokes) and here are my totally shallow observations after listening to myself:

  1. I did a really good job of not talking fast. I talk much faster than that normally.
  2. I sound a little bit like Kevin Smith and that kind of scares me.
  3. Note to self: don’t laugh into the mic
  4. Don’t encourage Marc Canter. No good can come of it
  5. My panelists kicked ass.
  6. Jeremy Keith loves Mr. Chipman\
    It makes me want to do a panel next year… even though it was really stressful getting this one together.\
    Update: Steve and got a transcript from Casting Words, you can go look at it if you want.

S5 and Presentation Remotes

I use s5 for all my presentations, and I’ve been giving a lot of them the past couple years. Although I’ve been tempted, I haven’t yet broken down and purchased a presentation remote, because I’m not sure any of them will work with:

  • A mac
  • arrow keys in a web browser\
    So, all you s5-presentation-givin’-standards-nerds out there, if you use a presentation remote, which one do you use, and do you like it?

Microformats for APIs

There was a fun discussion at Mashup Camp about Microformats for APIs. It started as a question about using microformats for documenting APIs, which I think was resolved fairly quickly by deciding to try it using XMDP. There’s a short example on the wiki now that I came up with. It’s not complete and doesn’t contain eveything I think should be in it (error codes, response format, etc), but its a start. (Christine Herron posted some notes as well)\
The discussion turned into a plea (from me) to start thinking about using microformats instead of coming up with new XML languages for APIs. There are already competing formats that replicate, in entirely new markup, structures available in HTML. Why not just use XHTML?\
For example, instead of the various formats returned by the different search engines (and I’ve used several by now), why not return this (inside an XHTML document)?

<code>
<ol start="1">
<li><a href="http://url">Document Title</a>
<p class="description">Description goes here</p>
<blockquote>Snippet goes here</blockquote>
</li>
</ol>
</code>

You could, of course, add more, but that’s basically what you get back in any search API. Why does it need to be any more complicated than that? For sites who want something simple, they wouldn’t even need to parse the result, just display it. They could even use javascript on the client side once it’s displayed to come up with the proper next/previous links.\
I think there’s a lot of room for discussion here, and I don’t think that we can reasonably replace all XML-based APIs with microformatted XHTML, but it’s a discussion worth having.

I Left My Bowels In San Francisco

I’ve been good, I swear. Maybe it was the carpaccio last night. Maybe it was the chocolate mousse. Maybe it was something else, like the amorphous blob we had for lunch yesterday. Anyway, I skipped the end of Supernova today to spent some quality time with the hotel bathroom.\
But, yesterday was good. Rohit Khare gave name to a game I’ve played before, and we had a great time playing at lunch: Acronomious. Given a word, you have to come up with the most implausible acronym for it, extra credit for recursion (using the acronym in the acronym, for exmaple: Bases Around Strategic Emplacements). I met the guys from Netvibes, and we had a lovely conversation about building modules, and we talked about how similar our approaches to development are. It was fun, and they’re the friendliest Frenchmen I’ve ever met. The day before, I met the guys from ATTAP and we had a lovely talk about their new open source javascript framework: Jitsu. It’s definitely something worth keeping up with.\
Last night, I went out to dinner with Kristin and Jessica and we had a lovely time at The Steps of Rome (where we had the carpaccio, the best bruschetta ever, and some lovely prosciutto and mozzarella). The food was amazing, and surprisingly cheap for the quality and quantity. After dinner, we walked around Little Italy for a little while, and got dessert at Stella’s Pastery. Yummy yummy chocolate mousse!\
This week has been pretty good. Mashpit was a great experience, and will help me in a couple weeks. We’re running an internal Mashpit at AOL to work on module, and it was nice to get a “real” Mashpit experience under my belt before I try to replicate it at work.\
The Supernova workshops on Wednesday were very interesting, and I think our Decentralized Data panel went really well, and so did my short talk on Modular Web Development that I hope to expand into a real proposal or set of best practices. I get to work on refining it a little bit more before Mashup Camp. The panels yesterday were a disappointment. It was mostly “my company believes in these buzzword and I’ll say them over and over again and ignore what anyone else is saying.” The best stuff was happening in IRC, where the snark overflowed.\
That’s what I’ve been up to this week. Tomorrow, it’s back home for a little while before Mashup Camp, and then I’m really taking the rest of the summer off from traveling.

Notes from Supernova: Personal Infosphere

This panel’s all about how we can keep up of all the information that comes in every day. We’re\
h4. Dalton from imeem

  • We’re reaching some limit as to the amount of information we can handle.
  • imeem creates both an IM client and web client
  • Instant messaging is useful as a communications tool, but about presence. Presence is actually the most important part of IM clients.
  • They’ve got real-time notification of new blog posts, profile updates, etc.
  • They have groups to “aggregate people around particular topics”
  • Trying to manage all forms of digital information, can pull in data from other services
  • They have a unified tag space across media types (eeenteresting). I wonder how that plays out with users. People tag different content differently, do users of imeem use consistent tags across media?\
    h4. Yael from eSnips
  • They have mainstream users, not teens.
  • Social, but focused on content, not people
  • It’s for sharing interest and passions but lets you go one step further\
    h4. Ben from Plaxo
  • 5 year-old company
  • Synchronized address book
  • People have on average:
    • 3-4 phone numbers
    • 2-3 e-mail addresses
    • 2-3 physical addresses
  • And this information is always changing
  • 33% of mobile phone numbers and 24% of e-mail addresses change annually\
    h4. Tariq Krim from Netvibes
  • Create a single place for your entire digital life. Another personal portal.
  • They have an open API for module developers.
  • They have a public wiki for users to request features and report bugs
  • They have a really cool live translating tool
  • So they want to use “open standards”, but didn’t really say which ones\
    h4. Hans from Plum
  • Connect with each others “heads”, not with dates.
  • Collect data of all types and drop it into buckets
  • “Communities of Knowledge”
  • Tiny little application that runs and allows you to add anything you read into a collection.
  • Wow… this is really cool. Collect anything from your desktop and throw it up into a collection. Neato.
  • Everything is indexed and searchable.
  • Works great on the Mac too. Yay!!
  • Also allows you to connect to people with similar collections to yours.
  • They dig microformats as well.
  • They use Amazon’s S3 for the data.\
    h4. Discussion
  • Collaborative Filtering
    • imeem uses collaborative filtering to decide how popular or “good” something is. Compared to PageRank
    • Plum called on “big” companies like Yahoo and AOL to come up with a good scheme for licensing documents or declaring document license. Time to go read up on rel license, isn’t it?
  • Lot of talk of ownership while avoiding completely the topic of lock-in and open API’s. Oh well, we’ll talk about it in the next panel.

My Favorite AIM Pages Feature

Since it launched yesterday, I can talk about it now. With the whole microformat thing, we’ve started thinking about the pages created in AIM Pages as mini web services, and the first step to doing really cool things with that is being able to pull out modules from the page so you can use them in other modules. You don’t want to have to grab the whole page just to get a piece, so today, you can request a particular module on the page and get back an XML document that contains just that piece. You could also request it with all the scripts it needs to run so you could embed your Buddy Gallery on your own web page if you wanted.\
How do you do it? If you wanted to get my buddy gallery, you’d grab:

<code>http://www.aimpages.com/kplawver/profile.html?moduleid=buddy-gallery-0</code>

If you wanted to get it with all its scripts and CSS, you’d grab:

<code>http://www.aimpages.com/kplawver/profile.html?moduleid=buddy-gallery-0&aspage</code>

Now, this opens up all kinds of possibilities for new modules that I can’t wait to start playing with. I hope you’ll beat me to it…\
update: There are a couple “quirks” with it at the moment. When you use aspage, the module’s onload isn’t being called, and there’s a lonely little double-quote in the body element. Not sure what’s up, but we’ll get it fixed. Getting just the module’s markup works fine (which is really the important bit, right?).

AOL Is Fun Again!

Things at AOL are changing, and it feels great to be in the middle of it. Every day, it becomes more and more clear that a small number of people are driving gigantic changes all throughout the company, and I’m both honored and a little nervous to be considered part of that group. It makes me a little self-conscious, to be honest.\
It just feels like everything is coming toether. Last week, I was asked to speak at a conference for the first time (thanks, Tantek), which is a huge honor for me, especially considering who asked and who is on the panel. This week, I did training on semantic markup and CSS to a handful of designers, with the goal being to get the rest of the designers through the course by the end of the summer. I also found out that I’ll be speaking at Mashup U in July. And just today, I was asked to join a small group doing something extremely cool that I don’t think I can talk about publicly yet (maybe never, I’m not sure yet). This is all on top of the privelage I have to work on AIM Pages.\
I’m extremely lucky to be in the position I’m in. I’m not quite sure how it happened, or really where it will lead, but I love it. I work with the best people, get to play with and develop the coolest stuff (cool to me, and that’s really all the matters), get to share what I’m passionate, and feel like what I do affects and influences other people.\
I’ve been at AOL for eleven years, and this is the most fun I’ve ever had. I can’t wait to see what happens next!

How I Write Presentations

I do a lot of presentations now, and because I’m the “web standards guy” I can’t go around doing them in Powerpoint or Keynote (I’ve tried using both and yuck, they’re not made for writing). Over the past year or so, I’ve tried a couple different things, but here’s the system I’ve got down, and the technology pieces that make it happen:

# Movable Type – I love MT’s template system. I don’t have to write code, and I can make them do pretty much whatever I want. And, if I run into something they can’t, there’s either a plugin to do it, or I can write a teeny bit of PHP glue to fill the gaps.

# Textile – I love it. It’s the easiest of the pseudo-markup languages out there (Markdown is the other well-known one).

# S5 – Eric Meyer is a genius. It’s got everything I need from Powerpoint or Keynote in an HTML page.

# MarsEdit – Best blog editor ever, does what I need without getting in the way with things that I don’t. The preview is nice too.\
I created a Movable Type archive template out of S5 (which you’re free to use if you want), a lot like I did for Instiki a while ago, and now all my presentations go up on my little presentations site. Now, I can get to them from anywhere, they’re publicly available and stored somewhere other than my laptop (the problem with doing them all in my locally hosted copy of Instiki).\
I start with all the slide titles as an outline, move them around, tweak, etc, and then go back and add the bullet points, most of which end up being removed. Then I publish and run through it quickly to make sure it all makes sense. Then I’m done! With Textile, there’s no real markup to write except to go back and wrap things up in the slide divs. If I know exactly what I want to say, I can go from idea to completed presentation in about 10 minutes.\
Here’s what a typical slide looks like:

<code><div class="slide">
h1. My Slide Title
* This point is spectacular
* Can I get an "Ooooh" from the audience?
* Give yourselves a round of applause!
</div></code>

And the best part is, they all come out as standards-compliant, semantic little presentations without me having to write all the markup (which as fun as it is, takes time to get right, time that I’d rather spend thinking about what I’m going to say).\
You’re free to use the archive template and make your own little presentations site. If you do, send me a link!

Presenting to The Webfather

I just did my first presentation at WWW on our microformat, and who was in the audience, but Tim Berners-Lee, the father of the web. There was a moment, sitting at the front of the room, waiting for my turn to present, that I got really nervous. I’m not normally nervous before I speak in front of a fairly small group (less than 100). This time, I was. I had a thirty minute presentation that I had to compress into 10, which didn’t help.\
I think Friday’s will be easier. I get to talk about CSS, on stage with two people I know fairly well, and I have my full time. If you’re at the conference, Friday’s Style and Layout panel should be a lot of fun. I get to talk about the guidelines we set up for CSS in modules and themes in AIM Pages, and how that process has worked out for us so far.