The short-form week of 5–11 Aug 2013
12 Aug 2013; last modified 16 Aug 2013
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.
In a conversation that started on Sunday at 03:14pm
WTF is "Newark Penn Station"?—@ndw
@ndw Newark, NJ. It's a stop or two from NY Penn Station.—@andersoncliffb
@ndw there used to be a pennsylvania railroad. so, many of the stations along that line
are called penn station (new york penn, newark...—@smyles
Monday at 09:48am
Monday at 11:54am
Monday at 02:54pm
There's no such thing as coincidence; there's only insufficiently advanced skepticism.—@kendall
In a conversation that started on Monday at 03:42pm
I’m sure @sgmlguru will be pleased that I just pushed an update to #XMLCalabash that supports a cx:wait-for-update step. #Balisage—@ndw
@ndw @sgmlguru #xmlcalabash finally makes sense- i have been saying calabash out loud for like three months and
wondering—@drabshadow
In a conversation that started on Monday at 09:22pm
In a conversation that started on Tuesday at 10:21am
In @docum3nt’s honor, I have registered http://t.co/YogfnpXOoEE. Submissions welcome. #Balisage #DocBook—@ndw
In a conversation that started on Tuesday at 02:13pm
Trick of representing complex data structures as seqs of functions interesting, even
if you don't buy into sticking to pure XPath. #balisage—@mathling
@jonathan_robie @mathling And how would you do that in Schematron or another language that leverages only XPath?—@ndw
@ndw @mathling i mostly see two cases: systems or languages that won't do more than xpath 1.0, and
those that can do xquery #balisage—@jonathan_robie
@jonathan_robie @mathling That's silly. XProc uses XPath (will use XPath 2/3) but will never support XQuery
as an expression language.—@ndw
@ndw @mathling do you need more than xpath 3.0 but seriously less than xquery? once you add element
construction and functions, you're close—@jonathan_robie
@ndw @jonathan_robie @mathling What’s in XQuery 3 minus XPath 3 which warrants your “never”?—@ebruchez
@ebruchez i do not understand the question. i want xpath to remain a subset of xquery, and
significantly simpler than xquery @ndw @mathling—@jonathan_robie
@jonathan_robie @ndw @mathling How much simpler is XPath 3 than XQuery 3? Feature delta is small.—@ebruchez
@ebruchez if people want to add element construction and libraries to xpath, you basically
have xquery - so just use xquery @ndw @mathling—@jonathan_robie
@jonathan_robie @ndw @mathling Right, so what XQuery adds over XPath is small. In which case, why would XQuery be
out but XPath in?—@ebruchez
@jonathan_robie @ndw @mathling I use more and more Scala for XML processing. I would want more, not less, from XPath/XQuery.
#background—@ebruchez
@jonathan_robie @ndw @mathling Background: I would like XPath 3, but no implementation so I can’t use it.—@ebruchez
@jonathan_robie @ndw @mathling But even if I had XQuery 3, as a language it lags behind other programming languages.
#background—@ebruchez
@ebruchez the biggest problem in xpath 3 adoption is that implementors want something not more
complex than xpath 1.0 @ndw @mathling—@jonathan_robie
@jonathan_robie @ndw @mathling XPath 2 adoption 6 years after rec is abysmal. XPath 3 adoption likely to be way
worse.—@ebruchez
@jonathan_robie @ndw @mathling Biggest problem for XPath 3 adoption is that “nobody” is implementing it (nobody
as open source).—@ebruchez
@ebruchez but i want an xpath 3 profile no more complex than xpath 1 to encourage browser vendors
and others to implement @ndw @mathling—@jonathan_robie
@jonathan_robie @ndw @mathling We already have XPath 1… and Browsers don’t want XML, period.—@ebruchez
@ebruchez for the most part, xpath 3.0 is the common subset of xquery / xslt. good to have
even if not widely used elsewhere @ndw @mathling—@jonathan_robie
In a conversation that started on Tuesday at 02:32pm
Spending too much time lately marveling at how bad tools for connecting humans to
code and data remain after decades of work. #balisage—@simonstl
@simonstl Very enjoyable talk, but I was left with no idea of any, single practical change
proposed.—@ndw
@ndw actually, one other thought. Does XProc support steps that require a pause for human
input? I think it's possible as extension....—@simonstl
@sgmlguru @ndw wonderful! I'll to take a look. Always best when practical steps have already happened...—@simonstl
@simonstl @sgmlguru Docs: http://t.co/xNa8EbJrvQ (And this is just my experiment, suggestions welcome)—@ndw
In a conversation that started on Tuesday at 03:16pm
@georgebina Not this year, we’re hosting the pizza social this evening instead this time.—@ndw
Tuesday at 03:39pm
Tuesday at 06:28pm
God's plan - 1) Make humans after getting bored with Dinosaurs; 2) Drown most humans;
3) Kill myself (as my son); 4) Hide.—@Woodlandbookshp
Tuesday at 06:42pm
“Why is iTunes using 79% of my CPU?” “Because you’ve got it open?”—@liza
Tuesday at 08:54pm
Nothing fixes stupid but death.—@kendall
In a conversation that started on Tuesday at 09:47pm
Werewolf again. Victorious again. Dead in the first round evermore, I fear.—@ndw
Wednesday at 07:12am
In a conversation that started on Wednesday at 08:57am
In a conversation that started on Wednesday at 08:57am
If it’s any consolation, the XSLT 2.0 stylesheets are a whole lot simpler in this
regard.—@ndw
Wednesday at 09:02am
Evil? Meh.—@ndw
Wednesday at 09:06am
DocBook V5.x has autoplay and other HTML5 control attributes on audiodata, FWIW—@ndw
Wednesday at 09:17am
Ad hoc “standard” extensions to XHTML5 are…oh, never mind.—@ndw
In a conversation that started on Wednesday at 09:24am
Is it too early to start drinking?—@ndw
In a conversation that started on Wednesday at 09:55am
Dream of the day when the XML core community gets over this strange lingering thought
that HTML is dirty inferior stuff. #balisage—@simonstl
Wednesday at 12:40pm
In a conversation that started on Wednesday at 06:53pm
#balisage people are: A. eating, B. their brains are full, or C. having a <beer/> (or all three).
It is lonely on twitter now. SO lonely.—@alexmilowski
@alexmilowski so... best balisage topic so far?—@adamretter
Thursday at 08:29am
Curly quotes in code listings on slides is one of the reasons I could never use PowerPoint
or its ilk for presentations.—@ndw
In a conversation that started on Thursday at 01:23pm
In a conversation that started on Thursday at 02:29pm
In a conversation that started on Thursday at 04:31pm
Used to use RDF (in my weblog), now just use XML. Now wondering if I should try using
RDF again. #Balisage—@ndw
@ndw Use #RDFa instead. I think you'll find it easier to mix together with your existing #XML—@alexmilowski
@ndw what has changed for you?—@david_megginson
@david_megginson Interesting support for triples in MarkLogic server. :-)—@ndw
@ndw I'd stick with the XML. You can say it the way you want to, and RDF (or TM, etc.)
is only an XSLT transform away.—@RichardOfSussex
In a conversation that started on Thursday at 07:26pm
Thursday at 09:06pm
Friday at 07:24am
Friday at 11:18am
@daldei I added a css-formatter step to #XMLCalabash that can use either Antenna House or PrinceXML for print formatting.—@ndw
In a conversation that started on Sunday at 03:08pm
Favorite bit of #balisage: I suggested a change to XProc to @ndw, and he'd already done it: http://t.co/K30506kfXG per @sgmlguru suggestion—@simonstl
Tuesday at 08:51am
RT @Elka72: Gotta love the Dutch. Amsterdam marks Putin's visit by flying gay pride flags on
all city council buildings: http://t.co/lZcAHZ…—@ndw