Created
November 14, 2010 09:14
-
-
Save sorear/676033 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Principles of JSYNC as understood by sorear | |
1. JSYNC exists to interchange data. As such, it should be made as simple to | |
parse as possible, so that parsers are more likely to be correct. | |
2. It should be possible to use existing JSON tools to manipulate JSYNC texts. | |
Therefore, if two texts are semantically equivalent (and thus interchangable) | |
as JSON, they *must* also be interchangable as JSYNC. | |
3. JSYNC should be semantically equivalent to YAML. That means, it needs to | |
support tags, scalars, mappings, sequences, and recursive structures; but it | |
does not need to handle anchors or tag aliases in the same way. More | |
obviously, things like string escaping and comment handling can be completely | |
different or nonexistant. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment