From 38bda92277e44694cbc81b50e9fbd2692d501165 Mon Sep 17 00:00:00 2001
From: Kevin Day
- 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 Contents, referred to as Section Operations.
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 bb93807..cf88c0a 100644 --- a/fll/specifications.html +++ b/fll/specifications.html @@ -183,7 +183,7 @@
#!/bin/bash
", the setting files should have the following: "# fss-????" format, such as "# FSS-0001
".?
representing the (hexadecimal/base-16) number that represents the particular specification structure.
- 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 FSS-0000 (Basic)
, Content is treated as a single item whereas in FSS-0001 (Extended)
, Content is broken apart in multiple sub-parts.
+ 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 FSS-0000 (Basic)
, Content is treated as a single item whereas in FSS-0001 (Extended)
, Content is broken apart in multiple sub-parts.
- 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.
+ 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.
These columns do not need to be setup in a column structure, the word column 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 fss-000 (Basic)
the entire Content may be further represented as a single column.
- For example, in fss-001 (Extended)
the entire Content may be further represented as multiple columns.
+ 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 fss-000 (Basic)
the entire Content may be further represented as a single column.
+ For example, in fss-001 (Extended)
the entire Content may be further represented as multiple columns.
- 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 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. All spaces after the first separating white space is generally ignored until the first non white space character is found, unless otherwise specified.
@@ -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.
- 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 Object or Content.
- 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 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 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 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, quotes may only be either a single quote '
, a double quote "
, or a grave `
and only a backslash \
may be used as a delimiter.
@@ -258,7 +258,7 @@
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 Objects, delimits would only apply when that Object could be potentially identified as an Object.
For example, FSS-0001 (Extended)
needs quotes to group parts that include spaces, if there is no initial quote, then a quote following the data must not be delimited.
@@ -309,20 +309,20 @@ Object_2 This is multiple\" Contents and the trailing quote does not need to be
All specifications are expected to support or be of the character encoding UTF-8; 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 Objects, Contents, and delimits. All specifications do assume ASCII and Unicode support.
Unless otherwise specified, comments are designated by the pound symbol #
but only if only white space is to the left of the pound or the pound #
is at the start of the line.
There is no support for inline comments.
- Unless otherwise specified, the start comment may be delimited by \
in the same manner as Objects and Contents are.
+ Unless otherwise specified, the start comment may be delimited by \
in the same manner as Objects and Contents are.
This delimit only applies to the start of a comment (the pound #
character) as there is no terminating character for a comment (other than a newline \n
).
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 #
character) then that white space is ignored.
Unless otherwise specified, all designation characters must represent ASCII codes.
- With designation characters being any character code used to designate how to identify an Object or Content (such as a colon :
at the end of a basic list).
+ With designation characters being any character code used to designate how to identify an Object or Content (such as a colon :
at the end of a basic list).
This keeps the processing and logic simple and safe, for both UTF-8 and ASCII.
White space used for designation characters must include support for UTF-8 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.
--
1.8.3.1