New York Center for Independent Publishing: "What's Next?"

Text-to-speech and the complexities of "books"

I wanted to turn folks on to a post by Bob Martinengo on Accessible Publishing. An excerpt:

[A]s the book form intersects with digital technology, surprisingly complex structures are being revealed, which, rather than point out the limitations of ‘old-fashioned print’, actually illustrate the boundaries of digital interfaces. In other words, the presumed simplicity of the book form has masked the truly complex information structures it can support.

 

Amazon Buying Lexcycle - Owning Stanza for iPhone

Oh God

Oracle buying Sun

Not usually my bailiwick, but my is one of Sun's best chip designers, so we've been swapping thoughts all morning.

Sun/Oracle Media Kit - Bro says the "highlights" are particularly good, so I checked them out (even though it's a PDF - grrr), and he's right.

NY Times - which is how I found out and accidentally sprung it on poor bro who hadn't gotten the memo yet....

Okay, so no libraries can change out their SPARC stations for 10 years because...I want little bro to keep working.

Google Book Search Settlement Analysis

Pam Samuelson has a great article on the O'Reilly blog - thanks to Colleen Lindsay for tweeting it - on the Google Book Search settlement. It's very thoughtful and well-articulated, and the comments are also well worth reading. She also links to some slides from a presentation she gave on the subject.

She's especially cogent on the subject of orphan works:

An estimated 70 per cent of the books in the Book Search repository are in-copyright, but out of print. Most of them are, for all practical purposes, “orphan works,” that is, works for which it is virtually impossible to locate the appropriate rights holders to ask for permission to digitize them.

A broad consensus exists about the desirability of making orphan works more widely available. Yet, without a safe harbor against possible infringement lawsuits, digitization projects pose significant copyright risks. Congress is considering legislation to lessen the risks of using orphan works, but it has yet to pass.

The proposed Book Search settlement agreement will solve the orphan works problem for books—at least for Google. Under this agreement, which must be approved by a federal court judge to become final, Google would get, among other things, a license to display up to 20 per cent of the contents of in-copyright out-of-print books, to run ads alongside these displays, and to sell access to the full texts of these books to institutional subscribers and to individual purchasers.

Future of Reading in the WSJ

Usually I roll my eyes at future-of-books/future-of-reading articles. But this guy knows what he's talking about.

Writers and publishers will begin to think about how individual pages or chapters might rank in Google's results, crafting sections explicitly in the hopes that they will draw in that steady stream of search visitors.

Individual paragraphs will be accompanied by descriptive tags to orient potential searchers; chapter titles will be tested to determine how well they rank. Just as Web sites try to adjust their content to move as high as possible on the Google search results, so will authors and publishers try to adjust their books to move up the list.

What will this mean for the books themselves? Perhaps nothing more than a few strategically placed words or paragraphs. Perhaps entire books written with search engines in mind. We'll have to see.

This correlates directly to what we found during our research on the StartwithXML Project.  The problem? There are no standardized descriptive tags right now. There are tags to describe entire books, but not describe parts of books.

At every turn in the article, I expected to start with the eye-rolling. But I never did. 

#amazonfail funny

Oh, and also?

This.

(Thanks to Evan Schnittman.)

Taxonomies and #amazonfail

This is a re-post, in a way - I posted to Peter Brantley's Read 2.0 listserv in response to Clay Shirkey's piece and Mary Hodder's other piece, and was urged to post publicly. 

I've done so much taxonomy work, both for Muze and BN.com - and my colleagues and I have all agonized over the political decisions we've had to make because in a taxonomy you have to articulate concepts and arrange them. Like staying-awake-at-night agonizing, because these articulations and arrangements either bring books to light or tuck them away where few can find them, depending. (Richard Nash also makes a great point up this same alley.)

And it's worth getting upset about. What happened at Amazon is the result of dozens of small decisions about how to name things and the structure of those names - whether the decisions were made by people at Amazon or they were importing other companies' taxonomies (probably both) or using semantics to create algorithms. Shirky is right in that it probably wasn't a person or group of people deciding that they didn't like gay people that day. But (as Richard points out) it was the result of heteronormative thinking creating search rules that ultimately resulted in...#.

What taxonomizing teaches you is that no worldview is neutral, and the best you can hope for is to keep trying to reach in that direction. Detangling what happened at Amazon is compounded by the fact that they aren't talking to anyone, but it appears to be a compilation of complacent taxonomizing, linking certain concepts to the theme "adult", imposing some sort of filter on the "adult" titles (without realizing what "adult" meant in terms of the terms that linked to it) in a misguided effort to make explicit books less visible, not fully investigating the problem when it first came to Amazon's attention (but dismissing it as a "policy" decision, which is most likely never was in the first place), and now not really responding effectively. Probably because those in charge of responding really have no idea how it happened.
 

AMG/Macrovision Acquires Assets of Muze, Inc.

AMZN responds to #amazonfail

The Seattle Post-Intelligencer (via Lilith Saint Crow's blog) has a statement from Amazon regarding the fiasco that reared its ugly head this weekend:

This is an embarrassing and ham-fisted cataloging error for a company that prides itself on offering complete selection.

It has been misreported that the issue was limited to Gay & Lesbian themed titles – in fact, it impacted 57,310 books in a number of broad categories such as Health, Mind & Body, Reproductive & Sexual Medicine, and Erotica. This problem impacted books not just in the United States but globally. It affected not just sales rank but also had the effect of removing the books from Amazon's main product search.

Many books have now been fixed and we're in the process of fixing the remainder as quickly as possible, and we intend to implement new measures to make this kind of accident less likely to occur in the future.

Authors everywhere appear to be awaiting Amazon's apology.

#amazonfail Afternoon Roundup

Okay, a flurry of links to digest, so I'll do the best I can:

• Speculation that it's a hacker using Amazon's metadata against it here.
• Daily Kos on the "New Morality For Your Protection".
• Neil Gaiman's take on #. 
• The Smart Bitches have a lot to say here.
• Speculation that it wasn't a hacker after all.
• Speculation that it's the French.
• Dear Author gets under the hood of the metadata and tries to figure out exactly how it could have happened.
• An anonymous coder from inside Amazon apparently has this to offer.
• Does #amazonfail mean that Amazon's now too big for its britches?
  
• And a summary of the whole hoo-ha is here.

#amazonfail

There'll be a lot more about this in The Big Picture on Wednesday, but for now I wanted to give a link roundup to folks who've been covering Amazon's whacked-out metadata issue. Apparently books classified as "adult" - many of which are gay/lesbian/bisexual/transgender titles which are not explicit, making it appear that Amazon has an anti-gay bias - are not appearing in search results. In addition to it being a GLBT issue, it's also a women's sexuality issue, as many of the books not appearing are erotica titles aimed at women. Clearly someone at Amazon made a decision not to display "adult" titles, and the criteria for what constitutes "adult" titles is messed up.

Links!

• This first erupted on .
• But it really began with this blog post from Mark Probst.
• Gawker calls out Amazon for calling this a "glitch".
• Ron Hogan at Galleycat used to be the GLBT editor at Amazon and offers an interesting perspective.
• Publishers Weekly gives more or less objective coverage.
• Foreign Policy offers a great view on activism.
  

ONIX on iTunes

Kindle User Banned From AMZN - Kindle Now A Brick

Frantically being re-tweeted through the Twitter grapevine is a story via Teleread, originally from MobileReads - a Kindle user was banned from Amazon as a customer. He had "returned too many items for refunds" - three defective electronic products, to be exact. Nothing to do with the Kindle.

But as an Amazon customer, his Kindle account was killed too. In other words, when he was banned from Amazon, he was also banned from his Kindle library, which is stored on Amazon's servers. A library he paid for. 

Turns out he didn't pay for the library - he paid for access to the library.

Angela Bole back at BISG

Yes, you heard me right. Angela Bole is back at BISG, working with Karen Forster, Sara Raffel, and Michael Healy. Those who've been in BISG for a while know that this means all kinds of good things - Angela essentially ran BISG while the organization searched for a new executive director; she is deeply aware of all the issues in the book supply chain and it's a very good thing for our business that she has come home again. Just try leaving again, Angela! We will hunt you down and bring you back!

EPUB Boot Camp Slides Are Up!

So the slides from the Booknet Canada/ACP ePub Boot Camp are up here! It was a great session - jam-packed with information about ePub pretty much from soup to nuts: what is it, what does it do, how to do it, what you can do with it, and where it's going. I can honestly say that the time sped by - there was never a dry moment, which is pretty incredible when it comes to something this technical and specific.

I'll be covering the Boot Camp in detail in my newsletter this week (yes, I swear it's coming out this week), but you can follow the blow-by-blow on .