Metaformat

+2  

Create a polycontext metasymbol, and overcome the fact that standardization does not generalize.

YAML 想法

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:

Where, C1...CN are format or language contexts, and S1...SN are metasymbols, and N ∈ ℕ.

For example if we want to introduce a metasymbol in multiple languages and formats, which may be in conflict with the already-defined symbols and reserved words within the languages and formats, we can introduce a polycontext metasymbol with domain in those languages and formats, for example, XML, RDF, JSON, YAML, Python, JavaScript, Scheme , and codomain with our chosen values for S, for example __, _, *, *, #*, {/*S*/}, #|*|#, etc., and then use it for arbitrary semantic or syntactic purposes.

Universal Finger ☝️

Think of polycontext metasymbol as a universal pointer, that can point to anything, and acquires context-neutral form to go to point and ask questions about the things that monocontext metasymbols cannot. You may also think of polycontext metasymbol as an operator with domain spanning across the data specified in different languages, and thus enables us to talk about or operate on them all at once.

Metaformat

A metaformat, is a set of rules that specify, how the parsing (interpretation) rules are to be embedded within different contexts (data chunks). This is done via the polycontext metasymbol and a few standards, like URLs for referencing, and the serialization languages for schema specification within that URL. Many specific metaformats can be defined, by choosing different polycontext metasymbols, URL formats, and schema specification styles. The below example relies on what I call MFT-1 specification.

Usage Example

Suppose that we use polycontext metasymbol * in all contexts, except those where it is a reserved word, and use key-value pairs to provide formats via URLs as their values, with the format (schema) data in machine-human readable key-value specifications. Then here is how it may look as follows.

In JSON As * key, with value pointing to URL of specifications.

{"*": "https://github.com/infamily/_/wiki/example#test1", "field1": "Haiz", "field2": { "properties": { "field3": 12}}}

In XML As <?_ *=""> attribute at any level, with value pointing to URL of specification.

```

Haiz 12 ```

Specifying the value for the symbol, allows to link schema and data formats directly to the data instances, and have data self-normalizable, and ontologically automatically combine-able, and understand the above record as:

Simpler than JSON-LD

The LinkedData format, such as JSON-LD, we may have:

{ "@context": "https://json-ld.org/contexts/person.jsonld", "@id": "http://dbpedia.org/resource/John_Lennon", "name": "John Lennon", "born": "1940-10-09", "spouse": "http://dbpedia.org/resource/Cynthia_Lennon" }

We can write the same thing using the above metaformat, as:

{ '*': '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' }

This way, we do not require the standardization of @id field, because the mapping of the field specifying it can be described in the format specification itself, provided via the polycontext metasymbol. This adds additional degree of freedom for data authors, and less burden for data analysts.

Hypothesis -- the reason of small adoption of semantic web technologies is because of the overcomplexification of metastandards. This simplifies it, deconstrains, and reduces burden to stick with any particular vocabulary.



(別通知) (可選) 請,登錄

那麼,語義​​Web技術-過度約束的系統?

So, semantic web technologies -- overconstrained system?


相關協議: -[DID](https://w3c-ccg.github.io/did-spec/)s -[DCAT](https://www.w3.org/TR/vocab-dcat/)s

Related protocols: - DIDs - DCATs


嗯,現在有一個軟件包,可以使用以下工具進行測試:

嘗試pip install metaform,然後

導入變形

metaform.load({
'*':'https://github.com/mindey/terms/wiki/person#foaf',
 'url':'http://dbpedia.org/resource/John_Lennon',
 '全名':'約翰·列儂',
 '生日':'1940-10-09',
 '配偶':'http://dbpedia.org/resource/Cynthia_Lennon'
})。格式()

Umm, there is a package now, that can be tested with:

Try pip install metaform, and then

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()

我正在開發一個稱爲實時文檔的系統。這裏有一個截屏的鏈接:

https://github.com/samsquire/ideas

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


[按時間順序],首先,歡迎您來到Homebase!希望您發現這個地方有趣而有趣。真高興能有您在這裏!讓我看看這個。

[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.


//活動文檔是內部文檔CMS的概念,它具有任意數據格式的可插入性並在插入的內容塊之間提供集成。這是一個通用的數據結構編輯器。 //

很好的概念。但是,現在想象一下,在內部系統之外確實存在其他系統,並且您希望通過內部系統進行控制。怎麼辦metaform方法導致創建了我稱爲metadrive的東西(它是在這種想法下的項目之中,儘管不是處於“已發佈”狀態)。其概念是,如果我們有用於其他系統的驅動程序,則可以簡單地將它們安裝到我們的系統中。掛載任何內容,例如linkedin,youtube或其他更高級的內容,並使其成爲您的內部數據結構。

實際上,我認爲實現此目標所需的是Darklang之類的東西,但最好是開源的。選中[Darklang](https://www.youtube.com/watch?v=NDg6Ko9gbGk)。附言我將盡快解決降價問題。 :)

// 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. P.S. I'll fix the markdown, very soon. :)


最後,減價是固定的,您可以更好地看待它,希望它更容易理解。元格式的概念實際上很深。我在[這裏](https://book.mindey.com/metaformat/0001-metaform-philosophy/0001-metaform-philosophy.html)上寫了一本gitbook。從理論上講,需要做的是概括性地提取多上下文元符號的等價類。實際上,需要編寫許多驅動程序併爲我們要使其互操作的系統提供支持。

短期而言,需要完成的工作包括:從使用元格式爲數據集創建的較大數據註釋集中識別字段名稱以及數據類型和度量單位的格式。稱其爲“'自動格式'**”:-查看數據集->自動生成元格式描述-:)

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. 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- :)


語言