A recent comment on the Groklaw blog entitled Which Binary Key? claims that one needs a "binary key" to consume XML produced by Microsoft Office 2003. Specifically the post claims
No_Axe speaks as if MS Office 12 had already been released and everyone was using it. He assumes everyone knows the binary key is gone. Yet Microsoft is saying that MS Office 12 is more or less a year away from release. So who really knows when and if the binary key has been dropped? All i know is that MSXML 12 is not available today. And that MSXML 2003 has a binary key in the header of every file.
...
So let me close with this last comment on the fabled “binary key”. In March of 2005, when phase II of the ODF TC work was complete, and the specification had been prepared for both OASIS and ISO ratification, the ODF TC took up the issue of “compliance and conformance” testing. Specifically, we decided to start work on a compliance testing suite that would be useful for developers and application providers to perfect their implementations of ODF. Guess who's XML file format was the first test target? Right. And guess what the problem is with MSXML? Right. It's the binary key. We can't do even a simple transformation between MSXML and ODF!

As someone who's used the XML features of Excel and Word, I know for a fact that you don't need a "binary key" to process the files using traditional XML tools. Brian Jones, who works on a number of the XML features in Office, has a post entitled The myth of the Binary Key where he mentions various parts of the Office XML formats that may confuse one into thinking they are some sort of "binary key" such as namespace URIs, processing instructions and Base64 encoded binary data. All of these are standard aspects of XML which one may typically doesn't see in simple uses of the technology such as in RSS feeds.

Being that I used to work on the XML team there is one thing I want to add the Brian's list which often confuses people trying to process XML; the unicode byte order mark (BOM). This is often at the beginning of documents saved in UTF-16 or UTF-8 encoding on Windows. However as the Wikipedia entry on BOM's states

In UTF-16, a BOM is expressed as the two-byte sequence FE FF at the beginning of the encoded string, to indicate that the encoded characters that follow it use big-endian byte order; or it is expressed as the byte sequence FF FE to indicate little-endian order.

Whilst UTF-8 does not have byte order issues, a BOM encoded in UTF-8 may be used to mark text as UTF-8. Quite a lot of Windows software (including Windows Notepad) adds one to UTF-8 files. However in Unix-like systems (which make heavy use of text files for configuration) this practice is not recommended, as it will interfere with correct processing of important codes such as the hash-bang at the start of an interpreted script. It may also interfere with source for programming languages that don't recognise it. For example, gcc reports stray characters at the beginning of a source file, and in PHP, if output buffering is disabled, it has the subtle effect of causing the page to start being sent to the browser, preventing custom headers from being specified by the PHP script. The UTF-8 representation of the BOM is the byte sequence EF BB BF, which appears as the ISO-8859-1 characters "" in most text editors and web browsers not prepared to handle UTF-8.

I wouldn't be surprised if the alleged "binary key" was just a byte order mark which caused problems when trying to process the XML file using non-Unicode savvy tools. I suspect some of the ODF folks who had problems with the XML file would get some use out of Sam Ruby's Just Use XML talk at this year's XML 2005 conference. 


 

Categories: XML

I've been using MSN Virtual Earth for a while now and like it quite a lot. However there is definitely room for improvement and I'm glad to see that the team is soliciting feedback from users on what features they consider most important for the next release. In the post Suggestions for Virtual Earth Release 2? they write

The VE team is rolling on the next release and is interested in your feature requests. Lets make it interesting - You have 10 bucks to spend on features. How would you spend 'em? Post your comments here. My shopping list might look like this -
 
4  Street maps for Italy
3  Driving directions integrated in the application and not linked off to maps.msn.com
3  improved WiFi coverage for the Locate me feature in rural areas.
 
You get the idea. Go ahead, buy your features. Just remember to stay within your budget :-)

If you use VE and have some features you'd like to see in the next release, go ahead and post a comment with your requests. Here's how I'd spend my $10 on features; $2 to expand the Virtual Earth API to include conversions from physical addresses to latitudes & longitudes (aka geocoding), $3 to integrate driving directions into VE as opposed to being linked to http://maps.msn.com as is done today, $4 to add the ability to store my favorite locations in VE, and $1 to add maps of Canada to the service.

So how would you spend your dollars on VE features?


 

Categories: MSN

October 17, 2005
@ 04:51 PM

Every week or so I get a complaint from someone using Safari on Mac OS X complaining about the fact that my blog looked wacky in their browser. I finally got around to fixing the templates used by my blog and now it should look fine in Safari.

