It's not every day that construction equipment literally crosses your path. This particular bulldozer was clearly just entering the job site to get some work done.
I have no idea where we were or what we were doing, but my friend April who I had just met at SXSW, was wearing a t-shirt that said big O little o and while I first thought of the computer science notion of big O vs. little o, I had a feeling that's not what the shirt was about. So I asked her to explain it.
This past April I had the fun experience of getting in touch with a college pal who I had not seen or heard from since then. In short: we lived in the same dorm at Stanford one year during which time we did a bunch of things like go for motorcycle rides etc. but the most memorable was attending a Apple Holiday Party together (I was an intern at Apple at the time) and being surprised with a private performance by Ella Fitzgerald (yes the) - one of her last performances. Yes that's the kind of party Apple used to throw, even a private one just for employees.
Being Stanford types we both just got super busy and lost touch after that year. Fast forward to this year. Robin found me on the interwebs, and we ended up grabbing a bite together in LA and catching up on many years since we last saw each other. Our lives had taken very different paths, and over the course of the evening she made me explain how the internet came about. To see if I had made any sense, and see how well she retained it, I made her summarize the history of the internet for me in 30 seconds (actually 40, but what's 10 seconds among friends?). Judge for yourself, I think Robin did quite well.
Getting up at 5am for a marathon W3C Technical Plenary Day was quite a bit of work, and certainly had all the timezone shifting effects of jet lag even though my clocks didn't change.
More on the events of the day later, but for now, suffice it to say that the W3C Technical Plenary Day went very well, and had me once again regretting that I couldn't be there in person. Thanks once again to Citizen Agency for donating the use of Citizen Space to remotely participate. Their bandwidth was sufficient to both receive a live audio stream of the meeting, and answer a Skype call from Tim Berners-Lee himself in order to participate on a panel (I think I was a floating head on his computer next to him, those actually at the meeting will have to confirm what it was like).
Long day over, here is a bit of an audiovisual break. Pretend that you are at the beach, taking a walk in the Southern California surf.
Despite the fact that I was unable to make it to the W3C meetings this week in person, I wanted to very much participate remotely however I could, and if possible even do so by remote audio/video link for the panel I was invited to speak on.
Rather than remotely participate by myself, I figured that if I could find a suitable location, I might be able to organize remote participation for at least a few more interested folks who were also unable to make the trip to Cambridge in person.
Thanks to Citizen Agency's generous donation of space for a whole day, I've organized a last minute group W3C Tech Plenary day remote participation session for tomorrow (er, later today).
We'll have wifi, power, whiteboards, a projector, tables, chairs and will be able to interact with those onsite via IRC at a minimum, and possible by video feed.
Bring your laptop(s), your power supplies, and your thoughts on the below agenda.
|When:||5:45am - 3:45pm (East Coast schedules are quite painful for those of us on the West Coast. Yes I know that's less than four hours from now.)|
|Where:||Citizen Space, 425 Second St., #300, San Francisco, California 94107|
|What:||W3C Tech Plenary Remote Participation|
|Why:||For the good of open standards and the Web.|
|Who:||myself and anyone else who wants to help collaborate with W3C efforts to "lead the Web to its full potential".|
Check the official W3C Technical Plenary Day schedule for a listing of sessions and speakers. Remember to subtract 3 hours from the time slots to convert to Pacific time. Here is a brief summary in PST:
|5:45am-6am||Session 1: Welcome by Steve Bratt|
|6am-7am||Session 2: View from the Outside: Real World Perspectives on the W3C panel moderated by Molly E. Holzschlag|
|7:30am-8:30am||Session 3: Future Formats: HTML5 and XHTML2 moderated by Al Gilman|
|8:30am-9am||Session 4: Lightning Talks moderated by Rotan Hanrahan|
|9am-10:30am||Lunch (AKA second breakfast for us)|
|10:30am-11:30am||Session 5: Openness of W3C Working Groups moderated by Daniel Glazman|
|11:30am-12:15pm||Session 6: URI-Based Extensibility: Benefits, Deviations, Lessons-Learned moderated by David Orchard (this is the panel that I was invited to speak to represent microformats and will be attempting to participate via audio/video link)|
|12:15pm-12:45pm||break (perhaps get food to go from South Park)|
|12:45pm-1:15pm||Session 7: Lightning Talks moderated by Rotan Hanrahan|
|1:15pm-2:15pm||Session 8: Making Video a First-Class Citizen of the Web moderated by Philippe Le Hegaret|
|2:15pm-3pm||Session 9: Discussion with the Director, Tim Berners-Lee moderated by T.V. Raman|
|3pm-3:15pm||Wrap-Up and Adjourn|
|3:15pm-3:45pm||buffer (inserted because from experience these things run late)|
Please RSVP on the Upcoming page.
Add yourself, your notes, links to your related blog posts to the W3C Technical Plenary Day wiki page on the microformats wiki.
I'll be bringing chocolate covered espresso beans to help anyone stay awake who dares to get up that early. See you in a few hours.
I had planned originally to attend the W3C Technical Plenary / Advisory Committee Meetings Week this week, including meeting with the CSS working group, and a day with the HTML working group as well, in addition to participating on a panel during the Technical Plenary Day itself. Unfortunately for a number of reasons I had to cancel my attendance. In approximate order of significance (though each were perhaps sufficient on their own).
When I look at all the above however, I can't help but conclude that in each instance I'm responsible. That night I fell and badly sprained my ankle, I pushed myself too hard when I went bouldering after an exhausting day at the Graphing Social Patterns conference for which I had gotten up at 6am after only 4 hours of sleep, mere days after returning from Spain. I allowed too many tasks to build-up and/or committed to too many things in early November. And I failed to both properly evaluate the full extent and impact of the costs of attending W3C meetings in Cambridge for a week, and request sponsorship accordingly.
As such, I must offer my regrets and sincere apologies to my fellow colleagues and W3C community members for missing the W3C Plenary / All Group Meetings Week for the first time ever (I've made it to all previous such events). I'm sorry I am unable to meet with you in person. I wish you all a very productive week.
Sometimes you see very strange things on freeways in San Francisco. This past April, I think as I was getting a ride to SFO from my friend Carla, this guy driving alongside us was looking over and gesturing wildly with a book. I looked over, and he rolled his window down and started shouting, so of course I rolled down my window and recorded him. That's the way it works folks - act strange in public, get recorded and published on the internets.
I used to eat lunch in South Park several times a week, and a few times we spotted this guy dressed in the typical business casual bizdev costume doing what appeared to be Tai Chi but with perhaps a little extra flair. It was out of the ordinary enough that I decided I had to capture it.
There is a lot of freeway reconstruction going on in the SOMA part of San Francisco. Having worked for Technorati on 3rd street and often walked underneath the freeways being carefully torn down or built up, these few seconds of a bulldozer moving deconstructed concrete around with a Gap billboard in the background caught my eye.
Continuing with videos from seasons past, the following is a quick walkthru of a party called "Ye Olde Bunny Jamme VII" that aptly demonstrates how quite a few in San Francisco celebrate the arrival of spring.
Chris Messina recently wrote a heartfelt post titled hCard for OpenID Simple Registration [SREG] and Attribute Exchange. It's a really well written post with lots of deep thinking about how we should "just" use hCard for OpenID SREG. Go read it, as the rest of my post will assume you have.
There are three key points I would like to follow-up on, the first of which I will dive into in here, saving the latter two for follow-up posts.
As Chris has already documented, the vast majority of SREG attributes are simply renamed versions of well established vCard (and hence hCard) properties. Here is what I think are the three key discrepencies and respective modest proposals for reconciling them.
gender. SREG has a gender property. vCard (and thus hCard) does not. This has not gone unnoticed in the microformats community which has done research for gender information, including collecting gender examples on real world sites, and pre-existing gender formats. For maximum interoperability, compatibility, and minimum vocabulary drift/expansion, the microformats community has resisted adding anything to hCard above and beyond vCard. Thus:
Modest proposal 1: Let's write a draft Internet RFC to add a "gender" property extension to vCard RFC2426 that takes an arbitrary string value with predefined semantic values (case insensitive of course) of "M", "F", "OTHER" , and "NA" (aka "Not Applicable", for organizations and named locations). Then reference that accordingly in an iteration of hCard. Problem solved.
preferred language. SREG also has a preferred language property. vCard (and thus hCard) does not. This is the first I have heard of such a property, and quickly browsing a few social networking sites, Flickr is the only one that I found offhand that obviously supports such a profile preference. For this property I'm calling edge case. That is, such a property may actually be useful, but should not merit inclusion from the perspective of what is commonly supported across sites today. Thus:
Modest proposal 2: Drop the preferred "language" property from SREG.
URLs for properties. Every SREG property has a URL in its Attribute Exchange (AX) version that defines that property. hCard does too, through the hCard profile. However, there are two differences which may be seen as shortcomings. Currently the hCard profile on microformats.org is in a wiki, and not proper XMDP (there is an hCard XMDP profile at W3C that some are using), and, URLs for specific properties use # fragment identifiers. Thus:
Modest proposal 3, in two parts:
For now, I would like to hear what the members of both the microformats and OpenID communities think of the above modest proposals. Are they reasonable and practical? Can we do them quickly? And most importantly, are they sufficient for OpenID to use hCard for profile data?
It has been a while since I last posted a video and NaVloPoMo is the perfect excuse to try to get thru the collection of short videos I've taken and filtered. This is a short 360 degree video of Justin.TV being interviewed by NPR in South Park, San Francisco. You can see my colleagues Stephen and Andrei in the background.
Michael E. Rubin asked on Twitter earlier today:
Question for Open Social evangelists -- where is identity portability? When do we get to truly 'own' our personal data and friends (isntead of renting to Facebook)?"
An excellent question.
For anyone not paying attention to Twitter, or their feed reader the past 24 hours, "OpenSocial", a set of APIs for social network applications, and a set of companies signed on to support it (like Google , Plaxo , MySpace , Bebo, and several others), is currently the top talk of the web technology world. If you "track opensocial" in Twitter, your IM or SMS will buzz/ding every few seconds. Technorati search already has over 2900 results for OpenSocial.
Back to the question at hand. Michael asks a very good question, and in response I twittered that OpenSocial is a key step forward for social application portability, while for other forms of portability, we already have well implemented solutions (Chris Messina reminded me of the importance of "OAuth for provisioning access to all your portable facets"). Here is a portability map of the technologies, what portability they enable, and who they primarily help today:
|social application||OAuth , OpenSocial||developers(1)|
All of these are components of social network portability.
Identity Portability could be argued to be a combination of the latter three, your portable social profile, your portable friends list, and your portable login / authentication.