Categories
Writing

Practical RDF Weblog—Back in Action

Recovered from the Wayback Machine.

The Practical RDF book weblog is back in action. I’ll be posting chapters, slowly, starting in the next couple of days. We’re trying to get the book into the publication process by end of the year, which means less weblogging, more book writing, and more coding.

Discipline. Aren’t INTJ’s supposed to be disciplined?

The material has been altered, considerably, from the first draft. I’ve added coverage of additional technologies, refocused the audience a bit, and updated the material to reflect the newest edition of the RDF specification documents. Still, the material is in draft form, which means no editorial polish and the usual Burningbirdisms. In between releases of chapters, I’ll also be covering other RDF-related topics, to add a bit of variety. Keep you all hungry for more.

The release of the chapters will also signify the release of some new goodies I’ve been playing around with for a time. All open source, of course. Many are weblog or web site-related so I hope that they might be of interest.

Categories
Just Shelley

The Letter

Recovered from the Wayback Machine.

I received a rare letter from my Father today. He doesn’t write too many letters now because his hand writing has become increasingly bad over the years. What with the stroke and all the cancers and the radiation overdose I’m glad just to be getting a letter, much less one that’s legible.

Of course, my father’s hand writing never was good. It’s a version of printing I call the Powers Print — a combination of upper and lower case block-like print letters, lightly scrawled as if the writer is too impatient with the slowness of the ink and the inefficiency of the pen and paper. Hasty marks barely touching the page.

Reading my Dad’s letters requires intuition, imagination, and no little detective skill. I usually only attempt the process when I can get my roommate to help me with the deciphering.

“‘I went to the doctor ______.’ Does that look like a Tuesday or Thursday to you?”

“Looks like a Sunday.”

“Can’t be. You don’t go to the doctor on Sunday.”

“You’re right. It’s probably Thursday. I think that’s a ‘ur’ not a ‘ue’.”

“I think you’re right. ‘I went to the doctor Thursday. He said that I need to consider getting a _____’. I have no idea what this word is. Can you recognize it?”

“Hmmm. Rocker? Do you think it says ‘rocker’?”

“Why would a doctor recommend a rocker? Must be something else. ‘I went to the doctor Tuesday. He said I need to consider getting a ‘blank’. He’s concerned I’m going to’, does this look like ‘fall’ to you?”

“I’d say it was fall. If that’s fall, then the previous word could be ‘walker’. That would make sense.”

And on it goes, in an exercise that provides both news and entertainment until just before his usual signoff of ‘Love, Dad’, when he writes with unusual clarity:

“I bet you can’t read half this letter.”

Categories
Legal, Laws, and Regs Weblogging Writing

Licensed to weblog

Recovered from the Wayback Machine.

I’ve added a Creative Commons License to the Burningbird Weblog. You’ll see it at the end of my blogroll.

The generated license code embedded in the page validates as XHTML 1.0 strict as long as you remove the ‘border=”0″‘ attribute from the image.

I’ve licensed myself as Attribution-NoDerivs-NonCommercial 1.0:

Attribution: The licensor permits others to copy, distribute, display, and perform the work. In return, licensees must give the original author credit.

No Derivative Works: The licensor permits others to copy, distribute, display and perform only unaltered copies of the work — not derivative works based on it.

Noncommercial: The licensor permits others to copy, distribute, display, and perform the work. In return, licensees may not use the work for commercial purposes — unless they get the licensor’s permission.

Easy as 1-2-3 — fill in a couple of forms asking simple questions, mail the HTML to yourself, make the modification I recommended, paste it into your weblog template, and baby, you’ve just joined the Commons.

Update: I incorporated the CCL RDF into my PostCon RDF, as demonstrated in the example PostCon RDF file. This is a good fit because the PostCon RDF file is a description about the web resource, and this includes licensing information as well as format, validation, history, and so on. I’ll also add ability to add CCL to the PostCon generation tool, but not using the Common’s form — people will have to know the specific license type ahead of time. At least for the first release of PostCon.

Categories
RDF Writing

Practical RDF Book Cover

Recovered from the Wayback Machine.

Todd Mezzulo from O’Reilly, the person responsible for marketing the Practical RDF book sent me a copy of the cover, which I’ve embedded below. Now, the book isn’t going to be on the streets until Spring, so contain your excitement…a little.

(To be honest, I’m really excited about this book. Really, really.)

The bird pictured is a Secretary Bird, a predator bird originally from South Africa. The Secretary Bird is known for it’s prowess in killing snakes, having the nickname of “serpent eater”.

It grabs the snake with its strong toes and beats it to death on the ground, while protecting itself from bites with its large wings. Finally, it seizes its prey and hurls it into the air several times to stun it.

I found this particularly humorous because my last sole-author book for O’Reilly was Developing ASP Components, featuring none other than a serpent on the cover. I joked with Todd that the choice of critter for the Practical RDF book is especially appropriate because once I made the decision to go with RDF for my next subject, I never looked back at COM+ and ASP. RDF figuratively ‘killed’ ASP for me; I just didn’t pick it up by the tail and throw it around. Much.

But all this isn’t why the cover design folks at O’Reilly picked the Secretary Bird. I think they just liked the long tail.


Cover for Practical RDF book
Hey! Don’t mess with the Burningbird — Serpent Killer!

Categories
Just Shelley Weblogging

Perils of YASD

Recovered from the Wayback Machine.

I’ve had a weblog since 1995, my own domain since ’96. My first domain was yasd.com, based on my company name at the time: YASD, inc. YASD stood for “Yet Another Software Developers”, which I thought was a chi-chi clever take on YACC — Yet Another Compiler Compiler. Trust me, you had to be have there at the time.

What I didn’t know when I signed up for this domain is that YASD is a common term used in electronic gaming, meaning Yet Another Sudden Death or a variation, Yet Another Stupid Dead. As in, “YASD I was eaten by an Ochre Jelly”.

YASD is also related to something Japanese, I have no idea what because I can’t read the web sites. Same with several Iranian sites. A common translation is “Young Adult Services Division”. In fact, if you Google on YASD, you’ll see about a hundred different interpretations for this acronym/word.

This wouldn’t be bad, except, on an average, I get about 20 emails a day related to someone using a ‘@yasd.com’ email address to sign up for software or other services. It’s bad enough getting spam because of spam, but I’m also getting hit because my domain is a popular acronym.

Sigh.

Perhaps I should auction the name off. Anyone want to buy a domain name?