SUGGESTION: Revision to data fields, an openspool 1.1 if you will #37

What has been created with OpenSpool is so much more than just a way to update color on the printer, its also an easy way to document key data about each filament. With the custom of re-spooling, or using "universal" spools, the information that was on the original spool is often lost once the cardboard spool ends are peeled off and discarded, making it nearly impossible to go back and buy the same color or shade when you run out, and hex colors aren't at all accurate when you've got things like tri-color silk filaments. For that reason, I would like to suggest some minor changes to the json data structure, adding a couple key data points, and in addition keeping some consistency with what Bambu Studio uses

version: 1.x
protocol: openspool
color_hex: RRGGBBAA (add optional alpha channel data to be passed to the host machine, 00 = translucent color FF= solid color)
color_name: vendor's color name, i.e. "Burnt Titanium" or "
type: PLA (types listed in Bambu slicer)
min_temp:
max_temp:
brand: PolyLite (i.e. PolyLite, PolyTerra, Fiberon, Bambu, Flashforge, Voxel, Jayo, Inslogic, Sunlu, eSun, Generic) this is the value passed to the printer allow anything here, the printer should take anything it doesn't recognize as "Generic"
vendor: Polymaker (This seems redundant, but with brands such as Voxelab, one wouldn't know the actual vendor is Flashforge for example)
serial: basic, matte, silk, galaxy, glow, marble, HS, HF, Rapid (this is the field name designated in Bambu Studio for this info)
misc: miscellaneous data the end user wishes to record, could be amount on spool, drying temps and times, bed temp, volumetric flow rate, etc.

Obviously one could keep going on what data you wanted to record, but with only 492 bytes on most NFC chips, it obviously has to have some limits,