The following sites were helpful in showing me what my site looked like in Safari; http://www.danvine.com/icapture/ and http://www.fundisom.com/g5/. Thanks to Martin Dittus for pointing me out to these sites without which I wouldn't have been able to confirm my changes.


 

Categories: Ramblings

Dave Sifry, the CEO of Technorati, has a regular series of posts called The State of the Blogosphere where provides various statistics about the number of blogs Technorati is tracking. In State of the Blogosphere, October 2005 Part 1: On Blogosphere Growth he writes

About 70,000 new weblogs are tracked every day, which is about a new weblog created each second, somewhere in the world. It also appears that blogging is taking off around the world, and not just in English. Some of the significant increases we've seen over the past 3 months have been due to a proliferation of chinese-speaking weblogs, both on MSN Spaces as well as on Chinese sites like blogcn.com .

The growth of the Chinese blogosphere on MSN Spaces is a trend those of us working on Spaces have seen first hand. I wouldn't be surprised if we are one of the biggest blog hosting services for Chinese bloggers. An interesting side effect of this growth is that an increasing number of blogs in the Technorati Top 100 are blogs that are popular with Chinese users of MSN Spaces.

Below is a list of the MSN Spaces on today's version of the top 100 list 

27. spaces.msn.com/members/princesscecicastle
11,999 links from 3,455 sites. View All »

30. Hack MSN Spaces
­Spaces Customization at its Best™
By Devdutt Parikh
12,540 links from 3,329 sites. View All »

41. spaces.msn.com/members/slim
By slim
8,569 links from 2,771 sites. View All »

47. Herramientas para Blogs
Herramientas para spaces. Un blog sobre personalización de los spaces
By mmadrigal madrigal
7,309 links from 2,578 sites. View All »

49. Scott's "SiteExperts" Place
Web developers, Web developers, Web developers! MSN Client architect who shares his thoughts on DHTML, AJAX, Client Frameworks, etc., and how we are engineering MSN properties.
By Scott Isaacs
7,103 links from 2,509 sites. View All »

66. spaces.msn.com/members/flowersummer
6,405 links from 2,118 sites. View All »

71. spaces.msn.com/members/locker2man
By locker2man
5,358 links from 2,026 sites. View All »

74. spaces.msn.com/members/hcy521
6,640 links from 2,007 sites. View All »

It is interesting to note that every space on the Technorati Top 100 list is either Chinese or is about customizing/hacking the MSN Spaces user interface which is popular among our Chinese users. I'd never have guessed that these would be the most popular spaces when we launched the service last year.


 

Categories: MSN

A comment to my post Some Thoughts on the Mini-Microsoft blog struck me as so good that it was worth sharing. So I'm reposting it here so others get to see it

The Lessons of Longhorn
I’ve worked at MS for many, many years in the product groups. I love the company, and have prospered with it. I’m not some disgruntled flunky. I manage a big group, and am committed to doing everything I can to make my group a great place to be and build really compelling products that lots of customers will want to buy. We were and still are a great company in many ways. But we could be even greater.

The Longhorn saga highlights some stark lessons about why employees are pissed off and frustrated with the very top handful of execs. We are all held to very high standards. We write annual commitments, and work very hard to achieve them. If we don’t achieve them, we know we will not be rewarded. We want to do great work, make great products, and be rewarded for it, personally and financially. We don’t shirk from this challenge, we are up to it! But, we expect these rules to apply to everyone, evenly and openly. All the way to the top.

Longhorn will be a good product when it ships, but it will ship two years later than it should have. That extra two years represents what, maybe 8,000 man years of work? At a fully burdened cost of say $150k/head/year that’s $1.2Billion in direct costs of our resources flushed down the toilet. But far worse than those direct costs are the lost opportunity costs of not having the product in market two years earlier and getting started on Vnext.

Who is to blame for this debacle? First BillG himself, for pushing the Windows group to take on huge, extremely difficult technical projects that destabilize all the core parts of the OS, and hold shipping hostage. Even worse, in some cases these efforts seem to be little more than ‘pet’ ideas of Bill’s, with little clear customer value, at least to my understanding. Second, the very top handful of execs in the Windows group are to blame, for placating Bill and not applying the most basic good judgment on engineering and project management. From my perspective, it was clear to nearly every engineer in every product group at MS that Longhorn was badly screwed up, for far too long. But no one at the top would admit it or come to grips with it for far too long. For top product execs as MS, there is a long history of a culture that Bill is right, do what he says, always stay in his good graces no matter what. If you do that, you will likely make a huge fortune. If you don’t, your career at MS is over. I understand the pressure on execs to behave that way and always say ‘Yes’ to Bill. But that’s not the leadership we need. We are not helping anyone with this game, neither customers nor ourselves.

