The short-form week of 6–12 Feb 2012
13 Feb 2012
The week in review, 140 characters at a time.
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.
Thursday at 04:10am
I hear that you have a looming deadline and a presentation to prepare for later today.
Here, have a hard drive failure. Love 'n' hugs, Life.—@philhawksworth
Thursday at 04:32am
You know those 80Mb power point presentations? Please stop sending them to me in email,
kthxbai.—@ndw
In a conversation that started on Thursday at 05:40am
Managed to remove 10 slides from my #xmlprague presentation. It was just way too long.—@vojtechtoman
@vojtechtoman Can I have ‘em? I usually run short :P—@ndw
Thursday at 07:07am
In a conversation that started on Thursday at 08:05am
If anyone is interested in the bleeding edge, I’ve done substantial hacking on my
“auto-caching” XML resolver: https://t.co/4u0d88gB—@ndw
In a conversation that started on Friday at 12:02pm
Just arrived at #xmlprague, Hotel Ariston. Anyone around?—@robinberjon
@robinberjon I'm at the same hotel, but I'm at the conf venue right now, for the #xmlprague pre-conf.—@fgeorges
@fgeorges Ok, I'm off to find Norm — text me if you're on your way out!—@robinberjon
@fgeorges How long are you staying there? I'm meeting Norm at 1900 at his hotel. Neither is
far from the Uni.—@robinberjon
@robinberjon That was the plan too, but the panel is still going on. Can you keep me posted on
the address once you're there?—@fgeorges
Friday at 02:04pm
In a conversation that started on Friday at 02:51pm
In a conversation that started on Saturday at 03:48am
Saturday at 03:50am
@ndw We should figure out which one of us does what part at some point :)—@robinberjon
Saturday at 03:53am
Saturday at 03:54am
Saturday at 03:56am
Saturday at 03:58am
Saturday at 04:13am
In a conversation that started on Saturday at 04:23am
I'm offering good alcohol to anyone who can come up with a good DocBook joke before
11h45. #xmlprague—@robinberjon
@robinberjon Nice. I wonder if I should offer more for not sending it to you? Phphttpbt! #xmplrague—@ndw
@robinberjon I guess you get your joke then. I’ll even try to laugh if it’s funny. #xmlprague #docbook—@ndw
@ndw announces support for HTML5 parsing rules in DocBook V6.0 (docbook jokes ... #xmlprague #docbook)—@jonathan_robie
.@jonathan_robie I often use DE to add HTML elements (script & style mostly) to #DocBook. #xmlprague—@ndw
Distributed extensibility is more important in collections of documents than in a
single document. cc @ndw @jonathan_robie #xmlprague—@jpcs
@jpcs You may have a case for the defunct head/@profile HTML attribute there. @ndw @jonathan_robie—@robinberjon
@robinberjon Yesterday, @evlist had a pretty good one about French administration rules and LivreDoc. #xmlprague—@fgeorges
Saturday at 04:30am
Saturday at 04:32am
Saturday at 04:38am
Saturday at 04:41am
@ndw @JeniT @robinberjon sounds fun, sorry I couldn't get the train down to join you for a beer later...—@fidothe
Saturday at 05:09am
Saturday at 05:25am
Saturday at 05:34am
@ndw Have you committed the change you wanted to make? Pull tells me it's up to date.—@robinberjon
Saturday at 05:55am
Saturday at 05:58am
Saturday at 06:01am
@ndw mentioned @robinberjon #xmlprague paper. Which reminds me - proceedings are available at http://t.co/9n4d5xzK—@jirkakosek
In a conversation that started on Saturday at 06:08am
Surprised by @ndw mentioning me in his and @robinberjon's #xmlprague talk. JS XProc for the curious: http://t.co/IFVceAme—@vojtechtoman
@vojtechtoman #xmlprague without your #balisage talk, Saxon-CE would probably not have happened.—@michaelhkay
Saturday at 06:14am
Saturday at 06:21am
Saturday at 06:33am
In a conversation that started on Saturday at 06:51am
It's probably time to disclose who has sent me non-well-formed paper :-) #xmlprague—@jirkakosek
@jirkakosek name and shame them (hoping its not me!)—@adamretter
@jirkakosek How many non-WF papers did you get? Are there anonymised stats?—@robinberjon
@robinberjon IIRC non-WF paper was just one. But valid DocBook was only half of them. Fortunatelly
DocBook XSL are very forgiving #xmlprague—@jirkakosek
@robinberjon Stop making jokes about DocBook or you will be DEAD MAN. I and @ndw are watching you! #xmlprague—@jirkakosek
@innovimax I can't stop producing proceedings from DocBook, pals. But then there will be no
proceedings at all #xmlprague—@jirkakosek
In a conversation that started on Saturday at 06:53am
nice! so wish I was there! RT @thomas0007 Photos from XML Prague 2012, day one at http://t.co/xtCLI8jf #xmlprague—@peteaven
In a conversation that started on Saturday at 08:47am
Saturday at 08:51am
.@vojtechtoman doing a great job exploring the structure of XProc pipelines with respect to non-XML
data.—@ndw
Saturday at 08:54am
.@vojtechtoman doing a great job exploring the structure of XProc pipelines with respect to non-XML
data. #xmlprague—@ndw
In a conversation that started on Saturday at 08:57am
Wonder if non-XML XProc extracts out other metadata from e.g. images @vojtechtoman? #xmlprague—@JeniT
@JeniT The WG discussed extending @vojtechtoman’s media type “side car” with a map that could contain other extracted metadata #xmlprague—@ndw
In a conversation that started on Saturday at 09:09am
How could I forget to include a design for JSProc in the paper? If only for @ndw… #xmlprague—@robinberjon
@robinberjon So is your basic approach to take all the good ideas from XML technologies and try
to make Javascript equivalents? #xmlprague—@JeniT
@JeniT Not necessarily Javascript — but to find a way to bring them into the ecosystem.
#xmlprague—@robinberjon
In a conversation that started on Saturday at 09:12am
I can't decide if I think @vojtechtoman's ideas are fantastic or just make me think of emacs. #xmlprague—@CorbasLtd
In a conversation that started on Saturday at 09:20am
@michaelhkay #xmlprague I like the fast streaming of cocoon. Also dislike the xproc syntax. Cocoon makes
xslt into a functional language.—@nverwer
In a conversation that started on Saturday at 09:32am
In a conversation that started on Saturday at 09:35am
@ndw Ouch, man, why?—@robinberjon
Saturday at 09:37am
@ndw - does "compact" non-XML look like RELAX-NG compact syntax?—@jonathan_robie
Saturday at 09:37am
Saturday at 09:50am
In a conversation that started on Saturday at 11:13am
I'm sitting behind @JeniT now, so I can't tell when she's laughing #xmlprague any more—@jonathan_robie
@jonathan_robie Should I ask video guy to stream @JeniT image instead of @ndw so you can watch her? #xmlprague—@jirkakosek
Saturday at 11:16am
Saturday at 11:18am
In a conversation that started on Saturday at 11:21am
In a conversation that started on Saturday at 11:47am
@ndw Agreed — hence my question on making it better adapted to that environment :)—@robinberjon
@robinberjon Because that environment is incapable of adapting?—@ndw
@ndw It can — I'm just pointing out the lowest energy approach that will yield the same
result :)—@robinberjon
@ndw why do people complain about lack of browser support instead of forking and implementing?—@eedeebee
RT @ndw It would be lovely if #XForms was widely supported in the browser. #godeclarative // I'd settle for android /iphone #xmlprague—@tingenek
Saturday at 02:57pm
In a conversation that started on Sunday at 01:09am
Sunday at 05:02am
Sunday at 05:56am
Sunday at 05:57am
In a conversation that started on Sunday at 06:07am
Sunday at 06:09am
I like @adamretter's XQuery annotations for REST. But it kind of weakens my argument vs @ndw for multi-tier REST apps {sigh} #xmlprague—@ronhitchens
In a conversation that started on Sunday at 08:44am
Sunday at 09:00am
In a conversation that started on Sunday at 10:22am
FYI: the plan is to create a W3C CG for XML5 with a less loaden name. @robinberjon suggested XML-ER. #xmlprague—@annevk
@sgmlguru Too loaded, gives the impression that it's the next version of XML. It would be too
political. @annevk—@robinberjon
@ndw @annevk @jenit @innovimax I checked, 5 individuals can support a group, no need for companies. Go click on
http://t.co/ThBRK1tX—@robinberjon
@robinberjon Count me in, I can get one member vote for er...XML group /cc @ndw @annevk @jenit @innovimax—@jirkakosek
@annevk You somewhere around man?—@robinberjon
@robinberjon occupied until after dinner. Could do drinks tonight.—@annevk
In a conversation that started on Sunday at 10:33am
Even logged in, I can’t for the life of me see how to “show support” for a group /cc
@w3c @robinberjon—@ndw
@roessler @ndw error recovery proposal does not show for me (yes, I logged in 1st <grin/>)—@jeffsonstein
@roessler Yeah. Well. If only there was a button. All I see is the current supporters and “Report
a problem” /cc @jirkakosek @robinberjon—@ndw
@robinberjon There was only one the first time I looked. I think it’s some sort of authentication
problem.—@ndw
@ndw @roessler Note that it says "You are one of the 5 people who support this group. Once 5 people
support the group it will be created" :)—@robinberjon
@ndw What do you see at http://t.co/ThBRK1tX ? No "Yes, create community group" button? @w3c—@robinberjon
@ndw Click "YES, create community group". I aggree it's UX fail sort of—@jirkakosek