Skip to content

Register five tmatic FWM ontologies (TravelStory, StoryProvenance, StoryRequest, StoryListen, TravelStoryPreferences) - #1116

Merged
coodos merged 1 commit into
mainfrom
tmatic-fwm-ontologies
Sep 1, 2026
Merged

Register five tmatic FWM ontologies (TravelStory, StoryProvenance, StoryRequest, StoryListen, TravelStoryPreferences)#1116
coodos merged 1 commit into
mainfrom
tmatic-fwm-ontologies

Conversation

@EgorPPS

@EgorPPS EgorPPS commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Ontologies of the tmatic.travel FWM (free walking mode) platform — AI-generated location-bound audio stories with trigger zones, plus listener-side records.

What each schema is

Schema Lives on What it is
travelStory.json company vault (Minstrel Technologies), acl ["*"] One language version of a location-bound story: text, trigger zones (CIRCLE/POLYGON, tmatic.travel semantics), narrated audio as w3ds://file
storyProvenance.json company vault, next to the story How the version came to be: who it was created for, request context, text/voice models, translation source. Language versions of one story are linked through provenance
storyRequest.json requester's vault One button-press context (geo/camera/voice); referenced by both StoryListen and StoryProvenance — written once, never copied
storyListen.json listener's vault One playback; exactly one of storyRef / tmaticStoryId (formalized via oneOf), tmaticLanguage requires tmaticStoryId (dependencies)
travelStoryPreferences.json person's vault, updated in place Narrow taste profile for travel stories (content languages, topics, provider affinity); deliberately not a general travel profile

Design rules

  • No field copies across ontologies — everything else is a link; titles/languages live only in the story.
  • Cross-vault links: w3ds://envelope?id=@<ename>/<envelopeId> — the owner eName is required in every link (vault hosting can change, the entity's eName cannot).
  • Provenance separated from content; one envelope per language version.
  • Reuses existing ontologies instead of minting rivals: User (inLanguage), uploadFile/File, FileExtraction (Add FileExtraction ontology schema #1110) for photo/voice readings, PersonalNote (Add PersonalNote ontology schema #1100) for free-form notes.

Already written in production by the platform; self-description: https://tmatic.postplatforms.com/.well-known/w3ds-platform.json

🤖 Generated with Claude Code

…oryRequest, StoryListen, TravelStoryPreferences)

Ontologies of the tmatic.travel FWM (free walking mode) platform: AI-generated
location-bound audio stories with author-designed trigger zones, their
provenance, and the listener-side records (requests, listens, taste profile).

Design rules followed: no field copies across ontologies (links only),
cross-vault references as w3ds://envelope?id=@<ename>/<id> with the owner
eName required, provenance separated from content, one envelope per language
version. StoryListen formalizes 'exactly one of storyRef/tmaticStoryId' via
oneOf and tmaticLanguage dependency per current review conventions.

Self-description: https://tmatic.postplatforms.com/.well-known/w3ds-platform.json

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@EgorPPS
EgorPPS requested a review from coodos as a code owner August 30, 2026 07:41
@coderabbitai

coderabbitai Bot commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 00a7efed-6062-48f9-ab11-a71ad8f91b35


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coodos
coodos merged commit 15ab96f into main Sep 1, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants