Skip to content

Main content

Public Term Source Namespace Tool

Qualify a supplied public term by source/language metadata without authenticating language, meaning or access permission.

Loading tool…

Description

Serialize source, languageLabel, and term as qualifiedKey without modifying their strings.

Source-scoped cultural and historical records preserve an edition, naming convention, or local identifier. Literal agreement is useful bookkeeping but does not establish interpretation, authenticity, or authority.

Serialize source, languageLabel, and term as qualifiedKey without modifying their strings.

When to use this tool

Use Public Term Source Namespace when you need a precise source-token or range consistency check.

How to use the tool and how it works

  1. Enter term, source, languageLabel. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read qualifiedKey. Use the output convention below.

Serialize source, languageLabel, and term as qualifiedKey without modifying their strings.1

Input fieldMeaning and unitsAccepted input
termSingle mathematical contribution; aggregation and normalization are separate.Required. Text; maximum UTF-16 length 8192.
sourceSource label or index interpreted under the specific calculation above.Required. Text; maximum UTF-16 length 8192.
languageLabelLanguage LabelRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
qualifiedKeyJSON-array serialization preserving the source-scoped identifier components.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "term": "term-A",
    "source": "public-source-2",
    "languageLabel": "supplied-language"
  },
  "output": {
    "qualifiedKey": "[\"public-source-2\",\"supplied-language\",\"term-A\"]"
  }
}

Limitations and assumptions

  • This preserves source scope rather than imposing equivalence across languages or communities; cultural authority and reuse permission are not inferred.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Consult the source edition and relevant community or scholarly guidance before interpreting or reusing the material.

References

  1. Calculation and input contract: indigenous-studies/public-term-source-namespace — tool.io

Similar or alternative tools