tar and rsync

[rbdr/blog] / doc / specs / 20200601-serving-different-versions.md

diff --git a/doc/specs/20200601-serving-different-versions.md b/doc/specs/20200601-serving-different-versions.md
index 545febbf3213c8df548f970d0ea747c8e33b1a3a..9eb1bd8b76e68be6ca372dd72907067bd272a7bf 100644 (file)
--- a/doc/specs/20200601-serving-different-versions.md
+++ b/doc/specs/20200601-serving-different-versions.md
@@ -118,7 +118,7 @@ a new generator that will generate an RSS 2.0 file
 ## When Adding a Post
 
 When the add function of the blog is triggered, it will shift the posts
 ## When Adding a Post
 
 When the add function of the blog is triggered, it will shift the posts

-as it currently does and then will generate a new UUID and take the
+as it currently does and then will generate a new unique ID and take the

 current timestamp. This will be saved in a JSON file in the output
 directory called "metadata.json"
 
 current timestamp. This will be saved in a JSON file in the output
 directory called "metadata.json"
 


@@ -156,9 +156,14 @@ This spec introduces a data structure to help generate output.
 tPost <Object>
   +html <String> // The markup of the post
   +publishedOn <Number> // The timestamp when this post was added
 tPost <Object>
   +html <String> // The markup of the post
   +publishedOn <Number> // The timestamp when this post was added

-  +uuid <String> // The UUID for this post
+  +id <String> // The Unique ID for this post

 ```
 
 ```
 

+Given that posts won't come in at a high enough rate, and that the
+purpouse is only to help feed readers identify each unique piece of
+content, for this version the `id` will be the same number as the
+`publishedOn`.
+

 ## The Generator Interface
 
 Every generator must implement this interface in order to work with
 ## The Generator Interface
 
 Every generator must implement this interface in order to work with