While it's cool that we have bits and electrons at this year's Developer's Conference, unfortunately the speaker has to compete with the entire web during their talk. This means that if you're less than completely riveting (which few speakers are), folks check out and often can't catch up. It's hard enough to give a good talk, but that's just brutal.

Here.

Here. Aaron joins in the fun.

Here. Rory Blyth seems to be keeping track of who he's eating with and who he meets in the rest room, so clearly, a must read. : )

Here. Don's blogging the Applied XML Developer's Conference.

10. WS-IrishSpring: for scented, more pleasing SOAP packets

9. WS-UPS: for sending SOAP packets in real envelopes

8. WS-USPS: for sending SOAP packets that dont need to get there

7. WS-PrisonShower: for picking up the dropped SOAP packets

6. X-Wife: protocol for monetary transfer

5. WS-Insecurity: dating protocol for web services programmers

4. WS-Monopoly: protocol used to keep antitrust penalties to manageable levels

3. NICKLE: for encoding smaller binary attachments

2. SFFCI: Syndication Format for Complete Idiots

1. WS-XXX: bringing a business model to XML, e.g.

<xxx:image xmlns:xxx=“uri://hustler.com/2003/oohlala”>
  <xxx:setting>the storeroom</xxx:setting>
  <xxx:model gender=“female” tattoo=“skull” />
  <xxx:model gender=“male” moustache=“true” />
  <xxx:pose>saucy</xxx:pose>
</xxx:image>

Chris Sells, Jason Whittington, Tim Ewald, Becky Dias & Brian Jepson
Presented at the Applied XML Developer’s Conference West 2003
July 10, 2003

Here. I'm posting this using the wireless access from the room where the Applied XML Developer's Conference will be going on tomorrow (testing from the back to make sure it works). If I wanted to, I could plug into the readily available power as well. Very spiffy. If you'd like to participate in the conference, head over to the conference home page for the link to the message board and post to your heart's content.

Here. My favorite thing about the term "refactoring" is that it gives a trendy name to architecting for today, knowing full well that we'll need to re-arch (and re-code) tomorrow when we've got new requirements. Stu says this in more detail for the unconvinced.