color: hsl(0, 100%, 50%) } http://upload.wikimedia.org/wikipedia/commons/6/66/Eric-meyer.jpg /* red 

Eric-meyer.jpg (JPEG Image, 1024x767 pixels) - Scaled (70%) upload.wikimedia.org

via upload.wikimedia.org

Eric-meyer.jpg (JPEG Image, 1024x767 pixels) - Scaled (70%):www.creativecommons.org/licenses/by/2.0)], via Wikimedia Commons">

			aliceblue	#f0f8ff	240,248,255
		antiquewhite	#faebd7	250,235,215
		aqua	#00ffff	0,255,255
		aquamarine	#7fffd4	127,255,212
		azure	#f0ffff	240,255,255
		beige	#f5f5dc	245,245,220
		bisque	#ffe4c4	255,228,196
		black	#000000	0,0,0
		blanchedalmond	#ffebcd	255,235,205
		blue	#0000ff	0,0,255
		blueviolet	#8a2be2	138,43,226
		brown	#a52a2a	165,42,42
		burlywood	#deb887	222,184,135
		cadetblue	#5f9ea0	95,158,160
		chartreuse	#7fff00	127,255,0
		chocolate	#d2691e	210,105,30
		coral	#ff7f50	255,127,80
		cornflowerblue	#6495ed	100,149,237
		cornsilk	#fff8dc	255,248,220
		crimson	#dc143c	220,20,60
		cyan	#00ffff	0,255,255
		darkblue	#00008b	0,0,139
		darkcyan	#008b8b	0,139,139
		darkgoldenrod	#b8860b	184,134,11
		darkgray	#a9a9a9	169,169,169
		darkgreen	#006400	0,100,0
		darkgrey	#a9a9a9	169,169,169
		darkkhaki	#bdb76b	189,183,107
		darkmagenta	#8b008b	139,0,139
