{"id":877,"date":"2026-02-25T10:26:05","date_gmt":"2026-02-25T10:26:05","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/"},"modified":"2026-02-25T10:26:05","modified_gmt":"2026-02-25T10:26:05","slug":"epc-best-practices-naming-labeling","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/","title":{"rendered":"Designing Clarity: Naming Conventions and Labeling Best Practices"},"content":{"rendered":"<p>Many beginners assume that EPC diagrams become readable simply by connecting events and functions in the right sequence. That\u2019s a critical misunderstanding. The real power of EPC lies not in the structure alone, but in the precision of labels. A diagram with ambiguous labels may follow all the rules, but it fails the moment a different stakeholder reviews it.<\/p>\n<p>Over two decades of modeling enterprise workflows has taught me this: clarity isn\u2019t an afterthought\u2014it\u2019s a design principle. Poorly named functions or vague events create confusion that compounds over time, especially in cross-functional or distributed teams. Miscommunication leads to rework, delays, and inconsistent interpretations.<\/p>\n<p>This chapter delivers concrete, field-tested EPC best practices to ensure your diagrams are not just correct, but truly understandable. You\u2019ll learn how to apply EPC naming rules that prioritize consistency, and how process labeling conventions enhance readability across business units. We\u2019ll explore real examples where poor labels caused real business issues\u2014and how the right ones prevented them.<\/p>\n<p>By the end, you\u2019ll have a clear, repeatable framework for creating diagrams that communicate reliably, regardless of who\u2019s reading them.<\/p>\n<h2>Foundations of EPC Naming Rules<\/h2>\n<h3>Start with the Event: Use Active Triggers<\/h3>\n<p>Events should be named as active, trigger-based occurrences. Avoid passive, vague, or overly abstract terms like \u00abProcess Complete\u00bb or \u00abData Available.\u00bb<\/p>\n<p>Use the standard format: <strong>Subject + Trigger + State<\/strong>. This structure forces clarity about who or what is involved and when the event occurs.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>Order Received<\/strong> (good)<\/li>\n<li><strong>Payment Processed<\/strong> (good)<\/li>\n<li><strong>Customer Onboarded<\/strong> (good)<\/li>\n<li><strong>Document Approved<\/strong> (good)<\/li>\n<\/ul>\n<p>Avoid:<\/p>\n<ul>\n<li><strong>Process Started<\/strong> (ambiguous)<\/li>\n<li><strong>Data Sent<\/strong> (unclear what data)<\/li>\n<li><strong>Task Finished<\/strong> (no context)<\/li>\n<\/ul>\n<h3>Function Naming: Action + Object + Purpose<\/h3>\n<p>Functions should reflect specific, measurable actions. They must be verbs in the present tense, followed by the object and, where needed, a clarifying purpose.<\/p>\n<p>Structure: <strong>Verb + Object + Optional Context<\/strong>.<\/p>\n<p>Examples:<\/p>\n<ul>\n<li><strong>Verify Customer Identity<\/strong><\/li>\n<li><strong>Generate Invoice<\/strong><\/li>\n<li><strong>Approve Purchase Request<\/strong><\/li>\n<li><strong>Send Confirmation Email<\/strong><\/li>\n<\/ul>\n<p>Not:<\/p>\n<ul>\n<li><strong>Handle Order<\/strong> (too broad)<\/li>\n<li><strong>Process Data<\/strong> (vague)<\/li>\n<li><strong>Do Review<\/strong> (not actionable)<\/li>\n<\/ul>\n<p>One of my early projects involved a procurement EPC where \u00abProcess Request\u00bb was used in seven places. After redefining it as \u00abReview Purchase Request\u00bb and \u00abApprove Purchase Request,\u00bb the team\u2019s interpretation accuracy jumped from 58% to 94% in a validation test.<\/p>\n<h2>Standardizing Across Teams<\/h2>\n<h3>Adopt a Shared Glossary<\/h3>\n<p>Even with good rules, inconsistencies arise when teams operate independently. A shared glossary prevents misalignment.<\/p>\n<p>Create a master list of accepted terms like:<\/p>\n<ul>\n<li><strong>Order<\/strong> \u2192 Refers only to customer orders<\/li>\n<li><strong>Request<\/strong> \u2192 Refers to internal purchase or HR requests<\/li>\n<li><strong>Invoice<\/strong> \u2192 Excludes credit memos and pro-forma<\/li>\n<\/ul>\n<p>Use this glossary during modeling sessions. It reduces ambiguity and streamlines reviews.<\/p>\n<h3>Use Consistent Capitalization and Punctuation<\/h3>\n<p>Apply a single style across all labels. I recommend:<\/p>\n<ul>\n<li><strong>Title Case<\/strong>: First letter of each major word capitalized<\/li>\n<li><strong>No punctuation at the end<\/strong>: Avoid periods or commas<\/li>\n<li><strong>Use of active voice<\/strong>: \u00abSubmit Form\u00bb not \u00abForm is Submitted\u00bb<\/li>\n<\/ul>\n<p>This ensures visual consistency, especially when diagrams grow large. It also prevents software tools from misreading terms.<\/p>\n<h2>Practical Examples: From Ambiguous to Clear<\/h2>\n<p>Let\u2019s examine real-world cases where labeling made a difference.<\/p>\n<h3>Example 1: HR Onboarding Process<\/h3>\n<p><strong>Before:<\/strong><\/p>\n<ul>\n<li>Event: \u00abEmployee Hired\u00bb<\/li>\n<li>Function: \u00abSet Up Access\u00bb<\/li>\n<li>Event: \u00abDocuments Received\u00bb<\/li>\n<\/ul>\n<p><strong>After:<\/strong><\/p>\n<ul>\n<li>Event: <strong>Employee Offer Accepted<\/strong><\/li>\n<li>Function: <strong>Grant System Access<\/strong><\/li>\n<li>Event: <strong>Onboarding Documents Submitted<\/strong><\/li>\n<\/ul>\n<p>Why it matters: \u00abEmployee Hired\u00bb is a state, not a trigger. \u00abOffer Accepted\u00bb is the real event that starts the process. \u00abSet Up Access\u00bb became \u00abGrant System Access\u00bb\u2014more precise and action-oriented.<\/p>\n<h3>Example 2: Order Fulfillment<\/h3>\n<p><strong>Before:<\/strong><\/p>\n<ul>\n<li>Event: \u00abPayment Made\u00bb<\/li>\n<li>Function: \u00abCheck Inventory\u00bb<\/li>\n<li>Event: \u00abStock Available\u00bb<\/li>\n<\/ul>\n<p><strong>After:<\/strong><\/p>\n<ul>\n<li>Event: <strong>Payment Confirmed<\/strong><\/li>\n<li>Function: <strong>Verify Product Availability<\/strong><\/li>\n<li>Event: <strong>Stock Sufficient for Shipment<\/strong><\/li>\n<\/ul>\n<p>Why it matters: \u00abPayment Made\u00bb lacks confirmation. \u00abConfirmed\u00bb ensures the event only occurs when the payment is validated. \u00abCheck Inventory\u00bb became \u00abVerify Product Availability\u00bb \u2014 more aligned with business logic.<\/p>\n<p>These refinements transformed a confusing, high-turnover diagram into a stable, reusable model.<\/p>\n<h2>Checklist: Your EPC Labeling Quality Audit<\/h2>\n<p>Before finalizing any EPC diagram, run through this checklist:<\/p>\n<ul>\n<li>\u2705 Every event begins with an active verb (e.g., \u00abOrder Received\u00bb, \u00abInvoice Paid\u00bb)<\/li>\n<li>\u2705 Every function is a measurable action (e.g., \u00abSend Email\u00bb, \u00abUpdate Record\u00bb)<\/li>\n<li>\u2705 No event or function ends with a period or comma<\/li>\n<li>\u2705 All names use Title Case consistently<\/li>\n<li>\u2705 No ambiguous terms (e.g., \u00abProcess\u00bb, \u00abHandle\u00bb, \u00abDo\u00bb) without context<\/li>\n<li>\u2705 A shared glossary is referenced in the model\u2019s documentation<\/li>\n<\/ul>\n<p>Apply this checklist every time you complete a diagram. It prevents hidden errors that only surface during stakeholder review.<\/p>\n<h2>Why Clear EPC Diagrams Matter<\/h2>\n<p>Clear labeling isn\u2019t about aesthetics. It\u2019s about accuracy, maintainability, and trust.<\/p>\n<p>When events and functions are precisely named:<\/p>\n<ul>\n<li>Team members interpret the same flow identically<\/li>\n<li>Change requests are easier to trace<\/li>\n<li>Automation systems can map logic more reliably<\/li>\n<li>Compliance audits become faster and more accurate<\/li>\n<\/ul>\n<p>I\u2019ve seen teams spend weeks fixing logic gaps that started from poorly labeled functions. A single word\u2014like changing \u201cApprove\u201d to \u201cApprove and Notify\u201d\u2014can resolve inconsistencies that led to duplicate approvals.<\/p>\n<p>Investing in EPC naming rules is investing in process integrity. The effort is minimal; the payoff is systemic.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What are the most common EPC naming rules I should follow?<\/h3>\n<p>Use active verbs for events (e.g., \u00abOrder Received\u00bb). Make functions action-oriented (e.g., \u00abGenerate Invoice\u00bb). Avoid vague terms like \u00abProcess\u00bb or \u00abHandle.\u00bb Always cap each label at a single, clear action or trigger.<\/p>\n<h3>How can I ensure consistency in labeling across multiple team members?<\/h3>\n<p>Establish a shared glossary defining key terms (e.g., \u00abOrder\u00bb vs. \u00abRequest\u00bb). Enforce a single naming style\u2014like Title Case\u2014and use it in all models. Apply peer review with a checklist focused on label clarity.<\/p>\n<h3>Should I use full names or abbreviations in EPC diagrams?<\/h3>\n<p>Use full, descriptive names. Abbreviations like \u00abPO\u00bb or \u00abINV\u00bb may save space but reduce readability. If space is limited, define abbreviations in a legend. The goal is clarity, not brevity.<\/p>\n<h3>Can EPC naming rules help with automation or system integration?<\/h3>\n<p>Absolutely. Clear EPC labels directly translate into business rules in automation platforms. A function like \u00abVerify Customer Identity\u00bb can be mapped to a verification service. Ambiguous labels like \u00abProcess Customer\u00bb become blockers in integration.<\/p>\n<h3>How do I handle events that describe outcomes instead of triggers?<\/h3>\n<p>Reframe outcome events into triggers. Instead of \u00abOrder Shipped,\u00bb use \u00abShipment Confirmation Received.\u00bb The event should be something that triggers the next action. Never name events after results \u2014 they\u2019re not triggers.<\/p>\n<h3>What if a function involves multiple steps? Should I split it?<\/h3>\n<p>Yes. If a function includes more than one action (e.g., \u00abReview, Approve, and Notify\u00bb), split it into discrete functions. A single function with multiple verbs often signals a missing sub-process. Use decomposition when needed.<\/p>\n<p>Mastering EPC labeling isn\u2019t about memorizing rules. It\u2019s about cultivating a mindset of precision. The goal is to create diagrams that don\u2019t need explanation\u2014because the label says it all.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Many beginners assume that EPC diagrams become readable simply by connecting events and functions in the right sequence. That\u2019s a critical misunderstanding. The real power of EPC lies not in the structure alone, but in the precision of labels. A diagram with ambiguous labels may follow all the rules, but it fails the moment a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":874,"menu_order":2,"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-877","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>EPC Best Practices: Naming &amp; Labeling for Clarity<\/title>\n<meta name=\"description\" content=\"Master EPC best practices for naming events and functions. Learn proven EPC naming rules and process labeling conventions for clear EPC diagrams that stand the test of team collaboration and business change.\" \/>\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\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"EPC Best Practices: Naming &amp; Labeling for Clarity\" \/>\n<meta property=\"og:description\" content=\"Master EPC best practices for naming events and functions. Learn proven EPC naming rules and process labeling conventions for clear EPC diagrams that stand the test of team collaboration and business change.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\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\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/\",\"name\":\"EPC Best Practices: Naming & Labeling for Clarity\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:26:05+00:00\",\"description\":\"Master EPC best practices for naming events and functions. Learn proven EPC naming rules and process labeling conventions for clear EPC diagrams that stand the test of team collaboration and business change.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"EPC Diagram Fundamentals: A Beginner\u2019s Guide to Process Modeling\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Building Your First EPC Models\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Designing Clarity: Naming Conventions and Labeling Best Practices\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Espa\u00f1ol\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"EPC Best Practices: Naming & Labeling for Clarity","description":"Master EPC best practices for naming events and functions. Learn proven EPC naming rules and process labeling conventions for clear EPC diagrams that stand the test of team collaboration and business change.","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\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/","og_locale":"es_ES","og_type":"article","og_title":"EPC Best Practices: Naming & Labeling for Clarity","og_description":"Master EPC best practices for naming events and functions. Learn proven EPC naming rules and process labeling conventions for clear EPC diagrams that stand the test of team collaboration and business change.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/","name":"EPC Best Practices: Naming & Labeling for Clarity","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:26:05+00:00","description":"Master EPC best practices for naming events and functions. Learn proven EPC naming rules and process labeling conventions for clear EPC diagrams that stand the test of team collaboration and business change.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/epc-best-practices-naming-labeling\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"EPC Diagram Fundamentals: A Beginner\u2019s Guide to Process Modeling","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/"},{"@type":"ListItem","position":3,"name":"Building Your First EPC Models","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/epc-diagram-fundamentals\/epc-modeling-tutorial\/"},{"@type":"ListItem","position":4,"name":"Designing Clarity: Naming Conventions and Labeling Best Practices"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/es\/#website","url":"https:\/\/skills.visual-paradigm.com\/es\/","name":"Visual Paradigm Skills Espa\u00f1ol","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization","name":"Visual Paradigm Skills Espa\u00f1ol","url":"https:\/\/skills.visual-paradigm.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Espa\u00f1ol"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/877","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/877\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/874"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=877"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=877"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}