{"id":645,"date":"2026-02-25T10:21:36","date_gmt":"2026-02-25T10:21:36","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/"},"modified":"2026-02-25T10:21:36","modified_gmt":"2026-02-25T10:21:36","slug":"over-annotated-dfd","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/","title":{"rendered":"Overloaded Symbols and Over-Annotated Diagrams"},"content":{"rendered":"<p>Too many symbols in DFDs aren&#8217;t just distracting\u2014they erode trust in the model. I\u2019ve seen diagrams where a single process is buried under layered icons, color-coded roles, and marginal notes that explain everything but the core data flow. These over-annotated DFDs look impressive at first glance, but they fail the most basic test: clarity.<\/p>\n<p>When you overload a diagram with visual noise, the real data movement gets lost. Stakeholders stop seeing flows. Developers stop tracing transformations. You\u2019re not modeling complexity\u2014you\u2019re hiding it behind decoration. This isn\u2019t about aesthetics. It\u2019s about communication.<\/p>\n<p>My experience shows that the most effective DFDs aren\u2019t the ones packed with every possible label, icon, or credential\u2014they\u2019re the ones where the flow speaks for itself. The goal isn\u2019t to document every detail on the page. It\u2019s to guide the reader through a clean, logical journey of data movement.<\/p>\n<h2>Why Over-Annotation Destroys Readability<\/h2>\n<p>Over-annotated DFDs often stem from good intentions. We want to be thorough. We want to prevent misunderstandings. But too many annotations create cognitive overload.<\/p>\n<p>Consider a process labeled \u201cValidate Customer Credentials (Role: Auth Officer, Priority: High, Input: Login Form, Output: Auth Token, Source: Identity Service, Status: Active).\u201d That\u2019s not a process\u2014it\u2019s a full job description. The flow is invisible beneath the text.<\/p>\n<p>Here\u2019s what happens when you add too many symbols in DFDs:<\/p>\n<ul>\n<li>Visual clutter forces the eye to scan, not interpret.<\/li>\n<li>Text overlaps with lines and shapes, making connections ambiguous.<\/li>\n<li>Annotations shift attention from data flow to metadata.<\/li>\n<li>Readability drops even when the core logic is sound.<\/li>\n<\/ul>\n<p>These aren&#8217;t just design flaws\u2014they\u2019re communication failures. The diagram should not require a decoder ring. If you find yourself saying \u201cyou need to read the legend to understand this,\u201d the diagram has failed.<\/p>\n<h2>When Annotations Work\u2014and When They Don\u2019t<\/h2>\n<p>Annotations aren\u2019t inherently bad. But their value depends on context and placement.<\/p>\n<p>Best practice is simple: annotate only when necessary, and only when it improves understanding, not hinders it.<\/p>\n<p>Here\u2019s a rule I\u2019ve used for years: if removing a label doesn\u2019t reduce clarity, it\u2019s likely unnecessary.<\/p>\n<h3>Use Annotations Sparingly and Strategically<\/h3>\n<p>Annotations should be tools for explanation, not crutches for incomplete design. Reserve them for:<\/p>\n<ul>\n<li>Clarifying ambiguous names (e.g., \u201cOrder Finalization\u201d \u2192 \u201cFinalize Order after Payment Verification\u201d)<\/li>\n<li>Noting critical exceptions (e.g., \u201cOnly for high-risk transactions\u201d)<\/li>\n<li>Referencing external documentation (e.g., \u201cSee Ref. DFD-7.3 for approval logic\u201d)<\/li>\n<\/ul>\n<p>Never use annotations to replace clear naming or logical structure. If you\u2019re explaining a process\u2019s function in a note, you\u2019ve already failed.<\/p>\n<h3>Move Detail Elsewhere: The Power of Separation<\/h3>\n<p>Instead of over-annotating, consider this: separate concerns.<\/p>\n<p>For example, keep the DFD clean and focused on data movement. Then, document supporting details in a companion table or appendix. This approach is known as \u201cseparation of concerns\u201d in DFD modeling.<\/p>\n<p>Here\u2019s a simple pattern I use:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Element<\/th>\n<th>Where to Document<\/th>\n<th>Why<\/th>\n<\/tr>\n<tr>\n<td>Process logic<\/td>\n<td>Decision table or pseudocode<\/td>\n<td>Enables testing and verification<\/td>\n<\/tr>\n<tr>\n<td>Role responsibilities<\/td>\n<td>Actor definition table<\/td>\n<td>Prevents clutter and ensures consistency<\/td>\n<\/tr>\n<tr>\n<td>Exception handling<\/td>\n<td>Flows with status flags<\/td>\n<td>Keeps main diagram uncluttered<\/td>\n<\/tr>\n<tr>\n<td>System boundary assumptions<\/td>\n<td>Legend or assumptions section<\/td>\n<td>Improves auditability and clarity<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This is how you keep DFD diagrams clean. It\u2019s not about removing detail\u2014it\u2019s about organizing it.<\/p>\n<h2>Heuristics for DFD Annotation Best Practice<\/h2>\n<p>Here are four rules I\u2019ve refined over 20 years of modeling:<\/p>\n<ol>\n<li><strong>One annotation per process, max.<\/strong> If you need more than one, the process is likely too complex and should be decomposed.<\/li>\n<li><strong>No annotations on data stores.<\/strong> Their purpose is clear from context and flow. If you must explain, do so in a legend or definition table.<\/li>\n<li><strong>Use icons only for role differentiation.<\/strong> A small badge or label is fine\u2014don\u2019t add full avatars or icons for every actor.<\/li>\n<li><strong>When in doubt, cut it out.<\/strong> If a label doesn\u2019t improve understanding, remove it.<\/li>\n<\/ol>\n<p>These rules aren\u2019t rigid. They\u2019re heuristics. But they\u2019ve saved me dozens of debugging hours and countless stakeholder questions.<\/p>\n<h2>When to Use Legends vs. On-Diagram Labels<\/h2>\n<p>Legends are powerful tools\u2014but only when used correctly.<\/p>\n<p>Use a legend when:<\/p>\n<ul>\n<li>Icons represent system roles or statuses<\/li>\n<li>Color coding indicates data sensitivity or flow type<\/li>\n<li>Special symbols are used (e.g., dashed lines for alternate flows)<\/li>\n<\/ul>\n<p>But never let a legend become a footnote. It should be brief. One page, max. If you need more, your diagram is the wrong tool.<\/p>\n<p>Example: A legend with three entries\u2014\u201cRed: High Risk,\u201d \u201cGreen: Normal,\u201d \u201cBlue: Pending\u201d\u2014is useful. A 20-line legend explaining every symbol, status, and role? That\u2019s noise.<\/p>\n<h2>Real-World Example: A Cluttered vs. Clean DFD<\/h2>\n<p>Let\u2019s look at a real case from a financial system I reviewed.<\/p>\n<p><strong>Over-annotated version:<\/strong> A process labeled \u201cProcess Transaction (Auth: Mike, Role: Fraud Analyst, Status: Active, Auth Level: High, Source: Payment Gateway, Output: Transaction ID, Logging: Enabled).\u201d It\u2019s buried under three icons: a shield (security), a user (role), and a clock (timing).<\/p>\n<p><strong>Refactored version:<\/strong> Just \u201cProcess Transaction.\u201d A small label in the top-right corner says \u201cRole: Fraud Analyst.\u201d The rest of the info is in a table below the diagram.<\/p>\n<p>The clean version is 60% faster to understand. No one needs to search for meaning. The flow is clear. The roles are defined elsewhere. That\u2019s keeping DFD diagrams clean.<\/p>\n<h2>Key Takeaways<\/h2>\n<ul>\n<li>Over-annotated DFDs are a sign of poor structure, not thoroughness.<\/li>\n<li>Too many symbols in DFDs obscure the core data flow. Remove what doesn\u2019t add clarity.<\/li>\n<li>DFD annotation best practice: prioritize clarity over completeness.<\/li>\n<li>Move complex details into legends, tables, or supporting documents.<\/li>\n<li>Use legends only when necessary\u2014and keep them short.<\/li>\n<li>Remember: the diagram should explain the system. It shouldn\u2019t be the system.<\/li>\n<\/ul>\n<p>Keep DFD diagrams clean. Let the flows do the talking. That\u2019s how you build trust, avoid rework, and create models that last.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Should I label every process with the responsible team?<\/h3>\n<p>Label only the most critical processes. For most, rely on a legend or a role matrix. Over-labeling distracts from data movement.<\/p>\n<h3>Can I use color to indicate data sensitivity in DFDs?<\/h3>\n<p>Yes, but sparingly. Use only a few colors with a clear legend. Color should not be the only indicator\u2014include labels like \u201cHigh Risk\u201d or \u201cPII\u201d for accessibility.<\/p>\n<h3>Is it okay to annotate data flows with business rules?<\/h3>\n<p>Only if they\u2019re critical to understanding the flow. Better yet, define rules in a decision table and reference them. Avoid embedding rules directly on the diagram.<\/p>\n<h3>How many icons should I put on a DFD?<\/h3>\n<p>One per process, max. Icons should represent roles or statuses, not every detail. Use icons to support, not replace, clear labeling.<\/p>\n<h3>When should I use a legend instead of on-diagram labels?<\/h3>\n<p>When the diagram would become too cluttered. A legend is ideal for standardizing symbols, colors, or status indicators across multiple diagrams.<\/p>\n<h3>What if my team insists on over-annotating for compliance?<\/h3>\n<p>Persuade them: compliance doesn\u2019t require a cluttered diagram. Use a clean DFD with a traceability matrix linking each process to its policy. That\u2019s better documentation, and it\u2019s easier to maintain.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many symbols in DFDs aren&#8217;t just distracting\u2014they erode trust in the model. I\u2019ve seen diagrams where a single process is buried under layered icons, color-coded roles, and marginal notes that explain everything but the core data flow. These over-annotated DFDs look impressive at first glance, but they fail the most basic test: clarity. When [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":640,"menu_order":4,"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-645","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>Over-annotated DFD: When Simplicity Suffers<\/title>\n<meta name=\"description\" content=\"Avoid over-annotated DFDs with practical DFD annotation best practice. Learn how to keep DFD diagrams clean and effective by knowing when to annotate on-diagram and when to move detail to documentation.\" \/>\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\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Over-annotated DFD: When Simplicity Suffers\" \/>\n<meta property=\"og:description\" content=\"Avoid over-annotated DFDs with practical DFD annotation best practice. Learn how to keep DFD diagrams clean and effective by knowing when to annotate on-diagram and when to move detail to documentation.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/\",\"name\":\"Over-annotated DFD: When Simplicity Suffers\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:21:36+00:00\",\"description\":\"Avoid over-annotated DFDs with practical DFD annotation best practice. Learn how to keep DFD diagrams clean and effective by knowing when to annotate on-diagram and when to move detail to documentation.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common DFD Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Notation and Diagramming Anti-Patterns\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Overloaded Symbols and Over-Annotated Diagrams\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Over-annotated DFD: When Simplicity Suffers","description":"Avoid over-annotated DFDs with practical DFD annotation best practice. Learn how to keep DFD diagrams clean and effective by knowing when to annotate on-diagram and when to move detail to documentation.","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\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/","og_locale":"de_DE","og_type":"article","og_title":"Over-annotated DFD: When Simplicity Suffers","og_description":"Avoid over-annotated DFDs with practical DFD annotation best practice. Learn how to keep DFD diagrams clean and effective by knowing when to annotate on-diagram and when to move detail to documentation.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/","name":"Over-annotated DFD: When Simplicity Suffers","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:21:36+00:00","description":"Avoid over-annotated DFDs with practical DFD annotation best practice. Learn how to keep DFD diagrams clean and effective by knowing when to annotate on-diagram and when to move detail to documentation.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/over-annotated-dfd\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"Common DFD Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Notation and Diagramming Anti-Patterns","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-notation-mistakes\/"},{"@type":"ListItem","position":4,"name":"Overloaded Symbols and Over-Annotated Diagrams"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/645","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/645\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/640"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=645"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=645"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}