Media in category "Programmers" Show Slideshow The following 129 files are in this category, out of 129 total. 20060424 Nat Friedma... 2,011,026 bytes 20081103 Nate Parker... 1,597,830 bytes Adam Bosworth, Cedri... 271,829 bytes Adam leventhal.jpg 135,232 bytes Adam Nathan.jpg 2,188,049 bytes Alan hshieh.jpg 89,090 bytes Alanhshieh.jpg 156,682 bytes Alexandre Julliard 2... 114,602 bytes Alexandre Julliard.jpg 181,905 bytes Sam Altman in 2009.jpg 409,891 bytes Andrew Tridgell reci... 10,539 bytes Andrew Tridgell.jpg 446,549 bytes Anthony Towns.jpg 230,316 bytes Kent Beck 1.jpg 29,842 bytes BEich.jpg 79,334 bytes Bob Wallace 1977.jpg 255,226 bytes Bradfitzb2b.jpg 51,687 bytes Bram-cohen-codecon-2... 441,993 bytes Carl Albing.jpg 1,992,668 bytes Chris Blizzard1.jpg 148,338 bytes Chris-Blizzard-2010-... 46,125 bytes Chris-Blizzard-2010.jpg 630,576 bytes Chris-Blizzard.jpg 2,946,714 bytes ChuckMoore.jpg 37,214 bytes Dan Ingalls.jpg 49,351 bytes Dave Cross at UKUUG.jpg 59,298 bytes Davehaynie.jpg 26,673 bytes David Axmark at MySQ... 188,954 bytes via commons.wikimedia.org		darkolivegreen	#556b2f	85,107,47
		darkorange	#ff8c00	255,140,0
		darkorchid	#9932cc	153,50,204
		darkred	#8b0000	139,0,0
		darksalmon	#e9967a	233,150,122
		darkseagreen	#8fbc8f	143,188,143
		darkslateblue	#483d8b	72,61,139
		darkslategray	#2f4f4f	47,79,79
		darkslategrey	#2f4f4f	47,79,79
		darkturquoise	#00ced1	0,206,209
		darkviolet	#9400d3	148,0,211
		deeppink	#ff1493	255,20,147
		deepskyblue	#00bfff	0,191,255
		dimgray	#696969	105,105,105
		dimgrey data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAIAAACQd1PeAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAABhJREFUeF4FwTEBAAAAgjD7FzESWfjYdgwEoAJ4lTsaxgAAAABJRU5ErkJggg==	#696969	105,105,105
		dodgerblue	#1e90ff	30,144,255
		firebrick	#b22222	178,34,34
		floralwhite	#fffaf0	255,250,240
		forestgreen	#228b22	34,139,34
		fuchsia	#ff00ff	255,0,255
		gainsboro	#dcdcdc	220,220,220
		ghostwhite	#f8f8ff	248,248,255
		gold	#ffd700	255,215,0
		goldenrod	#daa520	218,165,32
		gray	#808080	128,128,128
		green	#008000	0,128,0
		greenyellow	#adff2f	173,255,47
		grey	#808080	128,128,128
		honeydew	#f0fff0	240,255,240
		hotpink	#ff69b4	255,105,180
		indianred	#cd5c5c	205,92,92
		indigo	#4b0082	75,0,130
		ivory	#fffff0	255,255,240
		khaki	#f0e68c	240,230,140
		lavender	#e6e6fa	230,230,250
		lavenderblush	#fff0f5	255,240,245
		lawngreen	#7cfc00	124,252,0
		lemonchiffon	#fffacd	255,250,205
		lightblue	#add8e6	173,216,230
		lightcoral	#f08080	240,128,128
		lightcyan	#e0ffff	224,255,255
		lightgoldenrodyellow	#fafad2	250,250,210
		lightgray	#d3d3d3	211,211,211
		lightgreen	#90ee90	144,238,144
		lightgrey	#d3d3d3	211,211,211
		lightpink	#ffb6c1	255,182,193
		lightsalmon	#ffa07a	255,160,122
		lightseagreen	#20b2aa	32,178,170
		lightskyblue	#87cefa	135,206,250
		on */The table below provides a list of the X11 colors [X11COLORS] supported by popular browsers with the addition of gray/grey variants from SVG 1.0. The resulting list is precisely the same as the SVG 1.0 color keyword names. This specification extends their definition beyond SVG. The two color swatches on the left illustrate setting the background color of a table cell in two ways: The first column uses the named color value, and the second column uses the respective numeric color value.	#778899	119,136,153
		lightslategrey	#778899	119,136,153
		lightsteelblue	#b0c4de	176,196,222
		lightyellow	#ffffe0	255,255,224
		lime	#00ff00	0,255,0
		limegreen	#32cd32	50,205,50
		linen	#faf0e6	250,240,230
		magenta	#ff00ff	255,0,255
		maroon	#800000	128,0,0
		mediumaquamarine	#66cdaa	102,205,170
		mediumblue	#0000cd	0,0,205
		mediumorchid	#ba55d3	186,85,211
		mediumpurple	#9370db	147,112,219
		mediumseagreen	#3cb371	60,179,113
		mediumslateblue	#7b68ee	123,104,238
		mediumspringgreen	#00fa9a	0,250,154
		mediumturquoise	#48d1cc	72,209,204
		mediumvioletred	#c71585	199,21,133
		midnightblue	#191970	25,25,112
		mintcream	#f5fffa	245,255,250
		mistyrose	#ffe4e1	255,228,225
		moccasin	#ffe4b5	255,228,181
		navajowhite	#ffdead	255,222,173
		navy	#000080	0,0,128
		oldlace	#fdf5e6	253,245,230
		olive	#808000	128,128,0
		olivedrab	#6b8e23	107,142,35
		orange	#ffa500	255,165,0
		orangered	#ff4500	255,69,0
		orchid	#da70d6	218,112,214
		palegoldenrod	#eee8aa	238,232,170
		palegreen	#98fb98	152,251,152
		paleturquoise	#afeeee	175,238,238
		palevioletred	#db7093	219,112,147
		papayawhip	#ffefd5	255,239,213
		peachpuff	#ffdab9	255,218,185
		peru	#cd853f	205,133,63
		pink	#ffc0cb	255,192,203
		plum	#dda0dd	221,160,221
		powderblue	#b0e0e6	176,224,230
		purple	#800080	128,0,128
		red	#ff0000	255,0,0
		rosybrown	#bc8f8f	188,143,143
		royalblue	#4169e1	65,105,225
		saddlebrown	#8b4513	139,69,19
		salmon	#fa8072	250,128,114
		sandybrown	#f4a460	244,164,96
		seagreen	#2e8b57	46,139,87
		seashell	#fff5ee	255,245,238
		sienna	#a0522d	160,82,45
		silver	#c0c0c0	192,192,192
		skyblue	#87ceeb	135,206,235
		slateblue	#6a5acd	106,90,205
		slategray	#708090	112,128,144
		slategrey	#708090	112,128,144
		snow	#fffafa	255,250,250
		springgreen	on */The table below provides a list of the X11 colors [X11COLORS] supported by popular browsers with the addition of gray/grey variants from SVG 1.0. The resulting list is precisely the same as the SVG 1.0 color keyword names. This specification extends their definition beyond SVG. The two color swatches on the left illustrate setting the background color of a table cell in two ways: The first column uses the named color value, and the second column uses the respective numeric color value.	0,255,127
		steelblue	#4682b4	70,130,180
		tan	#d2b48c	210,180,140
		teal	#008080	0,128,128
		thistle	#d8bfd8	216,191,216
		tomato	#ff6347	255,99,71
		turquoise	#40e0d0	64,224,208
		violet	#ee82ee	238,130,238
		wheat	#f5deb3	245,222,179
		white	#ffffff	255,255,255
		whitesmoke	#f5f5f5	245,245,245
		yellow	#ffff00				yellowgreen

