The short-form week of 16–22 Mar 2009

23 Mar 2009; last modified 13 Mar 2011

The week in review, 140 characters at a time. This week, 38 messages in 33 conversations. (With 1 favorite.)

This document was created automatically from my archive of my Twitter stream. Due to limitations in the Twitter API and occasional glitches in my archiving system, it may not be 100% complete.

Monday at 03:22pm

Playing around for XML Prague: implemented an XProc "eval" step. Remarkably straightforward.—@ndw

In a conversation that started on Monday at 04:13pm

Washington-Dulles has immigration processing designed to make visiting the USA miserable. #boarding IAD—@webmink
@webmink What gate? #boarding IAD—@ndw

Monday at 05:13pm

Enjoying an American Ale, a pretty good one, before my departure to LHR.—@ndw

In a conversation that started on Monday at 05:34pm

I think Facebook is throwing down the gauntlet and going to everything. They're getting more attractive to this Twitter user every day.—@davewiner
@davewiner AFAICT Facebook's disregard for user privacy us still a problem.—@ndw

Monday at 05:38pm

Scored seat 30H on this 777 IAD-LHR, it ain't business class, but I can haz legroom yes plz ty.—@ndw

Monday at 05:41pm

If only United provided in-seat power like American...—@ndw

Tuesday at 03:33am

I miss the old-school 'clackity-clackity-clack' tumbler-style departure board at London Liverpool Street. Digital? Bah. Who needs it?—@ndw

Saturday at 02:42am

I can haz bits. For the first time in almost a week, I can haz bits.—@ndw

Saturday at 10:15am

Getting bashed by Robin over DocBook element names...—@ndw

Saturday at 10:20am

The historical rationale on DocBook names is that they weren't case sensitive in SGML—@ndw

Saturday at 10:28am

wrt XLink: my *biggest* mistake was agreeing to edit XLink 1.1.—@ndw

Saturday at 10:46am

@JeniT +1—@ndw

In a conversation that started on Saturday at 11:00am

MLA FAIL: “the MLA no longer recommends the inclusion of URLs in the works-cited-list entries for Web publications.” http://bit.ly/yiL76—@jschneider
@jschneider There may be problems with URLs, but not pointing to them isn't the answer for any of them.—@ndw

Saturday at 11:12am

@JeniT Phhtphhbbtt!—@ndw

Saturday at 11:18am

Making mental note to take oXygen out for a test drive again. Cool stuff #xmlprague—@ndw

In a conversation that started on Sunday at 03:06am

@ndw - would really like to get MarkLogic involved with this - www.exquery.org - perhaps we could have a chat later?—@adamretter
@adamretter Absolutely!—@ndw

In a conversation that started on Sunday at 03:27am

@ndw Why not use the output of the store step (the URI of the document) as the value of the args option on the exec step?—@JeniT
@JeniT Duh. Why didn't I think of that?—@ndw

In a conversation that started on Sunday at 03:38am

@ndw - Stand still Norm, for the video :-)—@dpawson
@dpawson Sorry, Dave. I'm nearly incapable of standing still and presenting simultaneously. I'll work on it!—@ndw
@ndw: Good present, got a bit hairy for newbies though, at least via video! good night last night? Lots of water?—@dpawson
@dpawson @ndw did very well, especially for someone who only had 4 hours sleep after a lot (a *lot*) of beer.—@JeniT
@JeniT Oh, so that was water you were drinking? :-P—@ndw

In a conversation that started on Sunday at 04:05am

Optimizing XML Content Delivery with XProc Vojtěch Toman coming up next—@xmlprague
@xmlprague Is the video being recorded for later playback, or just streamed?—@ndw

In a conversation that started on Sunday at 04:19am

@JeniT @ndw And there was I feeling sorry for this person new to public speaking :-) I thought it was nerves—@dpawson
@dpawson It was nerves, nevermind what Jeni says.—@ndw

Sunday at 04:26am

‚ô∫@xproc: Updated xproc.org; added pointer to Roger and James' XProc tutorial—@ndw

In a conversation that started on Sunday at 04:28am

You don't need to create new pipelines to wrap built-in steps, do you? Can't you invoke them directly just like user-defined steps?—@JeniT
@JeniT Yes, you can run them directly, though exactly how is implementation defined. So wrapping them may be easiest for most users.—@ndw

Sunday at 04:39am

@adamretter exproc is designed with the same sorts of goals in mind as exslt and exquery.—@ndw

In a conversation that started on Sunday at 04:53am

Interesting overlap between XProc and exslt 2.0 #xmlprague—@ndw
@ndw (bout overlap btwn XProc & EXSLT) Yes, cause those samples are high-level, but there are ext. opprt. at XDM level as well (nested seq.)—@fgeorges
@fgeorges Yes, lots of opportunities!—@ndw

Sunday at 05:24am

Adreneline wearing off. Higher brain functions shutting down...—@ndw

Sunday at 05:55am

Someone (Rick Jelliffe, I think) asked me about federating some things at Apache. Another option, I suppose.—@ndw

In a conversation that started on Sunday at 06:05am

s/XSLT/XProc/—@fgeorges
@fgeorges :-)—@ndw

In a conversation that started on Sunday at 08:58am

Updated the XProc test coverage report. We have a ways to go... http://tinyurl.com/c65fjd—@ndw
@ndw I can't find any way to point to a particular step (say with an a/@id or something.) Did I miss it?—@fgeorges
@fgeorges You can put xml:id attributes on them.—@ndw
@ndw Well, I was speaking about linking to a particular step in the coverage HTML report on the website. Cannot put anything there ;-)—@fgeorges
@fgeorges Ah. Well. I should fix that :-)—@ndw
@ndw I tried to get from that xpath test suite to the issues list... no joy. No link to wg home, spec. "I am a rock. I am an iiiiiisland."—@dckc
@dckc Good catch. Fixed.—@ndw

Sunday at 09:27am

fears there are holes in his test suite coverage generation stylesheet. Surely try-001.xml and try-002.xml use, you know, p:try?—@ndw

In a conversation that started on Sunday at 09:33am

Tks!—@fgeorges
@fgeorges Fixed, I believe.—@ndw

Sunday at 09:34am

Sunday at 10:24am

Cool SVG demos from Robin #xmlprague—@ndw

Sunday at 10:31am

Just what I always wanted, more video on the web. #cranky—@ndw