150:
color coordinates of the color in RGB, CMYK, HSV and Hex values. This is wholly incorrect. RGB values in themselves cannot depict color appearance. In order to do so, the RGB triplet has to be connected to physical reality through, at the minimum, the definition of the RGB color space used, the white point of the illuminant, and in certain cases, the gamma function. The ICC specifications can help one understand what these requirements are. If
Prussian Blue has such and such color coordinates, they have to be qualified as, for example, in AdobeRGB color space. Better still, linear XYZ color coordinates should be used. Furthermore the conversion of RGB to CMYK is wholly dependent on the particular transfer functions used for a specific set of inks and paper combination - the idea of posting the CMYK color coordinates for a physical color appearance is naïve at best and mostly preposterous.
158:
standards body are the ones that should be used. They won't be bound to the specific gamut of display color spaces such as sRGB. Many natural pigments fall completely outside the gamut of sRGB, and henceforth, your entire SRGB-normalized reference system collapses like a deck of cards. Being aware of the CIECAM02 model of color appearance would help convert the CIE coordinates into practical RGB values for users who wish to simulate naturally-occuring colors under specific constraints of illumination, and avoid some surprises with metameric behavior.
313:. For colorhexa, the RGB coords are the primary key and CIE just a conversion with fake accuracy. Handprint gives the pigment PB27, and "average CIECAM J,a,b values for iron blue (PB27) are: 19, -17, -36, with chroma of 40 (estimated hue purity of 45) and a hue angle of 245." The average across paints is great data, but handprint is a primary source and I don't know that it is considered a standard. If there is an authoritative source that is widely accepted as a standard across color-using industries and is accessible to us, let's use it. The
351:
converting RGB colors to CMYK. I won't say that CMYK is perfect or better than any other color system, but to refer to a system which is the lifeblood of an entire industry as "something of a disaster" and as "device-specific" (which would mean that, on top of multiple print houses houses having varying color outputs on a given layout, most print houses with more than a single printer would *also* experience this phenomenon) seems a bit disingenuous at best.
81:
63:
32:
395:
can be characterized by its frequency or wavelength, its peak amplitude, its phase relative to some reference phase, its direction of propagation, and its polarization. The whole purpose here must be to be able to use the name of a color in a meaningful way. If there are different ways of interpret "red", then it can not really be used for anything but poetry.
394:
It seems like the only way to specify a color in such a way that no matter how the color is produced, it should look, behave and have the exact same physicals attributes, is to specify the monochromatic parts of the electro magnetic waves that make up the color. A monochromatic electromagnetic wave
229:
a few times to end up here, and I'm not sure that this page is entirely appropriate as a link from mainspace articles - the presentation is geared very much towards colour value syntax conversion and says little about the infobox or values contained therein. Would anyone agree that we need a colour
157:
Use of sRGB as a connection space neutral ground for RGB triplets is laughable. When specifying colors that relate to the physical world, there are radiometric and photometric values one can use, that have been designed specifically for that. Photometric values such as those standardized by the CIE
499:
But wait! CSS Color Module 4 quite heavily promotes Oklab, which does improve on things like these weird blue-purple hues. The important point for computer people is that it does not add computational complexity like the CIE CAMs do, so they are going for it to be the next thing. Knowledge doesn't
304:
I agree, from a color science point of view, standardized color coordinates would best as the reference, with RGB, etc. conversions from the reference. But to do that, we need authoritative references for colors in terms of those standard coordinates. Instead, we have sources for
Prussian Blue, as
149:
As any formally trained color scientist would confirm, it is inappropriate to use unqualified color coordinates to specify a color appearance. In the color item articles, as I would guess all the other color-related articles, there is a box on the upper-right of the page that pretends to state the
495:
My understand is that HWB does not add much more to the existing HSV/sRGB situation, while the newfangled RGBs are cool but there are just too many of them. This leaves us with CIELAB and CIEXYZ, which aren't going to change anytime soon since they cover everything a human can see. And of these
350:
I won't claim to be the most learned on this aspect, but as I understand it, this is incorrect. In my multiple dealings with the print industry, color layouts are always requested to be submitted in CMYK both because of CMYK's palette consistency as well as the inherent shift that occurs when
164:
There is plenty of reference available on the subject, from books by
Billmeyer & Salzman for the less technically enclined, to more recent works. An authoritative source on the topic is definitely Prof. Mark Fairchild of the Munsell Color Science Laboratory in Rochester, NY.
366:
It is very device-specific in the same way "RGB" is. When you say CMYK there are unlimited ways to define what each ink-paper combination is, just as with RGB there's sRGB, Adobe RGB, P3, etc. The closest thing to a "universal" CMYK electronically is probably
153:
As such the article runs contrary to the most basic precepts of color science, and is wholly misleading to uninformed readers. Trying to digitally reproduce the appearance of
Prussian Blue using the information contained herein will not work at all.
340:
I know this article isn't a typical Wiki entry, but considering its explanatory purpose, shouldn't it still be held to the same content standards regarding the interjection of clear opinion and unverified claims? For example, you have this passage:
257:
In the section on HSV coordinates it states that a fully saturated color should be at 50% value as in the
Munsell system, but the example box shows a fully saturated orange with a value at 100%. Which is the preferred method for Knowledge?
191:
Web color is only very recently starting to be aware of the whole "sRGB not enough" idea. The only two useful things in the infoboxes are really sRGB (because it's the web and we got to display something, duh) and CIELCH(uv) .
345:
CMYK is generally something of a disaster, except as used in the internals of a printer driver. Unlike RGB, which is well-standardized as sRGB and which generally has a 1:1 mapping between coordinates and colors, CMYK is
248:, though it needs major work. I hope you don't mind that I used the American spelling, but figured it should match the spelling used by the infobox. 03:54, 9 May 2007 (UTC)
500:
really care about that (and might actually worry about whether it's a fad), but being able to stuff in a CSS color is nice. Do we choose it over CIELAB instead?
368:
212:
99:
584:
245:
589:
352:
107:
410:
226:
579:
525:
508:
431:
379:
200:
103:
17:
529:
512:
482:
435:
383:
360:
329:
298:
267:
238:
231:
204:
181:
473:
should definitely be added, since nowadays CSS Color Level 4 allows web designers to use any of these to specify a colour.--
43:
111:
88:
68:
371:
since almost every computer comes with one of their profiles, but numeric color charts don't always care for it.
356:
406:
263:
220:
402:
324:
49:
277:
I agree with
Ppanzini's remark above. Though RGB is useful for talking about colors on monitors, it is
259:
521:
504:
470:
427:
398:
375:
317:
is a standard in the textile industry, but I don't know that it extends beyond textiles. Thoughts? --
286:
282:
196:
169:
478:
173:
450:
420:
294:
177:
320:
518:
501:
446:
424:
372:
193:
490:
474:
235:
573:
290:
462:
80:
62:
545:
310:
225:
454:
390:
Define colors before trying to map them to different device-dependent systems
466:
458:
161:
As it currently is, the system used in
Knowledge is completely inadequate.
517:
Ah welp, we do have CIELCh(uv). Why are we going back to LAB again? --
562:
306:
496:
CIELAB is probably more intuitive, so we should go with just that.
94:
25:
281:
a complete, standardized color system. Why aren't we showing
314:
145:
Unqualified and inappropriate use of color coordinates
289:coordinates, which are complete and standard. --
92:, a project that provides a central approach to
8:
396:
57:
42:does not require a rating on Knowledge's
546:"Electromagnetic radiation - Wave model"
98:-related subjects on Knowledge. Help us
537:
59:
213:Knowledge:How to read a colour infobox
246:Knowledge:How to read a color infobox
7:
31:
29:
48:It is of interest to the following
244:I've started a draft of a page at
24:
224:
79:
61:
30:
18:Knowledge talk:WikiProject Color
232:Knowledge:How to read a taxobox
268:00:38, 28 September 2008 (UTC)
1:
483:09:48, 26 December 2022 (UTC)
361:22:58, 15 November 2021 (UTC)
585:NA-importance color articles
330:19:26, 20 January 2020 (UTC)
299:18:32, 20 January 2020 (UTC)
590:All WikiProject Color pages
120:Knowledge:WikiProject Color
606:
530:06:11, 28 March 2023 (UTC)
513:05:56, 28 March 2023 (UTC)
436:06:13, 28 March 2023 (UTC)
384:05:47, 28 March 2023 (UTC)
205:06:10, 28 March 2023 (UTC)
123:Template:WikiProject Color
86:This page is supported by
74:
56:
563:CSS Color Module Level 4
580:NA-Class color articles
239:16:27, 8 May 2007 (UTC)
442:Add more colour spaces
419:We are humans. We do
110:standards; visit the
253:Value and saturation
219:I've clicked on the
273:Why not CIE or NCS?
421:Metamerism (color)
44:content assessment
528:
511:
434:
414:
401:comment added by
382:
203:
187:
172:comment added by
142:
141:
138:
137:
134:
133:
114:for more details.
89:WikiProject Color
597:
565:
560:
554:
553:
542:
524:
507:
494:
430:
378:
346:device-specific.
328:
228:
199:
185:
166:
128:
127:
124:
121:
118:
112:wikiproject page
83:
76:
75:
65:
58:
35:
34:
33:
26:
605:
604:
600:
599:
598:
596:
595:
594:
570:
569:
568:
561:
557:
544:
543:
539:
488:
444:
392:
338:
336:Biased content?
318:
275:
255:
217:
167:
147:
125:
122:
119:
116:
115:
22:
21:
20:
12:
11:
5:
603:
601:
593:
592:
587:
582:
572:
571:
567:
566:
555:
536:
535:
534:
533:
532:
497:
443:
440:
439:
438:
391:
388:
387:
386:
353:107.77.204.154
337:
334:
333:
332:
274:
271:
254:
251:
250:
249:
216:
209:
208:
207:
146:
143:
140:
139:
136:
135:
132:
131:
129:
126:color articles
84:
72:
71:
66:
54:
53:
47:
36:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
602:
591:
588:
586:
583:
581:
578:
577:
575:
564:
559:
556:
551:
547:
541:
538:
531:
527:
523:
520:
516:
515:
514:
510:
506:
503:
498:
492:
487:
486:
485:
484:
480:
476:
472:
468:
464:
460:
456:
452:
448:
441:
437:
433:
429:
426:
422:
418:
417:
416:
412:
408:
404:
403:195.67.91.199
400:
389:
385:
381:
377:
374:
370:
365:
364:
363:
362:
358:
354:
348:
347:
342:
335:
331:
326:
322:
316:
312:
308:
305:for instance
303:
302:
301:
300:
296:
292:
288:
284:
280:
272:
270:
269:
265:
261:
252:
247:
243:
242:
241:
240:
237:
233:
227:
222:
221:color infobox
214:
210:
206:
202:
198:
195:
190:
189:
188:
183:
179:
175:
171:
162:
159:
155:
151:
144:
130:
113:
109:
105:
101:
97:
96:
91:
90:
85:
82:
78:
77:
73:
70:
67:
64:
60:
55:
51:
45:
41:
37:
28:
27:
19:
558:
549:
540:
463:ProPhoto RGB
445:
397:— Preceding
393:
349:
344:
343:
339:
315:Colour index
278:
276:
260:Justin Foote
256:
230:analogue of
218:
168:— Preceding
163:
160:
156:
152:
148:
102:articles to
93:
87:
50:WikiProjects
40:project page
39:
415:(2022 Apr)
321:Mark viking
574:Categories
455:Display P3
550:Knowledge
491:RekishiEJ
475:RekishiEJ
467:Rec. 2020
459:Adobe RGB
311:handprint
307:Colorhexa
236:Nihiltres
411:contribs
399:unsigned
291:Macrakis
182:contribs
174:Ppanzini
170:unsigned
519:Artoria
502:Artoria
425:Artoria
373:Artoria
194:Artoria
100:improve
471:CIEXYZ
451:CIELAB
186:, 2006
46:scale.
117:Color
95:color
69:Color
38:This
16:<
479:talk
469:and
423:. --
407:talk
369:SWOP
357:talk
325:Talk
323:}} {
319:{{u|
309:and
295:talk
285:and
264:talk
223:'s
178:talk
106:and
104:good
522:2e5
505:2e5
447:HWB
428:2e5
376:2e5
287:NCS
283:CIE
279:not
197:2e5
108:1.0
576::
548:.
526:🌉
509:🌉
481:)
465:,
461:,
457:,
453:,
449:,
432:🌉
413:)
409:•
380:🌉
359:)
297:)
266:)
234:?
201:🌉
192:--
184:)
180:•
552:.
493::
489:@
477:(
405:(
355:(
327:}
293:(
262:(
215:"
211:"
176:(
52::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