All of us know that if we screwed up like this, we would likely be forced out of our groups, with our reputations as product people shot, and for good reason. But when Bill and Jim et al screw up, nothing happens.

I really want Bill to be man enough to stand up and say, “I made a big mistake. This is what we’ve learned, and this is how we are going to do even better.” Bill is a tremendous thinker, but he is human too, and sometimes can make mistakes. We can’t have a culture that holds he is semi-divine. We need leaders who really lead, pragmatically and effectively, who hold themselves openly to the same standards that we are all held to. That is how we can become an even better company and reach more of our still great potential.



 

Categories: Life in the B0rg Cube

In his post Betty Dylan, Railroad Tavern, Sunday 8PM Jon Udell writes

I wondered why online services like upcoming.org hadn't yet gone viral, and I made a few suggestions, which were well received. But to be honest, the Keene, NH metro in Upcoming is no more lively now -- a day after Yahoo acquired Upcoming -- than it was six months ago.

Case in point: the Betty Dylan band is coming to Keene on Sunday and Monday. I know this because a friend organized the event. But neither of the venues' websites -- Railroad Tavern and Keene State College -- has the information. Nor does the Keene Sentinel. What's more, none of these three websites makes calendar information available as RSS feeds.

Yahoo's acquisition of Upcoming will certainly help move things along. As will the growing visibility of other such services, notably EVDBEventful. But since I expect no single one of these to dominate, or to supplant the existing calendars maintained by newspapers, colleges, and other venues, we have to think in terms of syndication and federation.

RSS is a big part of the story. Calendar publishers need to learn that information made available in RSS format will flow to all the event sites as well as to individual subscribers.

I think, like me, Jon Udell is grabbing a hold on things from the wrong end of the stick. When I first started working on the platform behind MSN Spaces, one of my pet scenarios was making it easier to create blog posts about events then syndicating them easily. One of the things I slowly realized is that unlike blogging which has killer apps for consuming syndicated content (RSS readers) there really isn't anything similiar for calendar events nor is there likely to be anything compelling in that space in the near future. The average home user doesn't utilize calendaring software nor is there incentive to start using such software. Even if every eventing website creates RSS feeds of events, the fact is that my girlfriend, my mom and even me don't maintain calendars which would benefit from being able to consume this data.

The corporate user is easier since calendaring software is part of communications clients like Outlook and Lotus Notes. However those aren't really the targets of sites like Upcoming or Eventful, however I suspect those are their best bets for potential users in the near term.  


 

October 16, 2005
@ 05:46 PM

Richard McManus has a blog post on his Read/Write Web blog entitled craigslists gets heavy with Oodle where he writes

Uber classifieds site craiglist has requested that Oodle , a classifieds 'meta' search engine, refrain from scraping its content. This has the potential to be the first high-profile case of a mash-up site being slapped for taking another site's content.

In a recent ZDNet post , I wrote that the business models for Web 2.0 mash-ups are beginning to ramp up. Some of the revenue possibilities for sites like Oodle are advertising, lead generation and/or affiliates, transactional, subscription.

Oodle wrote on their blog that they send craigslist "free traffic" and they "don't compete with them by taking listings." John Battelle said that craigslist's response to Oodle "feels counter to the vibe craigslist has always had".

This reminds me of the panel on business models for mash-ups at the recent Web 2.0 conference. One of the things that had me scratching my head about the panel is that it seemed to have skipped a step. Before you talk about making money from mash-ups, you have to talk about how people providing the data and services mash-ups are built on make money.

Providing data and services isn't free; servers cost money, system administrators and other operations folks cost money, and even the bandwidth costs money.  Simply claiming to be sending a service "free traffic" may not justify the cost to them of supporting your service and others like it. Then there's the fact that the site may have strategic reasons for not wanting their data syndicated in other sites.

A good example that comes to mind is eBay. Although eBay has an extensive API for developers who want to consume its data and services yet they aggressively defend themselves against screen scraping services to the extent that they created a legal precedent for services based on screenscraping their site to be considered tresspassers. On the one hand this seems schizophrenic but the fact is that it makes sense from a business perspective for eBay to do this.

Personally, I think more companies need to be like eBay and decide where it makes business sense to open up their website or service as a web platform. As part of my ThinkWeek paper on MSN as a Web Platform I've tried to create a taxonomy that can be used as a starting point for web companies to decide where they should consider being open. This taxonomy will  also be part of my talk at O'Reilly's Emerging Technology Conference if my proposal gets accepted. 


 

