OntoBoomOntoBoomHub
← Hub

@ontoboom/telecom

Telecom / CSP ontology aligned with the TM Forum SID (Shared Information/Data Model): the Party, Customer, Product, Service, and Resource domains plus catalog, order, agreement/SLA, usage, billing, and trouble-management entities. The classic Product → CustomerFacingService → ResourceFacingService → Resource decomposition is modeled explicitly, so agents can reason from a customer's product down to the network resources that realize it.

39
Classes
38
Object properties
60
Data properties
0
Individuals

Connect this ontology

● Checking…
MCP endpoint
https://mcp.ontoboom.com/o/@ontoboom/telecom@0.1.0
{
  "mcpServers": {
    "ontoboom": {
      "url": "https://mcp.ontoboom.com/o/@ontoboom/telecom@0.1.0",
      "transport": "sse"
    }
  }
}

Two manifest-derived tools are exposed in this iteration:list_entities anddescribe_entity. More tools (find_relationship, enumerate_values) ship as followups.

README

@ontoboom/telecom

A communications-service-provider ontology whose structure follows the TM Forum SID (Shared Information/Data Model) — the de-facto information model behind TM Forum Frameworx and Open Digital Architecture (ODA).

Not affiliated. This is an independently authored ontology aligned with / inspired by the TM Forum SID. It is not an official TM Forum artifact and is not affiliated with, sponsored by, or endorsed by TM Forum. "TM Forum", "SID", and "Frameworx" are trademarks of their respective owner.

Coverage (by SID domain)

  • Party — Individual / Organization play PartyRoles (Customer, Supplier), with CustomerAccount, BillingAccount, and ContactMedium.
  • Product — ProductCatalog → ProductCategory → ProductOffering (priced by ProductOfferingPrice, specified by ProductSpecification with ProductCharacteristics); the realized instance is Product.
  • Service — ServiceSpecification, Service split into CustomerFacingService (CFS) and ResourceFacingService (RFS).
  • Resource — ResourceSpecification, Resource split into PhysicalResource (Equipment) and LogicalResource (TelephoneNumber, IPAddress).
  • Engaged party / order — ProductOrder + ProductOrderItem, Agreement, ServiceLevelAgreement.
  • Usage & billing — UsageRecord, AppliedBillingRate, CustomerBill, Payment.
  • Assurance — TroubleTicket, ServiceProblem.
  • Location — GeographicSite, GeographicAddress.

The SID decomposition (why it matters for agents)

Customer ── owns ──> Product ── realized by ──> CustomerFacingService
                                                      │ uses
                                                      ▼
                                              ResourceFacingService ── uses ──> Resource

An agent can answer "which network resources are at risk if this customer's broadband product degrades?" by walking Product → CFS → RFS → Resource.

SHACL highlights

  • Lifecycle/status fields are enumerated to SID-style vocabularies: ProductOrder.state (acknowledged | inProgress | completed | cancelled | …), Service.operationalState (inService | outOfService | …), TroubleTicket.status and severity.
  • TelephoneNumber.e164 matches ^\+?[1-9]\d{1,14}$; IPAddress.address matches an IPv4 pattern.
  • Monetary amounts (price, bill, payment, appliedRate) are >= 0; currency matches ^[A-Z]{3}$.

Forking

For a mobile-only operator, drop IPAddress / broadband CFS and add SIM / IMSI logical resources. For wholesale, extend PartyRole with Partner and add inter-carrier settlement on top of AppliedBillingRate.

Reviews

Sign in to review

No reviews yet · Be the first to review.

Sort: