I would suggest to use 1D barcode and 2D barcode. In the future there will be a 3D barcode which have different colors. QR is just a 2D barcode format, like EAN is for a 1D barcode.
Even if it is possible to add another library, I hoped that the 2D-matrix format was added also. This is rapidly becoming the industry standard.
The main problem with all the variety of barcode is that they do not fit in a single API to generate them. For 1D barcode this can almost be possible because the number of parameters is limited (but still there are 1D barcode with colors). But for the 2D barcode the variety is very large. See https://en.wikipedia.org/wiki/Barcode#Types_of_barcodes.
So I think it is better to fit with common name and logical group that share the same parameters (so mainly what a library propose). If a third type of barcode become a defacto standard, we could still add it to the tools with its own name. For me the important part is to not expose API of the underlying library so we can easily switch if needed.