Hi John,

In my "gifticlib 1.0.4: Label RGBA attributes" posting, I mention
that if one label has RGBA values, they all must. So as of Oct 27,
the gifticlib implementation requires either a complete color RGBA
listing or none at all.

Personally, I would rather not even allow ambiguity in the color
table. If we are going to forcibly attach colors to the data,
declaring the appropriate way to color the image, then I think the
color table should be complete.

---

A default color does not seem so reasonable to me. If the writing
program wants a default color, it should just write it to the table.
If the writing program is deciding on the coloring, there is no
reason why it should write it in an ambiguous way.

Also, that would remove one basic color from the color map. For
example, if we choose some sort of green as the default, then any
color close to that would make a user wonder whether that node/ROI
has the default color. It would effectively remove variants on
green from the color map.

---

A label that is not to be colored could be written with alpha=0, as
you noted. It makes more sense to me to define what is uncolored
based on the color value, rather than the label text. Of course,
either works.

---

A similar question is what to do for a node value that is not listed
in the label table. It would certainly make sense to not color it at
all. Maybe that should be considered an error case, too. Again, it
would be an incomplete colormap.

I guess my point is that if we are going to allow the writing program
to tell us how to color the image, there should be no ambiguity.

- rick