Final Schedule for XML 2005

The final sched­ule is up on the XML 2005 web site and I think it’s the best yet (maybe I say that every year, but there are some really good talks on the pro­gram this year). We have big com­pan­ies talk­ing about what they’re doing, small com­pan­ies talk­ing about new tech­no­lo­gies, and inde­pend­ent people talk­ing about what they’re cook­ing up in their base­ments or gar­ages. There are talks for the new­comers to XML, talks for the cyn­ics, and talks for those in between, so take a look!

And of course the tutori­als are avail­able for regis­tra­tion; I’d urge every­one who is inter­ested in attend­ing a tutori­al to register as soon as pos­sible. If we don’t get enough regis­trants for some tutori­als we need to can­cel them, which is dis­ap­point­ing for the con­fer­ence, and the tutori­al presenter, and espe­cially for people who wanted to attend the tutori­al but did­n’t register in time. You don’t need to attend the con­fer­ence to attend a tutori­al; we try to be flex­ible to meet attendees’ needs (per­son­ally I think you should, of course, but every­one has dif­fer­ent ideas as to what they want to do in any giv­en year).

There are also more ways to take part in the con­fer­ence: every registered con­fer­ence attendee, as well as registered booth staff, can put up a poster (or two). Posters can be on any (reas­on­able) sub­ject; posters on new product ideas, new tech­no­logy ideas, form­ing groups to work on either of the above, advert­ising your avail­ab­il­ity for full-time hire, or advert­ising your con­sult­ing ser­vices are all wel­come. The poster dead­line for guar­an­teed space is Novem­ber 4; space may be avail­able at the con­fer­ence as well, but that’s not guaranteed.

We also have an art­work exhib­it each year to show how tech­no­logy and artistry are not mutu­ally exclus­ive; any ideas are wel­come. These pieces are shown next to the pieces in the exhib­it hall, so any­one can admire your work, wheth­er signed or anonym­ous. Dead­line to guar­an­tee space is Octo­ber 28; there may be space avail­able later as well.

It’s going to be a fun and inter­est­ing con­fer­ence again this year, I can just tell!

Speaking at Conferences

Shel­ley’s post­ing Maids, Mom­mies, and Mis­tresses made me decide to throw in my own few cents on what makes a good con­fer­ence sub­mis­sion, and how talks are accep­ted, to add to what Kathy Sierra and Adam Trachten­burg said (and there are good points in both). I’ve chaired a con­fer­ence since 2001, organ­ized tracks, and been a speak­er at vari­ous con­fer­ences for many years, so I know some­thing about the subject.

Num­ber 1 has to be: if there are guidelines, read them and act on them! The con­fer­ence organ­izers wrote them for a reas­on. I’m always amazed how many people obvi­ously don’t read the ones I have for XML 2005 at Abstract Writ­ing Hints — we get abstracts that are two sen­tences long, with mis­spellings, and acronyms used wrongly. The review­ers uncere­meni­ously dump all of these.

I’ve been involved in lots of con­fer­ences and they range from the peer-reviewed to the “people we know or who pay get pref­er­ence”; you need to fig­ure out which con­fer­ence you want to speak at and why, and which sys­tem they use, and how to have your talk accep­ted in that sys­tem. If the inform­a­tion isn’t on the con­fer­ence web site about how talks are selec­ted, email someone from the organ­iz­ing com­mit­tee and ask! Or find the name of a speak­er from the pre­vi­ous year and ask them — most people don’t mind a brief polite email ask­ing how they got on the program. 

At the XML 2005 Con­fer­ence I chair we use a blind peer review pro­cess to grade the abstracts. The Plan­ning Com­mit­tee then takes those grades and looks for pro­gram bal­ance to cov­er inter­est­ing top­ics, know­ing who the speak­ers are. This sort of sys­tem means that if you write a good abstract on an inter­est­ing top­ic, that isn’t topped by an even bet­ter abstract on a related top­ic, you’ll find your­self on the pro­gram. (Key­notes are a dif­fer­ent story, of course, they’re invited). Most of the speak­ers each year are new speak­ers; some are “per­en­ni­als” but that’s because they are involved in inter­est­ing work and know how to describe it in ways that make the review­ers want to attend the talk. The blind review sys­tem is biased towards sub­mit­ters who can explain what they’re doing and why it’s inter­est­ing in 500 words or less, but I fig­ure that’s a reas­on­able indic­at­or for being a good speak­er as well. It does­n’t always work that way (and we col­lect attendee reviews of the speak­ers each year to catch those cases), but usu­ally it does. Oh, and anoth­er thing — it’s so much easi­er to have 100+ people help us fig­ure out which talks are good than to rely on only 7 people on a Plan­ning Committee! 

The final piece of advice I’d give, once your talk is accep­ted, is to prac­tise, if you’re not an exper­i­enced speak­er. Even bet­ter, record your talk (audio and video) and watch the video to fig­ure out what you can do bet­ter. Prac­tise to your­self, the cat, or your fam­ily. Doing some pro­fes­sion­al train­ing is good, but being famil­i­ar with the mater­i­al so you’re not talk­ing to the pro­jec­ted slides, or your notes, is bet­ter. Being pre­pared for likely ques­tions is also good, and hav­ing a couple of “pro­posed” ques­tions to give the chair of your ses­sion should nobody in the audi­ence have ques­tions nev­er hurts. In oth­er words, be prepared!

