I’m thoroughly pleased to have my paper accepted for the Balisage 2024 conference. I will be talking about age-old messaging standards and the absolute pain of implementing those for the 21st century when all they were doing was to shut down a mainframe computer.
The Balisage 2023 markup conference is over. I presented, and I think my paper was well received. There was a good discussion afterwards, in any case, and I certainly enjoyed it.
There were a good number of great talks, too. For whatever reason, my favourite as I write this is Amanda Galtman’s clear overview of accumulators in XSLT 3.0 and all the things you can do with them, not to mention how you can test them. Before the conference, there’s no way I could have predicted this; there was any number of other talks I imagined would have taken that spot.
What struck me the most, though, was the feedback session afterwards. We all agreed it was a great conference. We all lamented the demise of the physical meetup in Rockville, and we all discussed ways to mitigate the fact that we are now meeting online only. There was, in fact, a push for meeting more than once a year. Maybe shorter talks without a peer review? A Slack channel at xml.com leading to those, or maybe some more impromptu meetings? A hybrid conference was mentioned, and people reminisced on the past and briefly wondered about what the logistics of a hybrid conference might look like. Brief thought was given to specifics, including where and how to ask questions, but there was no consensus or will to say “yes, let’s meet in person again.” Which is fair enough, in a way. Getting to Rockville was never an easy task.
Only afterwards did it occur to me that no space was given to thinking about how we might want to bring in new blood. Young people. Fresh minds still thinking clearly, with strong views unaffected by decades of compromise. We are all getting older, and this was not a discussion about anyone below 50. I am by no means an SGML old-timer, I but was there using it before there was XML, which means I am actually getting old, too.
I am in a position now where I can bring in young people to work with markup, so that’s what I try to do. It makes perfect sense; younger people will have more ambition, more will to achieve things, and if I can guide them in a certain direction, then I will.
See, when you get older, you will no longer be the bright new talent and that will feel very much like a loss, but you can possibly, maybe, be that experienced old hand and be able to guide the younger ones, influence them in one direction or another.
What does that mean?
Well, for one thing, you can demonstrate the value of semantic markup and declarative languages. You can highlight the benefits of XML technologies and get them interested, inspire them to use those technologies to solve a problem. And then, when they succeed or at least get interested enough, you can point them at markup conferences. You can encourage them to present, talk about a project that went well or an idea they had to make a difference.
And that was never even mentioned at the feedback talk, and now I find it remarkable.
Balisage 2022 is over, and I had a great time.
I’ve said it before (I think) but the real power of Balisage is that it invigorates me because it reminds me of what I love about my chosen field.
Most years, following the closing of the conference I go back to work, straight away. Yup. Could be a particularly tricky problem, or maybe an alternative to something I have been pondering, but most years it’s just been sheer inspiration. I like what I do, and I like talking to, and listening to, people in my field. They provide inspiration, and they make me want to do more.
It’s a wonderful thing when a conference can remind me of all this, and it’s what Balisage does.
As I write this, Balisage 2021 is four days away and my presentation less than a week away.
I am writing this instead of the presentation.
My paper is about this recent SGML project of mine. It’s a war story, really, and, to a large degree, a rant. It’s about all the reasons to why SGML is no longer a viable solution and why everyone should do XML instead, and I’m procrastinating endlessly about the presentation, to the extent it feels like being back at the uni, studying for an exam, and how I found the time to (finally) do the dishes and reorganise the bookshelf.
I know what I want to be in it, but the contents differ from the paper that was approved, so I’m a bit hesitant. Not that I don’t always do this before Balisage, I do, but this time feels special and different, and I am wondering where to draw the line. How different from the paper can the presentation be, really? Where’s the line? Is it just the title? The structure? The fact that I have evolved from the me that submitted the paper, that I now know what I didn’t know then, that my views have changed a bit and I really can’t (and won’t) go back?
Is this (shudder) an existential crisis?
I should probably do the dishes now.
This year’s Balisage conference is over and I miss it. I miss the people and I miss the talks, but above all, I miss the sense of community.
See, this year’s Balisage was all about communities and the softer values of markup. Don’t get me wrong; there were some great talks on markup theory (overlap, anyone?) and how to make JavaScript into something tolerable in a markup context. But above all, there were numerous talks on communities and on what we do and on how we regard our profession.
Steven Pemberton (who held the mic on no less than four occasions) delivered a brilliant talk on the virtues of declarative markup while killing off HTML5, once and for all.
Mary Holstege discussed the metaphors we code by, and how it’s easy to take those metaphors too far. I chose my words very carefully for the rest of the conference.
Bethan Tovey and Norman Walsh invited us all to rediscover our passion for declarative markup with Markup Declaration, a call for arms to unite the community and to find XML and its kin a new home.
Allen Renear discussed the ethics of XML (really!), and I am unable to do that talk justice here. You should have been there.
Abel Braaksma gave us a tour of the declarative (and functional) programming paradigm, and my only complaint is that he should have been allowed at least twice the time to do the topic justice.
And there was yours truly who discussed the virtues of style guides, that perfect complement to schemas and validation.
The list goes on. I can’t possibly mention everyone here, but I could have mentioned at least as many more talks, every one of them every bit as good as those mentioned above.
Balisage, more than anything else, was about the community we inhabit and participate in, and how we all stand a better chance united. It’s not about just SGML or XML, even though both are important; it’s about declarative markup and our chosen field. It’s about all those standards starting with X but also quite a few that do not, and the power offered to us by semantics, and it’s about us all acknowledging each other’s work. And yes, it’s also about JSON and Markdown, and a whole bunch of other things that we may or may not approve of.
So, from one addict to a bunch of other addicts: I miss you.
P.S. You should all look up Developing SGML DTDs. Yes, there was also a book discussion.
Just finished revising my paper for this year’s Balisage conference.
I have to say, I’m really looking forward to the conference now. In the past, I sometimes forced out a paper because that was the only way for me to attend – my employer would pay only if I presented – but this year’s is what I’ve labelled as my “soapbox paper”. It’s all about my opinions. No new ground, no, say, versioning theory or markup, just me being pissed off about the lack of style guides in today’s (XML-based or otherwise) authoring departments. I don’t just offer my opinions, I provide them as the (absolute) truth.
This will be so much fun.
In Rockville, MD, for this year’s Balisage conference. Yesterday, I gave a talk on my current project at LexisNexis, migrating legal commentary in RTF format to XML. The talk seemed to go well, with people laughing in the right places, asking excellent questions, and listening and participating, and I’m just so very pleased at being here again.
Balisage is an institution where markup practitioners gather to listen to each other telling stories and giving talks. It’s a geek holiday, the kind that you look forward to every year. You meet old friends and make new ones, you exchange ideas, you play games, and you talk about pretty much everything. The atmosphere is relaxed and friendly, and everyone is included.
This shows whenever a first-timer presents. You tend to be deathly nervous but that passes because the audience wants you to succeed. I still remember my first time; I’ve never seen so many encouraging smiles in an audience as at Balisage. I knew I couldn’t go wrong.
This doesn’t mean that the follow-up discussion is without edge. Often, the guy who wrote the book on your subject is in the audience, quite literally, and you’d better do your homework well because these guys know what they are talking about.
I love Balisage.
I’m pleased to tell you that my paper was accepted at Balisage. This, as far as I remember, is my sixth consecutive year speaking at Balisage, and my seventh overall paper (yes, I submitted two papers one year because I desperately wanted to be there and my employer would only finance the trip if I was speaking).
My paper? Oh, it’s about a huge migration project I’m currently involved in at LexisNexis. More specifically, it’s about the pain you’ll only recognise if you’ve converted RTF to XML on a large scale.
I’m in Bethesda, MD, just outside of Washington DC, and this year’s Balisage conference starts tomorrow. I’m excited and a bit nervous.
I’ve spent most of today preparing my talk, which is why I’m nervous. It always happens. While planning a paper, I tend to be convinced that it’s the greatest thing ever, or not very far off. While writing it, uneasiness creeps in and while I’m still convinced of the paper’s merits, I am no longer sure I should be the one writing it. I put it off, one day at a time, thinking that I have plenty of time to rediscover the enthusiasm that led me to the subject to begin with and decide I should clean up my computer instead. Or something equally pointless.
This goes on until the last possible moment, that is, a few days before the submission deadline, after which I force myself to write the first draft and submit it, usually minutes before midnight on the final day. A more charitable person might call this “process”, but “terror” is probably closer to the truth.
Completing the second draft, provided that the first is accepted, of course, tends to be similar. If my self-doubt runs sufficiently deep, I will have trouble opening the reviewers’ comments and much more trouble updating the paper itself. Again, a last-minute fix is required and is what usually happens.
Wash, rinse, repeat for the slides.
Which is why I’m writing this instead of finalising the slides.
My paper submission for this year’s Balisage was accepted. I’ll be talking about toys, among other things.