Older blog entries for connolly (starting at number 27)

29 Jun 2005 (updated 8 Jul 2005 at 04:08 UTC) »

The --xml-output option on darcs commands is something I hope hg picks up; let's not do much more microparsing than we have to.

OpenID looks kinda cool, but I don't quite see how it works; I hope they add a story/example showing what happens if a black hat puts my homepage URL in the field.

Some CVS (related) features I depend on that I wonder if/when hg has: emacs support (ctrl-x-v-v is burned into my medulla), keywords support.

Hmm... PHP is clearly the dominant server-side deployment vehicle these days. I wonder if its namespace management will catch up with Modula-3 and python... or if the .NET/mono CLR stuff has much chance; IronPython and the like look promising. I suppose JSP hosting is a commodity these days... and .Net... I wonder what the prices and trends are; and I wonder if there's mono hosting yet.

Hmm... a bunch more certs... ugh... they're all spam. How do I certify somebody as pest or fraud or leech?

Tags: scm

Using hCard, XSLT, and RDF to sync the family cellphones

Mary got a new Motorola V188, which iSync supports. Buoyed by the success of moving the kitchen calendar from paper to iCal, I took her paper address book and keyed it into Apple's addressbook. Now I want to sync (or at least copy) several of the categories (family, medical) from the contacts in my gizmo to hers.

In palmagent, dangerSync.py produces contact.rdf; I could use N3 rules to convert that to a vCard RDF vocabulary, and then do a syntactic RDF to vCard syntactic transform, but I'm a little down on N3 rules lately; the rules I use to process my calendar are really slow. I have been thinking about having dangerSync.py spit out .ics format directly. Or maybe having it spit out RDF diffs is the way to go...

Meanwhile, there's hCard, whence comes X2V including xhtml2vcard.xsl. And I'm a big fan of using XHTML to archive important data anyway, so I think I'll write some XSLT to convert contact.rdf to XHTML and then use xhtml2vcard.xsl to get vcard syntax.

grumble... advogato diary entries don't have titles, do they?

Tags: hCard, WearableGizmo, palmagent, RDF diff/sync, DIG

I'm no longer happy with my personal wiki; since upgrading to a version of zwiki that supports dated comments, I find that I'm more comfortable doing "episodic publishing" (i.e. blogging) than collaborating on collected wisdom. A personal wiki is an oxymoron; the wiki genre is all about collaboration.

So I started thinking about how to migrate my content to a blogging system. The first step was to somehow grok all the data I've got in there. I asked in the #zope channel about .zexp format and was discouraged from peeking inside. I was advised to write an external method that runs inside Zope to export my data, but by the time I saw that advice, I already had dumpwiki.xsl converting the zope XML export format to XHTML. The actual contents of the wiki pages was quoted, so I'm undoing that with python and xmltramp. I think I hit a bug in the xmltramp serializer. Gotta look into that.

Anyway... the #zope guys were surprised that I had never done any Zope methods. I explained that I use Zope because it's the only server you can apt-get and write to (with iPhoto or emacs eldav mode) out of the box, with elephant-never-forgets versioning.

That got me thinking... with the "cvs is good enough" orthodoxy eroding, and all the work on subversion and arch and darcs, maybe it's time to take another look at the versioning part of WebDAV. Especially git, with its cryptographically secure history... because the problem with the writeable web is more social than technical. People use sftp rather than HTTP because the social protocol is well known, not because FTP is a better protocol than HTTP for writing.

Hmm... if I had a PAW blog or a DIG blog, this might belong there. Maybe reltag will work...

I sure wish python had more penetration in the blogging world. PHP is clearly the server-side deployment vehicle these days, and javascript is the way to juice up clients, but neither PHP nor javascript meets the unambiguity requirement that I think is critical for software engineering in the large.

Got tired of the manual login-and-download-statement ritual with my bank, and since ClientForm and ClientCookie are such a joy and python has SSL built-in, I cooked up grabst.py that automates it. Heaven forbid the bank website should allow me to just bookmark my statement so I could directly GET (with SSL and password auth) it, without all the frames and javascript malarky.

Glom reports looks interesting... using XSLT and CSS for reports... GTK... python API... postgress; that reminds me that In quacken I have code to transfer all my Quicken data (about 10 years worth) to postgress in one go for use with an old version of saCASH. saCASH development has since gone in a direction that I'm not so interested in, but this glom thing looks like a good match for my FractalAccounting goals.
Grokking Triples from Spreadsheets

Sean notes that there are lots of triples in spreadsheets. Yup. After my Aug 2003 trip to Montreal for Extreme, I used gnumeric as an RDF authoring tool to collect all the gas receipts and such; then the Makefile has this stanza to convert it to RDF:

triplog.rdf: triplog.xml grokSheet.xsl
	$(XSLTPROC) --novalid grokSheet.xsl triplog.xml >$@

I haven't scrubbed the data, so this is somewhat incomplete as a demo.

Yes, this is another GRDDL style transformation.

A comment on Sean's blog said "don't forget RDBs". Of course not. See Relational Databases and the Semantic Web; I hope to update my implementation, dbview.py to use SPARQL before too much longer.

Hmm... where are timbl's slides on RDF, trees, tables, and such?

WordPress Struggles

Famous 5-Minute Install "2. Create a database for WordPress on your web server, as well as a MySQL username to access it." Umm... that step alone is taking me a lot longer than five minutes. The debian package doesn't seem to get along with Dom's installation:

Installing new version of config file /etc/wordpress/index.php ...
ERROR 1007 at line 1: Can't create database 'wordpress'. Database exists

IntegrityIsJobOne does gnome blog know this? they advertise... "Entries can be written gradually over the course of a day, popping gnome blog open and closed as you have thoughts to jot down and then posting at the end of the day"

What if my computer crashes in the middle of the day?

19 Feb 2005 (updated 19 Feb 2005 at 03:31 UTC) »
testing gnome blog

My son is supposed to keep a reading response journal. I wonder about having him do it with a blog... maybe using livejournal's friends-only authentication stuff... or better: is there an easy-to-administer blog thingy for zope?

I keep bugging TimBL and EricM about blogging (esp with trackback and comments) too.

This posting got kinda mangled; the title got thrown away.

Hmm... hypertext UI? my home page hmm... klunky dialog interface, but the resulting text is OK.

Suppose I drag n drop from my web browser? Ugh. lose. Where's paste link when we need it? Hmm... recoverable... gnome blog

19 Feb 2005 (updated 8 Mar 2005 at 18:51 UTC) »
taking the plunge to Ubuntu Hoary

For those of you who have missed the daily churn of new packages, Hoary is for you.

-- GuideToHoary

They've got me pegged. I've been scratching the itch with some 3rd party repositories and having trouble. If Hoary is just two months from release, I'm sure it'll work well enough for the kids' PC.

OS X keychain trustworthy?

Every time I log in with SSH Agent, that little "add to keychain" checkbox is staring at me, but I don't know if keychain source is open to the security community, and I don't understand its architecture. Any reading recommendations? Maybe drop them in the del.icio.us keychain tag.

postscript: yes, it's trustworthy. under the hood of the OS X keychain -- 19 Feb 2005. Love having a separate keychain for financial stuff. Camino groks, but Firefox doesn't. But Camino doesn't grok type-ahead-find... BrowserChecklist

18 older entries...

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!