From: Kevin Day Date: Tue, 20 Dec 2022 00:24:45 +0000 (-0600) Subject: Update: Specifications markup to match recent specification clarifications. X-Git-Url: https://git.kevux.org/?a=commitdiff_plain;h=211d25c023d1391077a690ca70aacc2db6fc2f7f;p=kevux.org-website Update: Specifications markup to match recent specification clarifications. Also make some tweaks to the markup. --- diff --git a/fll/specifications/fss/fss-0000.html b/fll/specifications/fss/fss-0000.html index d810363..8c94dee 100644 --- a/fll/specifications/fss/fss-0000.html +++ b/fll/specifications/fss/fss-0000.html @@ -79,13 +79,14 @@
-

+

Each Object starts at the beginning of a line and white space to the left of the Object is not treated as part of the object. White space separates an Object from the Content. An Object may be preceded by a newline, in which case means that the Object has no Content. If only printing white spaces or non-printable characters follow a valid Object, then that Object is considered to have no Content. + An Object may be quoted to include whitespace where a single quote ' (U+0027), a double quote " (U+0022), or a backtick ` (U+0060) are used to quote.

-

+

Content exists on the same line as the Object. Content is represented as a single Content column terminated by a newline. Content column consists of everything following the first non-white space character until the newline. @@ -93,36 +94,36 @@ Content column does not include any of the leading white space. No delimits are supported in the Content.

-

+

Key:

-

+

Before Structure:

-

+

Structure:

-

+

After Structure:

-

+

Example: 

 # fss-0000
@@ -130,16 +131,16 @@
 "The Object" Content until newline.
 Second object set.
-

- Example Results: +

+ Example Result: 

 Object would be:
-1) The Object
-2) Second
+  1) The Object
+  2) Second
 
 Content would be:
-1.1) Content until newline.
-2.1) object set.
+  1.1) Content until newline.
+  2.1) object set.
diff --git a/fll/specifications/fss/fss-0001.html b/fll/specifications/fss/fss-0001.html index 09a62bc..bcf58c7 100644 --- a/fll/specifications/fss/fss-0001.html +++ b/fll/specifications/fss/fss-0001.html @@ -80,49 +80,50 @@
-

+

Each Object starts at the beginning of a line and white space to the left of the Object is not treated as an object. White space separates an Object from the Content. An Object may be followed by a newline, in which case means that the Object has no Content. If only printing white spaces or non-printable characters follow a valid Object, then that Object is considered to have no Content. + An Object may be quoted to include whitespace where a single quote ' (U+0027), a double quote " (U+0022), or a backtick ` (U+0060) are used to quote.

-

+

Content exists on the same line as the Object. Content is represented as multiple Content columns. Content columns are white space separated parts within the Content and terminated by a newline. Any number of Content columns may exist in the Content until the newline is reached.

-

+

Key:

-

+

Before Structure:

-

+

Structure:

-

+

After Structure:

-

+

Example: 

 # fss-0001
@@ -130,7 +131,7 @@
 "The Object" Content "content 2" content_3.
 Second object set.
-

+

Example Results: 

 Objects would be:
diff --git a/fll/specifications/fss/fss-0002.html b/fll/specifications/fss/fss-0002.html
index 8884443..71b7603 100644
--- a/fll/specifications/fss/fss-0002.html
+++ b/fll/specifications/fss/fss-0002.html
@@ -80,23 +80,23 @@
             
 
             

-              

+              

                 Each Object starts at the beginning of a line and white space to the left of the Object is not treated as an object.
                 A colon : (U+003A) followed by any white space until a newline terminates a valid Object.
                 Non-white space printable characters may not follow the colon of a valid Object.
               

-              

+              

                 Content is represented as a single Content column of every line following a valid object until the end of file (or string) or until the next valid Object is found.
                 Any Content that could be interpreted as a valid Object must have the colon delimited.
               

-              

-                There is no single-quote or double-quote delimitation in this specification.
-                Only the colon that would result in a valid Object can be delimited.
+              

+                There is no single-quote, double-quote, or backtick delimitation in this specification.
+                Only a colon : (U+003A) that would result in a valid Object can be delimited.
               

-              

+              

                 Empty Objects are allowed, that is, the length of the object may be zero.
               

-              

+              

                 Key:
               

               
    
@@ -107,25 +107,25 @@
                 
  • \n = Newline.
    • 
                 
  • * = Zero or more occurrences.
    • 
               

