|
| 1 | +************** |
| 2 | +Global structure |
| 3 | +*************** |
| 4 | +* Each .src document should contain head, body, title, and link tags |
| 5 | + to the next .src file to be printed. |
| 6 | + |
| 7 | + |
| 8 | +* The TOC and Indexes will be generated by the magic scripts of ALH. |
| 9 | + The DTD fragments that appear in the body of the specification will |
| 10 | + have links from attribute names to their definitions. |
| 11 | + |
1 | 12 | * It's ok to use <TABLE>. |
2 | 13 |
|
3 | 14 | * It's ok to include GIF files in the spec. |
|
7 | 18 | Properties |
8 | 19 | ************ |
9 | 20 |
|
10 | | -* To mark up property definitions: |
| 21 | +* To mark up property definitions. For a property named "propname", use: |
11 | 22 |
|
12 | 23 | <DIV class="propdef"> |
13 | | - <Hn class="propname">'prop-name'</Hn> |
14 | | - <TABLE> |
15 | | - <TR><TH><em>Value:</em><TD>...</TR> |
16 | | - <TR><TH><em>Initial:</em><TD>...</TR> |
17 | | - <TR><TH><em>Applies to:</em><TD>...</TR> |
18 | | - <TR><TH><em>Inherited:</em><TD>...</TR> |
19 | | - <TR><TH><em>Percentage values:</em><TD>...</TR> |
| 24 | + <Hn class="propname"><span class="index-def">'propname'</a></Hn> |
| 25 | + (generates <a name="propdef-propname"> </a>) |
| 26 | + <TABLE class="propinfo"> |
| 27 | + <TR><TH>Property name:<TD>...</TR> |
| 28 | + <TR><TH>Value:<TD>...</TR> |
| 29 | + <TR><TH>Initial:<TD>...</TR> |
| 30 | + <TR><TH>Applies to:<TD>...</TR> |
| 31 | + <TR><TH>Inherited:<TD>...</TR> |
| 32 | + <TR><TH>Percentage values:<TD>...</TR> |
20 | 33 | </TABLE> |
21 | 34 | </DIV> |
22 | 35 |
|
| 36 | + Can we generated section numbers in front of 'propname' (printed |
| 37 | + and electronic): Arnaud says yes. |
| 38 | + |
| 39 | + - An index will be generated from the property definitions. |
| 40 | + - Property names will also appear in the TOC. They may be |
| 41 | + abbreviated (e.g., "border-*" -> border properties). They may |
| 42 | + be listed in a paragraph (not a vertical list). |
| 43 | + - Therefore: Two links will be generated: one in the index, one in the TOC. |
| 44 | + |
23 | 45 | * To mark up property instances: |
24 | 46 |
|
25 | | - <span class="propinst">'prop-name'</span> |
| 47 | + <span class="propinst">'propname'</span> |
26 | 48 |
|
| 49 | + - Property instances will link to the definitions. |
27 | 50 |
|
28 | 51 | ************ |
29 | | -Concept index markup |
| 52 | +Value types |
30 | 53 | ************ |
| 54 | +There are three types of value types: |
| 55 | +(1) Key words |
| 56 | +(2) Basic |
| 57 | +(3) Other |
31 | 58 |
|
32 | | -* To mark up terms for the concept index, use several classes: |
| 59 | +Each Value specification in a property definition will include |
| 60 | +some combination of these three. |
33 | 61 |
|
34 | | - concept-index: Indicates that the term belongs in the index |
| 62 | + - Basic values will be delimited by single <'s. (E.g., <length>) |
| 63 | + and will link to their definitions in syndata.src |
35 | 64 |
|
36 | | - The second class may be either "def" or "inst", for whether |
37 | | - the occurrence is the defining instance of a term or just an |
38 | | - instance of use. |
| 65 | + - Other values will be defined below the property definition. They |
| 66 | + will be indicated by single "<'s" *and* |
| 67 | + by <em>. They will link to their definitions. |
39 | 68 |
|
40 | | - The third class will be the term to use in the index. |
| 69 | +MarkUp all value definitions with: |
41 | 70 |
|
42 | | - [Subsequent class names indicate Nth level index entries] |
| 71 | + <span class="value-def">value</span> |
| 72 | + |
| 73 | +MarkUp all value instances with |
| 74 | + |
| 75 | + <span class="value-inst">value</span> |
| 76 | + |
| 77 | +************ |
| 78 | +Indexes |
| 79 | +************ |
| 80 | +* <span> will be used to markup the source. Index entries will |
| 81 | + be generated from this markup. |
43 | 82 |
|
44 | | - <span class="concept-index, inst, cascade">cascading stuff</span> |
| 83 | +* One class name will be used to specify which index the information |
| 84 | + is destined for and whether an entry is the defining instance. |
| 85 | + For the CSS2 spec: |
45 | 86 |
|
46 | | - [The value of the SPAN element will not be used?] |
| 87 | + index-def |
| 88 | + index-inst |
| 89 | + |
| 90 | +* If the title attribute is not set, the span content goes in the |
| 91 | + index (alphabetized) and links to the marked-up source. |
| 92 | + |
| 93 | +* If the title attribute is set, it becomes the index entry key. The |
| 94 | + attribute value may be a comma-separated list of index keys. |
| 95 | + |
| 96 | +For example: |
| 97 | +-- |
| 98 | + <span title="word-spacing, definition of" |
| 99 | + class="index-def">Word spacing is defined as ...</span> |
| 100 | + |
| 101 | + <span title="word-spacing, use with blah" |
| 102 | + class="index-inst">In the context of blah blah, |
| 103 | + word spacing ...</span> |
| 104 | + |
| 105 | + Discussion of <span class="index-inst">foo bar</span> |
| 106 | +-- |
| 107 | +* Generated anchors: |
| 108 | + |
| 109 | + The "name" used for anchors and links may be generated numbers since |
| 110 | + each link only refers to one anchor. |
| 111 | + |
| 112 | +* For index keys that point to several locations in the spec, the |
| 113 | + formatting of the keys in the spec must be considered. |
47 | 114 |
|
48 | 115 | ************ |
49 | 116 | Examples |
50 | 117 | ************ |
51 | 118 | * In accordance with the HTML spec, use uppercase for |
52 | | - element names and lowercase for attribute names. |
53 | | - |
54 | | - |
| 119 | + HTML element names and lowercase for HTML attribute names. |
| 120 | + |
| 121 | +<div class="example"><P> |
| 122 | +<pre> |
| 123 | +... |
| 124 | +</pre> |
| 125 | +</div> |
| 126 | + |
| 127 | +Deprecated examples should be as follows: |
| 128 | + |
| 129 | +<div class="deprecated-example"><P> |
| 130 | +<span class="example-title">DEPRECATED EXAMPLE:</span><br> |
| 131 | +<pre> |
| 132 | +... |
| 133 | +</pre> |
| 134 | +</div> |
| 135 | + |
| 136 | +Illegal examples should be as follows: |
| 137 | + |
| 138 | +<div class="illegal-example"><P> |
| 139 | +<span class="example-title">ILLEGAL EXAMPLE:</span><br> |
| 140 | +<pre> |
| 141 | +... |
| 142 | +</pre> |
| 143 | +</div> |
| 144 | + |
| 145 | +<div class="note"><P> |
| 146 | +<em><strong>Note.</strong> ...</em> |
| 147 | +</div> |
| 148 | + |
| 149 | +********** |
| 150 | +References |
| 151 | +********** |
| 152 | +* References. *All* references to WWW pages, books, etc. will appear in |
| 153 | +a single file: ref/references.src. Each reference entry will contain |
| 154 | +an anchor whose name has the prefix "ref-". If the reference is to a |
| 155 | +document online, the URL of the document will be displayed as well |
| 156 | +as linked to (for printing). |
| 157 | + |
| 158 | +All references within the rest of the specification will point to |
| 159 | +the appropriate entry in references.src. These links should have the |
| 160 | +following syntax: |
| 161 | + |
| 162 | + <a rel="biblioentry" |
| 163 | + href="<path>/ref/references.html#ref-SYMBOL"</a>[SYMBOL]</a> |
| 164 | + |
| 165 | +********** |
| 166 | +Document HEAD |
| 167 | +********** |
| 168 | + |
| 169 | +<!DOCTYPE HTML SYSTEM "http://www.w3.org/TR/WD-html40/sgml/HTML4.dtd"> |
| 170 | +<html lang="en"> |
| 171 | +<!-- $Id: CONVENTIONS,v 1.2 1997-07-29 17:14:16 ijacobs Exp $ --> |
| 172 | +<HEAD> |
| 173 | +<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> |
| 174 | +<TITLE>CSS2 Specification</TITLE> |
| 175 | +<LINK rel="next" href="?.html"> |
| 176 | +<LINK rel="previous" href="?.html"> |
| 177 | +<LINK rel="STYLESHEET" href="style/default.css" type="text/css"> |
| 178 | +</HEAD> |
| 179 | +<BODY> |
| 180 | +<H1 align="center">CSS2 Specification</H1> |
| 181 | +</BODY> |
| 182 | +</HTML> |
55 | 183 |
|
0 commit comments