Categories
Critters Legal, Laws, and Regs

Will first horse meat plant open September 23

update

Looking through the Decision Document, given as an attachment to the court filing mentioned earlier, I found that the wastewater treatment plant that the USDA based its environmental review on is located in Gallatin, Tennessee, not Gallatin, Missouri.

Oopsie.

Earlier

Last Friday, the USDA filed a motion in the Front Range Equine Rescue et al v. Vilsack et al federal lawsuit to add Rains Natural Meats from Gallatin, Missouri, to the Temporary Restraining Order (TRO). The reason given is that Rains has now met the guidelines for being given a inspection permit, and is demanding the presence of inspectors at the plant by Monday, Sept. 23.

From the court document:

Rains Natural Meats has informed FSIS that it is ready to begin operations, and has requested inspectors at its facility in Gallatin, Missouri, no later than September 23, 2013. Because FSIS is required, as a matter of law, to provide inspectors for these operations, see 21 U.S.C. § 603(a), FSIS must do so, in the absence of an amendment to the Court’s temporary restraining order, as specified above. Federal Defendants have advised Plaintiffs and Defendant-Intervenor Rains Natural Meats, through counsel of record, of Federal Defendants’ positions on the issues discussed in this Notice and that Federal Defendants intended to file this Notice.

A Missouri state judge has issued an order prohibiting the Missouri Department of Resources (DNR) from giving Rains Natural Meats a wastewater discharge permit because of the strong possibility of equine drug residue that can contaminate both land and water. However, according to the attachment provided with the USDA filing, it would seem that Rains has found a way around this injunction by contracting with a rendering plant and the City of Gallatin to use their facilities to handle solid and liquid waste:

Following section 401(a) of the Clean Water Act (33 U.S.C. § 1341) (“CWA”), 9 CFR §304.2(c)(1) requires any applicant for federal meat inspection at an establishment where the operations thereof may result in any discharge into navigable waters as defined by the CW A to provide the Administrator, FSIS, with certification, obtained from the State in which the discharge will originate, that there is reasonable assurance that said operations will be conducted in a manner that will not violate the applicable water quality standards. On September 3, 2013, Mr. Rains provided the Administrator, FSIS, with an attestation that equine slaughter operations at Rains Natural Meats will not result in any discharge into any navigable waters as define by CW A. Mr. Rains also provided the Administrator, FSIS, with copies of letters from Darling International Inc., a rendering company, and the City of Gallatin agreeing to dispose of Rains Natural Meats’ liquid and solid waste.

Darling International Inc is in Iowa, and not impacted by a Missouri court order. The City of Gallatin’s wastewater treatment system already has a permit, and presumably would not be impacted by the Missouri Judge’s order. According to MO-G822, which is the general permit Rains applied for, a plant would be exempt if it discharged wastewater into an existing sewer system:

Facilities that are of the types listed above and do not discharge into a public sewer system will need to either obtain this General Operating Permit or a site-specific permit. [emph. added]

Again returning to the USDA attachment:

Rains Natural Meats’ disposal of wastewater is governed by Missouri’s Clean Water Law (Mo. Rev. Stat. 640.006 et seq.). In accordance with the Clean Water Law, Rains Natural Meats will discharge its wastewater into the City of Gallatin’s wastewater collection system which consists of over 191 miles of sanitary sewer lines and 22 sanitary sewer pumping stations. 14 This system will transport water from Rains Natural Meats to the Gallatin Wastewater Treatment Plant for processing and eventual discharge of a high quality effluent back into Old Hickory Lake.

As of this morning, Judge Armijo has not modified the TRO in the Front Range Equine Rescue federal case. I have asked the attorney representing the animal welfare groups in the Missouri state case, Stephen Jeffery, for confirmation or correction, and will post an update, accordingly. I’ll also post an update if Judge Armijo modifies the TRO to include Rains.

Categories
Critters Legal, Laws, and Regs

Two new stories on horse meat lawsuit

I just published two new stories related to the Front Range Equine Rescue et al v. Vilsack et al horse meat lawsuit.

In Cages at Burningbird I write that the USDA is not the enemy in this case and they aren’t. If we’re going to fight for the welfare of horses in this country, we need to be very careful with where we paint our targets.

I also introduce another new site, Eats at Burningbird, with another story: Eating Flicka: A Good Idea?. This story focuses on the food safety aspects of horse meat and the horse meat industry. All I can say is you’ll never look at your hamburgers the same way again.

I am trying comments again, at least with select stories. Last few times, I had a lot of spam. And yes, I actually used a spam service, and still had a lot of spam.

I’m also concerned at how quickly comments degenerate into slugfests nowadays. I don’t really think tossing insults at each other adds to the quality of a story. Popularity really isn’t everything.

We’ll see how it goes. Hope springs eternal.

Categories
Copyright Weblogging

There’s an echo with Echo

Joe Shelby, in the comments associated with my last posting made a good point about “Echo” as name of this weblogging initiative:

Echo is already a name for a product, a Java web application framework, that just released its 1.0 earlier this month, and very nicely under the LGPL license. By choosing “Echo”, the Wiki participants have effectively hijacked that name and may potentially destroy a product from a company doing TheRightThing ™, before that product even gets off the ground.

