Eating Flicka: A Good Idea?

If we separate the moral argument about eating companion animals and instead focus on the safety of horse meat, the end result remains the same: starting up the horse meat industry in the United States is not a good idea. To get a good understanding why, we need to take a closer look at what’s happening with the horse meat industry where the meat is currently allowed: The European Union (EU).

The EU has had procedures in place to ensure healthy horse meat for years, yet stories this year about horse meat incorporated into beef products, and horse meat testing positive for drug residue have surfaced repeatedly.

Horses in the EU are required to get a “passport” by six months of age, and all administered medications get recorded in the passport. Yet there have been a significant number of incidents where a passport for one horse is used with another, as well as incidents of fake passports.

Equine Essentials notes the issues in The Problem with Horse Passports:

The passport system has had plenty of criticism for not functioning properly, not being enforced and being subject to a lot of abuse. In February 2013 the BBC reported that 7000 unauthorised documents have been circulating in the UK since 2008. Not to mention the fake horse passports that are being made continuously. Owners report that veterinarians often don’t use the passport to record care history and many opt for the old way of doing things and issue vaccination cards instead. Many competing grounds are also happy to just see the vaccination card and don’t check passports.

Problems aside, the supposed benefit of the Passport system is it provides traceability of the horse, ensuring that meat from horses that have received hazardous drugs doesn’t enter the food chain. There is no such system in the United States. At one time, the USDA considered implementing a system of traceability known as the National Animal ID System, or NAIS. However, because of pushback from farmers and livestock associations, the USDA dropped its plans. Instead, the USDA adopted a relatively weak rule that animals transported across border will have to be accompanied by formal identification, including a veterinarian certificate or owner statement. No passport, no electronic tracking, just paperwork.

The new rule’s purpose is to track the course of a diseased horse across state borders. However, tracking a diseased horse is only one component of ensuring the safety of the meat. It’s also important to know what drugs a horse has been given. As the USDA notes in its inspection procedure, horses are companion animals and are usually given medications forbidden a food animal like a cow. In particular, one drug, phenylbutazone or “bute” as it’s commonly called, is frequently used with companion horses. But bute can also cause a fatal disease in humans called aplastic anaemia. The drug is so dangerous that any use in the horse makes that horse ineligible for processing as meat.

To check for drugs, the USDA implemented an inspection routine that randomly samples horses, based on the number of horses within a “lot”. If the lot consists of 10 horses, the USDA inspectors will test 1 horse; between 11 and 50, 2 horses; between 51 and 100 horses, 3 horses are tested; and if the lot consists of 100 or more horses, a maximum of 4 horses are tested.

Is this random sampled testing sufficient to ensure that the horse meat is free from drug or other residue that can cause harm? Well, to answer that, we have to visit our neighbors to the north.

The Toronto Star has written a series of investigative stories about the processing of horse meat in Canadian factories. It followed a race horse named Backstreet Bully, as it left a race course only to be shot dead in a knacker’s yard. The story detailed how, through a series of deceptions widely practiced in the kill horse auction community, a horse who had been administered drugs typically given to companion horses, ends up at a horse meat slaughter auction house. The story effectively demonstrates how ineffectual Canada’s own “passport”, the Equine Information Document, is when it comes to preventing drug tainted meat from entering the human food chain.

The federal government relies heavily on the accuracy of the passports, which have been in existence since 2010 and are the first line of defence in keeping tainted horse meat from the human food chain. The government does not require owners selling a horse for meat to provide additional medical history such as veterinary records.

Dr. Martin Appelt, the Canadian Food Inspection Agency’s national veterinary program manager, acknowledged the government relies on an honour system and hopes that the documents are “a reflection of the truth.”

But it’s far from a foolproof system: last year, tainted horse meat from Canada, bound for Belgium, was found to contain traces of two controversial drugs, bute and clenbuterol, the latter on the list of drugs in Canada that are never to be given to animals sold for human food.

The Canadian Food Inspection Agency began testing horse meat for bute in 2002. In detecting prohibited veterinary drug residues in meat, there is an overall compliance rate of 96 to 98 per cent, according to an agency spokesperson. Testing is random though a horse or its carcass will be tested if there are red flags or concerns.

Though Canada has implemented it’s own passport system, it also relies on random testing, just like the USDA. Yet horse meat tainted with dangerous drugs has still managed to slip through to the European market. We, in the US, rely only on random testing—how safe do you think the meat will be?

Of course, one can always choose not to eat horse meat. We’re not going to be exposed to bute-tainted meat if we don’t eat horse meat. The problem with this approach, though, is that sometimes people are eating horse meat and aren’t even aware they’re doing so.

