Also make some tweaks to the markup.
</header>
<div class="section-content">
- <p>
+ <p class="p">
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 <code class="code">'</code> (<code class="code">U+0027</code>), a double quote <code class="code">"</code> (<code class="code">U+0022</code>), or a backtick <code class="code">`</code> (<code class="code">U+0060</code>) are used to quote.
</p>
- <p>
+ <p class="p">
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.
Content column does not include any of the leading white space.
No delimits are supported in the Content.
</p>
- <p>
+ <p class="p">
Key:
</p>
<ul>
- <li><code class="code">\s</code> = white space, except newline.</li>
- <li><code class="code">\b</code> = either white space or printable, except newline.</li>
- <li><code class="code">\q</code> = non-white space or quoted white space with no white space outside of the quotes.</li>
- <li><code class="code">\n</code> = newline.</li>
- <li><code class="code">*</code> = zero or more occurrences.</li>
- <li><code class="code">+</code> = one or more occurrences.</li>
+ <li><code class="code">\s</code> = White space, except newline.</li>
+ <li><code class="code">\b</code> = Either white space or printable, except newline.</li>
+ <li><code class="code">\q</code> = Non-white space or quoted white space (and non-whitespace) with no white space outside of the quotes.</li>
+ <li><code class="code">\n</code> = Newline.</li>
+ <li><code class="code">*</code> = Zero or more occurrences.</li>
+ <li><code class="code">+</code> = One or more occurrences.</li>
</ul>
- <p>
+ <p class="p">
Before Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Structure:
</p>
<ul>
<li><code class="code">\s*\q+\s+\b*\n</code></li>
</ul>
- <p>
+ <p class="p">
After Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0000
"The Object" Content until newline.
Second object set.
</pre>
- <p>
- Example Results:
+ <p class="p">
+ Example Result:
</p><pre class="preserve">
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.
</pre>
</div>
</section>
</header>
<div class="section-content">
- <p>
+ <p class="p">
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 <code class="code">'</code> (<code class="code">U+0027</code>), a double quote <code class="code">"</code> (<code class="code">U+0022</code>), or a backtick <code class="code">`</code> (<code class="code">U+0060</code>) are used to quote.
</p>
- <p>
+ <p class="p">
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.
</p>
- <p>
+ <p class="p">
Key:
</p>
<ul>
<li><code class="code">\s</code> = White space, except newline.</li>
<li><code class="code">\b</code> = Either white space or printable, except newline.</li>
- <li><code class="code">\q</code> = Non-white space or quoted white space with no white space outside of the quotes.</li>
+ <li><code class="code">\q</code> = Non-white space or quoted white space (and non-whitespace) with no white space outside of the quotes.</li>
<li><code class="code">\n</code> = Newline.</li>
<li><code class="code">*</code> = Zero or more occurrences.</li>
<li><code class="code">+</code> = One or more occurrences.</li>
<li><code class="code">()*</code> = Grouping that repeats zero or more times.</li>
</ul>
- <p>
+ <p class="p">
Before Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Structure:
</p>
<ul>
<li><code class="code">\s*\q+\s+(\s*\q+)*\s*\n</code></li>
</ul>
- <p>
+ <p class="p">
After Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0001
"The Object" Content "content 2" content_3.
Second object set.
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
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 <code class="code">:</code> (<code class="code">U+003A</code>) 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.
</p>
- <p>
+ <p class="p">
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.
</p>
- <p>
- 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.
+ <p class="p">
+ There is no single-quote, double-quote, or backtick delimitation in this specification.
+ Only a colon <code class="code">:</code> (<code class="code">U+003A</code>) that would result in a valid Object can be delimited.
</p>
- <p>
+ <p class="p">
Empty Objects are allowed, that is, the length of the object may be zero.
</p>
- <p>
+ <p class="p">
Key:
</p>
<ul>
<li><code class="code">\n</code> = Newline.</li>
<li><code class="code">*</code> = Zero or more occurrences.</li>
</ul>
- <p>
+ <p class="p">
Before Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Structure:
</p>
<ul>
<li><code class="code">\s*\o\l*:\s*\n\c*\n*</code></li>
</ul>
- <p>
+ <p class="p">
After Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0002
All white space, including newline (and leading white space) is "part of content."
# Valid comments are still ignored.
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
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 <code class="code">{</code> (<code class="code">U+007B</code>) 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 <code class="code">}</code> (<code class="code">U+007D</code>) 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 <code class="code">{</code> (<code class="code">U+007B</code>) of a valid Object.
</p>
- <p>
- 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 <code class="code">}</code>.
+ <p class="p">
+ 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 <code class="code">}</code> (<code class="code">U+007D</code>).
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 <code class="code">}</code> (<code class="code">U+007D</code>) but a terminating newline must be present to designate a valid end of Content.
</p>
- <p>
- 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.
+ <p class="p">
+ There is no single-quote, double-quote, or backtick delimitation in this specification.
+ Only an open-brace <code class="code">{</code> (<code class="code">U+007B</code>) that would result in a valid Object or a close-brace <code class="code">}</code> (<code class="code">U+007D</code>) that would terminate valid Content can be delimited.
+ When inside potentially valid Content (which follows a valid Object) the open-brace <code class="code">{</code> (<code class="code">U+007B</code>) 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 <code class="code">}</code> (<code class="code">U+007D</code>) may only be delimited if it is within any potentially valid Content.
</p>
- <p>
- Each delimit slash in a delimitable open-brace is treated as a potential delimit such that two slashes represents a single delimited slash (<code class="code">\\{</code> would represent <code class="code">\{</code>).
- Only the first delimit slash in a delimitable close-brace is treated as a potential delimit (<code class="code">\\\}</code> would represent <code class="code">\\}</code>).
+ <p class="p">
+ Each delimit slash in a delimitable open-brace <code class="code">{</code> (<code class="code">U+007B</code>) is treated as a potential delimit such that two slashes represents a single delimited slash (<code class="code">\\{</code> would represent <code class="code">\{</code>).
+ Only the first delimit slash in a delimitable close-brace <code class="code">}</code> (<code class="code">U+007D</code>) is treated as a potential delimit (<code class="code">\\\}</code> would represent <code class="code">\\}</code>).
</p>
- <p>
+ <p class="p">
Empty Objects are allowed, that is, the length of the object may be zero.
- <p>
+ <p class="p">
Key:
</p>
<ul>
<li><code class="code">\n</code> = Newline.</li>
<li><code class="code">*</code> = Zero or more occurrences.</li>
</ul>
- <p>
+ <p class="p">
Before Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Structure:
</p>
<ul>
<li><code class="code">\s*\o\l*{\s*\n\c*\n\s*}\s*\n</code></li>
</ul>
- <p>
+ <p class="p">
After Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0003
# Valid comments are still ignored.
}
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is a <code class="code">fss-0002 (Basic List)</code> whose Content is then processed as <code class="code">fss-0000 (Basic)</code>.
</p>
- <p>
+ <p class="p">
All <code class="code">fss-0002 (Basic List)</code> escapes are applied before any <code class="code">fss-0000 (Basic)</code> is identified.
</p>
- <p>
+ <p class="p">
See the <a href="fll/specifications/fss/fss-0000.html" class="link">fss-0000 (Basic)</a> and <a href="fll/specifications/fss/fss-0002.html" class="link">fss-0002 (Basic List)</a> specifications for details on the syntax rules.
</p>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0004
All white space, including newline (and leading white space) is "part of content."
# Valid comments are still ignored.
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Outer Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is a code"fss-0002 (Basic List)" whose Content is then processed as <code class="code">fss-0001 (Extended)</code>.
</p>
- <p>
+ <p class="p">
All <code class="code">fss-0002 (Basic List)</code> escapes are applied before any <code class="code">fss-0001 (Extended)</code> is identified.
</p>
- <p>
+ <p class="p">
See the <a href="fll/specifications/fss/fss-0001.html" class="link">fss-0001 (Extended)</a> and <a href="fll/specifications/fss/fss-0002.html" class="link">fss-0002 (Basic List)</a> specifications for details on the syntax rules.
</p>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0005
All white space, including newline (and leading white space) is "part of content."
# Valid comments are still ignored.
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Outer Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is a <code class="code">fss-0003 (Extended List)</code> whose Content is then processed as <code class="code">fss-0000 (Basic)</code>.
</p>
- <p>
+ <p class="p">
All <code class="code">fss-0003 (Extended List)</code> escapes are applied before any <code class="code">fss-0000 (Basic)</code> is identified.
</p>
- <p>
+ <p class="p">
See the <a href="fll/specifications/fss/fss-0000.html" class="link">fss-0000 (Basic)</a> and <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specifications for details on the syntax rules.
</p>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0006
# Valid comments are still ignored.
}
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Outer Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is a <code class="code">fss-0003 (Extended List)</code> whose Content is then processed as <code class="code">fss-0001 (Extended)</code>.
</p>
- <p>
+ <p class="p">
All <code class="code">fss-0003 (Extended List)</code> escapes are applied before any <code class="code">fss-0001 (Extended)</code> is identified.
</p>
- <p>
+ <p class="p">
See the <a href="fll/specifications/fss/fss-0001.html" class="link">fss-0001 (Extended)</a> and <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specifications for details on the syntax rules.
</p>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0007
# Valid comments are still ignored.
}
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Outer Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is a <code class="code">fss-0003 (Extended List)</code> whose Content is then recursively processed as <code class="code">fss-0003 (Extended List)</code>.
</p>
- <p>
+ <p class="p">
See the <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specification for details on the syntax rules.
</p>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0008
}
}
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Outer Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is based off of <code class="code">fss-0000 (Basic)</code>, except the Object is at the end of the line.
</p>
- <p>
+ <p class="p">
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 <code class="code">'</code> (<code class="code">U+0027</code>), a double quote <code class="code">"</code> (<code class="code">U+0022</code>), or a backtick <code class="code">`</code> (<code class="code">U+0060</code>) are used to quote.
</p>
- <p>
+ <p class="p">
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.
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.
</p>
- <p>
+ <p class="p">
Key:
</p>
<ul>
- <li><code class="code">\s</code> = white space, except newline.</li>
- <li><code class="code">\b</code> = either white space or printable, except newline.</li>
- <li><code class="code">\q</code> = non-white space or quoted white space with no white space outside of the quotes.</li>
- <li><code class="code">\n</code> = newline.</li>
- <li><code class="code">*</code> = zero or more occurrences.</li>
- <li><code class="code">+</code> = one or more occurrences.</li>
+ <li><code class="code">\s</code> = White space, except newline.</li>
+ <li><code class="code">\b</code> = Either white space or printable, except newline.</li>
+ <li><code class="code">\q</code> = Non-white space or quoted white space (and non-whitespace) with no white space outside of the quotes.</li>
+ <li><code class="code">\n</code> = Newline.</li>
+ <li><code class="code">*</code> = Zero or more occurrences.</li>
+ <li><code class="code">+</code> = One or more occurrences.</li>
</ul>
- <p>
+ <p class="p">
Before Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Structure:
</p>
<ul>
<li><code class="code">\s*\b*\s+\q+\s*\n</code></li>
</ul>
- <p>
+ <p class="p">
After Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-0009
Content from newline. "The Object"
object set. Second
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Object would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is based off of <code class="code">fss-0001 (Extended)</code>, except the Object is at the end of the line.
</p>
- <p>
+ <p class="p">
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 <code class="code">'</code> (<code class="code">U+0027</code>), a double quote <code class="code">"</code> (<code class="code">U+0022</code>), or a backtick <code class="code">`</code> (<code class="code">U+0060</code>) are used to quote.
</p>
- <p>
+ <p class="p">
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.
</p>
- <p>
+ <p class="p">
Key:
</p>
<ul>
<li><code class="code">\s</code> = White space, except newline.</li>
<li><code class="code">\b</code> = Either white space or printable, except newline.</li>
- <li><code class="code">\q</code> = Non-white space or quoted white space, no white space outside of quotes.</li>
+ <li><code class="code">\q</code> = Non-white space or quoted white space (and non-whitespace) with no white space outside of the quotes.</li>
<li><code class="code">\n</code> = Newline.</li>
<li><code class="code">*</code> = Zero or more occurrences.</li>
<li><code class="code">+</code> = One or more occurrences.</li>
<li><code class="code">()*</code> = Grouping that repeats zero or more times.</li>
</ul>
- <p>
+ <p class="p">
Before Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Structure:
</p>
<ul>
<li><code class="code">\s*(\s*\q+)*\s+\q+\s*\n</code></li>
</ul>
- <p>
+ <p class="p">
After Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-000a
Content "content 2" content_3. "The Object"
object set. Second
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is similar to <code class="code">fss-0008 (Embedded List)</code>, except it is an <code class="code">fss-0003 (Extended List)</code> with a (non-recursive) <code class="code">fss-0002 (Basic List)</code> inside the Content.
</p>
- <p>
+ <p class="p">
See the <a href="fll/specifications/fss/fss-0002.html" class="link">fss-0002 (Basic List)</a> and <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specifications for details on the syntax rules.
</p>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-000b
There is parallel to Second rather than nested within Second.
}
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Outer Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
The IKI specifications are separate specifications from the <abbr title="Featureless Settings Specifications">FSS</abbr>.
This is simply a more formal way to designate that this format utilizes IKI syntax.
</p>
- <p>
+ <p class="p">
The IKI syntax may be used in any <abbr title="Featureless Settings Specifications">FSS</abbr>.
The IKI format may be added to the.
</p>
- <p>
+ <p class="p">
See the file:"iki.txt" specification for details on the IKI specifications.
</p>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-000c iki-0000
This is a emphasis:"formal example" utilizing the FSS headers.
</pre>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# iki-0000
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is a special case that follows <code class="code">fss-0002 (Basic List)</code>, and different <abbr title="Featureless Settings Specifications">FSS</abbr> formats inside this <code class="code">fss-0002 (Basic List)</code>.
This <code class="code">fss-0002 (Basic List)</code> is considered the "Outer List" and the Content of this Outer List is considered the "Inner Content".
</p>
- <p>
+ <p class="p">
The Inner Content may be any of the following <abbr title="Featureless Settings Specifications">FSS</abbr> formats: <code class="code">fss-0000 (Basic)</code>, <code class="code">fss-0001 (Extended)</code>, and <code class="code">fss-0003 (Extended List)</code>.
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 <code class="code">fss-0003 (Extended List)</code> Object, then check to see if it is an <code class="code">fss-0000 (Basic)</code> or <code class="code">fss-0001 (Extended)</code> Object.
</p>
- <p>
+ <p class="p">
The <code class="code">fss-0000 (Basic)</code> and <code class="code">fss-0001 (Extended)</code> Objects have the same format for Object names but the <code class="code">fss-0003 (Extended List)</code> Object is slightly different.
Anything that would match an <code class="code">fss-0003 (Extended List)</code> Object must therefore be an <code class="code">fss-0003 (Extended List)</code> Object.
</p>
- <p>
+ <p class="p">
This supports the use of <code class="code">iki-0000 (Unrestricted)</code> but only within the Content of the outermost <code class="code">fss-0002 (Basic List)</code>.
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 <code class="code">iki-0001 (Basic)</code>.
</p>
- <p>
+ <p class="p">
Anything implementing this specification may impose its own restrictions on when to determine if the Inner Content is what <abbr title="Featureless Settings Specifications">FSS</abbr> format, based on Object names.
</p>
- <p>
+ <p class="p">
See the <a href="fll/specifications/fss/fss-0000.html" class="link">fss-0000 (Basic)</a>, <a href="fll/specifications/fss/fss-0001.html" class="link">fss-0001 (Extended)</a>, and <a href="fll/specifications/fss/fss-0003.html" class="link">fss-0003 (Extended List)</a> specifications for details on the syntax rules.
</p>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-000d
start mount -a -O no_netdev
stop umount -arf -O no_netdev
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Outer List Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is a <code class="code">fss-0002 (Basic List)</code> with two required objects:
</p>
<ol>
<li><em class="em">header</em>.</li>
<li><em class="em">payload</em>.</li>
</ol>
- <p>
+ <p class="p">
The <em class="em">header</em>:
</p>
<ul>
<li>The recommended <em class="em">status</em> represents status codes (such as success or failure) and multiple.</li>
<li>The Content for the recommended <em class="em">length</em> and <em class="em">status</em> are positive whole numbers (including zero) that may be in <em class="em">binary</em>, <em class="em">octal</em>, <em class="em">decimal</em>, <em class="em">duodecimal</em>, or <em class="em">hexidecimal</em> numerical format.</li>
</ul>
- <p>
+ <p class="p">
The <em class="em">payload</em>:
</p>
<ul>
<li>Comments in the <em class="em">payload</em> are not considered comments and are instead considered part of the payload, as-is.</li>
<li>Essentially, the <em class="em">payload</em> should be treated as binary data embedded in a text file.</li>
</ul>
- <p>
+ <p class="p">
The recommended <em class="em">length</em> <em class="em">header</em> Object used to designate the <em class="em">payload</em> size does not necessarily have to be defined in the <em class="em">header</em>.
That is to say, if the <em class="em">payload</em> is expected to be of some pre-defined or static length then a length does not need to be provided in the <em class="em">header</em>.
</p>
- <p>
+ <p class="p">
The recommended <em class="em">status</em> <em class="em">header</em> Object may be a string, such as <code class="code">F_none</code>, 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 <abbr title="Featureless Linux Library">FLL</abbr> status code.
</p>
<li>The <abbr title="Featureless Linux Library">FLL</abbr> status code as a number is binary sensitive and may not be portable across binaries or systems.</li>
<li>For best portability, consider using status as a name string to ensure cross-system or cross-binary compatibility.</li>
</ul>
- <p>
+ <p class="p">
Example:
</p><pre class="preserve">
# fss-000e
payload:
The program is out of memory.
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve">
Outer Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This is a network packet format that contains <code class="code">fss-000e (Payload)</code> within it.
</p>
- <p>
+ <p class="p">
The Simple Packet structure is described in blocks, of which are structured in bytes.
</p>
- <p>
+ <p class="p">
There are only three blocks in this format:
</p>
<ol>
<li>Size Block.</li>
<li>Payload Block.</li>
</ol>
- <p>
+ <p class="p">
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 <em class="em">string</em> or <em class="em">binary</em> bit.
The second bit following that bit represents the endianness bit.
</p>
- <p>
+ <p class="p">
The <em class="em">string</em> or <em class="em">binary</em> 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 <em class="em">string</em> packet or a <em class="em">binary</em> packet is referring to whether or not the Payload Block is in <em class="em">string</em> format or is in <em class="em">binary</em> format.
</p>
- <p>
+ <p class="p">
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).
</p>
- <p>
+ <p class="p">
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.
</p>
- <p>
+ <p class="p">
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.
</p>
- <p>
+ <p class="p">
The Payload Block is not defined by this standard of that that it exists and should be in <code class="code">fss-000e (Payload)</code> format.
The <code class="code">fss-000e (Payload)</code> may be represented in either string format or binary format.
The <code class="code">fss-000e (Payload)</code> may contain multiple <em class="em">header</em>(s) but may only contain a single <em class="em">payload</em>.
With this in mind, it is recommended that only a single <em class="em">header</em> be supported in the Payload Block.
</p>
- <p>
+ <p class="p">
See the <a href="fll/specifications/fss/fss-000e.html" class="link">fss-000e (Payload)</a> specification for details on the syntax rules for the Payload Block.
</p>
- <p>
+ <p class="p">
Example Packet Structure:
</p><pre class="preserve">
[ Control Block ] [ Size Block ] [ Payload Block ]
</header>
<div class="section-content">
- <p>
+ <p class="p">
This specification provides no restrictions on the vocabulary.
</p>
</div>
</header>
<div class="section-content">
- <p>
+ <p class="p">
IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
</p>
- <p>
+ <p class="p">
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 <em class="em">Object</em>.
The variable value is considered the <em class="em">Content</em>.
</p>
- <p>
+ <p class="p">
The IKI format will use <code class="code">iki-0000</code> to represent an IKI with no explicitly defined vocabulary.
Whereas <code class="code">iki-0001</code> and beyond represent a specific IKI vocabulary.
</p>
- <p>
+ <p class="p">
A potential IKI variable name starts on word (or <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) characters.
White space and non-word (and non <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) 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 (<code class="code">U+2010</code> and <code class="code">U+2011</code>).
</p>
- <p>
+ <p class="p">
Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash <code class="code">" before the colon code:</code>:" that is before the opening quote (single or double).
</p>
- <p>
+ <p class="p">
Unicode punctuation connector characters are supported just like <code class="code">_</code>, except when they connect outside the current line (such as <code class="code">U+FE33</code> <code class="code">︳</code>).
Unicode invisible punctuations (such as invisible plus: <code class="code">U+2064</code>) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid <code class="code">_</code>, <code class="code">-</code>, or <code class="code">+</code> Unicode equivalents.
</p>
- <p>
+ <p class="p">
Key:
</p>
<ul>
<li><code class="code">*</code> = zero or more occurrences.</li>
<li><code class="code">~</code> = one or more occurrences, or zero if at start of file.</li>
</ul>
- <p>
+ <p class="p">
Before Structure:
</p>
<ul>
<li><code class="code">\x*\W~\*:*</code></li>
</ul>
- <p>
+ <p class="p">
Structure:
</p>
<ul>
<li><code class="code">\o\e:\q\c\q</code></li>
</ul>
- <p>
+ <p class="p">
After Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Example File:
</p><pre class="preserve">
# fss-000c iki-0000
The following emphasis\:"is escaped to not be treated as IKI data".
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve margin-below">
Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This specification provides a small set of vocabulary names meant to be associated with common uses, such as e-mail addresses and <abbr title="Uniform Resource Locator">URL</abbr>s.
</p>
- <p>
+ <p class="p">
Vocabulary:
</p>
<dl class="dl">
</header>
<div class="section-content">
- <p>
+ <p class="p">
IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
</p>
- <p>
+ <p class="p">
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 <em class="em">Object</em>.
The variable value is considered the <em class="em">Content</em>.
</p>
- <p>
+ <p class="p">
The IKI format will use <code class="code">iki-0000</code> to represent an IKI with no explicitly defined vocabulary.
Whereas <code class="code">iki-0001</code> and beyond represent a specific IKI vocabulary.
</p>
- <p>
+ <p class="p">
A potential IKI variable name starts on word (or <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) characters.
White space and non-word (and non <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) 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 (<code class="code">U+2010</code> and <code class="code">U+2011</code>).
</p>
- <p>
+ <p class="p">
Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash <code class="code">" before the colon code:</code>:" that is before the opening quote (single or double).
</p>
- <p>
+ <p class="p">
Unicode punctuation connector characters are supported just like <code class="code">_</code>, except when they connect outside the current line (such as <code class="code">U+FE33</code> <code class="code">︳</code>).
Unicode invisible punctuations (such as invisible plus: <code class="code">U+2064</code>) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid <code class="code">_</code>, <code class="code">-</code>, or <code class="code">+</code> Unicode equivalents.
</p>
- <p>
+ <p class="p">
Key:
</p>
<ul>
<li><code class="code">*</code> = zero or more occurrences.</li>
<li><code class="code">~</code> = one or more occurrences, or zero if at start of file.</li>
</ul>
- <p>
+ <p class="p">
Before Structure:
</p>
<ul>
<li><code class="code">\x*\W~\*:*</code></li>
</ul>
- <p>
+ <p class="p">
Structure:
</p>
<ul>
<li><code class="code">\o\e:\q\c\q</code></li>
</ul>
- <p>
+ <p class="p">
After Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Example File:
</p><pre class="preserve">
# fss-000c iki-0001
The following emphasis\:"is escaped to not be treated as IKI data".
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve margin-below">
Objects would be:
</header>
<div class="section-content">
- <p>
+ <p class="p">
This specification provides a small set of vocabulary names meant to be used for substitution in simple scripts.
</p>
- <p>
+ <p class="p">
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.
</p>
- <p>
+ <p class="p">
The taxonomy for the <em class="em">context</em>, <em class="em">define</em>, and <em class="em">parameter</em> are intentionally not defined here and left open.
One utilizing this should document the taxonomy for each of these as desired.
</p>
- <p>
+ <p class="p">
Vocabulary:
</p>
<dl class="dl">
</header>
<div class="section-content">
- <p>
+ <p class="p">
IKI is a minimally structured WIKI-like syntax meant to be simpler than WIKI syntax.
</p>
- <p>
+ <p class="p">
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 <em class="em">Object</em>.
The variable value is considered the <em class="em">Content</em>.
</p>
- <p>
+ <p class="p">
The IKI format will use <code class="code">iki-0000</code> to represent an IKI with no explicitly defined vocabulary.
Whereas <code class="code">iki-0001</code> and beyond represent a specific IKI vocabulary.
</p>
- <p>
+ <p class="p">
A potential IKI variable name starts on word (or <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) characters.
White space and non-word (and non <code class="code">_</code>, <code class="code">-</code>, <code class="code">+</code>) 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 (<code class="code">U+2010</code> and <code class="code">U+2011</code>).
</p>
- <p>
+ <p class="p">
Any valid IKI data may be escaped to make it treated as non-IKI data by prepending a backslash <code class="code">" before the colon code:</code>:" that is before the opening quote (single or double).
</p>
- <p>
+ <p class="p">
Unicode punctuation connector characters are supported just like <code class="code">_</code>, except when they connect outside the current line (such as <code class="code">U+FE33</code> <code class="code">︳</code>).
Unicode invisible punctuations (such as invisible plus: <code class="code">U+2064</code>) are not considered a punctuations in this standard (because they a zero-width characters), therefore they are not to be considered a valid <code class="code">_</code>, <code class="code">-</code>, or <code class="code">+</code> Unicode equivalents.
</p>
- <p>
+ <p class="p">
Key:
</p>
<ul>
<li><code class="code">*</code> = zero or more occurrences.</li>
<li><code class="code">~</code> = one or more occurrences, or zero if at start of file.</li>
</ul>
- <p>
+ <p class="p">
Before Structure:
</p>
<ul>
<li><code class="code">\x*\W~\*:*</code></li>
</ul>
- <p>
+ <p class="p">
Structure:
</p>
<ul>
<li><code class="code">\o\e:\q\c\q</code></li>
</ul>
- <p>
+ <p class="p">
After Structure:
</p>
<ul>
<li><code class="code"></code></li>
</ul>
- <p>
+ <p class="p">
Example File:
</p><pre class="preserve">
# fss-000c iki-0000
The following emphasis\:"is escaped to not be treated as IKI data".
</pre>
- <p>
+ <p class="p">
Example Results:
</p><pre class="preserve margin-below">
Objects would be:
projects / kevux.org-website / commitdiff