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.
You might be wondering whether the node-set() function will be part of [XSLT 2.0 and XPath 2.0]. The answer is no, but don't worry. The authors of XSLT 2.0 made an important decision: result tree fragments are gone. There will be no need to use the node-set() function in XSLT 2.0 as you can operate directly on XML fragments stored in a variable, as on any other node-set. Regardless, you should put the node-set() function in your bag of tools as it will take several years before XSLT 2.0 will be deployed as widely as XSLT 1.0 is deployed today.
Subject: Re: Sam Ruby: Anatomy of a Well Formed Log EntryS From: Aaron Straup Cope To: Kellan Date: 17 Jun 2003 08:41:53 -0400 <snip> > Just in care you were, you know, wondering what a weblog was :) </snip> It frankly baffles me (actually what really baffles me is why they removed the Emacs key-bindings from Evolution 1.4 but that's another story.) What precisely drives this ever-faster flow of tripe about weblogs being "revolutionary"? I'm sorry but I just can't talk about weblogs the same way I might about, say, the wheel or, more recently, electricity. About the only comparison you can make between wheels and weblogs is that there isn't much you can say about them, when you get down to the brass tacks, and that is precisely what's so special about them. Wheels are round and that's their killer-app, so to speak. We've gussied them up with things inside them, we've gussied them up with things around them; but nothing has changed their fundamental nature: they're round and they travel well. End of story.
I have no idea what that last sentence is supposed to mean in the context of the one that came before it unless it's just the Times slagging MSNBC. I include it only for the sake of thoroughness.Even as American officials were preparing to install an interim government in Iraq, the hoisting of the American flag over the statue's face was a brief but powerful reminder that unlike the Soviet empire, Iraq's regime did not implode from within. A closer historical analogy could have been the photograph of a Red Army soldier raising the Soviet flag over a bombed-out Reichstag in 1945.
That iconic picture by the Russian photographer Yevgeny Khaldei was carefully planned and posed. In Baghdad, the Stars and Stripes were hurriedly pulled down and replaced with a pre-gulf-war Iraqi flag, tucked into a chain around the statue's neck like a large dinner napkin. As one commentator on MSNBC said, "It looks like cooler geopolitical heads have prevailed."
An inscrutable person.
ex. What's up with the shie? I don't get him.see also : shie dict-ified
umask perl
just to see what came back. And that got me thinking that I
might pay money if there were a framework and an API such
that I could build some sort of interactive
man
widget to query the Safari servers. Something along the
lines of...
$> safari perl umask Your query returned [2] options: [1] Programming Perl, yadda yadda yadda [2] Perl in a Nutshell, yadda yadda yadda Please choose one: 1 [ and so on and so on... ]...which presumably have support for open-ended queries like this .
<cache>
element, which was added to facilitate the parsing of
remote nodes. So, until I decide to bite the bullet it's a
beta. The changes are as follows :
* Added optional 'cache' element to xref element * Added optional 'content-type' attribute to xref element * Added optional 'xi:encoding' attribute to xref element * Added required 'created' attribute to node element * Added required 'modified' attribute to node element * Removed timestamp element from rev elementNote that the Perl widget is an alpha, warts and all, release. Feedback is welcomed and encouraged. I'll try and merge the old site with the new in the next few days.
To write or design something in a way that is generic or to change something to become generic--especially software.
ex. We should try to genericise this bit of the software.
Forlorn \For*lorn"\, n. 1. A lost, forsaken, or solitary person. Forced to live in Scotland a forlorn. --Shak. 2. A forlorn hope; a vanguard. [Obs.] Our forlorn of horse marched within a mile of the enemy. --Oliver Cromvell. web1913
forlorn adj 1: pitiable in circumstances especially through abandonment; "desolate and despairing"; "left forlorn" [syn: {desolate}, {godforsaken}, {lorn}] 2: marked by or showing hopelessness; "the last forlorn attempt"; "a forlorn cause" wn
I'll see you there.
I'm sure there is a graduate student working hard to
explain why we do these things but I'm also pretty sure
that anything they say will read like a Mark Dery book so
we'll just ignore that part of it for now. But it did get
me thinking about using a weblogging system as an email
application, rather than just using the latter to transit
the former. That is each message is
intercepted
by a filtering agent and "posted" to a private weblog (if
you're into hacking sendmail or postfix or whatever, I
think you're insane but that's your business.) The most
immediate win is that your email can suddenly take
advantage of the work that's been done on assigning
multiple categories in the blog world. Suddenly you never
have wonder whether it makes more sense whether to file an
email by topic/project or by sender. I'm told that much of
this has already been done, largely by individuals for
personal use. One person has widgets to automatically post
certain emails to the web using the Message-Id as permalink
/ primary key. Which got me thinking about
types
again. Specifically, if you wanted to have multiple
routing/archiving destinations -- the public web, the
private web for group "foo", etc. -- could you use an
existing category framework or would a "route" have to be
it's own type? Of course, the next logical step would be to
render and then read your email as
VRML
....
Celerity \Ce*ler"i*ty\, n. [L. celeritas, from celer swiftm speedy: sf. F. c['e]l['e]rit['e].] Rapidity of motion; quickness; swiftness. Time, with all its celerity, moves slowly to him whose whole employment is to watch its flight. --Johnson. web1913
celerity n : a rate that is rapid [syn: {quickness}, {rapidity}] wn
Someone who retires without first sorting out a life for herelf thereafter. Result--retirement zombies wander the streets aimlessly, usually accosting former colleagues and boring them to death with chat about "the old days."
ex. Watch, out Chris's coming--he's the worst of this year's crop of retirement zombies.
ex. All the hot Craver chicks are totally aws.
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