-              

+              

                 Before Structure:
               

               
    
                 
    • 
               

-              

+              

                 Structure:
               

               
    
                 
  • \s*\o\l*:\s*\n\c*\n*
    • 
               

-              

+              

                 After Structure:
               

               
    
                 
    • 
               

-              

+              

                 Example:
               
 # fss-0002
@@ -139,7 +139,7 @@ Second:
   All white space, including newline (and leading white space) is "part of content."
   # Valid comments are still ignored.
 

-              

+              

                 Example Results:
               
   Objects would be:
diff --git a/fll/specifications/fss/fss-0003.html b/fll/specifications/fss/fss-0003.html
index a256f77..c5e8b54 100644
--- a/fll/specifications/fss/fss-0003.html
+++ b/fll/specifications/fss/fss-0003.html
@@ -80,31 +80,31 @@
             
 
             

-              

+              

                 Each Object starts at the beginning of a line and white space to the left of the Object is not treated as an object.
                 An open-brace { (U+007B) followed by any white space until a newline terminates a possible valid Object.
                 An Object is not considered fully valid until a valid close-brace } (U+007D) is found, designating the end of the Content.
-                Non-white space printable characters may not follow the open-brace of a valid Object.
+                Non-white space printable characters may not follow the open-brace { (U+007B) of a valid Object.
               

-              

-                Content is represented as a single Content column of every line following a valid object until the end of file (or string) or until a non-delimited close-brace }.
+              

+                Content is represented as a single Content column of every line following a valid object until the end of file (or string) or until a non-delimited close-brace } (U+007D).
                 Any Content column that could be interpreted as an end of Content must be delimited if it should be part of the Content.
-                White space may follow a valid close-brace but a terminating newline must be present to designate a valid end of Content.
+                White space may follow a valid close-brace } (U+007D) but a terminating newline must be present to designate a valid end of Content.
               

-              

-                There is no single-quote or double-quote delimitation in this specification.
-                Only the open-brace that would result in a valid Object or the close-brace that would terminate valid Content can be delimited.
-                When inside potentially valid Content (which follows a valid Object) the open-brace cannot be delimited because this standard is not-recursive.
+              

+                There is no single-quote, double-quote, or backtick delimitation in this specification.
+                Only an open-brace { (U+007B) that would result in a valid Object or a close-brace } (U+007D) that would terminate valid Content can be delimited.
+                When inside potentially valid Content (which follows a valid Object) the open-brace { (U+007B) cannot be delimited because this standard is not-recursive.
                 When not inside any potentially valid Content (that is, there is no previous unclosed Object), then the Object may be delimited.
-                Likewise, the close-brace may only be delimited if it is within any potentially valid Content.
+                Likewise, the close-brace } (U+007D) may only be delimited if it is within any potentially valid Content.
               

-              

-                Each delimit slash in a delimitable open-brace is treated as a potential delimit such that two slashes represents a single delimited slash (\\{ would represent \{).
-                Only the first delimit slash in a delimitable close-brace is treated as a potential delimit (\\\} would represent \\}).
+              

+                Each delimit slash in a delimitable open-brace { (U+007B) is treated as a potential delimit such that two slashes represents a single delimited slash (\\{ would represent \{).
+                Only the first delimit slash in a delimitable close-brace } (U+007D) is treated as a potential delimit (\\\} would represent \\}).
               

-              

+              

                 Empty Objects are allowed, that is, the length of the object may be zero.
-              

+              

                 Key:
               

               
    
@@ -115,25 +115,25 @@
                 
  • \n = Newline.
    • 
                 
  • * = Zero or more occurrences.
    • 
               

-              

+              

                 Before Structure:
               

               
    
                 
    • 
               

-              

+              

                 Structure:
               

               
    
                 
  • \s*\o\l*{\s*\n\c*\n\s*}\s*\n
    • 
               

-              

+              

                 After Structure:
               

               
    
                 
    • 
               

-              

+              

                 Example:
               
 # fss-0003
@@ -150,7 +150,7 @@ Second {
   # Valid comments are still ignored.
 }
 

-              

+              

                 Example Results:
               
 Objects would be:
diff --git a/fll/specifications/fss/fss-0004.html b/fll/specifications/fss/fss-0004.html
index 7c03730..bcaf47b 100644
--- a/fll/specifications/fss/fss-0004.html
+++ b/fll/specifications/fss/fss-0004.html
@@ -80,16 +80,16 @@
             
 
             

