{"id":781,"date":"2026-02-25T10:24:32","date_gmt":"2026-02-25T10:24:32","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/"},"modified":"2026-02-25T10:24:32","modified_gmt":"2026-02-25T10:24:32","slug":"crc-modeling-mistakes-to-avoid","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/","title":{"rendered":"Common Mistakes in CRC Modeling (and How to Fix Them)"},"content":{"rendered":"<p>One of the most common pitfalls in CRC modeling is treating it as a mechanical exercise instead of a thinking tool.<\/p>\n<p>When responsibilities are vague or classes are duplicated, the model fails to reflect real behavior.<\/p>\n<p>My experience working with dozens of teams has shown that the best CRC models emerge not from perfect syntax, but from clear thinking and active collaboration.<\/p>\n<p>This chapter breaks down the most frequent CRC modeling mistakes, explains why they happen, and gives you practical CRC modeling tips to fix them\u2014so your design stays clean, focused, and meaningful.<\/p>\n<h2>1. Vague or Overloaded Responsibilities<\/h2>\n<p>Vague responsibilities are the most common CRC errors I see in beginner models. Phrases like \u201chandle data\u201d or \u201cmanage information\u201d don\u2019t tell you what the class actually does.<\/p>\n<p>These responsibilities are too broad and invite duplication. They also make it hard to assign work meaningfully.<\/p>\n<h3>Why it happens<\/h3>\n<ul>\n<li>Designers confuse responsibilities with features or outputs.<\/li>\n<li>Teams rush to list every possible task without probing deeper.<\/li>\n<li>Responsibilities are written from the perspective of the system, not the object.<\/li>\n<\/ul>\n<h3>How to fix it: Use action verbs and intent<\/h3>\n<p>Replace abstract verbs with specific ones tied to behavior. Turn \u201chandle orders\u201d into \u201cprocess payment for an order.\u201d<\/p>\n<p>Ask: \u201cWhat does this class do in response to a request?\u201d The answer should be a single, clear action.<\/p>\n<p><strong>Example:<\/strong> Instead of \u201cmaintain user data,\u201d write \u201cvalidate user email before saving.\u201d<\/p>\n<p><strong>Checklist for strong responsibilities:<\/strong><\/p>\n<ul>\n<li>Starts with an action verb (e.g., validate, calculate, notify).<\/li>\n<li>Describes a single, cohesive task.<\/li>\n<li>Can be implemented by one method or operation.<\/li>\n<li>Reflects what the class does, not what it contains.<\/li>\n<\/ul>\n<h2>2. Redundant or Overlapping Classes<\/h2>\n<p>When two classes do nearly the same thing, it\u2019s a red flag. It breaks cohesion and increases maintenance cost.<\/p>\n<p>I once saw a banking model with four classes named \u201cAccount,\u201d \u201cCheckingAccount,\u201d \u201cSavingsAccount,\u201d and \u201cAccountType.\u201d They all managed balance, interest, and transactions\u2014wasting time and creating inconsistency.<\/p>\n<h3>Root causes<\/h3>\n<ul>\n<li>Designers haven\u2019t yet identified the true abstraction.<\/li>\n<li>Overuse of inheritance without clear hierarchy.<\/li>\n<li>Trying to predict every possible future variation.<\/li>\n<\/ul>\n<h3>How to fix: Embrace abstraction and role separation<\/h3>\n<p>Ask: \u201cWhat is the core responsibility of this class? Does it really need to be a separate class?\u201d<\/p>\n<p>Group similar behaviors under a single class. If you need to model different types, use roles or state patterns, not redundant classes.<\/p>\n<p><strong>Example:<\/strong> Replace \u201cCheckingAccount\u201d and \u201cSavingsAccount\u201d with a single \u201cAccount\u201d class that supports different account types via a type field or polymorphic behavior.<\/p>\n<p>Use this table to compare:<\/p>\n<table border=\"1\" cellpadding=\"4\">\n<tbody>\n<tr>\n<th>Problem<\/th>\n<th>Fix<\/th>\n<th>CRC Modeling Tip<\/th>\n<\/tr>\n<tr>\n<td>Multiple classes for minor variations<\/td>\n<td>Use inheritance or type fields<\/td>\n<td>Start with one class. Add variation only when needed.<\/td>\n<\/tr>\n<tr>\n<td>Classes with identical responsibilities<\/td>\n<td>Combine or refactor into one<\/td>\n<td>Ask: \u201cCan one class do this work better?\u201d<\/td>\n<\/tr>\n<tr>\n<td>Class names that don\u2019t reflect function<\/td>\n<td>Re-name for intent (e.g., \u201cService\u201d \u2192 \u201cPaymentProcessor\u201d)<\/td>\n<td>Use names that describe behavior, not structure.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>3. Weak or Inactive Collaborations<\/h2>\n<p>Collaboration is where CRC modeling shines\u2014but only if the links between classes are meaningful.<\/p>\n<p>I\u2019ve seen many models where class A \u201ccollaborates with\u201d class B simply because they both appear in the same system. That\u2019s not collaboration\u2014it\u2019s a connection without purpose.<\/p>\n<h3>What good collaboration looks like<\/h3>\n<p>Collaboration should represent a concrete need: \u201cClass A sends a message to class B to confirm a transaction.\u201d<\/p>\n<p>Weak collaborations often occur when the team hasn\u2019t asked: \u201cWho triggers this behavior?\u201d or \u201cWhat does this class depend on?\u201d<\/p>\n<h3>How to strengthen collaborations<\/h3>\n<ul>\n<li>Only list a collaboration if the class actively sends a message or requests an action.<\/li>\n<li>Use real method names: \u201ccalls <code>calculateInterest()<\/code>\u201d instead of \u201cinteracts with\u201d.<\/li>\n<li>Revisit collaboration after each responsibility is defined.<\/li>\n<\/ul>\n<p><strong>Example:<\/strong> Instead of \u201cOrder collaborates with Payment,\u201d write \u201cOrder requests <code>processPayment()<\/code> from PaymentService.\u201d<\/p>\n<p>Remember: No message, no collaboration.<\/p>\n<h2>4. Neglecting the Role of the Facilitator<\/h2>\n<p>CRC is a team activity\u2014yet many groups treat it as an individual task.<\/p>\n<p>Without a facilitator, discussions drift, responsibilities get duplicated, and the model becomes a collection of opinions, not a shared understanding.<\/p>\n<h3>Why facilitation matters<\/h3>\n<ul>\n<li>Prevents dominance by one voice.<\/li>\n<li>Keeps the focus on behavior, not structure.<\/li>\n<li>Encourages questioning: \u201cIs this really something this class should do?\u201d<\/li>\n<\/ul>\n<h3>Facilitator checklist<\/h3>\n<ul>\n<li>Start with a clear problem statement.<\/li>\n<li>Encourage \u201cWhy?\u201d after each responsibility.<\/li>\n<li>Pause to discuss conflicts or overlaps.<\/li>\n<li>Use a timer to keep the session flowing.<\/li>\n<\/ul>\n<p>Even a simple \u201cno phones\u201d rule increases engagement.<\/p>\n<h2>5. Ignoring the \u201cWhy\u201d Behind the Design<\/h2>\n<p>Some teams build CRC models just to check a box\u2014or because the curriculum says so.<\/p>\n<p>But that\u2019s missing the point. CRC modeling is not a documentation step. It\u2019s a design conversation.<\/p>\n<p>When the team doesn\u2019t know the problem they\u2019re solving, the model becomes a meaningless map.<\/p>\n<h3>Ask the right questions<\/h3>\n<ul>\n<li>What user need are we addressing?<\/li>\n<li>What happens when a customer places an order?<\/li>\n<li>Who or what is responsible for confirming delivery?<\/li>\n<\/ul>\n<p>Start with the behavior, not the class. Let the responsibilities guide the class shape.<\/p>\n<h2>6. Skipping the Refinement Loop<\/h2>\n<p>First-pass CRC models are rarely perfect. That\u2019s normal.<\/p>\n<p>Some teams stop after one round, but good design requires iteration.<\/p>\n<p>I\u2019ve seen models improve dramatically after just one feedback round\u2014when the team re-examined responsibilities and removed redundant collaborations.<\/p>\n<h3>Refinement steps<\/h3>\n<ol>\n<li>Review all responsibilities: are they atomic and action-based?<\/li>\n<li>Check collaborations: are messages real and necessary?<\/li>\n<li>Look for duplicates: can two classes be combined?<\/li>\n<li>Ask: \u201cCan this model answer the original problem?\u201d<\/li>\n<\/ol>\n<p>Use this as your daily CRC troubleshooting checklist.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the biggest CRC modeling mistake in practice?<\/h3>\n<p>Writing responsibilities like \u201cmanage data\u201d or \u201cdo something.\u201d These are too abstract and lead to ambiguous design. Always replace them with specific actions.<\/p>\n<h3>How do I know if a class is redundant?<\/h3>\n<p>If two classes have identical or nearly identical responsibilities and collaborate with the same partners, they\u2019re likely redundant. Ask: \u201cCan one class cover this work?\u201d<\/p>\n<h3>Should I include getters and setters in CRC cards?<\/h3>\n<p>No. CRC focuses on behavior, not data access. Getters and setters are implementation details. Save them for the class diagram, not the CRC card.<\/p>\n<h3>Can CRC modeling mistakes break my code?<\/h3>\n<p>Not directly. But a flawed CRC model often reflects flawed design\u2014leading to poor cohesion, tight coupling, and hard-to-maintain code. The model is a warning sign, not the source.<\/p>\n<h3>How do I handle conflicting responsibilities in a team?<\/h3>\n<p>Use the facilitator to guide a discussion. Ask: \u201cWho is responsible for this decision?\u201d or \u201cWhat happens if we delegate this to another class?\u201d Often, the conflict reveals a missing abstraction.<\/p>\n<h3>Do I need to use CRC cards in every project?<\/h3>\n<p>No. Use them when the problem is complex or the team is new to object-oriented thinking. For simple tasks, CRC might be overkill. But for learning and team alignment, it\u2019s invaluable.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the most common pitfalls in CRC modeling is treating it as a mechanical exercise instead of a thinking tool. When responsibilities are vague or classes are duplicated, the model fails to reflect real behavior. My experience working with dozens of teams has shown that the best CRC models emerge not from perfect syntax, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":777,"menu_order":3,"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-781","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>CRC Modeling Mistakes to Avoid<\/title>\n<meta name=\"description\" content=\"Avoid common CRC modeling mistakes like vague responsibilities, redundant classes, and poor collaborations. Get actionable CRC troubleshooting tips and practical fixes for better object-oriented 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\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CRC Modeling Mistakes to Avoid\" \/>\n<meta property=\"og:description\" content=\"Avoid common CRC modeling mistakes like vague responsibilities, redundant classes, and poor collaborations. Get actionable CRC troubleshooting tips and practical fixes for better object-oriented design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/\" \/>\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\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/\",\"name\":\"CRC Modeling Mistakes to Avoid\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:24:32+00:00\",\"description\":\"Avoid common CRC modeling mistakes like vague responsibilities, redundant classes, and poor collaborations. Get actionable CRC troubleshooting tips and practical fixes for better object-oriented design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CRC Cards Explained: A Beginner\u2019s Modeling Guide\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Collaboration and Practice\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Common Mistakes in CRC Modeling (and How to Fix Them)\"}]},{\"@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":"CRC Modeling Mistakes to Avoid","description":"Avoid common CRC modeling mistakes like vague responsibilities, redundant classes, and poor collaborations. Get actionable CRC troubleshooting tips and practical fixes for better object-oriented 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\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/","og_locale":"es_ES","og_type":"article","og_title":"CRC Modeling Mistakes to Avoid","og_description":"Avoid common CRC modeling mistakes like vague responsibilities, redundant classes, and poor collaborations. Get actionable CRC troubleshooting tips and practical fixes for better object-oriented design.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/","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\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/","name":"CRC Modeling Mistakes to Avoid","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:24:32+00:00","description":"Avoid common CRC modeling mistakes like vague responsibilities, redundant classes, and poor collaborations. Get actionable CRC troubleshooting tips and practical fixes for better object-oriented design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/crc-modeling-mistakes-to-avoid\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"CRC Cards Explained: A Beginner\u2019s Modeling Guide","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/"},{"@type":"ListItem","position":3,"name":"Collaboration and Practice","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/crc-cards-explained\/crc-collaboration\/"},{"@type":"ListItem","position":4,"name":"Common Mistakes in CRC Modeling (and How to Fix Them)"}]},{"@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\/781","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\/781\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/777"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=781"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=781"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}