# <!-- METAHEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"*": "https://raw.githubusercontent.com/wefindx/schema/master/method/oo-item.yaml"
# <!-- HEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"base:title": "0oo - Interactive YAML Notes!"
"og:title": "Interactive YAML Notes!"
"og:description": "So, for example, [Metadrive](/project/854/i0), serializes data on disk in form of [YAML](https://yaml.org/), which brings methods to data instances (&quot;interactive data&quot;). We edit notes with various types of editors, which are [approaching](https://github.com/microsoft/vscode/issues/82084) what the functionality of [outliners](https://en.wikipedia.org/wiki/Outliner). In fact, YAML is perfect for serializing outlines, perhaps much more so than [OPML](https://en.wikipedia.org/wiki/OPML), because it the representation is much closer to what would be rendered as outlines. Considering that instances serialized have sessions and methods brought by metadrive, it is easy to imagine that editors could provide bindings to look up and call those methods associated with each file, this way providing the …"
"og:image": "https://avatars0.githubusercontent.com/u/28134655"
"og:url": "/method/897/"
"base:css": "/static/css/bootstrap.min.9c25540d6272.css"
"base:extra-css": "/static/css/base.57997aeac1df.css"
"base:favicon": "/static/favicon.acaa334f0136.ico"
"base:body_class": ""
"layout:logo": "/static/0oo.8d2a8bbef612.svg"
"layout:index": "/"
"layout:menu": "/menu/"
"layout:categories": "/intents/"
"layout:ideas": "/methods/"
"layout:projects": "/projects/"
"layout:users": "/users/"
"layout:about": "/about/"
"layout:help": "/help/"
"layout:bug_report": "https://github.com/wefindx/0oo"
"layout:login": "/accounts/login/"
"layout:light-off": "/darken/?darken=true"
"layout:set-multilingual": "/mulang/?mulang=true"
"layout:lang": "Language"
"layout:set-language-post-action": "/i18n/setlang/"
"layout:csrf-token": "t14GbIsIC6xTXtDtN5Mt9BqIrVDLlzhjBfLAeg2QparidFKchiYO9PgAcn7SIuvW"
"layout:input-next": "/method/897/"
"layout:languages": [{"code": "ja", "is-active": "false", "name": "日本語"}, {"code": "lt", "is-active": "false", "name": "Lietuviškai"}, {"code": "zh-hans", "is-active": "false", "name": "简体中文"}, {"code": "en", "is-active": "true", "name": "English"}, {"code": "ru", "is-active": "false", "name": "Русский"}, {"code": "oo", "is-active": "false", "name": "O;o,"}]
# <!-- TOPIC
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:parent:intents": [{"url": "/intent/1304/", "title": "Personal data collection for learning"}, {"url": "/intent/898/", "title": "Give power to users to initiate decisions directly from personal knowledge bases"}]
"item:title": ".:en:Interactive YAML Notes!"
"item:summary": "None"
"item:voting": 0
"item:voting:add": "/admin/hlog/voting/add/?method=897"
"item:voting:csrf_token": "t14GbIsIC6xTXtDtN5Mt9BqIrVDLlzhjBfLAeg2QparidFKchiYO9PgAcn7SIuvW"
"item:voting:submit-value-option": {"selected": "[-]", "value": "-"}
"item:base-administration": false
"item:body": |
    .:en
    So, for example, [Metadrive](/project/854/i0), serializes data on disk in form of [YAML](https://yaml.org/), which brings methods to data instances ("interactive data"). We edit notes with various types of editors, which are [approaching](https://github.com/microsoft/vscode/issues/82084) what the functionality of [outliners](https://en.wikipedia.org/wiki/Outliner). In fact, YAML is perfect for serializing outlines, perhaps much more so than [OPML](https://en.wikipedia.org/wiki/OPML), because it the representation is much closer to what would be rendered as outlines. Considering that instances serialized have sessions and methods brought by metadrive, it is easy to imagine that editors could provide bindings to look up and call those methods associated with each file, this way providing the interactivity to notes!
    
    So, for example, if this post is a "infinity post" (i.e., it's on api.infty.xyz), it can live on my desktop as a file, and I can reply it just directly through editor, while editing it in the serialized form.
    
    This kind of notes would give power back to users to initiate decisions directly from personal wiki, which stores partial copy of the web data.
    
    (One could imagine using MongoDB or something instead of Disk, sure.)
"item:source-date": ""
"item:permalink": "/method/897/?l=en"
"item:owner": "Mindey"
"item:created": "2019-10-14T14:04:44.771000"
"item:ownerlink": "/user/147/Mindey"
# <!-- LINKS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:link:add": "/admin/hlog/link/add/?parent=897"
"item:link:items":
"item:project:items":

# <!-- COMMENTS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:comment:items":
"base:js": "/static/js/base.c7357c06cc89.js"