-              

+              

                 This is a fss-0002 (Basic List) whose Content is then processed as fss-0000 (Basic).
               

-              

+              

                 All fss-0002 (Basic List) escapes are applied before any fss-0000 (Basic) is identified.
               

-              

+              

                 See the fss-0000 (Basic) and fss-0002 (Basic List) specifications for details on the syntax rules.
               

-              

+              

                 Example:
               
 # fss-0004
@@ -103,7 +103,7 @@ Second:
   All white space, including newline (and leading white space) is "part of content."
   # Valid comments are still ignored.
 

-              

+              

                 Example Results:
               
 Outer Objects would be:
diff --git a/fll/specifications/fss/fss-0005.html b/fll/specifications/fss/fss-0005.html
index 9bc4e0e..96eb54c 100644
--- a/fll/specifications/fss/fss-0005.html
+++ b/fll/specifications/fss/fss-0005.html
@@ -80,16 +80,16 @@
             
 
             

-              

+              

                 This is a code"fss-0002 (Basic List)" whose Content is then processed as fss-0001 (Extended).
               

-              

+              

                 All fss-0002 (Basic List) escapes are applied before any fss-0001 (Extended) is identified.
               

-              

+              

                 See the fss-0001 (Extended) and fss-0002 (Basic List) specifications for details on the syntax rules.
               

-              

+              

                 Example:
               
 # fss-0005
@@ -103,7 +103,7 @@ Second:
   All white space, including newline (and leading white space) is "part of content."
   # Valid comments are still ignored.
 

-              

+              

                 Example Results:
               
 Outer Objects would be:
diff --git a/fll/specifications/fss/fss-0006.html b/fll/specifications/fss/fss-0006.html
index 7d6cd31..c67c01a 100644
--- a/fll/specifications/fss/fss-0006.html
+++ b/fll/specifications/fss/fss-0006.html
@@ -80,16 +80,16 @@
             
 
             

-              

+              

                 This is a fss-0003 (Extended List) whose Content is then processed as fss-0000 (Basic).
               

-              

+              

                 All fss-0003 (Extended List) escapes are applied before any fss-0000 (Basic) is identified.
               

-              

+              

                 See the fss-0000 (Basic) and fss-0003 (Extended List) specifications for details on the syntax rules.
               

-              

+              

                 Example:
               
 # fss-0006
@@ -106,7 +106,7 @@ Second {
   # Valid comments are still ignored.
 }
 

-              

+              

                 Example Results:
               
 Outer Objects would be:
diff --git a/fll/specifications/fss/fss-0007.html b/fll/specifications/fss/fss-0007.html
index b8758bf..895a500 100644
--- a/fll/specifications/fss/fss-0007.html
+++ b/fll/specifications/fss/fss-0007.html
@@ -80,16 +80,16 @@
             
 
             

-              

+              

                 This is a fss-0003 (Extended List) whose Content is then processed as fss-0001 (Extended).
               

-              

+              

                 All fss-0003 (Extended List) escapes are applied before any fss-0001 (Extended) is identified.
               

-              

+              

                 See the fss-0001 (Extended) and fss-0003 (Extended List) specifications for details on the syntax rules.
               

-              

+              

                 Example:
               
 # fss-0007
@@ -106,7 +106,7 @@ Second {
   # Valid comments are still ignored.
 }
 

-              

+              

                 Example Results:
               
 Outer Objects would be:
diff --git a/fll/specifications/fss/fss-0008.html b/fll/specifications/fss/fss-0008.html
index 53d7f54..2f80425 100644
--- a/fll/specifications/fss/fss-0008.html
+++ b/fll/specifications/fss/fss-0008.html
@@ -80,13 +80,13 @@
             
 
             

-              

+              

                 This is a fss-0003 (Extended List) whose Content is then recursively processed as fss-0003 (Extended List).
               

-              

+              

                 See the fss-0003 (Extended List) specification for details on the syntax rules.
               

-              

+              

                 Example:
               
 # fss-0008
@@ -107,7 +107,7 @@ Second {
   }
 }
 

-              

+              

                 Example Results:
               
 Outer Objects would be:
diff --git a/fll/specifications/fss/fss-0009.html b/fll/specifications/fss/fss-0009.html
index 61f7f47..1502d34 100644
--- a/fll/specifications/fss/fss-0009.html
+++ b/fll/specifications/fss/fss-0009.html
@@ -80,16 +80,17 @@
             
 
             

