Update: Make Object and Content emphasized and add some abbreviations.

Make Object and Content emphasized for cases where Object and Content are used by themselves.

Designate the HTML5 as an abbreviation in the same way HTML is.

diff --git a/documentation/fake/specifications/fakefile.html b/documentation/fake/specifications/fakefile.html
index d40f69350ed84ece87f341accb0924f8915433c3..d35143b66b823904caaa5f3c1b20da12b43474c2 100644 (file)
--- a/documentation/fake/specifications/fakefile.html
+++ b/documentation/fake/specifications/fakefile.html
@@ -105,7 +105,7 @@
               A <strong class="strong">fakefile</strong> is broken up into multiple Basic Lists, referred to as Sections, with two special purpose reserved Sections.
             </p>
             <p class="p">
-              The Sections are broken up into multiple Extended Objects and their respective Contents, referred to as Section Operations.
+              The Sections are broken up into multiple Extended Objects and their respective <em class="em">Contents</em>, referred to as Section Operations.
             </p>
             <p class="p">
               Each of these non-reserved Sections acts as a set to perform some set of Section Operations.

diff --git a/fll/specifications.html b/fll/specifications.html
index bb938078a6efe6bde47169379199e3774bf5d448..cf88c0a04397afdaa4bafac39de98c28bedb10ae 100644 (file)
--- a/fll/specifications.html
+++ b/fll/specifications.html
@@ -183,7 +183,7 @@
               <ul>
                 <li>Will consist of numerous different kinds of specification files, depending on the type of information stored.</li>
                 <li>As with the practice of "<code class="code">#!/bin/bash</code>", the setting files <em class="em">should</em> have the following: "<code class="code"># fss-????" format, such as "# FSS-0001</code>".</li>
-                <li>Multiple sub-standards may be appended to the <abbr title="Featureless Settings Specifications">FSS</abbr> header, using the same format structure, such as supporting IKI: "# fss-0000 iki-0000" or HTML5: "# fss-0000 html-0005".</li>
+                <li>Multiple sub-standards may be appended to the <abbr title="Featureless Settings Specifications">FSS</abbr> header, using the same format structure, such as supporting IKI: "# fss-0000 iki-0000" or <abbr title="Hyper Text Markup Language 5">HTML5</abbr>: "# fss-0000 html-0005".</li>
                 <li>With the <code class="code">?</code> representing the (hexadecimal/base-16) number that represents the particular specification structure.</li>
                 <li>All settings specifications <em class="em">should</em> avoid any form of noise, relative to the data being stored.</li>
                 <li><abbr title="Extensible Markup Language">XML</abbr> would be considered anti-<abbr title="Keep It Simple Stupid">KISS</abbr> due to the extreme level of noise generated by the <abbr title="Extensible Markup Language">XML</abbr> language (not easy to read).</li>
@@ -196,28 +196,28 @@
               <dl class="dl">
                 <div class="di">
                   <dt class="dt"><strong class="strong">Object</strong></dt>
-                  <dd class="dd">Considered the name or identifier of some property or data. Objects do not require an associated <em class="em">Content</em>.</dd>
+                  <dd class="dd">Considered the name or identifier of some property or data. <em class="em">Objects</em>; do not require an associated <em class="em">Content</em>.</dd>
                 </div>
                 <div class="di">
                   <dt class="dt"><strong class="strong">Content</strong></dt>
-                  <dd class="dd">The data associated with a given Object; all Content <em class="em">must</em> have an associated <em class="em">Object</em>.</dd>
+                  <dd class="dd">The data associated with a given <em class="em">Object</em>; all <em class="em">Content</em> <em class="em">must</em> have an associated <em class="em">Object</em>.</dd>
                 </div>
               </dl>
               <p class="p">
-                Objects and Contents can include any characters allowed by the specifications.
-                The specification may choose how a given Object or Content are represented and parsed.
-                For example, in <code class="code">FSS-0000 (Basic)</code>, Content is treated as a single item whereas in <code class="code">FSS-0001 (Extended)</code>, Content is broken apart in multiple sub-parts.
+                <em class="em">Objects</em> and <em class="em">Contents</em> can include any characters allowed by the specifications.
+                The specification may choose how a given <em class="em">Object</em> or <em class="em">Content</em> are represented and parsed.
+                For example, in <code class="code">FSS-0000 (Basic)</code>, <em class="em">Content</em> is treated as a single item whereas in <code class="code">FSS-0001 (Extended)</code>, <em class="em">Content</em> is broken apart in multiple sub-parts.
               </p>
               <p class="p">
-                Contents may be broken up into zero or more discrete sets of Content.
-                Each of these discrete sets of Content are referred to as a column.
+                <em class="em">Contents</em> may be broken up into zero or more discrete sets of <em class="em">Content</em>.
+                Each of these discrete sets of <em class="em">Content</em> are referred to as a column.
                 These columns do not need to be setup in a column structure, the word <em class="em">column</em> is simply used as a grouping terminology.
-                While a Content refers to the entire set, a column (more specifically, a Content column) refers to the individual discrete sets within the Content.
-                For example, in <code class="code">fss-000 (Basic)</code> the entire Content may be further represented as a single column.
-                For example, in <code class="code">fss-001 (Extended)</code> the entire Content may be further represented as multiple columns.
+                While a <em class="em">Content</em> refers to the entire set, a column (more specifically, a <em class="em">Content</em> column) refers to the individual discrete sets within the <em class="em">Content</em>.
+                For example, in <code class="code">fss-000 (Basic)</code> the entire <em class="em">Content</em> may be further represented as a single column.
+                For example, in <code class="code">fss-001 (Extended)</code> the entire <em class="em">Content</em> may be further represented as multiple columns.
               </p>
               <p class="p">
