Categories
Critters

TRO For all horse meat plants set to same date

horses

Update on Front Range Equine Rescue et al v. Vilsack et al:

Responding to a filing yesterday, Judge Armijo agreed to set the expiration date for the TRO for Rains Natural Meats to the same date as the other two plants: October 31, 2013. By that time, Judge Armijo will have a decision in the case.

Rains Natural Meats has asked the court to include it in the bond set by Magistrate Judge Scott. In the meantime, the USDA has filed a Supplemental Administrative Record covering Rains. I have issued a FOIA for the associated documents. I am particularly interested in reading the communications related to not needing a wastewater permit from the Missouri DNR.

You can see all of these documents at Docs at Burningbird.

There was also a hearing in the Missouri court case related to Missouri DNR being prohibited from issuing wastewater permits for horse meat plants. I don’t have access to these court documents, but can guess from the docket filings (available on Case Net) that the purpose of the hearing was to expedite a decision on this case, too

Categories
Photography

Your photos are beautiful but…

Recovered from the Wayback Machine.

Thank you for sending your query to ____________ magazine. Your photographs are beautiful! The magazine has not published photo essays in the past, but that may change in the future.

I was thrilled when the managing editor of a magazine, known for the beautiful photography it uses to annotate its stories, wrote the words, Your photographs are beautiful! to me in an email response to a proposal I sent. And though this didn’t lead immediately to a gig, the editor is passing the proposal on to the editor in chief for consideration. It’s from tiny acorns such as these that little oak trees of hope blossom.

First, though, I have to build up my photo library.

I’ve finished putting my photo albums together and I have some regrets that most of the photos, taken with a digital camera, can’t be used in publications because of their low resolution. Some, but not much.

The problem with film photography is that the costs can be prohibitive, especially if you use professional film and development. With the digital camera, there were no costs involved and I felt free to experiment, try new things, explore new territory. By doing this, I was able to find not only the type of photography I enjoy – journalistic photography, not what is known as ‘art’ photography – but also to post examples online and get excellent, brilliant, and spot on feedback from readers, as I wrote about a few days ago.

In the meantime, I’m using my low resolution photos when I send out ideas to publications. However, I am not just sending queries about possible photography assignments; I’m also sending ideas and suggestions for stories, essays, and articles to technical, fictional, travel, nature, and community-based publications. This is in addition to two book ideas I’m putting together – one on technology and one that’s social/political/cultural flavored. I’m fairly sure the technical one will get a nibble, and I have hopes for the other.

If you can’t tell from this flurry of activity, I’ve stopped trying to find a fulltime computing gig. If I can find small jobs, short term contracts or gigs working at home (or abroad, which would be even better), I’ll grab them – but my days as a full time technology architect working for a single company are over. I reached burn out in California, and it shows in the interviews. My resume is too good not to have a job; it’s not the resume or my knowledge or my experience – it’s been me.

Before you all howl “Don’t quit your day job!”, be aware that I’m am looking for employment, but right now, I’m focused on temporary and seasonal work, and whatever I can grab short term. Since I no longer have to worry about bill payments other than my car and health insurance, I can get by on earning smaller amounts of money – I don’t have to go just for the high priced architect jobs.

(Anyone want a damn good technical architect or senior level software developer for a short term assignment, at basement prices? Throw in a few rolls of film, and I’m yours.)

Dorothea wrote today that she doesn’t have a lot of patience with the do-your-dream crowd. I can see her point, you have to be practical. No one is going to take care of you, you have to take care of yourself. But when you’re pushing 50 (49 in a few weeks), sometimes your dreams are the only thing that keeps you going.

I know about doing what needs to be done – when you’ve ironed ties for a living, you can hack most anything. It’s been a while since I fried hamburgers or stocked shelves, but if I must, I will. Hopefully a new book and some articles will preclude having to pursue this option, knock on squishy white bread buns. However, regardless of what I do to pay for Zoe’s kitty kibbles, I am a writer. Nothing’s going to change this but going to sleep some day and not waking up again.

My only regret is that I’m too old to get good tips as a bar maid. Darn it.

Categories
RDF

PostCon

Recovered from the Wayback Machine.

The RDF vocabulary used throughout the examples for Practical RDF is PostCon, example here, a Post Content information dataset. The plan was that I would finish the book and then finish a Java implementation of PostCon, the application, using PostCon, the vocabulary, before the book hit the street.

What I wasn’t counting on was that I wouldn’t have a Tomcat server to run the Java application on when it was finished. I am running my own server, but it’s shared by other folks and at this point in time, a Tomcat server would be too much for it.

I also wasn’t counting on how tired I was once the book was finished. When you’ve worked on a book for two years, through four major rewrites trying to keep up with changing specifications and attitudes and tools, you get tired. I got tired.

