krm_notes #

Overview and file formats #

A new file, krm_notes.tsv, has been created, containing detailed annotation information added to the KRM_definitions.tsv file.

This is available in both TSV and JSON formats. To explicitly indicate that these are the filenames after the specification change in March 2025, lowercase “krm” was used instead of uppercase “KRM,” resulting in the names krm_notes.tsv and krm_notes.json.

Column name comparison #

This section compares the column names in the new krm_notes.tsv (v1.2.6) with those in the previous files it replaces or incorporates data from.

Comparison with KRM_definitions.tsv (v1.1.55) #

The following table shows the correspondence between columns primarily related to definition details derived from the previous definitions file:

Incorporation of KRM.tsv (v1.1.347) content #

The new krm_notes.tsv also incorporates information previously stored in KRM.tsv. The corresponding column names are compared below:

Data Structure: ER Diagram and JSON Implementation #

The JSON representation of krm_notes utilizes a nested format, as detailed below.

In the ER diagram, the krm_notes table is shown as a child table linked to krm_main (as detailed in the krm_main section) by entry_id. However, in the actual JSON data, the equivalent of the krm_notes table is not flat: instead, it is implemented as a nested array of objects under the key "definitions" within each top-level record (referred to as a krm_main conceptual record).

Each object inside the definitions array corresponds to a definition note and contains the following fields:

• definition_seq_id
• definition_elements
• definition_type_code
• definition_type_name
• remarks

This structure can be conceptually represented in the ER diagram as follows:

• The krm_main table has a one-to-many relationship with a conceptual definitions or notes table.
• In the JSON representation, the definitions are embedded as an array of objects within each krm_main object, rather than being stored in a separate flat table.

Example JSON:

{
  "entry_id": "F00001",
  ...
  "definitions": [
    {
      "definition_seq_id": "F00001_01",
      "definition_elements": "音仁（LV）「ニン」",
      "definition_type_code": 215,
      "definition_type_name": "音注声点有_類音注等",
      "remarks": "広韻「如鄰切」..."
    },
    ...
  ]
}

Description of each column #

Next, the content of the column names will be explained.

Content and Significance of Compiler’s Remarks (the remarks Column) #

Please note that this remarks column stores the Compiler's Remarks (annotations by the database creators).

The remarks column provides the following types of information:

• Additional context: Supplementary background or related information that aids in understanding the Myōgishō’s entries.
• Scholarly observations: Philological, linguistic, or other expert perspectives on specific descriptions, including references to previous research.
• Results of textual collation: Findings from comparisons with variant manuscripts or related materials, and textual interpretations based on these collations.
• Source investigations: Results and considerations regarding the textual sources of the Myōgishō’s entries, including references to findings from previous studies.

These remarks are each associated with one of the following specific parts of a Myōgishō Entry:

• A specific definition_element (an individual component of the Definition (Original Glosses)): This refers to a distinct element within the Myōgishō’s original annotation for an Entry (such as a particular Note on Character Form, Phonetic Gloss, Semantic Gloss in Chinese, or Japanese Native Reading (*wakun*)), as itemized in the krm_notes file.
• Or the Headword: The main character(s) of the Entry.

In essence, the remarks column serves to provide specialized, supplementary information from the database compilers, enabling a deeper understanding and facilitating further research that goes beyond what can be gleaned from the Myōgishō’s main text and original glosses alone.