written in language

Relates an information object — an expression, a document, a source tree, an inscription reading — to a first-class gmeow:Language it is written in. The registry-independent replacement for flat inLanguage tags: the object is a Language IRI, never a code literal (codes are alignments via gmeow:languageCode). Non-functional: content mixes languages, and a codebase uses several.

Structure

Property shape: object property; gmeow:InformationObject -> gmeow:Language

Practical Pattern

Use gmeow:writtenInLanguage from gmeow:InformationObject to gmeow:Language when the relationship itself belongs in the native GMEOW graph.

Example Snippets

These snippets are generated from canonical slice examples and trimmed to the Turtle blocks where this term appears.

Multilingual Document

# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example: language as a first-class entity. A gmeow:Language is a
# reified individual carrying its gmeow:bcp47Tag — not a bare string column — so a
# document can be gmeow:writtenInLanguage SEVERAL co-equal languages at once
# (a bilingual manual), with no primary language privileged. The Language objects
# are minted (there is no closed enum of languages); the document is an
# InformationObject, the domain of gmeow:writtenInLanguage.
@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex:    <https://blackcatinformatics.ca/gmeow/examples/language/> .
@prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .

# --- A bilingual document: two co-equal languages, neither primary. The title is
#     carried as separate co-equal language-tagged literals, one per language.
ex:manual a gmeow:InformationObject ;
    gmeow:title             "Installation Manual"@en , "インストールマニュアル"@ja ;
    gmeow:writtenInLanguage gmeow:langEnglish , ex:japanese .

Common Companion Terms

gmeow:InformationObject, gmeow:Language

Usage Advice

Use when

Avoid when

How to use

Examples