Tiddlywiki Metadata Ontology v0.0.1 release

linonetwo · June 9, 2024, 7:23am

Following Suggestion for all Plugin developers about field name: Let’s use Ontology to maintain Interoperability, I made this new ontology plugin.

Docs: https://tiddly-gittly.github.io/super-tag/#$:/plugins/linonetwo/wmo

The effect may not be very significant in English, but under zh-Hans language, dynamic-table plugin translate fields using i18n information in this ontology (and tmo, task modeling ontology, another plugin)

Before:

After:

JS code to get i18n translation from trait tags:

github.com

tiddly-gittly/hyper-table/blob/3f7658d5693f62f25ec546dbd23b42dea2e5f07d/src/hyper-table/utils/getFieldName.ts

/* eslint-disable unicorn/no-null */
/* eslint-disable @typescript-eslint/strict-boolean-expressions */
import { JSONSchema4 } from 'json-schema';

/**
 * If no trait tag provide the translation, will have `null`. If unchecked, it will be `undefined`.
 */
const cachedFieldTranslation: Record<string, string | null | undefined> = {};
let traitTagSchemas: JSONSchema4[] | undefined;
/**
 * Get translated field name from available trait tags.
 * @param field english field name
 */
function getSchemas() {
  return $tw.wiki.filterTiddlers('[all[shadows+tiddlers]tag[$:/SuperTag/TraitTag]]')
    .map(title => $tw.wiki.getTiddler(title)?.fields?.schema)
    .map((schema: unknown) => {
      if (typeof schema === 'string') {
        try {
          return JSON.parse(schema) as JSONSchema4;

This file has been truncated. show original

It consolidate what field we can use, and let us know for sure what fields that other develoeprs are using, how our plugins will affect each other’s plugin and user’s wiki.