-              

+              

                 This is based off of fss-0000 (Basic), except the Object is at the end of the line.
               

-              

+              

                 Each Object starts at the end of a line and white space to the left of the Object is not treated as part of the object.
                 White space separates an Object from the Content.
                 An Object may be preceded by a newline, in which case means that the Object has no Content.
                 If only printing white spaces or non-printable characters precedes a valid Object, then that Object is considered to have no Content.
+                An Object may be quoted to include whitespace where a single quote ' (U+0027), a double quote " (U+0022), or a backtick ` (U+0060) are used to quote.
               

-              

+              

                 Content exists on the same line as the Object.
                 Content is represented as a single Content column that begins at a newline.
                 Content column consists of everything following the first non-white space character at the start of the line until the Object is reached.
@@ -97,36 +98,36 @@
                 Content column does not include any of the white space between the last non-white space character and the start of the Object.
                 No delimits are supported in the Content.
               

-              

+              

                 Key:
               

               
    
-                
  • \s = white space, except newline.
    • 
-                
  • \b = either white space or printable, except newline.
    • 
-                
  • \q = non-white space or quoted white space with no white space outside of the quotes.
    • 
-                
  • \n = newline.
    • 
-                
  • * = zero or more occurrences.
    • 
-                
  • + = one or more occurrences.
    • 
+                
  • \s = White space, except newline.
    • 
+                
  • \b = Either white space or printable, except newline.
    • 
+                
  • \q = Non-white space or quoted white space (and non-whitespace) with no white space outside of the quotes.
    • 
+                
  • \n = Newline.
    • 
+                
  • * = Zero or more occurrences.
    • 
+                
  • + = One or more occurrences.
    • 
               

-              

+              

                 Before Structure:
               

               
    
                 
    • 
               

-              

+              

                 Structure:
               

               
    
                 
  • \s*\b*\s+\q+\s*\n
    • 
               

-              

+              

                 After Structure:
               

               
    
                 
    • 
               

-              

+              

                 Example:
               
 # fss-0009
@@ -134,7 +135,7 @@
 Content from newline. "The Object"
 object set. Second
 

-              

+              

                 Example Results:
               
 Object would be:
diff --git a/fll/specifications/fss/fss-000a.html b/fll/specifications/fss/fss-000a.html
index fc25da3..14ff8e9 100644
--- a/fll/specifications/fss/fss-000a.html
+++ b/fll/specifications/fss/fss-000a.html
@@ -80,52 +80,53 @@
             
 
             

-              

+              

                 This is based off of fss-0001 (Extended), except the Object is at the end of the line.
               

-              

+              

                 Each Object starts at the end of a line and white space to the left of the Object is not treated as an object.
                 White space separates an Object from the Content.
                 An Object may be followed by a newline, in which case means that the Object has no Content.
                 If only printing white spaces or non-printable characters follow a valid Object, then that Object is considered to have no Content.
+                An Object may be quoted to include whitespace where a single quote ' (U+0027), a double quote " (U+0022), or a backtick ` (U+0060) are used to quote.
               

-              

+              

                 Content exists on the same line as the Object.
                 Content is represented as multiple Content columns.
                 Content columns are white space separated parts within the Content is terminated by the start of the Object.
                 Any number of Content columns may exist in the Content until the Object is reached.
               

-              

+              

                 Key:
               

               
    
                 
  • \s = White space, except newline.
    • 
                 
  • \b = Either white space or printable, except newline.
    • 
-                
  • \q = Non-white space or quoted white space, no white space outside of quotes.
    • 
+                
  • \q = Non-white space or quoted white space (and non-whitespace) with no white space outside of the quotes.
    • 
                 
  • \n = Newline.
    • 
                 
  • * = Zero or more occurrences.
    • 
                 
  • + = One or more occurrences.
    • 
                 
  • ()* = Grouping that repeats zero or more times.
    • 
               

-              

+              

                 Before Structure:
               

               
    
                 
    • 
               

-              

+              

                 Structure:
               

               
    
                 
  • \s*(\s*\q+)*\s+\q+\s*\n
    • 
               

-              

+              

                 After Structure:
               

               
    
                 
    • 
               

-              

+              

                 Example:
               
 # fss-000a
@@ -133,7 +134,7 @@
 Content "content 2" content_3. "The Object"
 object set. Second
 

-              

+              

                 Example Results:
               
 Objects would be:
