Update: Have fss-000e Payload be more specific about payload handling.

Because payload may be anything, especially a binary blob, having it always be last as a requirement makes the most sense.
This then allows me to guarantee comments and other lists may not be after or inside.
This allows for the payload to not have to have comments or delimited code to deal with.
The payload will be a complete virgin binary blob until EOF or a designated length is reached.

diff --git a/specifications/fss-000e.txt b/specifications/fss-000e.txt
index b319bb01b2c1eea6d9312aa21717c0e31cb010da..a1f97445eed314e1f1ff77b2d945d9226bec154b 100644 (file)
--- a/specifications/fss-000e.txt
+++ b/specifications/fss-000e.txt
@@ -11,10 +11,13 @@ Featureless Settings Specification: 000e - Payload:
   The header's Content is of type fss-0001 Extended.
   The payload's Content is of any type including raw binary data.
 
-  The payload is recommended to be the last list Object in the file.
+  The payload is required to be the last list Object in the file.
   The payload is recommended to have its size designated in some manner in the "header".
-  The designated size is sugggested to use the fss-0001 Object "length".
+  The designated size is recommended to use the fss-0001 Object "length".
   The payload may contain anything, including NULL characters.
+  The payload is terminated by the EOF (end of file) character or when a designated "length" is reached.
+  Nothing in the payload may be considered a valid list Object and therefore there will be no escaping allowed.
+  Comments are not considered comments inside the payload and are considered part of the payload.
 
   Other than the reserved list Objects "header" and "payload" any other valid Object may be specified.