{"id":1475,"date":"2026-02-25T10:42:06","date_gmt":"2026-02-25T10:42:06","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/"},"modified":"2026-02-25T10:42:06","modified_gmt":"2026-02-25T10:42:06","slug":"soaml-elements-you-must-know","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/","title":{"rendered":"Core Elements in SoaML You Must Know"},"content":{"rendered":"<p>Too many teams start modeling services by sketching operations and endpoints\u2014missing the real foundation. The strength of a service-oriented architecture begins not with APIs, but with how you define the players involved. SoaML provides a disciplined way to model these actors and their relationships.<\/p>\n<p>As a service architect, I\u2019ve seen teams struggle with ambiguity in roles: Is a participant a business unit, a system, or a team? The confusion leads to inconsistent models and poor alignment between business and IT. In this chapter, I\u2019ll clarify each core SoaML element with real modeling patterns, naming guidance, and practical examples from enterprise projects.<\/p>\n<p>You\u2019ll learn how to distinguish between a provider and a consumer, how to model capabilities as reusable building blocks, and how service channels reflect actual integration paths. These elements aren\u2019t just syntax\u2014they\u2019re the foundation of clarity, maintainability, and interoperability in complex enterprise systems.<\/p>\n<h2>Understanding the SoaML Participant Element<\/h2>\n<p>The <strong>SoaML participant element<\/strong> represents an autonomous entity capable of engaging in service interactions. It\u2019s the primary actor in a service ecosystem\u2014whether a business unit, a system, or a third-party service.<\/p>\n<p>Think of a participant as the host of services. For example, in an order management system, the \u201cOrder Processing System\u201d is a participant. But also, the \u201cCustomer Service Team\u201d might be a participant\u2014especially when modeling business-level interactions.<\/p>\n<p>Key modeling guidelines:<\/p>\n<ul>\n<li>Use clear, singular nouns: <code>Order Management System<\/code>, not <code>Order Management Systems<\/code>.<\/li>\n<li>Include a brief description: \u201cHandles order creation, validation, and fulfillment.\u201d<\/li>\n<li>Label only one role per participant unless it\u2019s a multi-role collaborator (e.g., a system that both provides and consumes).<\/li>\n<\/ul>\n<h3>When to Use a Participant vs. a Role<\/h3>\n<p>A participant is the entity; a role is its function within a collaboration. For instance, the \u201cPayroll System\u201d is a participant. In the context of \u201cEmployee Onboarding,\u201d it may play the role of <em>Payroll Provider<\/em>.<\/p>\n<p>Use roles to clarify behavior and avoid overloading participants with multiple responsibilities. This keeps your diagrams readable and supports reuse across different collaboration scenarios.<\/p>\n<h2>SoaML Provider and Consumer: The Heart of Interaction<\/h2>\n<p>Every service interaction hinges on two roles: provider and consumer. The <strong>SoaML provider<\/strong> offers a capability. The <strong>SoaML consumer<\/strong> requests or invokes it.<\/p>\n<p>This distinction is critical. Mixing up provider and consumer leads to misaligned contracts, failed integrations, and unclear ownership.<\/p>\n<h3>Modeling Patterns for Clarity<\/h3>\n<p>Use these patterns to keep your models unambiguous:<\/p>\n<ol>\n<li><strong>Directional naming:<\/strong> Name roles based on function: <code>Invoice Provider<\/code>, <code>Customer Lookup Consumer<\/code>.<\/li>\n<li><strong>Dependency arrows:<\/strong> Draw arrows from consumer to provider to show invocation flow.<\/li>\n<li><strong>Single responsibility:<\/strong> A participant should not be both provider and consumer in the same contract unless explicitly justified.<\/li>\n<\/ol>\n<p>Consider a logistics system where the \u201cShipment Tracking Service\u201d is a provider, and the \u201cCustomer Portal\u201d is the consumer. The consumer retrieves tracking data via a query operation. This relationship is clean, explicit, and easy to validate.<\/p>\n<h2>SoaML Capability Modeling: Reusable Building Blocks<\/h2>\n<p>Capabilities define what a participant can do\u2014without specifying how. A <strong>SoaML capability<\/strong> is a high-level business or technical ability that can be fulfilled by one or more services.<\/p>\n<p>For example, \u201cManage Customer Accounts\u201d is a capability. It may be implemented by a service in the \u201cCustomer Service\u201d participant, or split across multiple services depending on granularity.<\/p>\n<p>Modeling capabilities early helps avoid the common pitfall of modeling services before understanding the business domain. It promotes reuse and enables alignment between business strategy and technical design.<\/p>\n<h3>Best Practices for SoaML Capability Modeling<\/h3>\n<ul>\n<li>Use action-verb-noun patterns: <code>Process Orders<\/code>, <code>Validate Payments<\/code>, <code>Generate Invoices<\/code>.<\/li>\n<li>Group related capabilities under a participant: <code>Order Management<\/code> capability group.<\/li>\n<li>Ensure capabilities are independent of technology\u2014focus on business intent.<\/li>\n<li>Map capabilities to service interfaces during design to ensure traceability.<\/li>\n<\/ul>\n<p>Example: The \u201cFinance\u201d participant may have the <code>Manage Invoices<\/code> capability. This capability is implemented by a service that provides invoice creation, status updates, and payment reconciliation.<\/p>\n<h2>Service Channels: The Path of Communication<\/h2>\n<p>Communication doesn\u2019t just happen\u2014it happens through a <strong>service channel<\/strong>. This is the actual mechanism or protocol used to deliver messages: REST, SOAP, AMQP, gRPC, or even file-based transfer.<\/p>\n<p>A service channel defines how interactions are transported, not what they do. It\u2019s the difference between a capability (\u201cSend Notification\u201d) and the method (\u201cvia email via SMTP\u201d or \u201cvia HTTP POST to \/notify\u201d).<\/p>\n<p>When modeling, always specify the channel. A model showing a consumer using a service without a channel is incomplete. You can\u2019t validate, integrate, or secure without knowing the transport.<\/p>\n<h3>Common Service Channel Types<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Channel Type<\/th>\n<th>Use Case<\/th>\n<th>SoaML Modeling Tip<\/th>\n<\/tr>\n<tr>\n<td>REST<\/td>\n<td>Web APIs, microservices<\/td>\n<td>Label as <code>REST\/HTTP<\/code><\/td>\n<\/tr>\n<tr>\n<td>SOAP<\/td>\n<td>Enterprise messaging, legacy systems<\/td>\n<td>Specify version: <code>SOAP 1.2<\/code><\/td>\n<\/tr>\n<tr>\n<td>AMQP<\/td>\n<td>Message queues, event-driven<\/td>\n<td>Use <code>Message Broker<\/code> or <code>Event Bus<\/code> as channel name<\/td>\n<\/tr>\n<tr>\n<td>gRPC<\/td>\n<td>High-performance, internal services<\/td>\n<td>Mark as <code>gRPC (Binary)<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Tip: When a service uses multiple channels (e.g., REST for web, AMQP for background jobs), model separate service channels for clarity.<\/p>\n<h2>Putting It Together: A Real-World Example<\/h2>\n<p>Let\u2019s model a simplified \u201cOrder Fulfillment\u201d scenario:<\/p>\n<ul>\n<li><strong>Participant:<\/strong> Order Fulfillment System<\/li>\n<li><strong>Capability:<\/strong> Fulfill Orders<\/li>\n<li><strong>Provider:<\/strong> Inventory Service (of the Order Fulfillment System)<\/li>\n<li><strong>Consumer:<\/strong> Shipment Service (also in the same system)<\/li>\n<li><strong>Service Channel:<\/strong> REST\/HTTP<\/li>\n<\/ul>\n<p>The Shipment Service consumes the <code>Fulfill Order<\/code> capability via a REST call to <code>\/api\/fulfillment<\/code>. The channel is REST, the provider is the Inventory Service, and the consumer is the Shipment Service.<\/p>\n<p>This model is clear, traceable, and aligns business capabilities with technical implementation.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What is the difference between a SoaML participant and a service?<\/h3>\n<p>A participant is an entity that hosts or uses services. A service is a concrete offering (e.g., \u201cValidate Customer\u201d) with a contract. One participant can host multiple services.<\/p>\n<h3>Can a participant be both provider and consumer?<\/h3>\n<p>Yes\u2014especially in complex systems. For example, a monitoring system may provide health checks (provider) and consume logs from other systems (consumer). Always label the role clearly to avoid confusion.<\/p>\n<h3>How do I name capabilities effectively?<\/h3>\n<p>Use action-verb-noun pairs: <code>Process Payment<\/code>, <code>Generate Report<\/code>. Avoid generic terms like \u201cService 1\u201d or \u201cFunction A.\u201d Prioritize business clarity over technical syntax.<\/p>\n<h3>Why is SoaML capability modeling important?<\/h3>\n<p>It enables reuse, supports business-IT alignment, and helps avoid redundant or overlapping services. A capability can be fulfilled by different services over time, improving flexibility.<\/p>\n<h3>How do I choose the right service channel?<\/h3>\n<p>Match the channel to the interaction pattern: REST for stateless web calls, AMQP for event-driven decoupling, gRPC for internal high-speed services. Use the channel to guide technology selection and security policies.<\/p>\n<h3>What\u2019s the best way to visualize SoaML elements in tooling?<\/h3>\n<p>Use Visual Paradigm\u2019s SoaML palette: drag participants, assign roles, link to capabilities, and specify channels. Use color coding to distinguish between providers, consumers, and channels for fast visual scanning.<\/p>\n<p>Mastering these core SoaML elements isn\u2019t about memorizing syntax. It\u2019s about building models that reflect reality\u2014where roles are clear, capabilities are reusable, and interactions are traceable.<\/p>\n<p>You\u2019re now equipped to design service-oriented architectures that are not just functional, but understandable, maintainable, and future-proof.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many teams start modeling services by sketching operations and endpoints\u2014missing the real foundation. The strength of a service-oriented architecture begins not with APIs, but with how you define the players involved. SoaML provides a disciplined way to model these actors and their relationships. As a service architect, I\u2019ve seen teams struggle with ambiguity in [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1474,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1475","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Core SoaML Elements You Must Know<\/title>\n<meta name=\"description\" content=\"Master the essential SoaML elements: participants, providers, consumers, capabilities, and service channels. Learn practical modeling patterns, naming rules, and real-world applications for robust service-oriented architecture design.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Core SoaML Elements You Must Know\" \/>\n<meta property=\"og:description\" content=\"Master the essential SoaML elements: participants, providers, consumers, capabilities, and service channels. Learn practical modeling patterns, naming rules, and real-world applications for robust service-oriented architecture design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/\",\"name\":\"Core SoaML Elements You Must Know\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:42:06+00:00\",\"description\":\"Master the essential SoaML elements: participants, providers, consumers, capabilities, and service channels. Learn practical modeling patterns, naming rules, and real-world applications for robust service-oriented architecture design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SoaML Diagram Fundamentals: A Beginner\u2019s Guide\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Building Blocks of SoaML Diagrams\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Core Elements in SoaML You Must Know\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Core SoaML Elements You Must Know","description":"Master the essential SoaML elements: participants, providers, consumers, capabilities, and service channels. Learn practical modeling patterns, naming rules, and real-world applications for robust service-oriented architecture design.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/","og_locale":"pt_PT","og_type":"article","og_title":"Core SoaML Elements You Must Know","og_description":"Master the essential SoaML elements: participants, providers, consumers, capabilities, and service channels. Learn practical modeling patterns, naming rules, and real-world applications for robust service-oriented architecture design.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/","name":"Core SoaML Elements You Must Know","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:42:06+00:00","description":"Master the essential SoaML elements: participants, providers, consumers, capabilities, and service channels. Learn practical modeling patterns, naming rules, and real-world applications for robust service-oriented architecture design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/soaml-elements-you-must-know\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"SoaML Diagram Fundamentals: A Beginner\u2019s Guide","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/"},{"@type":"ListItem","position":3,"name":"Building Blocks of SoaML Diagrams","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/soaml-diagram-fundamentals\/soaml-modeling-basics\/"},{"@type":"ListItem","position":4,"name":"Core Elements in SoaML You Must Know"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1475","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1475\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1474"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1475"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}