diff --git a/fll/specifications/fss/fss-000b.html b/fll/specifications/fss/fss-000b.html
index 2413fd3..d5528d4 100644
--- a/fll/specifications/fss/fss-000b.html
+++ b/fll/specifications/fss/fss-000b.html
@@ -80,13 +80,13 @@
             
 
             

-              

+              

                 This is similar to fss-0008 (Embedded List), except it is an fss-0003 (Extended List) with a (non-recursive) fss-0002 (Basic List) inside the Content.
               

-              

+              

                 See the fss-0002 (Basic List) and fss-0003 (Extended List) specifications for details on the syntax rules.
               

-              

+              

                 Example:
               
 # fss-000b
@@ -105,7 +105,7 @@ Second {
       There is parallel to Second rather than nested within Second.
 }
 

-              

+              

                 Example Results:
               
 Outer Objects would be:
diff --git a/fll/specifications/fss/fss-000c.html b/fll/specifications/fss/fss-000c.html
index de97e38..95a6000 100644
--- a/fll/specifications/fss/fss-000c.html
+++ b/fll/specifications/fss/fss-000c.html
@@ -80,25 +80,25 @@
             
 
             

-              

+              

                 The IKI specifications are separate specifications from the FSS.
                 This is simply a more formal way to designate that this format utilizes IKI syntax.
               

-              

+              

                 The IKI syntax may be used in any FSS.
                 The IKI format may be added to the.
               

-              

+              

                 See the file:"iki.txt" specification for details on the IKI specifications.
               

-              

+              

                 Example:
               
 # fss-000c iki-0000
 
 This is a emphasis:"formal example" utilizing the FSS headers.
 

-              

+              

                 Example:
               
 # iki-0000
diff --git a/fll/specifications/fss/fss-000d.html b/fll/specifications/fss/fss-000d.html
index aab5d1c..977941a 100644
--- a/fll/specifications/fss/fss-000d.html
+++ b/fll/specifications/fss/fss-000d.html
@@ -80,32 +80,32 @@
             
 
             

-              

+              

                 This is a special case that follows fss-0002 (Basic List), and different FSS formats inside this fss-0002 (Basic List).
                 This fss-0002 (Basic List) is considered the "Outer List" and the Content of this Outer List is considered the "Inner Content".
               

-              

+              

                 The Inner Content may be any of the following FSS formats: fss-0000 (Basic), fss-0001 (Extended), and fss-0003 (Extended List).
                 The way in which each format is determined is first to see if the Inner Content Object would be a valid Extended List Object.
                 If the Inner Content Object is not a valid fss-0003 (Extended List) Object, then check to see if it is an fss-0000 (Basic) or fss-0001 (Extended) Object.
               

-              

+              

                 The fss-0000 (Basic) and fss-0001 (Extended) Objects have the same format for Object names but the fss-0003 (Extended List) Object is slightly different.
                 Anything that would match an fss-0003 (Extended List) Object must therefore be an fss-0003 (Extended List) Object.
               

-              

+              

                 This supports the use of iki-0000 (Unrestricted) but only within the Content of the outermost fss-0002 (Basic List).
                 That is to say, the IKI is only processed once.
                 Additional restrictions on the use of IKI syntax is allowed if explicitly defined in the implementing specification.
                 This additional restriction may also include using a more restrictive IKI syntax, such as iki-0001 (Basic).
               

-              

+              

                 Anything implementing this specification may impose its own restrictions on when to determine if the Inner Content is what FSS format, based on Object names.
               

-              

+              

                 See the fss-0000 (Basic), fss-0001 (Extended), and fss-0003 (Extended List) specifications for details on the syntax rules.
               

-              

+              

                 Example:
               
 # fss-000d
@@ -126,7 +126,7 @@ command:
   start mount -a -O no_netdev
   stop umount -arf -O no_netdev
 

-            

+            

               Example Results:
             
 Outer List Objects would be:
diff --git a/fll/specifications/fss/fss-000e.html b/fll/specifications/fss/fss-000e.html
index fc41614..7c43cb8 100644
--- a/fll/specifications/fss/fss-000e.html
+++ b/fll/specifications/fss/fss-000e.html
@@ -80,14 +80,14 @@
             
 
             

-              

+              

                 This is a fss-0002 (Basic List) with two required objects:
               

               
    
                 
  1. header.
    2. 
                 
  2. payload.
    3. 
               

-              

+              

                 The header:
               

               
    