This year, the EU and the UK were shaken when horse DNA was found in meat labeled as 100% beef. Food Safety News put together an infographic charting the early days of the scandal, but the problem is ongoing. Just last week, authorities noted that two people involved in the horse meat contamination were arrested in Britain.

The Horse DNA tainted beef has shown up all throughout Europe and the UK: in foods ranging from fast food burgers to the famous IKEA meat balls. Recent testing has shown that over 5% of meat labeled “beef” in Europe is contaminated with horse meat DNA. This isn’t a small percentage, and demonstrates that the horse meat contamination is endemic—especially when we consider the DNA testing is more thorough in some countries, than others.

What’s more critical is that testing also discovered that one half of one percent of the horse meat tested positive for bute—a far more alarming discovery. Authorities downplayed the findings, saying the percentage is trivial, but the assertion of “no worries” doesn’t jibe with the laws restricting any presence of bute in the human food chain.

The EU may state that the issue is a matter of food fraud and not of food safety, but in the end, it’s all about food safety. Food safety is about preventing harm to people, regardless of the impetus behind the harm: human greed or human carelessness. And, as noted in the NY Times article just linked, Europeans have only been testing for bute…there are other drugs used with horses that can also potentially cause harm if consumed by humans or other animals.

If you live in the United States, you may think this isn’t a problem for any of us. After all, we don’t typically eat horse meat in this country. None of the horse meat processed in the country is targeted for human consumption within the country. The meat is intended for human consumption in other countries, or supposedly for animals in zoos. Why should we worry, then?

Leaving aside the fact that we should question our indifference about inflicting potentially dangerous meat on the rest of the world, not to mention tigers, lions, and bears in zoos, we are at risk for our own version of the European horse meat scandal by starting up horse meat processing in this country.

Horse meat is generally less expensive than beef, especially horse meat from older horses or scrawny wild mustangs. It’s going to be tempting to shove a little horse meat into the beefwhen creating cheap frozen foods, or foods served at inexpensive restaurants. In addition, horse meat is leaner than beef, which has an appeal for a different reason. Because of our insistence of shoving corn down cows’ throats, we have almighty fatty beef in the US. Yet weight conscious people want low fat meats. Access to lean meat to mix with our fatter beef in order to control fat content is an attractive proposition. Right now, we’re actually importing lean beef trim from countries like New Zealand, just to get that “98% lean” label in the supermarket. Why not toss in a little leaner horse meat rather than import lean meat scraps?

We wouldn’t need to be concerned about our own version of “food fraud” if we did DNA testing on our meat in order to ensure that “beef” is “beef”. Canada did this recently, to assure its citizens that Canadian beef is real beef (they hope, because just like testing for drugs in horse meat, the horse DNA testing samples were limited). The problem is, the US doesn’t do any DNA testing of our locally derived meat. Some folks did for our seafood, and found a whole lot of “mislabeling”. We do species testing for imported meat, but we don’t do any DNA testing of our locally derived meat.

Well, isn’t that just peachy?

Let’s be blunt, we’re right there with the folks in Canada and the EU: food safety is based on the honor system more often than not. Most of the time, it works. Sometimes, though, the honor system doesn’t work as well as we’d like. Once we start processing horse meat in the US, the only way we can guarantee we don’t get any horse meat in our hamburgers is not to eat hamburgers.

Or chicken.

I’d stay away from goat, too.

ASPCA et al vs. Feld Entertainment Inc

I finally managed to get all of the ASPCA et al vs. Feld Entertainment court documents I have downloaded, linked to copies of the court dockets for your viewing pleasure.

Over 600 separate filings, many with multiple documents, each with hundreds of pages. I don’t have all the court documents, but I have most, including attachments and court exhibits. I typically didn’t download any court document that was a duplicate of a previous filing or had to do with court mechanics.

I also have uploaded the court documents for the associated RICO court case. Eventually, I’ll finish by uploading the appeal documents, as well as documents for peripheral court cases.

In addition to the court documents, the main index page includes links to many of the videos that were played during the trial.

Of the videos, the one that bothered Judge Sullivan the most is a young elephant, gently exploring a bike rack with her trunk. Ringling employee Troy Metzler casually walks up to her and strikes her trunk with a bullhook. An elephant’s trunk is very sensitive, and the young elephant is both startled, and in pain. Before the video clip ends, another older elephant reaches out, seemingly to comfort the younger.

Bad Dentists and Open Libraries

