henryluo

10 ms·

1. 91.▲
   by henryluo 9y ago

   Hexadecimal integer is not part of JSON. It is a new syntax introduced in JSON5 (not JSON version 5). I don't think this feature is that useful, thus does not incorporate it into Mark.
2. 92.▲
   by henryluo 9y ago

   Yes, I explicitly cut out DTD. I'm planning to developed a schema language for Mark, improving on prior art like XML Schema, JSON Schema, etc. There's already a transformation library - Mark Template ( https://github.com
3. 93.▲
   by henryluo 9y ago

   Current Mark design does not enforce a namespace standard. Namespace can be easily captured in Mark, e.g. {'ns:elmt' 'xml:attr':'value' ...} XML Namespace seems to have a lot issues, thus Mark does not want to
4. 94.▲
   by henryluo 9y ago

   Probably can consider convert to Mark ( https://mark.js.org ), instead of JSON.
5. 95.▲
   Mark – A simple and unified notation for both object and markup data(github.com)

   158 points by henryluo 9y ago|169 comments
6. 96.▲
   How the term 'open source' was coined 20 years ago(opensource.com)

   8 points by henryluo 9y ago|1 comments