However, PostCon the application begs to be created, and PostCon the vocabulary begs to be used.

So, what is PostCon? PostCon is a vocabulary that records information about a web resource, its movement, whether it’s been replaced, and why, and so on. It’s also an application that will maintain a history of your web content in a form that can be used to redirect HTTP requests when a resource is moved; track history of changes without the necessity of a complex change control system; and provide intelligent error handling when a resource is removed permanently. You can see the early prototype in action with this link.

The application has a user interface that allows one to query the PostCon record for a resource, add to it or modify it, and then persist the changes. Additionally, the application has a web services interface that can be utilized from other applications, such as weblog tools like the one I’m using for this page. Since the information about the change is persisted in a file (RDF/XML) rather than a database, other tools could access this information, such as webbots trying to new resources, or checking to see if a resource is still viable.

The vocabulary is based on RDF, and serialized using RDF/XML, so other vocabularies can be plugged in, simply and easily. Information about the creator is maintained in the PostCon vocabulary and this can be tied to the creator’s FOAF file. If the web resource is a weblog page, trackback information can be used to add PostCon related items for the specific page. For that matter, comments can also be added as part of the history of the resource – after all, a commented weblog posting is different than the posting by itself.

The long and short of it is that I’m returning to working on PostCon, but rather than work on it in the background, I’m going to implement the pieces and document them here in this weblog. This will not only give me incentive to get off my butt and get this done, but it should also, I hope, give me some decent feedback if I’m pursuing a less than efficient implementation strategy.

To start, I’m going to review the PostCon vocabulary one more time, to see how I want to modify it considering new efforts with Pie/Echo/Atom (to be called Atom it seems – thanks to Morbus Iff cutting through the crap – yay Morbus). Next, I’ll implement simple pages that can be used to read in and modify the RDF/XML files for a specific resource. I’ll be implementing these in PHP so that they can be accessed from my server. Later I may translate these to Java and JSP.

Next, I’m creating a second RDF vocabulary, this one to be used by an event queue system. When a resource is moved or removed, not only will the front end update the associated RDF/XML file for the document, it will also update an event queue RDF/XML file, which will then track the actions to be performed on the server side. I prefer this rather than having the front end pages implement file destruction or movement because it’s easier to secure a completely server-side application, then one that’s half front-end, half server.

In addition, by separating this layer of activity out, the application that will take the event queue information and do the actual work can be replaced depending on server-side languages supported, OS, that sort of thing.

I’ll create two versions of the application that processes the event queue – one in Java, one in Perl. The Java application won’t need a Tomcat server (no front end), and I don’t want to focus on just one langauge for this component of the entire system.

The final phase of implementing PostCon will be creating web services that can perform all of the functionality of the front-end interface functionality created in PHP. I’d like to implement these in Python and Perl. Perl because I want to try integrating this into a test copy of Movable Type; and Python because I want to improve my Python skills.

The code will be kept simple, and clean, with no frills. In addition, it’s pure open source, and can be copied, modified, and hopefully improved. When I’m finished, I’ll load all of the code to Source Forge.

I have other things to do, so I’m not going to be whipping this out over the next week, but it should be finished within the next month – knock on wood.

Categories
Writing

Truly understanding censorship

Sheila points to a nicely written how-to on newspapers having weblogs. This was spurred, in no small part, from the tempest in a teapost about Dan Weintraub and the Sacramento Bee’s new policy about editorial review of his weblog.

Many of the Blogging world’s illuminati became incensed by this action. Micky Klaus writes in a meandering, confused rant:

Unlike a mistake in a print column (or for that matter, a mistake on radio) a mistake in a “24-7 blog” can be easily and quite effectively corrected in the same place it was made. For this reason, the cost of a blog error is less than the cost of a print error. That means when you are balancing a) the cost of errors versus b) the cost of more procedures and “standards,” you come out in a different place for blogs than you do for print.

The cost of an error isn’t the amount of time to edit it, but the amount of damage the ‘error’, backed by a major publication, can do when read by thousands before correction.

Glenn Reynolds writes:

Unthinking political correctness, corporate-mandated dullness, and complete cluelessness, all in one event. If you want to know, in a nutshell, why Old Media is in trouble, this is it.

Taking a look at Weintraub’s statement that caused the uproar:

If [the California Lt. Governor’s] name had been Charles Bustmont rather than Cruz Bustamante, he would have finished his legislative career as an anonymous back-bencher. Thus there is reason to wonder how he would handle ethnic issues as governor.

And while people can debate forever whether MEChA and its more virulent cousins do or do not advocate ethnic separatism, it’s indisputably true that the Legislature’s Latino Caucus advocates policies that are destructive to their own people and to greater California, in the name of ethnic unity.