The newest addition to the document collection is an opinion by Judge Paul Crotty related to the case Robert Allen Lee vs. Stacey Makhnevich et al. The case is a class action lawsuit against a dentist who forces patients into signing a confidentiality document before treatment, and her attempts to intimidate the dental patient, Lee, who wrote uncomplimentary comments about her practice on Yelp and other online sites.

The opinion I snagged rejects the defendants’ attempts to have the case thrown out in court. It’s a lovely piece of legal writing. Don’t let anyone tell you that legal documents are dry and uninteresting. The best legal documents don’t just quote relevant law—they tell a story. They paint pictures, break new pathways, shape history.

I also wanted to point out the source of the document: the Santa Clara Law Digital Commons. This site is a rich pool of legal articles and opinions that are freely and openly available to everyone—the way such writings should be. The site is well organized, cleanly designed, and very accessible: a prince among sites. From its About page:

This digital repository is a project conducted by the Heafey Law Library located at Santa Clara University’s School of Law. This archive contains scholarly materials published by our faculty and other archival collections. The purpose of this digital repository is to preserve the scholarship of Santa Clara Law and enable wider access to these materials. (emph. added)

You can read more about our copyright-claiming dentist in the ABA Journal.

Any element can be replaced with something more relevant

I only check into the doings of the HTML WG at the W3C once a week.

Most of my time is spent on my new book, Learning Node. Frankly, Node has been a refreshing change from the smoky labyrinth which is the HTML5 spec process. I’d check in with the Working Group less often, but I still hope to provide at least some moral support for those still slogging away.

You all do realize that the battle over longdesc is still being fought, don’t you? Oh, there’s other new battles, including some interesting ones over a new path object added to the Canvas2D spec (Eh? What?), and encrypted media (very long discussion about this one), but longdesc still remains the perennial favorite.

The issue now is keeping any decision about longdesc separate from decisions being made about ARIA attributes. At least, I think this is the issue. What caught my eye today was something Sam Ruby wrote to the group:

My biggest concern is resolving ISSUE-30. By that I mean done. There may be Formal Objections, but there won’t be new information, so at that point this Working Group is done subject to Director approval.

Put another way, I have zero interest in a provisional decision that
would likely lead to a reopening based on new information. At the
present time, I see two potential candidates for new information. One
is the subject of issue 204. The other would be somebody putting
forward a spec for something akin to an aria-describedAt attribute.

The reason I state that is that at the present time I see wide support
for the idea of obsoleting longdesc once there is a viable and clearly
superior replacement. Note: some may not believe that a viable and
clearly superior replacement is possible. Others may not believe that
such is imminent. But I worded what I said carefully to include such
people’s opinion.

So the task we face is eliminating all alternatives.

I can agree that resolving this issue, completely, should be a goal. However, Sam demands that those who support longdesc provide a surety that there can be no better alternative in the future, and that’s just impossible. There is no surety for any component or element of the HTML5 specification. I have no doubts that, at some future time, better and improved replacements can be found for all HTML5 elements, attributes, and various and assorted sundry APIs.

(Simple elimination comes to mind as a way of improving some of the new additions.)

No other element or attribute in HTML has undergone such rigid opposition and such rigorous support. I would feel better, much better, about HTML5 if any of the new objects, elements, and attributes received even a tenth of the inspection and discussion that has been afforded to lowly, simple little longdesc. Objects, such as Path.

And now, the gauntlet has been tossed: longdesc is our princess in the tower, the W3C the wicked sorceress, and the demand has been made that either a knight in shining armor rescue the poor damsel or she be dragon kibble.

Eliminate all alternatives to longdesc? How many years do we have, Sam?

Why read about it when you can play

Earlier today I got into a friendly discussion and debate on Twitter about a new web site called W3Fools. The site bills itself as a “W3Schools intervention”, and the purpose is to wake developers up to the fact that W3School tutorials can, and do, have errors.

The problem with a site like W3Fools, I said (using shorter words, or course, since this was Twitter), is that it focuses too much on the negative aspects of W3Schools, without providing a viable alternative.

But, they said, W3Fools does provide links to other sites that provide information on HTML, CSS, or JavaScript. And, I was also told, the reason W3Schools shows up first in search results is because of uncanny use of SEO optimization.

Hmmm.

It may be true that W3Schools makes excellent use of SEO, and it may be equally true that W3Schools commits egregious and painful errors. However, neither of these account for what W3Schools is doing right. If you don’t acknowledge what the site does well, you’re not going to make much headway into turning people off the site—no matter how many cleverly named sites you create.

