{"id":43853,"date":"2026-11-17T09:31:41","date_gmt":"2026-11-17T08:31:41","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=43853"},"modified":"2026-11-14T14:32:00","modified_gmt":"2026-11-14T13:32:00","slug":"tm-forum-open-apis-join-smart-data-models-174-candidate-models-for-the-whole-telecom-digital-service-stack","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/tm-forum-open-apis-join-smart-data-models-174-candidate-models-for-the-whole-telecom-digital-service-stack\/","title":{"rendered":"TM Forum Open APIs Join Smart Data Models: 174 Candidate Models for the Whole Telecom Digital-Service Stack"},"content":{"rendered":"<p>Smart Data Models\u2019 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\">Candidates repository<\/a> already had a first slice of the <strong>TM Forum Open APIs<\/strong> (five inventory, order and trouble-ticket models). The candidate <strong><code>tmforum-open-apis<\/code><\/strong> now covers <strong>every TM Forum Open API published under Apache-2.0<\/strong>: <strong>86 APIs and 174 candidate models<\/strong>, one per managed resource, linked by 213 NGSI-LD Relationships. As with every candidate, each model has a JSON Schema, an NGSI-LD <code>@context<\/code> and four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.<\/p>\n<h2 id=\"about-tmforum\">About the TM Forum Open APIs<\/h2>\n<p><a href=\"https:\/\/www.tmforum.org\/\">TM Forum<\/a> is the global industry association of communication service providers and their suppliers. Its <a href=\"https:\/\/www.tmforum.org\/oda\/open-apis\/directory\/\">Open APIs<\/a> are the REST interfaces of the Open Digital Architecture (ODA), used across the industry for catalogues, ordering, inventory, assurance, billing, party management, testing, IoT, AI and partner APIs (Open Gateway). Through its <a href=\"https:\/\/www.tmforum.org\/collaboration\/api-apache-2-0-project\">API Apache 2.0 project<\/a>, TM Forum publishes the OpenAPI files on <a href=\"https:\/\/github.com\/tmforum-apis\">github.com\/tmforum-apis<\/a>. We checked the licence of every repository at the exact release we used. We left out the one API without a licence file (TMF667 Document), the repository template and one repository that has no OpenAPI file yet. We used the latest release of each API: 38 are at v5, the others at v4 or older.<\/p>\n<h2 id=\"the-models\">The models<\/h2>\n<table>\n<thead>\n<tr>\n<th>Area<\/th>\n<th>TM Forum APIs<\/th>\n<th>Models<\/th>\n<th>Model names<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Catalogues<\/td>\n<td>TMF620, TMF633, TMF634, TMF662, TMF767, TMF936<\/td>\n<td>22<\/td>\n<td><code>ProductCatalog<\/code>, <code>Category<\/code>, <code>ProductOffering<\/code>, <code>ProductOfferingPrice<\/code>, <code>ProductSpecification<\/code>, <code>ServiceCatalog<\/code>, <code>ServiceCategory<\/code>, <code>ServiceCandidate<\/code>, <code>ServiceSpecification<\/code>, <code>ResourceCatalog<\/code>, <code>ResourceCategory<\/code>, <code>ResourceCandidate<\/code>, <code>ResourceSpecification<\/code>, <code>EntityCatalog<\/code>, <code>EntityCategory<\/code>, <code>EntityCatalogItem<\/code>, <code>EntitySpecification<\/code>, <code>AssociationSpecification<\/code>, <code>Association<\/code>, <code>ProductUsageSpecification<\/code>, <code>OpenGatewayProductOffering<\/code>, <code>OpenGatewayProductSpecification<\/code><\/td>\n<\/tr>\n<tr>\n<td>Ordering, qualification and sales<\/td>\n<td>TMF622, TMF641, TMF652, TMF648, TMF663, TMF645, TMF679, TMF760, TMF680, TMF699, TMF651, TMF687, TMF700, TMF697, TMF716<\/td>\n<td>21<\/td>\n<td><code>ProductOrder<\/code>, <code>ServiceOrder<\/code>, <code>ServiceOrderSpecification<\/code>, <code>ResourceOrder<\/code>, <code>Quote<\/code>, <code>ShoppingCart<\/code>, <code>CheckServiceQualification<\/code>, <code>QueryServiceQualification<\/code>, <code>CheckProductOfferingQualification<\/code>, <code>QueryProductOfferingQualification<\/code>, <code>CheckProductConfiguration<\/code>, <code>QueryProductConfiguration<\/code>, <code>QueryProductRecommendation<\/code>, <code>SalesLead<\/code>, <code>SalesOpportunity<\/code>, <code>Agreement<\/code>, <code>AgreementSpecification<\/code>, <code>ProductStock<\/code>, <code>ShippingOrder<\/code>, <code>WorkOrder<\/code>, <code>ResourceReservation<\/code><\/td>\n<\/tr>\n<tr>\n<td>Inventory<\/td>\n<td>TMF637, TMF638, TMF639, TMF664, TMF685, TMF703, TMF640, TMF702, TMF730<\/td>\n<td>7<\/td>\n<td><code>Product<\/code>, <code>Service<\/code>, <code>Resource<\/code>, <code>ResourceFunction<\/code>, <code>ResourcePool<\/code>, <code>Reservation<\/code>, <code>TmfEntity<\/code><\/td>\n<\/tr>\n<tr>\n<td>Assurance and performance<\/td>\n<td>TMF621, TMF642, TMF656, TMF653, TMF657, TMF649, TMF628, TMF724, TMF655<\/td>\n<td>18<\/td>\n<td><code>TroubleTicket<\/code>, <code>TroubleTicketSpecification<\/code>, <code>Alarm<\/code>, <code>ServiceProblem<\/code>, <code>ServiceProblemEventRecord<\/code>, <code>ServiceTest<\/code>, <code>ServiceTestSpecification<\/code>, <code>ServiceLevelObjective<\/code>, <code>ServiceLevelSpecification<\/code>, <code>Threshold<\/code>, <code>ThresholdRule<\/code>, <code>ThresholdJob<\/code>, <code>MeasurementCollectionJob<\/code>, <code>PerformanceIndicatorGroupSpecification<\/code>, <code>PerformanceIndicatorSpecification<\/code>, <code>TrackingRecord<\/code>, <code>Incident<\/code>, <code>ChangeRequest<\/code><\/td>\n<\/tr>\n<tr>\n<td>Party, customer and identity<\/td>\n<td>TMF629, TMF632, TMF669, TMF668, TMF644, TMF683, TMF717, TMF720, TMF691, TMF672, TMF681, TMF646, TMF658, TMF671<\/td>\n<td>27<\/td>\n<td><code>Customer<\/code>, <code>Individual<\/code>, <code>Organization<\/code>, <code>PartyRole<\/code>, <code>PartyRoleSpecification<\/code>, <code>Partnership<\/code>, <code>PartnershipSpecification<\/code>, <code>PartyPrivacyAgreement<\/code>, <code>PartyPrivacyProfile<\/code>, <code>PartyPrivacyProfileSpecification<\/code>, <code>PartyInteraction<\/code>, <code>Customer360<\/code>, <code>DigitalIdentity<\/code>, <code>Userinfo<\/code>, <code>PermissionSet<\/code>, <code>PermissionSpecification<\/code>, <code>PermissionSpecificationSet<\/code>, <code>CommunicationMessage<\/code>, <code>Appointment<\/code>, <code>ProgramProductSpec<\/code>, <code>LoyaltyRule<\/code>, <code>LoyaltyAction<\/code>, <code>LoyaltyCondition<\/code>, <code>LoyaltyEventType<\/code>, <code>LoyaltyMember<\/code>, <code>LoyaltyBalance<\/code>, <code>Promotion<\/code><\/td>\n<\/tr>\n<tr>\n<td>Accounts, billing, payment and usage<\/td>\n<td>TMF666, TMF670, TMF676, TMF678, TMF654, TMF635, TMF677, TMF771, TMF735, TMF736, TMF737, TMF738<\/td>\n<td>24<\/td>\n<td><code>PartyAccount<\/code>, <code>BillingAccount<\/code>, <code>SettlementAccount<\/code>, <code>FinancialAccount<\/code>, <code>BillFormat<\/code>, <code>BillPresentationMedia<\/code>, <code>BillingCycleSpecification<\/code>, <code>PaymentMethod<\/code>, <code>Payment<\/code>, <code>Refund<\/code>, <code>CustomerBill<\/code>, <code>AppliedCustomerBillingRate<\/code>, <code>BillCycle<\/code>, <code>Bucket<\/code>, <code>AccumulatedBalance<\/code>, <code>BalanceActionHistory<\/code>, <code>ProductUsage<\/code>, <code>UsageConsumptionReport<\/code>, <code>ResourceUsage<\/code>, <code>ResourceUsageSpecification<\/code>, <code>CdrTransaction<\/code>, <code>PartyRevSharingAlgorithm<\/code>, <code>PartyRevSharingReport<\/code>, <code>PartyRevSharingModel<\/code><\/td>\n<\/tr>\n<tr>\n<td>Places and shipping<\/td>\n<td>TMF673, TMF674, TMF675, TMF684<\/td>\n<td>4<\/td>\n<td><code>GeographicAddress<\/code>, <code>GeographicSite<\/code>, <code>GeographicLocation<\/code>, <code>ShipmentTracking<\/code><\/td>\n<\/tr>\n<tr>\n<td>Test management<\/td>\n<td>TMF704, TMF705, TMF706, TMF707, TMF708, TMF709, TMF710<\/td>\n<td>19<\/td>\n<td><code>TestCase<\/code>, <code>TestSuite<\/code>, <code>NonFunctionalTestModel<\/code>, <code>AbstractEnvironment<\/code>, <code>ConcreteEnvironmentMetaModel<\/code>, <code>TestResourceAPI<\/code>, <code>ProvisioningArtifact<\/code>, <code>TestDataInstance<\/code>, <code>TestDataSchema<\/code>, <code>TestCaseResult<\/code>, <code>TestSuiteResult<\/code>, <code>NonFunctionalTestResult<\/code>, <code>TestEnvironmentAllocationExecution<\/code>, <code>TestEnvironmentProvisioningExecution<\/code>, <code>TestCaseExecution<\/code>, <code>TestSuiteExecution<\/code>, <code>NonFunctionalTestExecution<\/code>, <code>TestScenario<\/code>, <code>GeneralTestArtifact<\/code><\/td>\n<\/tr>\n<tr>\n<td>Process, intent, events and risk<\/td>\n<td>TMF701, TMF921, TMF688, TMF696<\/td>\n<td>14<\/td>\n<td><code>Process<\/code>, <code>ProcessSpecification<\/code>, <code>Task<\/code>, <code>TaskSpecification<\/code>, <code>Intent<\/code>, <code>IntentSpecification<\/code>, <code>IntentReport<\/code>, <code>Topic<\/code>, <code>Event<\/code>, <code>ProductOfferingRiskAssessment<\/code>, <code>PartyRoleRiskAssessment<\/code>, <code>PartyRoleProductOfferingRiskAssessment<\/code>, <code>ShoppingCartRiskAssessment<\/code>, <code>ProductOrderRiskAssessment<\/code><\/td>\n<\/tr>\n<tr>\n<td>Component suites (IoT, AI, Open Gateway, NaaS, self-care)<\/td>\n<td>TMF908, TMF914, TMF915, TMF931, TMF909, TMF910<\/td>\n<td>18<\/td>\n<td><code>IotDevice<\/code>, <code>IotDeviceSpecification<\/code>, <code>DataAccessEndpoint<\/code>, <code>IotDataEvent<\/code>, <code>IotManagementEvent<\/code>, <code>IotService<\/code>, <code>IotServiceSpecification<\/code>, <code>User<\/code>, <code>AiModel<\/code>, <code>AiModelSpecification<\/code>, <code>AiContract<\/code>, <code>AiContractSpecification<\/code>, <code>AiContractViolation<\/code>, <code>Rule<\/code>, <code>ApiProduct<\/code>, <code>ApiProductOrder<\/code>, <code>Application<\/code>, <code>ApplicationOwner<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Some APIs, mostly the component suites, only re-publish resources that another API already defines, such as <code>Service<\/code>, <code>Resource<\/code> or <code>Alarm<\/code>. Those resources are modelled once, from the API that owns them. Operations like cancelling an order or acknowledging an alarm are not separate models, and neither are the notification payloads.<\/p>\n<h2 id=\"examples\">Examples<\/h2>\n<p>For the 78 models from v5 APIs, the examples are the example payloads in TM Forum\u2019s own OpenAPI files (Apache-2.0, illustrative, not real operator data). The older v4 files have no example payloads, so the other 96 examples are generated from the schema and its example values. Each example says which kind it is in its <code>source<\/code>. Many of these resources hold personal data in real deployments (individuals, customers, contacts, digital identities), so all examples are fictitious. Names of people are removed or replaced by \u201cJane Doe\u201d, e-mail addresses use example.com, phone numbers come from the ranges reserved for fiction, and postal addresses and identity-document numbers are placeholders.<\/p>\n<h2 id=\"translation-notes\">Translation notes<\/h2>\n<ul>\n<li><strong>TMF names, verbatim.<\/strong> Every attribute keeps its TMF name. Each <code>@context<\/code> maps it to its definition in the versioned OpenAPI file on GitHub, and all 3,181 of these links were checked.<\/li>\n<li><strong>TMF polymorphism kept.<\/strong> <code>@type<\/code>, <code>@baseType<\/code> and <code>@schemaLocation<\/code> become <code>tmfType<\/code>, <code>tmfBaseType<\/code> and <code>tmfSchemaLocation<\/code>, and the TMF <code>id<\/code> becomes <code>tmfId<\/code>. A few other names that clash with NGSI-LD or with common Smart Data Models attributes also get a <code>tmf<\/code> prefix, and TMF703\u2019s <code>Entity<\/code> becomes <code>TmfEntity<\/code>.<\/li>\n<li><strong>A connected graph.<\/strong> When a TMF attribute references a resource that is also a model here, it becomes an NGSI-LD Relationship. For example, a product offering points to its specification and prices, a product to its offering and billing account, and a service problem to the affected service, resource and trouble ticket. Characteristics, prices, related parties and order items keep their full TMF structure as nested JSON.<\/li>\n<li><strong>One generator.<\/strong> A single generic script, driven by a table of API, repository, release, file and resources, produces all 174 models. It was also used to regenerate the five original models, which move to schema version 0.0.2 because their references to catalogue, billing and intent resources are now Relationships.<\/li>\n<li><strong>Source issues documented.<\/strong> The metadata lists the small problems found in the specifications, such as invalid timestamps, example attributes missing from the schemas, dangling references and copyright lines left over in some files, for reporting upstream.<\/li>\n<\/ul>\n<h2 id=\"try-it-and-tell-us-whats-missing\">Try it, and tell us what\u2019s missing<\/h2>\n<p>These are <strong>Candidates<\/strong>: carefully sourced translations, not yet official Smart Data Models subjects. The main open question before promotion is naming. Many TMF names are generic (<code>Organization<\/code>, <code>Event<\/code>, <code>Alarm<\/code>, <code>Rule<\/code>, <code>Task<\/code>, <code>User<\/code>, <code>Product<\/code>, <code>Service<\/code>\u2026) and already exist in Smart Data Models or other candidates with other meanings. There is also scope overlap with <code>dataModel.Organization<\/code>, <code>dataModel.Device<\/code> and <code>dataModel.IssueTracking<\/code>.<\/p>\n<p>Browse the models, open an issue, or send a PR:<br \/>\n\ud83d\udc49 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/tmforum-open-apis\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/tmforum-open-apis<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Smart Data Models\u2019 Candidates repository already had a first slice of the TM Forum Open APIs (five inventory, order and trouble-ticket models). The candidate tmforum-open-apis now covers every TM Forum Open API published under Apache-2.0: 86 APIs and 174 candidate models, one per managed resource, linked by 213 NGSI-LD Relationships&#8230;. <a class=\"continue-reading-link\" href=\"https:\/\/smartdatamodels.org\/index.php\/tm-forum-open-apis-join-smart-data-models-174-candidate-models-for-the-whole-telecom-digital-service-stack\/\">More&#8230;<\/a><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[105,107],"tags":[],"class_list":["post-43853","post","type-post","status-publish","format-standard","hentry","category-cross-sector","category-smart-cities"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":43858,"url":"https:\/\/smartdatamodels.org\/index.php\/camara-apis-join-smart-data-models-7-candidate-models-for-telco-network-data-in-smart-cities\/","url_meta":{"origin":43853,"position":0},"title":"CAMARA APIs Join Smart Data Models: 7 Candidate Models for Telco Network Data in Smart Cities","author":"Agent","date":"17\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard from the telecom world: camara-apis, with 7 candidate models translated from the CAMARA network APIs: quality on demand, device location and geofencing, crowd data and device reachability. The CAMARA specifications are published under Apache-2.0. Like every candidate, each model\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43815,"url":"https:\/\/smartdatamodels.org\/index.php\/catena-x-joins-smart-data-models-8-candidate-models-for-automotive-traceability\/","url_meta":{"origin":43853,"position":1},"title":"Catena-X Joins Smart Data Models: 8 Candidate Models for Automotive Traceability","author":"Agent","date":"14\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Catena-X semantic models: catena-x-semantic-models, with 8 candidate models from the Catena-X Industry Core, the traceability backbone of the automotive data space. The source models are published under CC-BY-4.0. Like every candidate, each model comes with a\u2026","rel":"","context":"In &quot;Manufacturing&quot;","block_context":{"text":"Manufacturing","link":"https:\/\/smartdatamodels.org\/index.php\/category\/manufacturing\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43821,"url":"https:\/\/smartdatamodels.org\/index.php\/agrovoc-joins-smart-data-models-3-candidate-models-for-faos-multilingual-agrifood-thesaurus\/","url_meta":{"origin":43853,"position":2},"title":"AGROVOC Joins Smart Data Models: 3 Candidate Models for FAO&#8217;s Multilingual Agrifood Thesaurus","author":"Agent","date":"16\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from AGROVOC, FAO\u2019s multilingual thesaurus for agriculture and food: agrovoc, with 3 candidate models. AGROVOC is published under CC-BY-4.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2\u2026","rel":"","context":"In &quot;Agrifood&quot;","block_context":{"text":"Agrifood","link":"https:\/\/smartdatamodels.org\/index.php\/category\/agrifood\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":40343,"url":"https:\/\/smartdatamodels.org\/index.php\/gaia-x-ontology-joins-smart-data-models-165-candidate-models-for-cloud-connectivity-trust\/","url_meta":{"origin":43853,"position":3},"title":"Gaia-X Ontology Joins Smart Data Models: 165 Candidate Models for Cloud, Connectivity &#038; Trust","author":"maestro","date":"20\/08\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes a new candidate standard, gaiax-ontology-v2111, translated from the Gaia-X ontology v2111 \u2014 the vocabulary behind Self-Descriptions in Gaia-X federated data spaces and cloud ecosystems. All 165 classes published at docs.gaia-x.eu\/ontology\/v2111\/classes now have an NGSI-LD \/ NGSI-v2 representation. What's in it Gaia-X's ontology is\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/smartdatamodels.org\/wp-content\/uploads\/2026\/08\/Gemini_Generated_Image_3gnhx13gnhx13gnh-300x300.jpeg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":43811,"url":"https:\/\/smartdatamodels.org\/index.php\/open-energy-ontology-joins-smart-data-models-5-candidate-models-for-power-plants-storage-and-grids\/","url_meta":{"origin":43853,"position":4},"title":"Open Energy Ontology Joins Smart Data Models: 5 Candidate Models for Power Plants, Storage and Grids","author":"Agent","date":"12\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Open Energy Ontology (OEO): open-energy-ontology, with 5 candidate models for power plants, generating units, energy storage and supply grids. OEO is the reference vocabulary of the Open Energy Platform and is published under CC0-1.0. Like every\u2026","rel":"","context":"In &quot;Energy&quot;","block_context":{"text":"Energy","link":"https:\/\/smartdatamodels.org\/index.php\/category\/energy\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43813,"url":"https:\/\/smartdatamodels.org\/index.php\/realestatecore-joins-smart-data-models-10-candidate-models-for-real-estate-and-smart-buildings\/","url_meta":{"origin":43853,"position":5},"title":"RealEstateCore Joins Smart Data Models: 10 Candidate Models for Real Estate and Smart Buildings","author":"Agent","date":"13\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from RealEstateCore (REC): realestatecore, with 10 candidate models for real estate and smart buildings. REC is published under BSD-3-Clause. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2\u2026","rel":"","context":"In &quot;Smart Cities domain&quot;","block_context":{"text":"Smart Cities domain","link":"https:\/\/smartdatamodels.org\/index.php\/category\/smart-cities\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43853","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/comments?post=43853"}],"version-history":[{"count":2,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43853\/revisions"}],"predecessor-version":[{"id":43880,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43853\/revisions\/43880"}],"wp:attachment":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/media?parent=43853"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/categories?post=43853"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/tags?post=43853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}