[cssom] (1) add copy of (minimal) anolis xref/ref data to ensure accurate data as required by cssom;

(2) elaborate CSS rule serialization rules for style and charset rules;

Author: skynavga

cssom/Overview.html

@@ -1181,11 +1181,11 @@
 
    <li>
     <p>When the resource is available, the document is in
-    <span data-anolis-spec=dom title=concept-quirks-mode>quirks mode</span>
+    <span data-anolis-spec=html>quirks mode</span>
     and the
-    <span data-anolis-spec=html>Content-Type metadata</span> of
+    <span data-anolis-spec=html title="content-type">Content-Type metadata</span> of
     the resource is not a <span>supported styling language</span> change the
-    <span data-anolis-spec=html>Content-Type metadata</span> of the resource
+    <span data-anolis-spec=html title="content-type">Content-Type metadata</span> of the resource
     to <code>text/css</code>.</p>
 
     <p class="note">This step might never actually happen, but is included
@@ -1259,10 +1259,10 @@
    <span data-anolis-spec=html>fetch</span> it.</p></li>
 
    <li><p>When the resource is available, the document is in
-   <span data-anolis-spec=dom title=concept-quirks-mode>quirks mode</span>
-   and the <span data-anolis-spec=html>Content-Type metadata</span> of
+   <span data-anolis-spec=html>quirks mode</span>
+   and the <span data-anolis-spec=html title="content-type">Content-Type metadata</span> of
    the resource is not a <span>supported styling language</span> change the
-   <span data-anolis-spec=html>Content-Type metadata</span> of the resource
+   <span data-anolis-spec=html title="content-type">Content-Type metadata</span> of the resource
    to <code>text/css</code>.</p></li>
 
    <li><p>If the resource is not in a
@@ -1340,21 +1340,40 @@
   <p class="issue">Should a rule be instantiated in OM if there is a parse error? To
   what extent should original (but non-valid) CSS text be captured in cssText?</p>
 
-  <p>To <dfn>serialize a CSS rule</dfn> depends on the type of CSS rule, as
-  follows:</p>
+  <p>To <dfn>serialize a CSS rule</dfn>, perform one of the following in accordance with the its <span>rule type</span>:</p>
 
   <dl class="switch">
    <dt><code>CSSStyleRule</code></dt>
-   <dd><p class="issue">...</p></dd>
+   <dd>
+    <p>The result of concatenating the following:</p>
+    <ol>
+     <li>The result of performing <span>serialize a group of selectors</span> on the rule's associated selectors.</li>
+     <li>The string "<code> { </code>", i.e., a single SPACE (U+0020), followed by LEFT CURLY BRACKET (U+007B),
+     followed by a single SPACE (U+0020).</li>
+     <li>The result of performing <span>serialize a CSS declaration block</span> on the rule's associated declarations.</li>
+     <li>If the rule is associated with one or more declarations, the string "<code> </code>", i.e., a single SPACE (U+0020).</li>
+     <li>The string "<code>}</code>", RIGHT CURLY BRACKET (U+007D).
+    </ol>
+   </dd>
 
    <dt><code>CSSCharsetRule</code></dt>
-   <dd><p class="issue">...</p></dd>
+   <dd>
+    <p>The result of concatenating the following:</p>
+    <ol>
+     <li>The string "<code>@charset</code>" followed by a single SPACE (U+0020).</li>
+     <li>The result of performing <span>serialize a string</span> on the <span data-anolis-spec=html>preferred MIME name</span> of the rule's encoding.</li>
+     <li>The string "<code>;</code>", i.e., SEMICOLON (U+003B).
+    </ol>
+    <div class="example">
+    <pre>@charset "UTF-8";</pre>
+    </div>
+   </dd>
 
    <dt><code>CSSImportRule</code></dt>
    <dd>
-    <p>The result of concatenating these strings:</p>
+    <p>The result of concatenating the following:</p>
     <ol>
-     <li>The literal string "<code>@import</code>", followed by a single SPACE
+     <li>The string "<code>@import</code>" followed by a single SPACE
      (U+0020), followed by the <span title="serialize a URL">URL escaped</span>
      value of the <code title="dom-CSSImportRule-href">href</code>
      attribute.</li>

cssom/cssom-source

@@ -0,0 +1,45 @@
+{
+  "CSS" : {
+    "href" : "http://www.w3.org/TR/CSS2/",
+    "title" : "CSS",
+    "authors" : ["Bert Bos", "Tantek Çelik", "Ian Hickson", "Håkon Wium Lie"],
+    "publisher" : "W3C"
+  },
+  "DOM" : {
+    "href" : "http://dom.spec.whatwg.org/",
+    "oldhref" : "http://www.w3.org/TR/domcore/",
+    "title" : "DOM",
+    "authors" : ["Anne van Kesteren", "Aryeh Gregor", "Ms2ger"],
+    "publisher" : "WHATWG"
+  },
+  "DOM2STYLE" : {
+    "href" : "http://www.w3.org/TR/DOM-Level-2-Style/",
+    "title" : "Document Object Model (DOM) Level 2 Style Specification",
+    "authors" : ["Chris Wilson", "Philippe Le Hégaret", "Vidur Apparao"],
+    "publisher" : "W3C"
+  },
+  "HTML" : {
+    "href" : "http://www.whatwg.org/specs/web-apps/current-work/multipage/",
+    "title" : "HTML",
+    "authors" : ["Ian Hickson"],
+    "publisher" : "WHATWG"
+  },
+  "RFC2119" : {
+    "href" : "http://tools.ietf.org/html/rfc2119",
+    "title" : "Key words for use in RFCs to Indicate Requirement Levels",
+    "authors" : ["Scott Bradner"],
+    "publisher" : "IETF"
+  },
+  "XML" : {
+    "href" : "http://www.w3.org/TR/xml/",
+    "title" : "Extensible Markup Language",
+    "authors" : ["Tim Bray", "Jean Paoli", "C. M. Sperberg-McQueen", "Eve Maler", "François Yergeau"],
+    "publisher" : "W3C"
+  },
+  "XMLSS" : {
+    "href" : "http://www.w3.org/TR/xml-stylesheet/",
+    "title" : "Associating Style Sheets with XML documents 1.0 (Second Edition)",
+    "authors" : ["James Clark", "Simon Pieters", "Henry S. Thompson"],
+    "publisher" : "W3C"
+  }
+}

cssom/data/references.json

@@ -0,0 +1,6 @@
+{
+  "dom": "dom/dom.json",
+  "html": "dom/html.json",
+  "xml": "dom/xml.json",
+  "xmlss": "dom/xmlss.json"
+}

cssom/data/specs.json

@@ -0,0 +1 @@
+{ "definitions": {}, "url": "http://dvcs.w3.org/hg/csswg/raw-file/tip/cssom/Overview.html#" }