Categories: Web Development

I've been to two O'Reilly Conferences this year and both times I've been struck by the homogeneity of the audience. Most of the speakers and attendees are white males in their mid-twenties to mid-thirties. There are few blacks, women, indians or east asians. Much fewer than I'm used to seeing during my typical workday or at other conferences I have attended. Shelley Powers has mentioned this before in posts such as Maids, Mommies, and Mistresses  but today was the first time I've seen this commented on by one of the folks I'd consider to be in the 'inner circle' of the O'Reilly Conference set.

In his post What it's like at Web 2.0 Anil Dash writes

So, there's the Old Boy's Club. And surprisingly, there's a 50-50 ratio of wanna-bes to real successes within that club. But the unsurprising part is probably what the makeup of that club looks like. Web 2.0 might be made of people, as Ross Mayfield said, but judging by the conference, Web 2.0 is pretty much made of white people. I'm not used to any event in a cosmopolitan area being such a monoculture.

Now, the folks who organized Web 2.0 are good people whom I genuinely believe want their event to be inclusive. But the homogeneity of the audience doesn't just extend to ethnicity, it's even more evident in the gender breakdown. There are others who've covered this topic better than me, but it's jarring to me not merely because the mix was such a poor representation of the web that I know, but because I think it's going to come back and bite the web in the ass if it doesn't change eventually.

See, it's not just making sure the audience and speakers represent the web we're trying to reach, but the fact that Bay Area tech conferences are so culturally homogenous is dangerous for the web industry. When people talk about buying a song on the iTunes music store, they're still using some tired Britney Spears example, or if they're under 35 or so, they might mention Franz Ferdinand. This is not an audience in touch with Bow Wow or Gretchen Wilson, even though they've sold millions of trackcs. When they talk about television, they're talking about broadcasting Lost or Desperate Housewives, but they're not aware of Degrassi or Ultimate Fighting. Worse, I met a number of people who were comfortable with being culturally illiterate about a great many people who live right here in the U.S.; I can't imagine how they would reach out to other cultures or countries.

I've been quite surprised by how much O'Reilly conferences fail to reflect the diversity of the software industry as I've experienced it, let alone the Web at large. This is "Web 2.0"? I surely hope not.


 

Categories: Ramblings

I've been watching this unfold at work and it's great to know it's now official. From the press release Microsoft and Yahoo! Announce Landmark Interoperability Agreement to Connect Consumer Instant Messaging Communities Globally we learn

SUNNYVALE, Calif., and REDMOND, Wash. — Oct. 12, 2005 — Yahoo! Inc. (Nasdaq: YHOO) and Microsoft Corp. (Nasdaq: “MSFTâ€) today announced a landmark agreement to connect users of their consumer instant messaging (IM) services on a global basis. The industry’s first interoperability agreement between two distinct leading global consumer IM providers will give MSN® Messenger and Yahoo!® Messenger users the ability to interact with each other, forming what is expected to be the largest consumer IM community in the world, estimated to be more than 275 million strong.

Being able to instant message between IM communities is one of the features most requested by MSN Messenger and Yahoo! Messenger users, and Microsoft and Yahoo! share a commitment to provide IM interoperability while keeping consumer security and privacy first and foremost. In addition to exchanging instant messages, consumers from both communities will be able to see their friends’ online presence, share select emoticons, and easily add new contacts from either service to their friends’ list, all as part of their free IM service.* Yahoo! and Microsoft plan to introduce these interconnectivity capabilities between MSN Messenger and Yahoo! Messenger to customers around the world in the second quarter of 2006, and in doing so expect to help make IM an even more useful part of consumers’ online communications and communities.

This is really good news and a step in the right direction with regards to interoperability across instant messaging applications. Now I have to go nag the folks across the hall about what this means for folks like me who use our "@yahoo.com" email addresses as our Messenger sign-in names. I already had to switch once from my "@microsoft.com" address when Microsoft started using Live Communication Server internally. 

I'll see what I can find out from folks when they get into work later today and report back.


 

Categories: MSN

More info keeps spilling out about the beta of the Hotmail "Kahuna" release. If you go to http://join.msn.com/mailbeta/features, you'll get an overview of the new features in the next version of Hotmail including screenshots. The list includes

As the saying goes a picture is worth a thousand words. It's a lot easier to appreciate the work that's gone into the next version of Hotmail when you actually see it. Even better is using it, so don't forget to sign up for the beta by going to http://www1.imagine-msn.com/minisites/hotmail/Default.aspx.


 

Categories: MSN