Update README.markdown

[x_status_git] / README.markdown

diff --git a/README.markdown b/README.markdown
index 8a29e731f8f9ac86281707d7f2deeb451e529814..a03f40a5f5a25b6e1eab3ff668e206780e56bbcd 100644 (file)
--- a/README.markdown
+++ b/README.markdown
@@ -1,6 +1,6 @@
-# Status.git
+# x_status_git

 
 

-A minimal git‐based self‐hosted status publishing solution.
+A minimal git‐based microblog.

 
 ## What It Is
 
 
 ## What It Is
 


@@ -154,6 +154,24 @@ In all cases, for `/$PATH.jsonld`, this just serves the file at
       `[0-9A-Za-z_-]+`):
     Serve the file at `/topics/$TOPIC/index.jsonld`.
 
       `[0-9A-Za-z_-]+`):
     Serve the file at `/topics/$TOPIC/index.jsonld`.
 

+### Atom responses
+
+These responses **should** be served with a `Content-Type` of
+  `application/atom+xml`.
+In all cases, for `/$PATH.atom`, this just serves the file at
+  `/$PATH/index.atom`.
+
+ +  **`GET /statuses.atom`**:
+    Serve the file at `/statuses/index.atom`.
+
+ +  **`GET /statuses/$YYYY-MM.atom`** (where `$YYYY-MM` is an
+      `xsd:gYearMonth`):
+    Serve the file at `/$YYYY-MM/index.atom`.
+
+ +  **`GET /topics/$TOPIC.atom`** (where `$TOPIC` matches
+      `[0-9A-Za-z_-]+`):
+    Serve the file at `/topics/$TOPIC/index.atom`.
+

 ### Other Headers
 
 All responses **should** have a `Access-Control-Allow-Origin` header
 ### Other Headers
 
 All responses **should** have a `Access-Control-Allow-Origin` header


@@ -240,7 +258,7 @@ The files which represent a status are as follows :—
 Files with names that begin with the strings `2=` or `x_status_git_`
   are reserved for backwards‐compatible extensions.
 
 Files with names that begin with the strings `2=` or `x_status_git_`
   are reserved for backwards‐compatible extensions.
 

-Status.git has no opinion on how these files make their way into the
+x_status_git has no opinion on how these files make their way into the

   Git repository, except that all the files for a single status should
   be added in the same commit.
 The intention is that the simple nature of these files will make them
   Git repository, except that all the files for a single status should
   be added in the same commit.
 The intention is that the simple nature of these files will make them


@@ -249,7 +267,7 @@ The intention is that the simple nature of these files will make them
 ## I Am Computer, How Do I Get Status?
 
 Assume you are given a U·R·L `resource_url` which you think points to
 ## I Am Computer, How Do I Get Status?
 
 Assume you are given a U·R·L `resource_url` which you think points to

-  some kind of Status.git resource.
+  some kind of x_status_git resource.

 Start by resolving it as follows :—
 
 01. Make a `HEAD` request to `resource_url`.
 Start by resolving it as follows :—
 
 01. Make a `HEAD` request to `resource_url`.


@@ -349,5 +367,8 @@ Statuses themselves have the following properties :—
  +  **`subject`** [`dcterms:subject`] (optional):
     The topic of the status, for topic statuses.
 
  +  **`subject`** [`dcterms:subject`] (optional):
     The topic of the status, for topic statuses.
 

+ +  **`title`** [`dcterms:title`] (optional):
+    The title of the status.
+

  +  **`content`** [`sioc:content`]:
     The content of the status, as an `rdf:XMLLiteral`.
  +  **`content`** [`sioc:content`]:
     The content of the status, as an `rdf:XMLLiteral`.