End of an Era

Now that the XML Cata­log spe­cific­a­tion has been approved as an OASIS Stand­ard, it feels like the end of an era to me. I’ve been chair­ing the Entity Res­ol­u­tion Tech­nic­al Com­mit­tee since its incep­tion way back in Octo­ber 2000 , work­ing with a good group of people. As Norm put it today, we’d be happy to work on any stand­ard with this group. Every­one work­ing togeth­er, no pos­tur­ing, no weird agen­das, just people try­ing to find the best solu­tion to a prob­lem. It made the group easy to chair, and I’m con­fid­ent the res­ults reflect that; I can­’t help but sus­pect that dys­func­tion­al com­mit­tee polit­ics res­ults in spe­cific­a­tions that are not as good as they could have been.

So I’m a little nos­tal­gic right now, remem­ber­ing the first dis­cus­sions, the meet­ings at con­fer­ences, as well as the break we took in the middle before decid­ing to go for that “OASIS Stand­ard” monik­er. The TC still has 3 of the ori­gin­al 4 co-pro­posers (Norm Walsh, Paul Grosso, and me; John Cow­an had to pull out part-way through due to work oblig­a­tions). New people joined, and oth­ers left, but over­all we had a pretty stable group. 

So I want to thank the mem­bers of the ER TC, both past and present, and also Mary McRae and Robin Cov­er of OASIS. Your good humour, desire to do the right thing, and will­ing­ness to put in the effort all meant a lot and made it pos­sible to final­ize the spe­cific­a­tion and show mem­bers of OASIS why it’s use­ful. I’d also like to thank the imple­ment­ors of the cata­log spec who proved that it’s imple­ment­able! I believe cata­logs will be widely used in the future, even if, like much XML plumb­ing, people won’t actu­ally see a cata­log very often. 

So feel free to drop by the Sun booth at XML 2005 to talk about cata­logs; either Norm or I are likely to be there and Norm will have his cata­log imple­ment­a­tion on his laptop to show people (along with a bunch of oth­er things, of course).

Northern Voice (2006)

So I’m up to my eye­balls in pro­ceed­ings papers for XML 2005 which is one end of the con­fer­ence spec­trum in terms of form­al­ity, work for the chair and the plan­ning com­mit­tee, and degree to which things must be organ­ised, when along comes the remind­er that the web site is up for North­ern Voice 2006. North­ern Voice is proof that there are cer­tain con­fer­ence con­cepts that don’t need a high degree of form­al­ity, in fact the concept of per­son­al blog­ging is, I think, dia­met­ric­ally opposed to too much form­al­ity, so as a mem­ber of the organ­ising group (plan­ning com­mit­tee seems a bit, ah, form­al a term) I’ve always been on the side of “keep it simple, keep it informal”. 

Last year’s event was a lot of fun and people seemed to really enjoy them­selves. So this year we’re put­ting a Moose Camp on the day before the con­fer­ence itself, where people can organ­ise them­selves into groups to dis­cuss whatever they want to dis­cuss that’s related in some way to per­son­al blog­ging. Dead­line for speak­er sub­mis­sions (we need to have some form­al­ity!) is Novem­ber 16, Moose camp is on Feb­ru­ary 10, the con­fer­ence is on Feb­ru­ary 11 and all the oth­er dates are on the web site. Yes, we still have the moose logo, although the col­ours are dif­fer­ent. Yes, we’re plan­ning on hav­ing more t‑shirts next year. No, we don’t yet know who the key­note speak­ers will be. Maybe we won’t have key­note speak­ers, we’ll fig­ure that out when we see the speak­er sub­mis­sions and see what sort of pro­gram we can build. Hope to see you there!

Okanagan Wineries

We went up to the Okanagan wine dis­trict for the Canada Day week­end this year, and I think it’s about time I wrote down some of my impres­sions of the vine­yards and the wine. We took my friend Sally (she of G&T fame who knows a lot about wine), and had a great time. Tim mostly enter­tained the off­spring while Sally and I tasted the wine, which seemed like a good divi­sion of labour to all of us. I typ­ic­ally like wines with body and heft, such as shiraz, much of the caber­net fam­ily, and rieslings; my impres­sions of oth­er wines depend on what they evoke (sit­ting on the deck in sum­mer, or some food pair­ing). So here are some notes about the winer­ies and the wines, none of them are any­thing sci­entif­ic or indeed any­thing oth­er than my impres­sion of that day!

