# <!-- METAHEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"*": "https://raw.githubusercontent.com/wefindx/schema/master/intent/oo-item.yaml"
# <!-- HEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"base:title": "0oo - Meta standard for data reusability"
"og:title": "Meta standard for data reusability"
"og:description": "Ever since the creation of first software systems, such as life itself, something akin to evolving file formats has emerged, and they had taken very specific shapes. For example, the fact that we are using very specific sequences of symbols like curly braces `{`, `}` (`01111011` and `01111101`) to group larger chunks of code in most programming languages, may be quite arbitrary. The fact that life in DNA often uses very specific sequences (such as `AUG` .. `TAG`) as `start` and `stop` codons to group a protein may also be quite arbitrary. Every new version of Microsoft Excel may define …"
"og:image": "https://avatars0.githubusercontent.com/u/28134655"
"og:url": "/intent/862/"
"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": "<n class="oo">O; </n>"
"layout:set-language-post-action": "/i18n/setlang/"
"layout:csrf-token": "6RcSOiE1kaNBQriL3ZztWEDegob3ViVCXWdwNFVuyBbHh5CUlAo1pPYmcX93jagp"
"layout:input-next": "/intent/862/"
"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": "false", "name": "English"}, {"code": "ru", "is-active": "false", "name": "Русский"}, {"code": "oo", "is-active": "true", "name": "O;o,"}]
# <!-- TOPIC
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:parent:intents": [{"title": "&lt;n class=&quot;oo&quot;&gt;n#``&amp;nbsp;&amp;nbsp; &lt;/n&gt;", "url": "/intent/924/"}, {"title": "Extropy", "url": "/intent/69/"}, {"title": "Content Reusability Problem", "url": "/intent/60/"}]
"item:title": ".:en:Meta standard for data reusability.:cn:创建元标准以最大化所有数据和系统的可重用性"
"item:votes": +1
"item:add-vote": "#addnote"
"item:intent": "/intent/862/?l=oo"
"item:base-administration": false
"item:body": |
    .:en
    Ever since the creation of first software systems, such as life itself, something akin to evolving file formats has emerged, and they had taken very specific shapes. For example, the fact that we are using very specific sequences of symbols like curly braces `{`, `}` (`01111011` and `01111101`) to group larger chunks of code in most programming languages, may be quite arbitrary. The fact that life in DNA often uses very specific sequences (such as `AUG` .. `TAG`) as `start` and `stop` codons to group a protein may also be quite arbitrary. Every new version of Microsoft Excel may define slightly different **.xls** file format. The same is true for APIs and their versions. We have a problem of **complex evolving data and systems**.
    
    Today, part of the problem is addressed via intermediate level **standardization**, such as REST (Representational State Transfer), and OpenAPI (aka Swagger) specifically, enabling to create generic clients. For the sake of interoperability, engineers tend to choose to comply with the standards. However, <span style="color: red">**standardization approach does not generalize.**</span>
    
    From the scientific and data analyst's perspective, much like the text written in languages of other cultures, the format and the very specific shape that the data comes in, carries the information about the circumstances and the nature of the information sources that created them. They are the cultural and technological legacy, which, ideally, is left functional, accessible and **easily reusable**.
    
    This goal would be to create a maximally general **metastandard that maximizes reusability of any data and any systems**, in order to make them relevant in the future of the evolution.
"item:permalink": "/intent/862/?l=oo"
"item:source-date": ""
"item:owner": "Mindey"
"item:ownerlink": "/user/147/Mindey"
"item:created": "2019-09-11T14:53:00.832000"
"item:intent:child:add": "/admin/hlog/intent/add/?parent=862"
# <!-- LINKS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:method:items":
  - "id": "i-863"
    "title": "Metaformat"
    "summary": "Create a polycontext metasymbol, and overcome the fact that standardization does not generalize."
    "url": "/method/863/"
    "owner": "Mindey"
    "permalink": "/intent/862/?l=oo#i-863"
    "ownerlink": "/user/147/Mindey"
    "created": "2019-09-11T15:01:44.134000"
"item:method:add": "/admin/hlog/method/add/?parent=862"
"item:comment:add": "/intents/addnote?parent=862"
"item:comment:add:csrf_token": "6RcSOiE1kaNBQriL3ZztWEDegob3ViVCXWdwNFVuyBbHh5CUlAo1pPYmcX93jagp"
"item:comment:form": |
    <li> <textarea name="text" cols="40" rows="10" id="addnote" class="comment-textarea" required>
    </textarea></li>
    <li><label for="id_vote">Vote&lt;n class=&quot;oo&quot;&gt;:` &lt;/n&gt;</label> <select name="vote" id="id_vote">
      <option value="-1">[−]</option>
      <option value="0" selected>-</option>
      <option value="1">[+]</option>
    </select></li>
    <li><label for="id_crawl">Silently&lt;n class=&quot;oo&quot;&gt;:` &lt;/n&gt;</label> <input type="checkbox" name="crawl" onchange="handleSilently(this)" id="id_crawl"></li>
    <li><label for="id_has_questions">Questions&lt;n class=&quot;oo&quot;&gt;:` &lt;/n&gt;</label> <input type="checkbox" name="has_questions" id="id_has_questions"> <span class="helptext">Mark if the comment raises new questions.</span></li>
    <li><label for="id_has_ideas">Ideas&lt;n class=&quot;oo&quot;&gt;:` &lt;/n&gt;</label> <input type="checkbox" name="has_ideas" id="id_has_ideas"> <span class="helptext">Mark if the comment contributes potential solutions.</span></li>
    <li><label for="id_has_facts">Facts&lt;n class=&quot;oo&quot;&gt;:` &lt;/n&gt;</label> <input type="checkbox" name="has_facts" id="id_has_facts"> <span class="helptext">Mark if the comment contributes facts for reasoning.</span></li>
    <a href="/accounts/login/">Please, <u>log in</u>.</a>
# <!-- COMMENTS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:comment:items":
  - "id": "r-13"
    "text": |
        [chronological], you might find this parent category interesting to take a look at.
    "owner": "Mindey"
    "ownerlink": "/user/147/Mindey"
    "permalink": "/intent/862/?l=oo#r-13"
    "created": "2020-03-04T02:45:50.604000"
    "vote": "[+]"
"base:js": "/static/js/base.c7357c06cc89.js"