20060424 Nat Friedma...
2,011,026 bytes

20081103 Nate Parker...
1,597,830 bytes

Adam Bosworth, Cedri...
271,829 bytes

Adam leventhal.jpg
135,232 bytes

Adam Nathan.jpg
2,188,049 bytes

Alan hshieh.jpg
89,090 bytes

Alanhshieh.jpg
156,682 bytes

Alexandre Julliard 2...
114,602 bytes

Alexandre Julliard.jpg
181,905 bytes

Sam Altman in 2009.jpg
409,891 bytes

Andrew Tridgell reci...
10,539 bytes

Andrew Tridgell.jpg
446,549 bytes

Anthony Towns.jpg
230,316 bytes

Kent Beck 1.jpg
29,842 bytes

BEich.jpg
79,334 bytes

Bob Wallace 1977.jpg
255,226 bytes

Bradfitzb2b.jpg
51,687 bytes

Bram-cohen-codecon-2...
441,993 bytes

Carl Albing.jpg
1,992,668 bytes

Chris Blizzard1.jpg
148,338 bytes

Chris-Blizzard-2010-...
46,125 bytes

Chris-Blizzard-2010.jpg
630,576 bytes

Chris-Blizzard.jpg
2,946,714 bytes

ChuckMoore.jpg
37,214 bytes

Dan Ingalls.jpg
49,351 bytes

Dave Cross at UKUUG.jpg
59,298 bytes

Davehaynie.jpg
26,673 bytes

