Saturday, February 13
Jsyn
Announcing Jsyn, the JSON syndication format for blogs and everything else.
Specification for version sqrt(-1):
1. Put a bunch of stuff in a data structure.
2. JSON-encode it.
3. Make it available somehow.
...
What, you need more of a spec? But I've registered a domain and everything!
Seriously, freedom from so-called "simple" syndication, coming soon! Part of the Pita* project.
Update: Spec version -1:
A Jsyn feed object will have precisely three first level sub-elements:
1. A
2. A
3. A
Example:
{"feed": {"source": "http://ai.mee.nu/feed.jsyn"},
"schema": {"source": "http://jsyn.net/schemas/blog.jsyn", "version": 1.0},
"items": []}
A client may use a local copy of the schema so long as the version matches that specified in the
* Which is part of the Minx project**, which is part of the make-Pixy-rich-or-drive-him-insane-either-is-fine project.
** I've subdivided Minx into three parts, like Gaul, only with less garlic: Minx, the bliki; Meta, the template, formatting, and scripting engine; and Pita, the database engine/abstraction layer. In addition, there's Miko, the planned desktop client.
Comments are disabled.
Post is locked.
Announcing Jsyn, the JSON syndication format for blogs and everything else.
Specification for version sqrt(-1):
1. Put a bunch of stuff in a data structure.
2. JSON-encode it.
3. Make it available somehow.
...
What, you need more of a spec? But I've registered a domain and everything!
Seriously, freedom from so-called "simple" syndication, coming soon! Part of the Pita* project.
Update: Spec version -1:
A Jsyn feed object will have precisely three first level sub-elements:
1. A
feed
element, an object containing the feed properties (required).2. A
schema
element, an object containing advisory schema information (optional).3. A
items
element, an array of objects representing the data items (required, but may be empty).Example:
{"feed": {"source": "http://ai.mee.nu/feed.jsyn"},
"schema": {"source": "http://jsyn.net/schemas/blog.jsyn", "version": 1.0},
"items": []}
A client may use a local copy of the schema so long as the version matches that specified in the
schema
object. The server must increment the version when updating the schema. The server may revert to an older schema with a lower version number; the client must not continue to use the local copy of the schema in this case.* Which is part of the Minx project**, which is part of the make-Pixy-rich-or-drive-him-insane-either-is-fine project.
** I've subdivided Minx into three parts, like Gaul, only with less garlic: Minx, the bliki; Meta, the template, formatting, and scripting engine; and Pita, the database engine/abstraction layer. In addition, there's Miko, the planned desktop client.
Posted by: Pixy Misa at
01:17 PM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 240 words, total size 2 kb.
46kb generated in CPU 0.0125, elapsed 0.1057 seconds.
54 queries taking 0.0972 seconds, 345 records returned.
Powered by Minx 1.1.6c-pink.
54 queries taking 0.0972 seconds, 345 records returned.
Powered by Minx 1.1.6c-pink.