-                In all cases, specifications that separate Objects from Contents using white space, the first white space separating the Object and Content must not be considered part of the Object nor part of the Content.
+                In all cases, specifications that separate <em class="em">Objects</em> from <em class="em">Contents</em> using white space, the first white space separating the <em class="em">Object</em> and <em class="em">Content</em> must not be considered part of the <em class="em">Object</em> nor part of the <em class="em">Content</em>.
                 All spaces after the first separating white space is generally ignored until the first non white space character is found, unless otherwise specified.
               </p>
               <p class="p">
@@ -234,15 +234,15 @@
                 Any specification may chose to limit, restrict, or otherwise prohibit special Unicode characters such as combining characters or zero-width characters.
               </p>
               <p class="p">
-                Unless otherwise specified, newlines designate the potential start (or end) of an Object or Content.
+                Unless otherwise specified, newlines designate the potential start (or end) of an <em class="em">Object</em> or <em class="em">Content</em>.
               </p>
               <p class="p">
-                Unless otherwise specified, white space may exist to the left of the start of Objects.
-                Unless otherwise specified, white space may exist to the right of the end of Objects, but only if that given Object is properly quoted and the white space is after the terminating quote but before any Content.
+                Unless otherwise specified, white space may exist to the left of the start of <em class="em">Objects</em>.
+                Unless otherwise specified, white space may exist to the right of the end of <em class="em">Objects</em>., but only if that given <em class="em">Object</em> is properly quoted and the white space is after the terminating quote but before any <em class="em">Content</em>.
               </p>
               <p class="p">
-                Unless otherwise specified, white space immediately both before (and after, outside of the terminating quote) an Object is not considered part of the Object.
-                This simplifies identifying the object, use quoted Objects to support white space before/after an object for styling purposes.
+                Unless otherwise specified, white space immediately both before (and after, outside of the terminating quote) an <em class="em">Object</em> is not considered part of the <em class="em">Object</em>.
+                This simplifies identifying the object, use quoted <em class="em">Objects</em> to support white space before/after an object for styling purposes.
               </p>
               <p class="p">
                 Unless otherwise specified, quotes may only be either a single quote <code class="code">'</code>, a double quote <code class="code">"</code>, or a grave <code class="code">`</code> and only a backslash <code class="code">\</code> may be used as a delimiter.
@@ -258,7 +258,7 @@
               </ul>
               <p class="p">
                 Unless otherwise specified, character/data delimits are performed only when required and not unilaterally.
-                In the case of Objects, delimits would only apply when that Object could be potentially identified as an Object.
+                In the case of <em class="em">Objects</em>, delimits would only apply when that <em class="em">Object</em> could be potentially identified as an <em class="em">Object</em>.
                 For example, <code class="code">FSS-0001 (Extended)</code> needs quotes to group parts that include spaces, if there is no initial quote, then a quote following the data <em class="em">must not</em> be delimited.
               </p>
               <p class="p">
@@ -309,20 +309,20 @@ Object_2 This is multiple\" Contents and the trailing quote does not need to be
 </pre>
               <p class="p">
                 All specifications are expected to support or be of the character encoding <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr>; however, there is no imposed restriction on supporting or using any other encoding.
-                Those encodings must only support the appropriate characters required by a given standard for differentiating Objects, Contents, and delimits.
+                Those encodings must only support the appropriate characters required by a given standard for differentiating <em class="em">Objects</em>, <em class="em">Contents</em>, and delimits.
                 All specifications do assume <abbr title="American Standard Code for Information Interchange">ASCII</abbr> and Unicode support.
               </p>
               <p class="p">
                 Unless otherwise specified, comments are designated by the pound symbol <code class="code">#</code> but only if only white space is to the left of the pound or the pound <code class="code">#</code> is at the start of the line.
                 There is no support for inline comments.
-                Unless otherwise specified, the start comment may be delimited by <code class="code">\</code> in the same manner as Objects and Contents are.
+                Unless otherwise specified, the start comment may be delimited by <code class="code">\</code> in the same manner as <em class="em">Objects</em> and <em class="em">Contents</em> are.
                 This delimit only applies to the start of a comment (the pound <code class="code">#</code> character) as there is no terminating character for a comment (other than a newline <code class="code">\n</code>).
                 A line containing a valid comment is in its entirety ignored.
                 This means that if there is white space before the designation symbol (the pound <code class="code">#</code> character) then that white space is ignored.
               </p>
               <p class="p">
                 Unless otherwise specified, all designation characters <em class="em">must</em> represent <abbr title="American Standard Code for Information Interchange">ASCII</abbr> codes.
-                With designation characters being any character code used to designate how to identify an Object or Content (such as a colon <code class="code">:</code> at the end of a basic list).
+                With designation characters being any character code used to designate how to identify an <em class="em">Object</em> or <em class="em">Content</em> (such as a colon <code class="code">:</code> at the end of a basic list).
                 This keeps the processing and logic simple and safe, for both <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> and <abbr title="American Standard Code for Information Interchange">ASCII</abbr>.
                 White space used for designation characters <em class="em">must</em> include support for <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> white space characters, unless otherwise specified.
                 However, these white space used as a designation character, must be printing white space that are not combining white space characters.