Because I work on DocumentCloud I very much do touch on both OCRing software and frontend JS libraries.
It will only make things confusing to have these two projects fighting over namespace. And the Tesseract OCR engine is not going away. It's the defacto standard for FOSS OCRing.
Edit: Having played around with the examples for this lib, it's awesome! I will have to find a project to work this into. Looks like fun.
Cubic Prism is another name for tesseract and could also remind one of both SQL data rollup and looking at data in new lights.
Looks like the perfect name to me. Sounds like the "other" project already has an established name of "tesseract ocr", don't see any reason why this library would be confused with that. Lame for people to focus on this instead of the crazy beautiful api that comes with this thing:
Tesseract goes by the name Tesseract, tesseract-ocr is just the name of the Google code project.
To be honest though, my view is very biased because I don't care about the ocr project at all. I'm sure it's a very nice project, but hardly a tesseract really.. =p
https://37signals.com/svn/posts/3112-how-basecamp-next-got-t...
Tesserect? ;p
Mind you Tesseract OCR did miss a chance to be TesseractOCRus, which would be great, obviously.
Another name option would be "hypercube," which means the same thing. It does make it sound more related to "cube" though.