Show HN: Veml – Vector Embedding Markup Language

My first take is that I can compute embeddings with one line of Python using sbeet.net and from there it is an automated process, I have a script that generates embeddings for 80,000 documents that runs every day and I barely think about it.

I think of GUI and I think somebody has to click through 80,000 documents to do this same and to get the same throughout I’d have to raise venture capital and hire an army of people to go click… click… click… That is it takes something easy and scalable and makes it difficult and expensive, It makes me think if the text retrieval experiments that Salton did with documents on IBM cards in the 1960s.

I know there is more to it than that, this simple approach is not so simple when you consider chunking and other choices that could make a big difference but i still think there would be some programming language function that takes a document and gives an embedding but some kind of suite to determine the parameters of that function (on the level of a document collection not individual documents) could be quite useful but I think a lot of people will want something that doesn’t have many knobs to turn.