Frequently Asked Questions
Why is it called “Puccini”?
Named after Giacomo Puccini, the composer of the Tosca opera (based on Victorien Sardou’s play, La Tosca), as well as La bohème, Madama Butterfly, and other famous works. The theme here is orchestration, orchestras, composition, and thus operas. Capiche?
How do I pronounce “Puccini”?
Usually: “poo-CHEE-nee” (“ch” as in “change”).
For a demonstration of its authentic 19th-century Italian pronunciation see this clip.
Haven’t we been here before?
Yes. Yes, we have. This is the third TOSCA parser with Tal Liron’s fingerprints.
The first was a group effort in Python: AriaTosca, 2016-2017. It was accepted as an incubation project at the Apache Software Foundation and was a component of the Linux Foundation’s OPEN-O telecommunications cloud orchestrator, later merged with ONAP. Work on AriaTosca was funded by Cloudify (currently part of Dell). Alas, the project did not graduate from incubation and is now archived. May it rest in peace.
Tal first revealed Puccini in 2018 as a personal initiative. It was initially written in Go and used an internal JavaScript interpreter to execute TOSCA functions. This early version of Puccini supports all versions of TOSCA since 1.0 as well as related dialects. TOSCA 2.0 support was contributed by Dario Mazza.
Around the release of TOSCA 2.0 in 2025 it became clear that Puccini could use a rewrite. Tal decided to do it in Rust and Wasm, and this is where work continues. So far this new direction has proven to be very excellent. Third time’s a charm?
Ever since the AriaTosca days Tal has been an active contributor to the TOSCA standard and the TOSCA community. Join us!