{"id":840,"date":"2026-02-25T10:25:36","date_gmt":"2026-02-25T10:25:36","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/"},"modified":"2026-02-25T10:25:36","modified_gmt":"2026-02-25T10:25:36","slug":"defining-decision-table-inputs","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/","title":{"rendered":"Defining the Decision Context and Inputs"},"content":{"rendered":"<p>When I walk into a project where the decision table is failing to capture edge cases, I rarely see misaligned conditions. I almost always find the root issue is a poorly scoped set of inputs\u2014variables not clearly defined, boundaries undefined, or contextual constraints ignored. It\u2019s not the rules that break; it\u2019s the foundation.<\/p>\n<p>Too many teams rush to write conditions without first asking: What exactly are we deciding? What factors matter? Who or what is being evaluated? The answers define the input space\u2014and if the inputs are fuzzy, so is the entire table.<\/p>\n<p>This chapter is built on over two decades of guiding teams through real-world rule modeling. You\u2019ll learn how to identify decision variables, define their valid ranges, and establish context boundaries that prevent gaps and overlaps. You\u2019ll also discover how to approach decision table setup with a rigor that scales from simple workflows to enterprise-grade logic.<\/p>\n<h2>Identifying the Core Decision Variables<\/h2>\n<p>Start not with a rule, but with the question: What decision are we actually making?<\/p>\n<p>Ask yourself: What is the outcome we are trying to determine? Is it eligibility? Risk level? Approval status? The answer defines the decision context.<\/p>\n<p>Once you know the decision type, extract the variables that influence it. These are your core decision table inputs.<\/p>\n<p>For example, in a loan approval system, the decision is \u201capprove loan.\u201d The inputs might include:<\/p>\n<ul>\n<li>Applicant income<\/li>\n<li>Debt-to-income ratio<\/li>\n<li>Credit score<\/li>\n<li>Loan-to-value ratio<\/li>\n<li>Employment duration<\/li>\n<\/ul>\n<p>These aren\u2019t just fields. They are decision variables\u2014each capable of taking discrete values or ranges that must be formally defined.<\/p>\n<h3>Defining Decision Variables with Precision<\/h3>\n<p>Each variable must be defined in a way that\u2019s unambiguous, measurable, and consistent across all rules. A common mistake is using vague terms like \u201chigh income\u201d or \u201cgood credit.\u201d These are not inputs\u2014they are interpretations.<\/p>\n<p>Instead, define variables with exact thresholds and clear data types:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Variable<\/th>\n<th>Definition<\/th>\n<th>Values\/Ranges<\/th>\n<\/tr>\n<tr>\n<td>Credit Score<\/td>\n<td>External bureau score (FICO)<\/td>\n<td>300\u2013850 (integer)<\/td>\n<\/tr>\n<tr>\n<td>Debt-to-Income Ratio<\/td>\n<td>Monthly debt \/ Gross monthly income<\/td>\n<td>0.0 to 1.0 (float, up to 2 decimals)<\/td>\n<\/tr>\n<tr>\n<td>Employment Duration<\/td>\n<td>Years employed at current job<\/td>\n<td>0.0 to 50.0 (float, 1 decimal)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>By defining inputs this way, you eliminate ambiguity. Every rule can now reference <em>credit score \u2265 700<\/em> or <em>debt-to-income ratio \u2264 0.35<\/em>\u2014not \u201cgood\u201d or \u201clow.\u201d<\/p>\n<h2>Setting Scope Boundaries and Context Constraints<\/h2>\n<p>Defining variables isn\u2019t enough. You must also define the operational scope: what\u2019s in, what\u2019s out, and what\u2019s assumed.<\/p>\n<p>Consider a healthcare eligibility table. You might need to ask:<\/p>\n<ul>\n<li>Are dependent children included in income calculations?<\/li>\n<li>Do we consider part-time employment as sufficient for coverage?<\/li>\n<li>Are applicants under 18 excluded by default?<\/li>\n<\/ul>\n<p>These aren\u2019t rules. They\u2019re constraints that shape the input space.<\/p>\n<h3>Documenting Context with Input Constraints<\/h3>\n<p>Always document the assumptions and exclusions that define the decision context. These are not part of the rule logic\u2014but they are essential for interpreting it correctly.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>Eligibility Age:<\/strong> Must be 18 or older. Applicants under 18 are not eligible, regardless of income or coverage type.<\/li>\n<li><strong>Dependents:<\/strong> Only children under 19 are eligible as dependents. Adult dependents are not covered unless they are disabled.<\/li>\n<li><strong>Income Source:<\/strong> Only gross monthly income from employment is considered. Retirement, disability, or investment income does not qualify.<\/li>\n<\/ul>\n<p>These constraints are not conditions to be evaluated. They are preconditions that must be enforced before any rule applies.<\/p>\n<p>When these are missing, teams often miss edge cases\u2014like a 17-year-old with high income or a disabled adult seeking coverage.<\/p>\n<h2>Validating Input Completeness<\/h2>\n<p>After defining variables and constraints, validate your inputs using a simple three-part checklist:<\/p>\n<ol>\n<li><strong>Are all relevant variables included?<\/strong> Ask: Could any rule be affected by a factor not listed? If yes, you\u2019ve missed an input.<\/li>\n<li><strong>Are all variables mutually exclusive and exhaustive?<\/strong> If a variable has overlapping ranges or undefined values, your table may miss cases.<\/li>\n<li><strong>Are there any hidden assumptions?<\/strong> If the variable behavior depends on an external system or policy not documented here, the table will fail in production.<\/li>\n<\/ol>\n<p>I once worked on a payroll system where the \u201covertime eligibility\u201d rule failed because the input \u201chours worked\u201d wasn\u2019t defined as \u201cweekly hours.\u201d The system assumed daily, causing incorrect overtime calculations.<\/p>\n<h3>Decision Table Setup: A Step-by-Step Framework<\/h3>\n<p>Here\u2019s how I structure decision table setup in practice:<\/p>\n<ol>\n<li><strong>Define the decision goal<\/strong> \u2014 \u201cDetermine if employee is eligible for overtime pay.\u201d<\/li>\n<li><strong>Extract influencing variables<\/strong> \u2014 Weekly hours, job classification, union rules, shift type.<\/li>\n<li><strong>Define values and ranges<\/strong> \u2014 e.g., <em>Weekly hours: \u226540<\/em>, <em>Job classification: exempt or non-exempt<\/em>.<\/li>\n<li><strong>Define context constraints<\/strong> \u2014 e.g., <em>Only full-time employees are considered<\/em>, <em>Shifts must be 8+ hours<\/em>.<\/li>\n<li><strong>Map constraints to input validation<\/strong> \u2014 Add a validation rule: <em>Reject if hours worked &lt; 0 or &gt; 80<\/em>.<\/li>\n<\/ol>\n<p>This process ensures your decision table inputs are not just defined\u2014but pre-validated.<\/p>\n<h2>Common Pitfalls in Decision Table Inputs<\/h2>\n<p>The most frequent errors I see stem from poor input modeling. Here are the top three:<\/p>\n<ul>\n<li><strong>Using natural language without definitions<\/strong> \u2014 \u201cGood credit\u201d or \u201cstable job\u201d are not inputs. They\u2019re interpretations.<\/li>\n<li><strong>Ignoring boundary conditions<\/strong> \u2014 What happens if income is exactly 70,000? Is it included? Define thresholds clearly.<\/li>\n<li><strong>Assuming input values are consistent<\/strong> \u2014 If one rule uses \u201cmonths\u201d and another \u201cyears,\u201d your logic will break.<\/li>\n<\/ul>\n<p>Always normalize input values. If your system uses months, convert all data to months. If it uses years, convert consistently. Inconsistency leads to logic errors.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know which variables to include in a decision table?<\/h3>\n<p>Ask: \u201cWhat changes in this decision if this factor changes?\u201d If the outcome could shift, it\u2019s a variable. If not, it\u2019s irrelevant. Use stakeholder interviews and workflow analysis to identify key influencers.<\/p>\n<h3>Can decision table inputs include external data sources?<\/h3>\n<p>Yes\u2014but only if they\u2019re stable, reliable, and consistently formatted. If the input relies on a third-party API, define its expected output format clearly. Treat external sources as variables with defined constraints.<\/p>\n<h3>What if the decision logic changes after the table is built?<\/h3>\n<p>Revisit your inputs. If the change affects an input variable (e.g., new eligibility age), update the definition and revalidate all rules. A modular input definition makes this easier.<\/p>\n<h3>How do I handle categorical inputs like \u201cstatus\u201d or \u201ctype\u201d?<\/h3>\n<p>Define each category explicitly. For example, \u201cEmployment Status\u201d should list: Full-Time, Part-Time, Contract, Temporary, Unemployed. Avoid open-ended values like \u201cactive\u201d or \u201cworking.\u201d Use standardized codes if needed.<\/p>\n<h3>Is it okay to have inputs that are not Boolean or numeric?<\/h3>\n<p>Yes\u2014but they must be fully defined. A string input like \u201clocation\u201d must specify valid values: e.g., \u201cNYC\u201d, \u201cLA\u201d, \u201cChicago\u201d. Use a controlled vocabulary to prevent invalid entries.<\/p>\n<h3>Why should I document context constraints separately from inputs?<\/h3>\n<p>Constraints are not conditions\u2014they are assumptions that govern the table&#8217;s validity. If you embed them in rules, you risk duplication and contradictions. Keeping them separate ensures clarity and easier maintenance.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I walk into a project where the decision table is failing to capture edge cases, I rarely see misaligned conditions. I almost always find the root issue is a poorly scoped set of inputs\u2014variables not clearly defined, boundaries undefined, or contextual constraints ignored. It\u2019s not the rules that break; it\u2019s the foundation. Too many [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":839,"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-840","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>Defining Decision Table Inputs<\/title>\n<meta name=\"description\" content=\"Learn how to define decision table inputs with precision. Master decision variables, scope boundaries, and contextual constraints for accurate, complete rule modeling in business logic 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\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Defining Decision Table Inputs\" \/>\n<meta property=\"og:description\" content=\"Learn how to define decision table inputs with precision. Master decision variables, scope boundaries, and contextual constraints for accurate, complete rule modeling in business logic design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/\",\"name\":\"Defining Decision Table Inputs\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:25:36+00:00\",\"description\":\"Learn how to define decision table inputs with precision. Master decision variables, scope boundaries, and contextual constraints for accurate, complete rule modeling in business logic design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Decision Tables Explained: From Concept to Implementation\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Designing Decision Tables Step by Step\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Defining the Decision Context and Inputs\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Defining Decision Table Inputs","description":"Learn how to define decision table inputs with precision. Master decision variables, scope boundaries, and contextual constraints for accurate, complete rule modeling in business logic 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\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/","og_locale":"pl_PL","og_type":"article","og_title":"Defining Decision Table Inputs","og_description":"Learn how to define decision table inputs with precision. Master decision variables, scope boundaries, and contextual constraints for accurate, complete rule modeling in business logic design.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/","name":"Defining Decision Table Inputs","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:25:36+00:00","description":"Learn how to define decision table inputs with precision. Master decision variables, scope boundaries, and contextual constraints for accurate, complete rule modeling in business logic design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/defining-decision-table-inputs\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Decision Tables Explained: From Concept to Implementation","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/"},{"@type":"ListItem","position":3,"name":"Designing Decision Tables Step by Step","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/decision-tables-explained\/decision-table-design-step-by-step\/"},{"@type":"ListItem","position":4,"name":"Defining the Decision Context and Inputs"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/840","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/840\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/839"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=840"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=840"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}