I posted a note at the wiki about this. I asked that the members form a consensus that they’re willing to use a name that could conflict with another newly released technology. This did start another discussion page.

Wikis are geared to fast, fast, fast. You have to hit the ground running, and be ready to move. Too much for this SysAdmin wore out from getting the Burningbird Network Co-op going (having fun, though). However, in this particular instance, I can also see the power of a wiki.

To me, what brings this all together is combining the technology: wiki to do the actual collaborative work; and weblog to summarize and involve others, to highlight specific points, and make specific persistent comments.

I’m getting a bit burned out on tech at the moment, and need to go back to literature, writing, funnies, life, politics, and photos – but I did want to take a moment to say that I think the wiki combined with weblog approach is very sexy.

Technically speaking. No worries, I’m not that far gone.

Reply from other project:

I do greatly appreciate you asking us before using the name, and
apologize for not having a positive answer. I’d request that you not
name your project Echo. I think the possibility of confusion is too
high, given that both projects are frameworks for building Web-based
applications. I realize that finding a name is very difficult to do (it
took what seemed like forever to settle upon “Echo” in our case).

I am not a lawyer, but I believe that I am required to inform you that
NextApp has a pending trademark registration on the term “Echo” in the
application of “A computer software framework/library used by software
developers for the creation of Internet-and Web-based applications.” It
is my understanding that I am required to state such information in
these circumstances in order to have our trademark be
considered valid, as trademarks must be actively defended. I apologize
again for even mentioning this as a response to your friendly request,
and only state this information because I believe I’m legally obligated
to do so.

I would say that Joe Shelby should take a bow for a good call on this one.

Categories
Copyright RDF Writing

Checking in

Thanks for well wishing. The suggestion of tea was a good one, but unfortunately I can’t drink any acidic juice such as OJ, as it hurts my throat more than a little.

Doing a bit of catch up. There were a couple of items of RDF I had to respond to over at Practical RDF, both of them related to postings from editors on the book. My only comment in addition to my two postings is this: I have a great deal of respect for the RDF Working Group. They worked, hard, to reach Last Call status on the newest RDF specification documents. All that’s left is a few odds and ends, and they can call their job done. It would be a real shame if the group took all that hard work and drop kicked it off a cliff in a burst of tired arrogance at the end of the day.

Liz joined the fun on Creative Commons with a challenge to Jonathon and myself to provide reasons for why not to use the licenses:

 

How ‘bout a “non-shithouse” version of why people might choose not to use the license, that can live side-by-side with the CC discussion of why they should?

Well, you only have to search on “creative commons” among my archives to see my comments, though I’m not sure about their ‘shithouse’ status. I look to Jonathon to provide a better answer to Liz, if he wishes, as the RDF posts took my time tonight, and I’m to bed. However, it seems to me that if Creative Commons is to be effective, it’s up the members of the CC to detail the problems associated with the CC licenses as well as the advantages. I’ve pointed out to a couple of members the writing that Tim Hadley has done; hopefully they’ll consider writing a post or two on these issues to go with all the postings about this artist or that blogger that has attached a CC license to their work.

I was more interested in responding to the discussion Liz and Dorothea are having about about academia. Specifically, I wanted to pursue the thread off this conversation that Baldur started:

 

Everybody speaks the same, in the same way, about the same thing, with little to no variation. We could easily turn into the lightspeed version of the same unsubstantiated bullshit of postmodern academia, shedding even the pretense of giving ideas space and scope for discussion.

What killed the author and poisoned academia is trying to return through the violated corpses of a horde of ’blogger-zombies spouting inane commentary on the links of the day.

But as the popularity of weblogging increases, the number of meme-victims will rise and the blogdex top fifty will not only describe the fifty most popular subjects amongst webloggers…

It will describe the only subjects.

What I’ve tried to say in a thousand words, Baldur said in a few. I wanted to write in response, but lacked the energy to respond well. I couldn’t do justice to Baldur’s words.

But when I’m well, and have the energy to respond, to do Baldur’s writing true justice, should I?

Categories
Burningbird Copyright

Domain for sale

Recovered from the Wayback Machine.

A quick note — Tim Hadley wrote a very detailed careful analysis of the Creative Commons license from the perspective of webloggers in general, Movable Type specifically. In particular the section that relates to the permanence of a CC license is worth extremely careful perusal if you’re thinking of pushing the button to have MT add CC licenses to your weblog.

Also, from what Dave Seidel said in my comments I could be looking at weeks of email spam problems. If this is a continuing problem, then it will show after midnight, as it did yesterday. We’ll see in the morning.

By default, I have all emails that don’t specifically go to anyone else come to me as main webmaster. This means, then, that the email spam messages come to the shelleyp AT burningbird DOT net email address.

As an interim solution, if you need to send an email to me, please use a new email address I created to bypass potential spam email floods: bb AT burningbird DOT net.

The yasd.com domain is coming up for renewing in 45 days. I consider this problem a sign of the times, and I’m going to look at either letting it expire, or the possibility of selling it. The acronym YASD does have significance to Japanese and other electronic game players, so I might be able to make a few bucks. Maybe enough for my server.

I hate to lose the domain, though, I’ve had it since early 1996.