Last week (3-6 August 2010), we attended Balisage in beautiful Montréal, Quebec. Mad props to Tommie Usdin, Michael Sperberg-McQueen, and all the organizers and instigators of the conference.
We were able to present a paper, and also had the opportunity to do a followup in a “nocturne,” the Balisage informal evening meeting format. It all seemed to go really well, which was an enormous relief, of course. Once the paper’s posted, we’ll link to it from here. If you’re interested in (or excited about!) XML, you really should check out Balisage and its Balisage Series on Markup Technologies … oh, and get yourself to Montréal next August!
A number of questions arose in the course of presentation, question and answer, followup, and in private discussions. I’m going to treat each of those in a sort of mini-series of posts, here, so I thought that I would set out a bit of a list, here, to let folks know what to expect.
- Why doesn’t it have a better name?
- Why should I implement now?
- Has the opportunity for an in-memory API other than the DOM already passed?
- Why not use an existing in-memory tree model API, then?
- What’s the advantage to using gXML?
- What is this “bridge” or “handle/body” pattern and why should I care?
- What can it do right now, today?
- Can it really grow to do all the things the developers say it could do?
- Give me some numbers!
- Why isn’t there a better web site, source code repository, and all the other infrastructure?
That looks like a pretty adequate start, no?