@@ -99,7 +99,7 @@
                 
  • The recommended status represents status codes (such as success or failure) and multiple.
    • 
                 
  • The Content for the recommended length and status are positive whole numbers (including zero) that may be in binary, octal, decimal, duodecimal, or hexidecimal numerical format.
    • 
               

-              

+              

                 The payload:
               

               
    
@@ -112,11 +112,11 @@
                 
  • Comments in the payload are not considered comments and are instead considered part of the payload, as-is.
    • 
                 
  • Essentially, the payload should be treated as binary data embedded in a text file.
    • 
               

-              

+              

                 The recommended length header Object used to designate the payload size does not necessarily have to be defined in the header.
                 That is to say, if the payload is expected to be of some pre-defined or static length then a length does not need to be provided in the header.
               

-              

+              

                 The recommended status header Object may be a string, such as F_none, or a positive whole number.
                 What the status code represents is application specific (or specific to a sub-standard) but may often be used to represent FLL status code.
               

@@ -125,7 +125,7 @@
                 
  • The FLL status code as a number is binary sensitive and may not be portable across binaries or systems.
    • 
                 
  • For best portability, consider using status as a name string to ensure cross-system or cross-binary compatibility.
    • 
               
-              
    
+              
    
                 Example:
               
     # fss-000e
@@ -138,7 +138,7 @@ header:
 payload:
 The program is out of memory.
 
    
-              
    
+              
    
                 Example Results:
               
     Outer Objects would be:
diff --git a/fll/specifications/fss/fss-000f.html b/fll/specifications/fss/fss-000f.html
index 3cb73f6..8c44b27 100644
--- a/fll/specifications/fss/fss-000f.html
+++ b/fll/specifications/fss/fss-000f.html
@@ -79,13 +79,13 @@
             
 
             
    
-              
    
+              
    
                 This is a network packet format that contains fss-000e (Payload) within it.
               
    
-              
    
+              
    
                 The Simple Packet structure is described in blocks, of which are structured in bytes.
               
    
-              
    
+              
    
                 There are only three blocks in this format:
               
    
               
      
@@ -93,44 +93,44 @@
                 
    1. Size Block.
      2. 
                 
    2. Payload Block.
      3. 
               
    
-              
    
+              
    
                 The Control Block is the first block in the packet and is considered endianless.
                 There exists only a single byte within the Control Block.
                 Regardless of the endianness of the packet, the leftmost bit is always the string or binary bit.
                 The second bit following that bit represents the endianness bit.
               
    
-              
    
+              
    
                 The string or binary bit, a value of 0 designates that the packet is in string format and a value of 1 designates that the packet is in binary format.
                 While the packet might be considered to be in string format, it is technically always in binary format due to the Control Block and Size Block.
                 This means that the bit designating the packet as a string packet or a binary packet is referring to whether or not the Payload Block is in string format or is in binary format.
               
    
-              
    
+              
    
                 The endianness bit designates whether or not the packet is in big endian or little endian format.
                 A bit value of 0 designates that this packet is in little endian and a value of 1 designates that this packet is in big endian format.
                 All binary data within this packet, following the Control Block, must respect this endianness bit (including the Size Block).
               
    
-              
    
+              
    
                 The remaining bits are not defined by this standard and are expected to be 0.
                 Non-formal or local uses may utilize these remaining 6 bits as desired.
                 However, there may be additional standards that expand upon this and utilize these remaining Control bits.
                 Anything that utilizes these unused Control bits may add or remove additional Blocks after the Control Block as they see fit.
               
    
-              
    
+              
    
                 The Size Block is an unsigned 32-bit integer representing the size of the entire packet, including the Control Block and Size Block.
                 This size must exactly match the packet to be a valid packet.
                 The size represents number of bytes in the file.
                 The Control Block is 1 byte long and the Size Block is 4 bytes long and so the maximum available size is (2^32)-6.
               
    
-              
    
+              
    
                 The Payload Block is not defined by this standard of that that it exists and should be in fss-000e (Payload) format.
                 The fss-000e (Payload) may be represented in either string format or binary format.
                 The fss-000e (Payload) may contain multiple header(s) but may only contain a single payload.
                 With this in mind, it is recommended that only a single header be supported in the Payload Block.
               
    
-              
    
+              
    
                 See the fss-000e (Payload) specification for details on the syntax rules for the Payload Block.
               
    
-              
    