Making sweeping statements such as ‘…it’s indisputably true that the Legislature’s Latino Caucus advocates policies that are destructive to their own people and to greater California…” is something I would expect to read from a weblogger who is throwing opinions around without due consideration of the impact of the words. Perhaps that’s what Klaus and Reynolds want – more rants, less news and thoughtful commentary.

Doc Searls points to most of the articles on this issue, and seems to agree with Roger Smith:

In the future, in order to demonstrate their integrity, true blogs may have to be completely independent of major media. And maybe that’s for the best. At least that way we will be able to scrutinize the bloggers intentions without having to see through a haze of editing or, worse, the agendas (hidden and not) of media corporations.

I share Sheila’s take:

Weintraub’s comments about Bustamante are the sort of words you might hear in a bar. If Weintraub wants to pop off with unsubstantiated personal slams like that, add a comments capacity to his blog and give his readers equal opportunity to publicly challenge him.

Weintraub’s weblog is not a personal weblog hosted on Blogspot. It’s hosted and paid for by the Sacramento Bee, which has an existing editorial policy for opinions expressed by employees of the newspaper. The only crime the Bee committed is that it’s following through on what webloggers have been asking for – treating Weintraub’s weblog like it was a ‘real’ journalist’s effort.

You can’t have it both ways. You can’t say weblogs are journalism,and should be treated as ‘real’ publications. and then deny the sometimes stringent requirements of newspapers and other publications. An error in a weblog can embarrass a weblogger; an error in a newspaper can get the paper sued, or unfairly and adversely impact on the events being reported.

It is a given, and known fact, that people who work for a newspaper or other publication are bound by the editorial process for same. Sometimes this results in the suppression of news, but many times, this prevents offhand remarks and ill-thought comments from hitting the streets and causing damage that a retraction just won’t heal. Even a digital retraction.

Of course, the uproar on this event has died since Weintraub himself doesn’t see himself the victim of censorship, or being muzzled.

Perhaps folks upset by Weintraub going through the editorial process need a reminder of what censorship really likes like:

  • This week is the ALA’s Banned Books Week. Books on the list include any of the Harry Potter novels, The Chocolate War, The Adventures of Huckleberry Finn, Native Son, To Kill a Mockingbird, and far too many others.
  • Amnesty International lists several authors imprisoned in their countries for speaking their mind, including Zouheir Yahiaoui who was arrested for for expressing his opinions online.
  • Al Jazeera has been banned from access to official sources of news in Iraq for supposedly sedicious reporting.
  • The directors of Zimbabwe’s four private newspapers have been charged with “illegally publishing” their newspapers. (Thanks to Frizzy Logic)
  • Reporters without Borders can also give you an eyeful, including the Defense Department’s clearance of all culpability for the death’s of journalists in Iraq by US soldiers
  • The Patriot Act

If Weintraub wants to start a personal weblog on Blogspot and carefully disassociate what he writes there from his newspaper, I’d be more supportive of him not ‘being censored’. However, the price a writer pays for a steady income from a publication is that the publication usually has some say in what’s written. It’s not just the writer who is credited, or discredited, when they spout off.

Categories
Media

Amazing what you can find online

Recovered from the Wayback Machine.

Dave Winer mentions a contribution he made to Boston’s NPR affiliate, WBUR. He’s curious, though, about the salaries of the folks, such as the general Manager Jane Christo’s pay:

How do I call in and ask questions on the air? How much salary does Ms Christo draw? How many execs are there at WBUR and what are their salaries? And how about the talent, how much of my money do they get? I suspect that public radio in the US is like most other industries, execs control the money, and get most of it, and don’t do very much for it.

A quick google search on “wbur” and “salaries” brings up a reference to Dave’s friend, Christopher Lydon, as luck would have it. It seems that when Lydon worked at the station, he was the highest paid talent, at 230,000. And he wanted more:

I like ‘’The Connection,’’ but I was stunned by the size of Lydon’s salary and the fact that he and his producer still weren’t satisfied; they wanted an ownership stake in the show. When Lydon and his cohorts at WBUR ask listeners like me to support the news, I knew salaries were an integral part of the news, but I had no idea they were such a large part.

The article also makes a good point about how we view charities differently from other types of business:

Kate Berseth, who has done fund-raising and fund-raising consulting for more than 10 years, said donors tend to overreact to high salaries. All too often, she said, donors harbor the incorrect assumption that ‘’do-gooder charitable work’’ isn’t worth as much as for-profit work.

Lots of online links about WBUR and salaries, and Lydon no longer being at WBUR. Rather than Dave calling the station and demanding that the station discuss what Jane Christo makes online, perhaps he should ask his friend, Lydon, what she was making when she fired him?