Das eez kaput! Sometime around 2002 I spaced the entire database table that mapped individual entries to categories. Such is life. What follows is a random sampling of entries that were associated with the category. Over time, the entries will be updated and then it will be even more confusing. Wander around, though, it's still a fun way to find stuff.
There's actually some good, even if ironic, news about data typing support in XSLT 2.0: if you're still using DTDs, and you're putting off a move to any schema format, you can use XSLT 2.0 stylesheets to add datatype checking to your system, further postponing a move to schemas.
From: Aaron Straup Cope
To: boris
Subject: Re: Hrm.. Echo?
Date: 27 Jun 2003 08:08:02 -0400
Yeah, I've heard of echo. I wish them luck, but I honestly don't think
it will fly. For a few reasons:
In among all the talk of a common syndication format is talk of a common
API and that's *never* going to happen. I spent a little bit of time
thrashing around with this on the weblog-devel list and it became clear
that given the difficulties in identifying just the parts of a post
(body; title, body; title,link,body; excerpt,body; etc.) we weren't ever
going to get very far.
Two points here: 1) that we were even able to agree on the idea of
"post" speaks volumes about the influence that RSS has had on things 2)
that we didn't succeed in creating a Grand Unifying Theory of Weblog is
okay and probably a Good Thing.
I've said this a few times in the last couple days, spewing almost
nothing but pure bile yesterday [1], these are technical problems.
Everybody wants some magic seamless import/export functionality (or at
least the idea of it; I have yet to understand what people are going to
*do* with it when they get it,) The impression I get is that they think
some kind of dorky, the network is my pal, group hug is the way to deal
with it. It is not.
It is not, because anything that gets developed will, in short order, be
RSS-ed. That is, no one is going to wait around to achieve consensus on
whether or not their patches to the spec are approved. Not users and
certainly not developers. Let me pause for a moment and say, lest you
think I have turned in to some kind of irate laissez faire crank that I
am all for consensus where applicable. XML is a good place for
standardization; weblogs and the various bits associated with them are
not. A weblog has always been, whatever anyone wanted to be (just do a
Google search on "Ben Brown 3000 words") and, by extension so, is its
static representation and its I/O "methods" (API, if any.)
Any standardization there is today is simply the result of convention
which is fine, but don't confuse it for the "stoneness of the stone" so
to speak.
People are trying to pin it down (again) because they think there's big
money somewhere in here, atleast in the short term. What they are really
trying to do is pin down RSS (which was pinned down a long time ago) and
formalize the weblog as its vehicle. They can probably do the first, but
people will continue to do whatever they want on their weblogs. That is
the Idea of Weblog.
RSS is not a weblog archive format, despite what other people may say.
It never was; it has always just been an XML representation of the
intersection of many different weblogs (what is the role of the
<link>
element, anyone?) and it sure looks like people got blinded by the
light. Weblog authors and tool-maker have too many divergent needs and
interests to ever follow one another's lead. Never mind the social
engineering.
It's not rocket science. All people need is for tool-makers to provide a
static XML dump of their content. The semantics don't really matter;
docs would help but it's not the end of the world. Any kind of
interchange of content is going to require human intervention. I sense
that people want to believe this isn't true but, well, they're wrong.
We're not crunching numbers here. It's human thought, with all its
subtleties and contradictions, and computers suck when it comes to
grokking stuff like that.
We're going to have to keep have holding their little binary hands for a
long time to come. We're going to have to keep on actively maintaining
lists, mental or otherwise, that say
aaron:2 + boris:2 = boris:5
.
Which sucks, perhaps, but people had better get used to it. That's life.
That's the bad news. The good news is that these days we have tools and
frameworks (repeat after me: weblogs are not a framework) that make the
actual drudgery easier.
---
[1] http://aaronland.info/weblog/archive/5100
You could tip the non dairy whitener over flames to make pretty green fireballs - this was obviously not great if you were trying to conceal your position but then you wouldn't be lighting a fire anyway.
You don't need to tell me who "to raise a glass to", you fucking idiot -- I raise six glasses every night, just to get drunk enough to love this country like I did as a kid: without feeling like it's using me .
Dork. For those of you not keeping score Paul Martin is, for all intents and purposes, the next Prime Minister of Canada in waiting. (It remains to be seen whether Ti Jean (that's Prime Minister Poutine for all you Americans out there) manages to shit-can his nemesis' run for the leadership of the Liberal Party (read:Ontario) between now and his supposed departure from politics.) Mr. Martin is perhaps best known for butchering federal spending on health care transfers to the provinces. He is less well-known for also slashing proposed federal funding for bringing high speed Internet access to rural Canada; a program that would have said so much more than a spattering of pithy comments from the campaign trail. So you've got a weblog, Paul. Big fucking deal: talk minus action equals zero. via montreal cityAfter all, it's not like I can pretend to be the kind of guy that spends a lot of time surfing the web. To be honest, until a few weeks ago, I didn't even know what the hell a blog was - I joked that I thought it was something that might climb out of a swamp.
Apparently, this is a Windows-only thing which doesn't really make a whole lot of sense but I haven't had a chance to look at the source yet. via a frog in the valleyis a complete small-to-medium-size site development kit created in XSLT ... utilizing XTM for structure, binding and other cleverness.
I guess it's time to start working on version 0.3 of Image::Shoehorn::Gallery ... via more like thisThis experimental metadata extractor will retrieve a document ... and look for embedded metadata stored using the Adobe XMP embedding conventions.
is an attempt to write an Open Source Apache module which implements asynchronous publish and subscribe messaging.
numinous adj 1: evincing the presence of a deity; "a numinous wood"; "the most numinous moment in the Mass 2: of or relating to or characteristic of a numen wn
Similar to "indeed" but used in a posh accent. Pronounced in-dig-narta.
ex. "Have you had enough caviar, Giles?" "Indignate, I have, Samuel."
Mellifluous \Mel*lif"lu*ous\, a. [L. mellifluus; mel, mellis, honey (akin to Gr. ?, Goth. milip) + fluere to flow. See {Mildew}, {Fluent}, and cf. {Marmalade}.] Flowing as with honey; smooth; flowing sweetly or smoothly; as, a mellifluous voice. -- {Mel*lif"lu*ous*ly}, adv. web1913
mellifluous adj : pleasing to the ear; "the dulcet tones of the cello" [syn: {dulcet}, {honeyed}, {mellisonant}, {sweet}] wn
When you walk up to a cute nose and squeeze it, you say staboogie.
ex. Hey, come here and let me staboogie your nose!
I never found the source, but apparently 80% of the budget that the
federal government allocates for Canada Day celebrations goes to
Quebec. This on a weekend where upwards of 80,000 families in Montreal
alone are moving apartments. This from a Minister of Heritage who blew
50 million bucks to give every Canadian a flag and who went to the
States and held up
The Rant
as a shining example of Canadian culture. So, if your country is in
need of a Minister of Patriotism, we'd be happy to sell you Sheila
Copps.dude, where's my car
This document uses CSS kung-fu and a small amount of JavaScript for rendering its contents. Efforts have been made to separate the form from the content so if you are viewing this in a text-based browser it shouldn't be an issue.
On the other hand it may look funny if you are viewing it in a browser with incomplete CSS and/or JavaScript implementations. Internet Explorer 6 comes to mind.
It's not that I don't love you. However, my time is limited and I no longer feel very good about spending it working around any one browser's inconsistencies with little, or no, confidence that they will ever be fixed or otherwise made more inconsistent at some later date.
On the other hand, if something is down-right unreadable please let me know and I will endeavour to fix it.
yes, we have no bananas
This page may not validate. It's not that I don't care, it's just that I'm not aware of it yet. Part of the reason that I rewrote the entire back-end for managing this site is that the old stuff made it too easy for these kinds of mistakes to slip through the cracks.
See also : W3C::LogValidator.pm
it's the software, stupid