Hawthorne Moun­tain Vineyards
Great view, but a very com­mer­cial vine­yard with lots of schnick-schnack to buy. I’d bought some caber­net franc here in 1995–6 which was great after a few years cel­lar­ing, but the 2003 Caber­net Franc they had on offer this year was too light and did­n’t give me any con­fid­ence it would devel­op the way I like. The pinot gris was good so I got some of that. The gewürztram­iner was ok though we’d had bet­ter at oth­er winer­ies, so that did­n’t go home with us, and although I thought the See-ya-later pinot noir could devel­op, I did­n’t feel like tak­ing the risk.
Wild Goose Vine­yards & Winery
Very friendly people, good whites (some have won prizes) though not what I’d call earth-shat­ter­ingly great. I bought a mixed case of whites, includ­ing the 2004 Riesling, 2003 Stony Slope Riesling, and the 2004 Gewürztraminer.
Stag’s Hol­low Winery
Unfriendly serv­er but a good vid­al (2004 Tra­gic­ally Vid­al), which is an unusu­al grape, and the 2002 Renais­sance Mer­lot struck me as worth tak­ing home, so I bought a couple of bottles for the cel­lar. It should be really good in a couple of years.
Hainle Vine­yards Estate Winery
Nice people, organ­ic wines; they’ve learned a lot about mak­ing organ­ic wines pal­at­able since I last vis­ited in 1996 or so. Good bis­tro for lunch out­side on the deck as well. The 2002 Hainle Chardon­nay, 2002 Hainle Pinot Blanc, 2002 Deep Creek Pinot Meuni­er (nice rich taste, like the Hawthorne Moun­tain one from 1995 or so), and 2003 Deep Creek Z2 were all good, the 2003 Hainle Syrah ok. Bought a mixed bunch to cel­lar, mostly the Pinot Meuni­er and Chardon­nay as they’re in short sup­ply and I figured I prob­ably could­n’t find them in Vancouver. 
Arrowleaf
New winery and quite far north. Friendly people. Bought a couple of bottles of 2002 Zei­gelt for the cel­lar, and some 2004 Bac­chus (nice light grape) and 2004 Gewürztram­iner for drinking. 
St Hubertus Estate Winery
Much of the winery was des­troyed in the big fire of 2003, but they’ve rebuilt with a big­ger tast­ing room. The rub­ber stamps are now in the tast­ing room rather than in a sep­ar­ate build­ing; they add a touch of eclecticism to the place. Decent selec­tion of wines. We picked the 2004 Dry Riesling to take home (with Tim warn­ing by this stage that we did­n’t have much room left in the car!)
Raven Ridge Cidery
Not quite a winery, this one, but a cidery con­nec­ted to an orch­ard with a good res­taur­ant. I picked up their last two bottles of Spark­ling Cider as well as a bottle of Brae­burn iced cider (like ice wine, but tastes of apples), just for a change. 

Tour­ing Okanagan winer­ies is an excel­lent exper­i­ence, and hav­ing the kid around meant we also tried out some of the oth­er tour­ist things rather than just sit­ting in the car. So although we did­n’t see as many winer­ies as the 1996 trip, we still filled the car and have wine enough to last us for quite a while!

Double Routing

Like prob­ably every oth­er com­puter geek out there, I do a cer­tain amount of help­ing friends set up their home sys­tems. This par­tic­u­lar friend knows noth­ing about net­works and fire­walls and the like, and just wanted some­thing secure that would allow her to have a reas­on­ably safe Win­dows box and the daugh­ter to have a reas­on­ably safe and vir­us-free Win­dows laptop. The easy bits were installing the spy­ware detect­ors (Ad-Aware and Spy­bot S&D) and the vir­us checker/utilities (Norton Sys­tem­Works); the tough bit was get­ting the routers to work.

The sys­tem that made most sense was to feed the DSL into a wired eth­er­net router with a built-in fire­wall (the D‑Link DI-604 has a reas­on­able price point and an integ­rated fire­wall) and then set up a wire­less point for the daugh­ter­’s laptop. So my friend got a Link­sys wire­less router (no fire­wall). We have this sys­tem at home, though with dif­fer­ent hard­ware (Linux fire­wall + Air­port wire­less) and it works just fine. So I was­n’t expect­ing any oddit­ies. I found the sup­port page on the Link­sys site that said to turn off the DHCP serv­er on the wire­less router, and to give it an IP address that fit­ted in with the IP setup of the wired router. That was easy enough to do. But some­how the laptop just nev­er man­aged to sync up.

Ah, how good it was that I allowed more time than I expec­ted to need to set it up! My basic idea was that eth­er­net comes out of the DSL mode, goes into the wired router in the uplink sock­et, then a cable comes out of the wired router and goes into the uplink sock­et of the wire­less router. Still seems logic­al to me, but in this case my logic was com­pletely wrong. For­tu­nately Link­sys has live chat to tech sup­port that works on a Sat­urday (good move, people!) and Mel­rose did­n’t need very long to fig­ure out the prob­lem and tell me to put the cable com­ing out of the wired router into one of the 4 reg­u­lar sock­ets. This worked just fine; the laptop synced up, my friend (and her daugh­ter) are happy and think I know exactly what I’m doing, while I’m still slightly baffled and won­der­ing what’s wrong with my simple hose-pipe ana­logy of inter­net con­nec­tions. Still, I now know empir­ic­ally what to do, so that’s the import­ant thing.