+              
    
                 Example Packet Structure:
               
     [ Control Block ] [ Size Block                                  ] [ Payload Block         ]
diff --git a/fll/specifications/iki/iki-0000.html b/fll/specifications/iki/iki-0000.html
index 35d25a7..198ed0e 100644
--- a/fll/specifications/iki/iki-0000.html
+++ b/fll/specifications/iki/iki-0000.html
@@ -82,7 +82,7 @@
             
 
             
    
-              
    
+              
    
                 This specification provides no restrictions on the vocabulary.
               
    
             
    
@@ -94,32 +94,32 @@
             
 
             
    
-              
    
+              
    
                 IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
               
    
-              
    
+              
    
                 The IKI syntax provides a vocabulary name (with specific context associated with it) followed by quoted code that is associated with the given vocabulary name.
                 The vocabulary represents a list of allowed variable names that may also have specific contextual meaning defined by a given IKI specification.
                 The variable name is considered the Object.
                 The variable value is considered the Content.
               
    
-              
    
+              
    
                 The IKI format will use iki-0000 to represent an IKI with no explicitly defined vocabulary.
                 Whereas iki-0001 and beyond represent a specific IKI vocabulary.
               
    
-              
    
+              
    
                 A potential IKI variable name starts on word (or _, -, +) characters.
                 White space and non-word (and non _, -, +) character punctuations may not exist as part of the variable name.
                 The only Unicode dash-like characters allowed as a "dash" are those intended to connect, such as the Unicode hyphens (U+2010 and U+2011).
               
    
-              
    
+              
    
                 Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash " before the colon code::" that is before the opening quote (single or double).
               
    
-              
    
+              
    
                 Unicode punctuation connector characters are supported just like _, except when they connect outside the current line (such as U+FE33 ︳).
                 Unicode invisible punctuations (such as invisible plus: U+2064) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid _, -, or + Unicode equivalents.
               
    
-              
    
+              
    
                 Key:
               
    
               
      
@@ -132,25 +132,25 @@
                   
    • * = zero or more occurrences.
      • 
                   
    • ~ = one or more occurrences, or zero if at start of file.
      • 
               
    
-              
    
+              
    
                 Before Structure:
               
    
               
      
                 
    • \x*\W~\*:*
      • 
               
    
-              
    
+              
    
                 Structure:
               
    
               
      
                 
    • \o\e:\q\c\q
      • 
               
    
-              
    
+              
    
                 After Structure:
               
    
               
      
                 
      • 
               
    
-              
    
+              
    
                 Example File:
               
     # fss-000c iki-0000
@@ -165,7 +165,7 @@ Quotes may be included, such as: code:"const char *string = \"My \\\"quoted\\\"
 
 The following emphasis\:"is escaped to not be treated as IKI data".
 
    
-              
    
+              
    
                 Example Results:
               
     Objects would be:
diff --git a/fll/specifications/iki/iki-0001.html b/fll/specifications/iki/iki-0001.html
index d8c8dd8..08ad1a6 100644
--- a/fll/specifications/iki/iki-0001.html
+++ b/fll/specifications/iki/iki-0001.html
@@ -83,10 +83,10 @@
             
 
             
    
-              
    
+              
    
                 This specification provides a small set of vocabulary names meant to be associated with common uses, such as e-mail addresses and URLs.
               
    
-              
    
+              
    
                 Vocabulary:
               
    
               
    
@@ -136,32 +136,32 @@
             
 
             
    
-              
    
+              
    
                 IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
               
    
-              
    
+              
    
                 The IKI syntax provides a vocabulary name (with specific context associated with it) followed by quoted code that is associated with the given vocabulary name.
                 The vocabulary represents a list of allowed variable names that may also have specific contextual meaning defined by a given IKI specification.
                 The variable name is considered the Object.
                 The variable value is considered the Content.
               
    
-              
    
+              
    
                 The IKI format will use iki-0000 to represent an IKI with no explicitly defined vocabulary.
                 Whereas iki-0001 and beyond represent a specific IKI vocabulary.
               
    
-              
    
+              
    
                 A potential IKI variable name starts on word (or _, -, +) characters.
                 White space and non-word (and non _, -, +) character punctuations may not exist as part of the variable name.
                 The only Unicode dash-like characters allowed as a "dash" are those intended to connect, such as the Unicode hyphens (U+2010 and U+2011).
               
    
-              
    
+              
    
                 Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash " before the colon code::" that is before the opening quote (single or double).
               
    
-              
    
