[Data-modeling] New properties for the "Visual Art" domain "Color" type

[John Giannandrea]

Ed Laurent wrote:
> Do you mean that a single set of sRGB palette objects would be added  
> as topics and each topic would have its "Also known as" common  
> property attributed with the names of objects from different  
> dictionaries? If so, this would result in the loss of a lot of  
> information such as the link to which dictionary includes the alias  
> pallet object.

If we want to represent that sRGB #80daeb is Crayola SkyBlue and  
#87ceeb is CSS3 skyblue then we have to decide if the name is the  
common topic or the sRGB value is.

If 'goldenrod' deosnt mean much semantically, 'azure' probably does  
and 'black' certainly does aspire to be a topic.

One option might be to have the sRGB topic defined by a particular  
value dominate and then have keys into various namespaces, /color/ 
crayola/skyblue

Alternatively we could endeavor to take the existing Azure topic /guid/ 
9202a8c04000641f8000000000385053 and add different properties for RGB  
or a compound value type that has the pair, sRGB and color  
dictionary.   I think this was where Faye was heading.

Your suggestion, if I understand it, is to make standalone topics even  
for the same sRGB triples but to have an explicit property that allows  
people to say that these are the same or corresponding colors?  I  
agree that that would most explicitly capture the arbitrary nature of  
this color matching.

-jg