From: Kevin Day Date: Fri, 24 Apr 2020 02:49:14 +0000 (-0500) Subject: Update: further clarify fss specification rules in regards to leading/trailing whites... X-Git-Tag: 0.5.0~343 X-Git-Url: https://git.kevux.org/?a=commitdiff_plain;h=31dc60a97ec8b45708414a5b66d33b1879283558;p=fll Update: further clarify fss specification rules in regards to leading/trailing whitespace in object names --- diff --git a/specifications/fss.txt b/specifications/fss.txt index 86a2595..d359284 100644 --- a/specifications/fss.txt +++ b/specifications/fss.txt @@ -29,6 +29,9 @@ Unless explicitly defined, newlines designate the start of a potential new Objec Unless explicitly defined, whitespace may exist to the left of the start of objects. +Unless explicitly defined, whitespace immediately both before and after an object is not considered part of an object. +This simplifies identifying the object, use quoted objects to support whitespace before/after an object. + Unless explicitly defined, quotes may only be either a single quote or a double quote and only a backslash may be used as a delimiter. Unless explicitly defined by the specification, character/data delimits are performed only when required and not unilaterally.