+              
    
                 Unicode punctuation connector characters are supported just like _, except when they connect outside the current line (such as U+FE33 ︳).
                 Unicode invisible punctuations (such as invisible plus: U+2064) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid _, -, or + Unicode equivalents.
               
    
-              
    
+              
    
                 Key:
               
    
               
      
@@ -174,25 +174,25 @@
                   
    • * = zero or more occurrences.
      • 
                   
    • ~ = one or more occurrences, or zero if at start of file.
      • 
               
    
-              
    
+              
    
                 Before Structure:
               
    
               
      
                 
    • \x*\W~\*:*
      • 
               
    
-              
    
+              
    
                 Structure:
               
    
               
      
                 
    • \o\e:\q\c\q
      • 
               
    
-              
    
+              
    
                 After Structure:
               
    
               
      
                 
      • 
               
    
-              
    
+              
    
                 Example File:
               
     # fss-000c iki-0001
@@ -207,7 +207,7 @@ Quotes may be included, such as: code:"const char *string = \"My \\\"quoted\\\"
 
 The following emphasis\:"is escaped to not be treated as IKI data".
 
    
-              
    
+              
    
                 Example Results:
               
     Objects would be:
diff --git a/fll/specifications/iki/iki-0002.html b/fll/specifications/iki/iki-0002.html
index e537ef5..6f4cd1d 100644
--- a/fll/specifications/iki/iki-0002.html
+++ b/fll/specifications/iki/iki-0002.html
@@ -82,19 +82,19 @@
             
 
             
    
-              
    
+              
    
                 This specification provides a small set of vocabulary names meant to be used for substitution in simple scripts.
               
    
-              
    
+              
    
                 This specification only loosely defines the vocabulary context.
                 This vocabulary may be further extended but must at least support the taxonomy defined here.
                 Flexibility on interpretation is intended so that the context can be more fine-tuned and customized.
               
    
-              
    
+              
    
                 The taxonomy for the context, define, and parameter are intentionally not defined here and left open.
                 One utilizing this should document the taxonomy for each of these as desired.
               
    
-              
    
+              
    
                 Vocabulary:
               
    
               
    
@@ -120,32 +120,32 @@
             
 
             
    
-              
    
+              
    
                 IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
               
    
-              
    
+              
    
                 The IKI syntax provides a vocabulary name (with specific context associated with it) followed by quoted code that is associated with the given vocabulary name.
                 The vocabulary represents a list of allowed variable names that may also have specific contextual meaning defined by a given IKI specification.
                 The variable name is considered the Object.
                 The variable value is considered the Content.
               
    
-              
    
+              
    
                 The IKI format will use iki-0000 to represent an IKI with no explicitly defined vocabulary.
                 Whereas iki-0001 and beyond represent a specific IKI vocabulary.
               
    
-              
    
+              
    
                 A potential IKI variable name starts on word (or _, -, +) characters.
                 White space and non-word (and non _, -, +) character punctuations may not exist as part of the variable name.
                 The only Unicode dash-like characters allowed as a "dash" are those intended to connect, such as the Unicode hyphens (U+2010 and U+2011).
               
    
-              
    
+              
    
                 Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash " before the colon code::" that is before the opening quote (single or double).
               
    
-              
    
+              
    
                 Unicode punctuation connector characters are supported just like _, except when they connect outside the current line (such as U+FE33 ︳).
                 Unicode invisible punctuations (such as invisible plus: U+2064) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid _, -, or + Unicode equivalents.
               
    
-              
    
+              
    
                 Key:
               
    
               
      
@@ -158,25 +158,25 @@
                   
    • * = zero or more occurrences.
      • 
                   
    • ~ = one or more occurrences, or zero if at start of file.
      • 
               
    
-              
    
+              
    
                 Before Structure:
               
    
               
      
                 
    • \x*\W~\*:*
      • 
               
    
-              
    
+              
    
                 Structure:
               
    
               
      
                 
    • \o\e:\q\c\q
      • 
               
    
-              
    
+              
    
                 After Structure:
               
    
               
      
                 
      • 
               
    
-              
    
+              
    
                 Example File:
               
     # fss-000c iki-0000
@@ -191,7 +191,7 @@ Quotes may be included, such as: code:"const char *string = \"My \\\"quoted\\\"
 
 The following emphasis\:"is escaped to not be treated as IKI data".
 
    
-              
    
+              
    
                 Example Results:
               
     Objects would be: