# "*": "https://raw.githubusercontent.com/wefindx/schema/master/method/oo-item.yaml" # "base:title": "0oo - Metaformat" "og:title": "Metaformat" "og:description": "The basic idea is that we can create a header ("metaheader") to bind format and schema specifications to data, and a single **polycontext metasymbol** (a map that specifies in which context what metasymbol is to be used) to bind it to data, and link them with global namespaces of ontologies, schemas, and user identities. For example, the polycontext metasymbol may be defined by providing a map: <center>![](https://wiki.mindey.com/shared/shots/d455a078fd8190bd14d6cba0c.png)</center> Where, <i>C<sub>1</sub>...C<sub>N</sub></i> are format or language contexts, and <i>S<sub>1</sub>...S<sub>N</sub></i> are [metasymbols](https://proofwiki.org/wiki/Definition:Metalanguage/Metasymbol), and <i>N ∈ ℕ</i>. For example if we want to introduce a metasymbol in multiple languages and formats, which may be in …" "og:image": "https://avatars0.githubusercontent.com/u/28134655" "og:url": "/method/863/" "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-monolingual": "/mulang/?mulang=false" "layout:lang": "Language" "layout:set-language-post-action": "/i18n/setlang/" "layout:csrf-token": "PJSxbPDqLcvnRYf5ZOilheUohwlqJ6Bj9K3waCFUMyqYCr4UjPVoKv4tz75wcMcb" "layout:input-next": "/method/863/" "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,"}] # "item:parent:intents": [{"url": "/intent/90001/", "title": "Smart ontologies"}, {"url": "/intent/924/", "title": "Technology"}, {"url": "/intent/1311/", "title": "Data Liquidity and Systems Interoperability"}, {"url": "/intent/862/", "title": "Meta standard for data reusability"}, {"url": "/intent/105001/", "title": "Programmatic Access and Control"}, {"url": "/intent/1366/", "title": "Cyberspace"}] "item:title": ".:en:Metaformat" "item:summary": ".:en:Create a polycontext metasymbol, and overcome the fact that standardization does not generalize." "item:voting": +2 "item:voting:add": "/admin/hlog/voting/add/?method=863" "item:voting:csrf_token": "PJSxbPDqLcvnRYf5ZOilheUohwlqJ6Bj9K3waCFUMyqYCr4UjPVoKv4tz75wcMcb" "item:voting:submit-value-option": {"selected": "[-]", "value": "-"} "item:voting:submit-value-option": {"selected": "[+]", "value": "+"} "item:base-administration": false "item:body": | .:en The basic idea is that we can create a header ("metaheader") to bind format and schema specifications to data, and a single **polycontext metasymbol** (a map that specifies in which context what metasymbol is to be used) to bind it to data, and link them with global namespaces of ontologies, schemas, and user identities. For example, the polycontext metasymbol may be defined by providing a map:
import metaform metaform.load({ '*': 'https://github.com/mindey/terms/wiki/person#foaf', 'url': 'http://dbpedia.org/resource/John_Lennon', 'fullname': 'John Lennon', 'birthdate': '1940-10-09', 'spouse': 'http://dbpedia.org/resource/Cynthia_Lennon' }).format()"owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/863/?l=en#a-800" "created": "" - "id": "a-827" "text": | I am working on a system I call living documents. There's a link to a screencast here: https://github.com/samsquire/ideas#4-living-documents "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/863/?l=en#a-827" "created": "" - "id": "a-830" "text": | [chronological], first of all, big welcome to Homebase! Hope you find the place fun and entertaining. It's amazing to have you here! Let me check this out. "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/863/?l=en#a-830" "created": "" - "id": "a-832" "text": | // Living documents are the idea of intra document CMS that features the insertability of arbitrary data formats and provides integrations between inserted content blocks. It's a general purpose data structure editor. // Very good concept. However, imagine now that there do exist other systems, outside your internal system, and you want to control them via your internal system. How can you do? The metaform approach results in creating something I call a metadrive (it's among projects under this idea, not in "published" state though). The concept is that if we have drivers for other systems, we could simply mount them to our system. Mount anything, -- e.g., linkedin, or youtube, or something more advanced, and let it become your internal data structure. In practise, I think what's needed for this to happen, is something like Darklang, but better be open source. Check [Darklang](https://www.youtube.com/watch?v=NDg6Ko9gbGk). P.S. I'll fix the markdown, very soon. :) "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/863/?l=en#a-832" "created": "" - "id": "a-841" "text": | Finally, the markdown is fixed, and you can take a look better, hopefully, more understandable. The concept of metaformat is actually very deep. I had written a gitbook on it [here](https://book.mindey.com/metaformat/0001-metaform-philosophy/0001-metaform-philosophy.html). More generall, what needs to be done, is theoretically extract the equivalence classes for polycontext metasymbols. Practically, many drivers need to be written and supported for the systems that we want to make interoperative. **In short term,** work that needs to be done includes: _recognition of field names and the formats of data types and measure units, from larger set of data annotations created for datasets using metaformat. Call it **'autoformat'**: -see a dataset -> automatically generate metaformat description- :)_ "owner": "Mindey" "ownerlink": "/user/147/Mindey" "permalink": "/method/863/?l=en#a-841" "created": "" "base:js": "/static/js/base.c7357c06cc89.js"