Translate natural-language 5G4Data requirements into TM Forum ontology-based Turtle intents, using only workloads available in the workload catalogue. Use when creating, revising, validating, or explaining 5G4Data intents involving NetworkExpectation, DeploymentExpectation, ReportingExpectation, bandwidth, latency, workload-chart objectives, UUID4 identifiers, ChartMuseum workload lookup, or Turtle intent files.
Translate natural language to legal 5G4Data TMF Turtle intents. Infer intent structure, ask minimal clarifying questions, and stay strictly within the allowed subset.
Resolve ontology/examples from workspace root. In managed-agent sessions, the private repo is mounted at /workspace/5G4Data-private.
| Workspace root | Ontology entrypoint | Example intents |
|---|---|---|
5G4Data-public (monorepo) | /workspace/5G4Data-private/TM-Forum-Intent-Toolkit/TMForumIntentOntology/IntentCommonModel.ttl | Intent-Simulator/intents |
AgentSyntheticTimeseriesGeneration (this package) | /workspace/5G4Data-private/TM-Forum-Intent-Toolkit/TMForumIntentOntology/IntentCommonModel.ttl | ../Intent-Simulator/intents |
Start with IntentCommonModel.ttl; include other ontology files only as needed.
https://start5g-1.cs.uit.no/wchartmuseumGET /api/charts, GET /api/charts/<name>, GET /api/charts/<name>/<version>Rules:
DeploymentExpectation is allowed only if a suitable catalogue workload exists.values.yaml.values.yaml objectives.http://start5g-1.cs.uit.no:7200/, graph http://intendproject.eu/telenor/infra.data5g:DataCenter.dct:description, imo:handler, imo:ownerRules:
objectives in selected chart values.yaml.name, suffixed with _<condition-id>.tmf-value-hint.value does not block condition creation.Example: