Case Study: Using DefinedTermSet for AI Visibility Terminology

Hi all,



I wanted to share a real-world implementation of DefinedTermSet and
DefinedTerm that others might find useful, as practical examples seem to be
scarce.



Context

We've published canonical definitions for a new domain of terms around "AI
Visibility" - how websites communicate with AI systems like LLMs and AI
search engines. The terminology includes:

*	AI Visibility (AV-001)
*	AI Visibility Checking (AV-002)
*	AI Discovery Files (AV-003)
*	AI Visibility Tracking (AV-004)
*	AI Visibility Monitoring (AV-005)
*	AI Retrieval Testing (AV-006)



Implementation

We used DefinedTermSet to group the terms as a controlled vocabulary, with
individual DefinedTerm items for each definition.



Key features of our implementation:

1.	Term codes - Each term has a termCode (AV-001, etc.) for citation
and reference
2.	@graph pattern - Single JSON-LD block with bidirectional links
between set and terms
3.	Wikidata sameAs - Cross-linked to Wikidata items for each concept
4.	Combined types - Same page includes TechArticle, WebPage, and
BreadcrumbList
5.	Machine-readable exports - JSON and YAML versions alongside HTML



Questions for the community

1.	DefinedTerm vs CategoryCode - We chose DefinedTerm because these are
prose definitions, not enumerated codes. Is that the right distinction?
2.	inDefinedTermSet warning - The validator flagged inDefinedTermSet on
the DefinedTermSet itself. We've removed it, but wanted to confirm:
inDefinedTermSet should only appear on child DefinedTerm items, correct?
3.	Hierarchy representation - Some of our terms have parent/child
relationships (AI Visibility Tracking → AI Visibility Monitoring). Is there
a preferred way to represent this beyond isPartOf?



Live implementation

*	Definition page: https://www.365i.co.uk/ai-visibility-definition/
*	JSON version:
https://www.365i.co.uk/ai-visibility-definition/ai-visibility-definition.jso
n
*	YAML version:
https://www.365i.co.uk/ai-visibility-definition/ai-visibility-definition.yam
l



Happy to answer questions about the implementation or update based on
community feedback.


Cheers,
Mark

  _____

(Note: We've also created Wikidata items for these terms - Q137757467
<https://www.wikidata.org/wiki/Q137757467>  for AI Visibility, Q137757511
<https://www.wikidata.org/wiki/Q137757511>  for AI Visibility Checking,
Q137757518 <https://www.wikidata.org/wiki/Q137757518>  for AI Discovery
Files - if anyone's interested in the knowledge graph integration side.)

Received on Tuesday, 13 January 2026 08:13:20 UTC