For instance, one of the superior information sites recommended by W3Fools is the Mozilla Doc Center, or MDC as it is affectionately known. Now, I’m a big fan of MDC. I use it all the time, especially when I want to get a better idea of what Firefox supports. But look at the work you have to put in to learn about a new HTML5 element, such as the new HTML5 hgroup element:

  1. Go to main page
  2. Click on HTML5 link
  3. Search through the topics until you see one that’s titled “Sections and outlines in HTML5”, which you know you want because it mentions hgroup
  4. Have a neuron fire and realize that you can just click directly on hgroup
  5. Go to the hgroup page, past the disclaimer about what version of Firefox supports the element, looking for an example of usage
  6. Realize there is no example of how to use hgroup
  7. Go to the original Sections and Outlines in HTML5 link
  8. Go past some stuff about elephants, looking for example
  9. Go past some bullets about why all this new sectioning stuff is cool, looking for an example
  10. Break down and use your in-page search to find hgroup
  11. Finally find an example of how to use hgroup

As compared to W3Schools:

  1. Go to main page
  2. Click on Learn HTML5 link
  3. Click on New Elements link
  4. Start to scroll down when you realize the new elements are listed along the left side
  5. Click on hgroup
  6. Look at example

One thing W3Schools does well is provide a clean, simple to navigate interface that makes it very easy to find exactly what you need with a minimum of scrolling or searching.

Returning to our comparison between W3Schools and MDC, we then search for information on SQL. Oh, wait a sec: there isn’t anything on SQL at the Mozilla site. That’s because Mozilla is primarily a browser company and is only interested in documenting browser stuff.

So then our intrepid explorer must find another site, this one providing information on SQL. And if they want to learn more about PHP, they have to find yet another site. To learn about ASP? Another site, and so on.

What W3Schools also provides is one-stop shopping for the web developer. Once you’ve become familiar with the interface, and once the site has proved helpful, you’re more likely to return when you need additional information. Let’s face it: wouldn’t you rather use one site than dozens?

Screenshot of W3Schools page showing many of the topics

Let’s say, though, that you need information on CSS3. Well, you know that MDC covers CSS, so you return to the MDC site, and you click on the link that’s labeled “CSS”, and you look for something that says CSS3.

What do you mean there isn’t anything that says CSS3? What do you mean that transitions are CSS3—how am I, a CSS3 neophyte, supposed to know this?

Returning to W3Schools, I click the link in the main page that is labeled CSS3. Oh look, in the page that opens, there’s a sidebar link that’s labeled “CSS3 transitions”. And when I click that link, a page opens that provides an immediate example of using CSS3 transitions that I can try, as well as an easy to read a table of browser support.

Screenshot of W3Schools CSS3 transitions page

W3Schools doesn’t throw a lot of text before the examples, primarily because we learn web material best by example. Remember that an entire generation of web developers grew up with “View Source” as our primary learning tool.

But so far, I’ve only compared W3Schools to MDC. There are other useful sites that the W3Fools site approves. So I try the “Google: HTML, CSS, and JavaScript from the ground up” web page. When it opens, I click the link labeled CSS…

And I get a video about using CSS.

A video.

Remember in junior high or high school, when your science teacher would bring out the projector and you knew you were going to get a video? Do you remember that feeling that came over you? How you kind of relaxed, because you know the teacher wasn’t going to ask you any questions, and you didn’t have to write any notes, or even really pay attention?

I bet some of you even fell asleep during the video.

Videos are good for specific types of demonstrations—when something is complex, with many different steps, and the order of the steps and other factors have to be just so.

When it comes to CSS, HTML, and so many other web technologies, though, video is about the most passive and non-interactive learning experience there is. More importantly, if the video doesn’t have captioning, and most don’t, you’re also leaving part of your audience behind.

Now let’s return to the W3Schools site, this time looking at one of the CSS selector tutorials. The first thing you notice is that right below the example there’s a button, labeled “Try it Yourself”.

W3Schools screenshot showing the Try It button

Why read about it, when you can play?

One of the more annoying aspects of trying to learn about a specific HTML element, or a bit of CSS, is that you have to create an entire web page just to try it out. What W3Schools provides is that all important, absolutely essential, one button click to Try it out.

I’m not defending W3Schools. The site has played off the W3C title, though that doesn’t have a lot of meaning nowadays. More importantly, some of the material has errors and the site is resistant to correcting any of these errors, and this is unconscionable.

But you aren’t going to dent the popularity of the site without at least understanding why it is so popular. The W3Schools’ site is not popular because of SEO, and it’s not popular because of the W3 part of the name.

The W3Schools website is so popular because it is so usable.