{ color: hsl(120, 100%, 50%) } /* lime */ * { color: hsl(120, 100%, 25%) } /* dark green */ * { color: hsl(120, 100%, 75%) } /* light green */ * { color: hsl(120, 75%, 75%) } /*

David Axmark at MySQ...
188,954 bytes

via commons.wikimedia.org

color: hsl(0, 100%, 50%) } http://upload.wikimedia.org/wikipedia/commons/6/66/Eric-meyer.jpg /* red  Eric-meyer.jpg (JPEG Image, 1024x767 pixels) - Scaled (70%) upload.wikimedia.org via upload.wikimedia.org Eric-meyer.jpg (JPEG Image, 1024x767 pixels) - Scaled (70%): www.creativecommons.org/licenses ...»See Ya

Allow <figure> where <img> is allowed, in <p> in particular

Written by Henri Sivonen with contributions from Leif Halvard Silli (add your name here if you edit the wiki page).

Summary

The proposed change is making it possible (and conforming) for authors to use <figure> where <img> can be used. In particular, with this change, it becomes possible to use <figure> as the first child of <p>, which is useful for floating figures.

Contents [hide] 1 Allow <figure> where <img> is allowed, in <p> in particular 1.1 Summary 1.2 Rationale 1.3 Details 1.4 Impact 1.4.1 Positive Effects 1.4.2 Negative Effects 1.4.3 Conformance Classes Changes 1.4.4 Risks 1.5 References

Rationale

Currently, HTML5 makes it impossible to for HTML authors to use <figure> as a child of <p>, because <figure> automatically closes <p> in the tree builder.

This is bad for authors on the conceptual level, because <figure> is primarily supposed to be a way to express images that have a caption, so being unable to use <figure> in places where <img> can be used is conceptually confusing.

This is bad for authors on the pragmatic level, because given the CSS features available to authors currently and in the foreseeable future, the easiest way to make the top edge of a float align with the top edge of the text in a block regardless of margin/padding/border on the block box is to place the float as the first child of the block. That is, one would want to place <figure> as the first child of <p> when making a floating figure associated with a paragraph. Floating figures are the typical expected use for <figure>.

For <figure> to be useful to authors, it is essential to make it easy to use <figure> where <img> can be used and, in particular, to make it easy to use floating figures within the practical constraints arising from the CSS formatting model as it is available to authors today.

The above is the rationale for making it conforming to use <figure> where <img> is conforming and the rationale for making <figure> not automatically close <p>.

However, making only those changes would make things confusing, because non-image figures, such as blocks of preformatted code marked up using the <pre> element, would automatically close <p>, and some kinds of figures couldn't be used inside <p> elements. This would be inconsistent and confusing. The problem is fixed by making <figure> prevent <p> autoclosing across it like <button>.

When <figure> prevents <p> autoclosing across it like <button>, it becomes unnecessary to propose that <figcaption> be made not close <p>. Hence, this proposal leaves <figcaption> as an element that autocloses <p>. (If <figure> become like <button>, it would be necessary to propose that <figcaption> not close <p>, either.)

Please note that this Change Proposal explicitly doesn't attempt to enforce any particular authoring practice. Instead, for pragmatic reasons, considering the Priority of Constituencies, this Change Proposal puts Authors ahead of Theoretical Purity by giving authors more options even if the options given could be viewed as possibilities for Authors to opt to violate Separation of Concerns.

Details

1. In the section The figure element, change "Flow content" under "Categories" to "Embedded content", change "flow content" under "Contexts in which this element can be used" to "embedded content" and in the text "The figure element represents some flow content" change "flow content" to "embedded content".
2. In the definition of have an element in button scope, add an item "figure in the HTML namespace" to the list.
3. In the Parsing HTML Documents section, replace all occurrences of "in button scope" with "in button or figure scope".
4. In the "in body" insertion mode, remove "figure" from the start tag token entry that now lists it. (To make <figure> behave like any other start tag. The end tag entry is left as is intentionally.)

Impact

Positive Effects

Legacy compatibility

Same way parsing → <p><figure><img><figcaption>Lorem ipsum</figcaption></figure>Dolor sit amet</p> would parse the same way in legacy browsers and HTML5-compliant browsers.

Authoring

Simple and logical floats → using the figure element as a child of the p element and float the figure box so that its top edge aligns with the top edge of the first line box in the p box regardless of the margin/padding/border on the p element. This is not only a practical thing – it might be entirely logical to place the image inside the p.

Simple logics = simple image captioning → to allow the figure element with img and figcaption as its children wherever the img element can be used is intuitive considering that figure is primarily a mechanism for attaching a caption to an img. It is difficult to answer the question why an image may have caption when it is placed outside a p, but not when it is placed inside a p.

Images and other figures are aligned → Once authors no longer care about browsers that don't implement this Change Proposal, authors will be able to use the figure element wherever an img element could be used regardless of the children of figure, which is intuitive. The figure element itself tells us that anything can be a figure, even ASCII art - it is not limited to embedded exterenal resources. This makes it difficult to explain, for example why one is permitted to place a “real”, embedded image inside a p, but not permitted to place an ASCII image inside a p.

Float anything, caption anything & anywhere → Once authors no longer care about browsers that don't implement this Change Proposal, the change proposed here would repair some of the damage caused by Acid2 and make it possible to put a floating table inside a p by placing the table as a child of figure and floating the figure.

Accessibility

Permission to use block elements inside object → HTML5 (unlike HTML4) currently considers the following as illegal nesting of p inside p: <p>Lorem <object data=foo ><p>Currently illegal nesting</p></object> Dolor.<p> This change proposal would offer an alternative way, which explicitly would separate the p's from one anothyer, namely the option to wrap the object inside a figure element:
<p>Lorem <figure><object data=foo ><p>Would become legal</p></object></figure> Dolor.</p>. (Note: This positive effect would a side effect of adopting this change proposal, but it would be possible to achieve the effect simply by modifying the conformance definition for the children of object independently of figure.)

Captions → The ability of an image to have a caption regardless of whether the image appeaers inside or outside a p element, is a positive thing for accessibility.

Negative Effects

• <p><figure><pre>Code example</pre><figcaption>Lorem ipsum</figcaption></figure>Dolor sit amet</p> (where pre is an example of any element that autocloses p) will parse sensibly in HTML5-compliant browsers but will fail to Degrade Gracefully in legacy browsers. Thus, the change being proposed would reach its full utility only once legacy browsers have faded away. (Authors could hack around this by writing <p><figure><figcaption>Lorem ipsum</figcaption></figure>Dolor sit amet</p>.)

Conformance Classes Changes

User agents (that support the text/html syntax) and HTML conformance checkers would have to change. Authoring tools that wish to support the full range of conforming documents would have to change, but authoring tools that don't wish to support the authoring of all possible conforming document wouldn't need to change.

Risks

The listed negative effect may cause author confusion as long as HTML5-incompliant user agents have a noticeable installed base. However, the negative effect would be no more confusing than <p>foo<section><p>bar</p></section><p>baz</p>.

A notable user agent (Chrome 7?) might ship without an implementation of this Change Proposal, which would cause confusion.

References

• ISSUE-128
• Bug 10589

via w3.org

Allow

where is allowed, in

in particular Written by Henri Sivonen with contributions from Leif Halvard Silli (add your name here if you edit the wiki page) . Summary The proposed change is making it possible (and conforming) for authors to use

where can be used. In ...»See Ya

via books.google.com

via books.google.com ...»See Ya

W3C Semantic Web Logos and Policies

Semantic Web Logos
(png, gif, svg, eps)	(png, gif, svg, eps)
Semantic Web Cube Alone and with "Semantic Web"
(png, gif, svg)	(png, gif, svg)	(png, gif, svg)

The three sides of the tri-color cube in these logos evoke the triplet of the RDF model. The peeled back lid invites you to Open Your Data to the Semantic Web!

W3C anticipates using the Semantic Web cube in conjunction with other imagery related to the Semantic Web.

2. W3C Semantic Web Technology Buttons

GRDDL	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)
OWL	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)
POWDER	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)
RDF	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)
RDFa	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)
RIF	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)
SKOS	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)
SPARQL	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)	(png, gif, svg)

3. Usage

These policies were adopted on 2 November 2007 based on feedback from the community.

Semantic Web Logos and Technology Buttons that include "W3C"

Not-for-profit use is governed by the W3C Document License with the following exceptions:

• For the Semantic Web logos (horizontal and vertical), logo size MAY be changed without permission.
• For the Technology Buttons, logo size, foreground, and background colors of the technology name MAY be modified without permission.
• On the Web, the Semantic Web logos MUST link to <http://www.w3.org/2001/sw/>
• On the Web the Technology Buttons MAY link anywhere, but W3C suggests the following URIs:
  • GRDDL Button: <http://www.w3.org/2001/sw/grddl-wg/>
  • RDF Button: <http://www.w3.org/RDF/>
  • SPARQL Button: <http://www.w3.org/2001/sw/DataAccess/>
  • OWL Button: <http://www.w3.org/2004/OWL/>
  • POWDER Button: <http://www.w3.org/2007/powder/>
  • RDFa Button: <http://www.w3.org/2006/07/SWD/>

For-profit use of these logos REQUIRES permission from W3C. Please send requests to w3t-pr@w3.org.

Semantic Web Cube alone and with "Semantic Web" (no W3C logo)

Use is governed by the W3C Document License with the following exceptions:

• Logo size, foreground, and background colors of the technology name MAY be modified without permission.
• When these logos are used on the Web, attribution is REQUIRED using any of the following techniques (possibly in combination):
  • The "alt" text of the image must be "W3C Semantic Web Logo", or
  • For the SVG version of the logo, using the original metadata provided by W3C in the logo souce code, or
  • The logo must link to the W3C Web site using the following URI: <http://www.w3.org/2001/sw/>
• In the case of attribution without using a link, the logos MAY link anywhere, but we suggest using <http://www.w3.org/2001/sw/>

4. Frequently Asked Questions (FAQ)

1. Why has W3C developed the Semantic Web logos?

Until now W3C has not had a high-level representation of the Semantic Web. Previous logos (such as the RDF logo) represented individual technologies. The new technology-specific buttons have been designed to be part of the Semantic Web brand. As we move forward, we are likely to create and use more specific imagery for some of the technologies that make up the Semantic web, e.g., for T-shirts or mugs. In that context, we are likely to use familiar blue RDF triple.

2. May I change the foreground and background colors of the text in the Technology buttons?

Yes.

3. May I change the cube colors?

If there is a "W3C" in the logo, no. Otherwise, yes.

4. May I change the size of all of the above logos?

Yes.

5. May I change the foreground or background color of the W3C logo?

No.

6. May I create a local copy of a Semantic Web logo or button?

Yes. If you make local copies, you should check periodically for updates from W3C (e.g., to account for small changes or new formats).

7. Why did you use the W3C Document License rather than a Creative Commons license?

Our goal is to allow certain types of derivative works (changes in size, colors) and to require attribution in a certain way (alt text or a specific URI). It is not clear from the Creative Commons Web site whether we can use a Creative Commons license to achieve this. On the one hand, we find, for example for "by-nd" this text: "You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work)." However, in section 4(b) of the detailed licensing terms, we find: "The credit required by this Section 4(b) may be implemented in any reasonable manner;...." which seems to be in contradiction with (or at least more permissive than) the first assertion.

The W3C Document License is very similar to "by-nd", and adding a constraint on not-for-profit use is similar to "by-nc-nd." If we learn more and there turns out not to be a contradiction, we may also start to use the appropriate Creative Commons license in this policy.

8. What are the Pantone values for the three colors of the cube?

• Green: 368 C
• Orange: 165 C
• Magenta: 2395 C

via w3.org

The three sides of the tri-color cube in these logos evoke the triplet of the RDF model. The peeled back lid invites you to Open Your Data to the Semantic Web! W3C anticipates using the Semantic Web cube in conjunction with other imagery related to the Semantic Web. 2. W3C Semantic Web Technology Bu ...»See Ya