{"id":574,"date":"2026-02-25T10:20:35","date_gmt":"2026-02-25T10:20:35","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/"},"modified":"2026-02-25T10:20:35","modified_gmt":"2026-02-25T10:20:35","slug":"sequence-flow-vs-message-flow-mistakes","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/","title":{"rendered":"Sequence Flows vs Message Flows: Mixing Worlds"},"content":{"rendered":"

Here\u2019s the one thing that changes everything: mixing up sequence flows and message flows is not just a notation error\u2014it\u2019s a semantic betrayal of responsibility. When you use a sequence flow to represent a message between two pools, you erase who\u2019s doing what, and that\u2019s where misunderstandings begin.<\/p>\n

For over two decades, I\u2019ve reviewed BPMN diagrams from dozens of organizations. The most persistent flaw? Using sequence flows across pools, or placing message flows inside a single process. These aren\u2019t just style issues\u2014they break the core intent of BPMN: to show who acts, when, and how.<\/p>\n

This chapter will clarify the distinction, walk through real examples of how these mistakes manifest, and give you a simple decision rule to follow in any collaboration scenario. You\u2019ll learn when to use sequence flow vs message flow, and how to avoid the most common BPMN flow type mistakes.<\/p>\n

Understanding the Core Difference<\/h2>\n

Sequence flows and message flows serve completely different purposes\u2014and confusing them undermines the entire model.<\/p>\n

Sequence flows<\/strong> represent the order of execution within<\/em> a single process. They show the logical progression from one activity to the next, and are always drawn as solid lines with arrowheads.<\/p>\n

Message flows<\/strong> represent communication between two separate participants: two pools, two lanes, or a process and an external agent. They are dashed lines with arrowheads and imply a sender and receiver.<\/p>\n

It\u2019s a fundamental split: sequence flows are about internal control flow<\/em>, message flows are about external communication<\/em>.<\/p>\n

When to Use Each: The Decision Rule<\/h3>\n

Ask this question: Are both ends of the flow inside the same pool or lane?<\/em><\/p>\n

If yes \u2192 Use a sequence flow<\/strong>. The flow is part of the same process\u2019s execution.<\/p>\n

If no \u2192 Use a message flow<\/strong>. The action is sent from one participant to another.<\/p>\n

There\u2019s no ambiguity. No exceptions. This rule prevents the most common BPMN flow type mistakes.<\/p>\n

Common Mistakes and How to Fix Them<\/h2>\n

Mistake 1: Using Sequence Flows Between Pools<\/h3>\n

Imagine a process where a customer submits a form, and then the sales team responds. If you draw a sequence flow from the customer\u2019s task to the sales task across two different pools, you\u2019re saying the sales team is executing a step within the customer\u2019s process\u2014which is false.<\/p>\n

This misrepresents responsibility and blurs process boundaries. It makes no distinction between execution order and communication.<\/p>\n

Fix:<\/strong> Replace the sequence flow with a message flow from the customer\u2019s task to the sales task. This clearly shows that the customer sends<\/em> a message, and the sales team responds<\/em>.<\/p>\n

Mistake 2: Using Message Flows Inside a Single Process<\/h3>\n

Now imagine a process with two tasks in the same lane: \u201cReview Application\u201d and \u201cApprove Application.\u201d If you connect them with a message flow, you\u2019re implying that one step sends a message to the other\u2014like they\u2019re separate entities.<\/p>\n

But they\u2019re in the same process. The second task is not receiving a message from the first\u2014it\u2019s just the next logical step.<\/p>\n

Fix:<\/strong> Use a sequence flow instead. The message flow implies a communication event that doesn\u2019t exist. This preserves the logical flow and avoids confusion.<\/p>\n

Mistake 3: Confusing Message Flows with Association Lines<\/h3>\n

Association lines (dotted lines) are used to link artifacts (like text annotations or data objects) to activities. They should never be used to represent control or message flow.<\/p>\n

Using an association to connect two tasks in different pools is a serious error. It\u2019s syntactically invalid and semantically meaningless.<\/p>\n

Fix:<\/strong> Only use message flows for communication between pools. Use associations only for linking artifacts to elements.<\/p>\n

Real-World Examples<\/h2>\n

Example: Customer Onboarding Collaboration<\/h3>\n

Consider a customer onboarding process involving two pools: Customer<\/em> and Onboarding Team<\/em>.<\/p>\n

Bad: A sequence flow from \u201cSubmit Application\u201d (Customer) to \u201cVerify Documents\u201d (Onboarding Team).<\/p>\n

Good: A message flow from \u201cSubmit Application\u201d to \u201cVerify Documents.\u201d<\/p>\n

The message flow makes it clear that the customer sends a message, and the onboarding team receives and acts upon it.<\/p>\n

Example: Internal Approval Process<\/h3>\n

In a single process, a manager must approve a request.<\/p>\n

Bad: A message flow from \u201cReview Request\u201d to \u201cApprove Request\u201d in the same lane.<\/p>\n

Good: A sequence flow from \u201cReview Request\u201d to \u201cApprove Request.\u201d<\/p>\n

The sequence flow reflects the natural, ordered execution within a single business process.<\/p>\n

Quick Reference: Flow Type Decision Table<\/h2>\n\n\n\n\n\n\n\n\n
Context<\/strong><\/th>\nFlow Type<\/strong><\/th>\nWhy<\/strong><\/th>\n<\/tr>\n<\/thead>\n
Within a single pool\/lane<\/td>\nSequence flow<\/td>\nControl flow, execution order<\/td>\n<\/tr>\n
Between two different pools\/lane<\/td>\nMessage flow<\/td>\nCommunication between participants<\/td>\n<\/tr>\n
Linking an artifact (e.g., annotation) to an activity<\/td>\nAssociation (dotted)<\/td>\nNon-execution link<\/td>\n<\/tr>\n
Handoff from one role to another in the same process<\/td>\nSequence flow<\/td>\nSame process, same flow<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Best Practices for Modeling Collaboration<\/h2>\n

When modeling collaboration, always ask: Who is sending? Who is receiving? Are they part of the same process?<\/em><\/p>\n

Use message flows to represent interactions between distinct roles. This preserves clarity and ensures the model reflects reality, not illusion.<\/p>\n

Never use sequence flows to represent communication across pools. It\u2019s a red flag for poor responsibility modeling.<\/p>\n

When in doubt, check your model with a simple test: If you removed the message flow, would the process still make sense? If yes, you\u2019ve likely used the wrong flow type.<\/p>\n

Remember: A message flow cannot be used inside a single process to show execution order. If the action is part of the same process flow, use sequence flow.<\/p>\n

Why This Matters for Execution<\/h2>\n

Incorrectly using sequence flows between pools makes it impossible to determine who triggers the next step. Is the customer supposed to initiate it? Is it automatic? Is it a handover?<\/p>\n

When automation tools parse these models, they rely on correct flow semantics. A message flow tells them a communication event is expected. A sequence flow tells them the next step is automatic.<\/p>\n

Mixing them up leads to failed implementations, incorrect automation, and audit failures.<\/p>\n

Final Checklist: Before You Finalize Your Diagram<\/h2>\n
    \n
  • Verify all flows between pools are message flows (dashed).<\/li>\n
  • Confirm all flows within a single pool are sequence flows (solid).<\/li>\n
  • Ensure no message flows are used inside a single process to represent control flow.<\/li>\n
  • Double-check that associations (dotted lines) are only for linking artifacts, not activities.<\/li>\n
  • Use the decision rule: \u201cSame pool? \u2192 sequence flow. Different pool? \u2192 message flow.\u201d<\/li>\n<\/ul>\n

    These checks are not optional. They\u2019re the difference between a model that works and one that misleads.<\/p>\n

    Frequently Asked Questions<\/h2>\n

    Can I use a sequence flow between two lanes in the same pool?<\/h3>\n

    Yes, but only if the flow is part of the same process execution. If the two lanes represent different roles in the same process (e.g., \u201cManager\u201d and \u201cHR\u201d), and one hands off to the other, use a sequence flow. But if it\u2019s between two distinct processes (e.g., \u201cHR\u201d and \u201cFinance\u201d), use a message flow.<\/p>\n

    Why can\u2019t I use a message flow inside a single process?<\/h3>\n

    Because message flows imply communication between separate participants. Inside a single process, tasks are part of the same execution flow. Using a message flow here misrepresents the model and breaks the semantic meaning.<\/p>\n

    What happens if I mix sequence flow and message flow in the same collaboration?<\/h3>\n

    It creates confusion about responsibility and triggers. The process may become unexecutable, or automation tools may fail to interpret the correct flow. It also violates BPMN semantics and makes the model unreliable for audits or implementation.<\/p>\n

    Is it okay to use a message flow to show a notification within a process?<\/h3>\n

    No. If a task triggers a notification to another task in the same process, use a sequence flow. Use message flows only when the receiver is a separate participant (e.g., a different pool or external system).<\/p>\n

    Can I use message flows to represent data exchange?<\/h3>\n

    Only if the data exchange is part of a communication between participants. If the data is passed as input\/output within a single process, use sequence flows. Message flows are for communication events, not data transfer.<\/p>\n

    How do I know if I\u2019m using sequence flows between pools?<\/h3>\n

    Check the ends of the flow. If the two tasks are in different pools or lanes, and you\u2019re using a solid line, you\u2019re using sequence flow incorrectly. Replace it with a message flow (dashed line).<\/p>\n

    Always double-check your flow types. It\u2019s one of the easiest fixes that has the biggest impact on clarity and correctness.<\/p>\n

    Mastering sequence flow vs message flow isn\u2019t about memorizing rules. It\u2019s about understanding who does what\u2014and when. When you get this right, your model becomes trustworthy, executable, and truly business-aligned.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Here\u2019s the one thing […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":571,"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-574","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nSequence Flow vs Message Flow: Avoid the Mix-Up<\/title>\n<meta name=\"description\" content=\"Fix common BPMN flow type mistakes: learn when to use sequence flow vs message flow, avoid using sequence flows between pools, and model collaboration correctly for clearer, audit-ready diagrams.\" \/>\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\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Sequence Flow vs Message Flow: Avoid the Mix-Up\" \/>\n<meta property=\"og:description\" content=\"Fix common BPMN flow type mistakes: learn when to use sequence flow vs message flow, avoid using sequence flows between pools, and model collaboration correctly for clearer, audit-ready diagrams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9810\u4f30\u95b1\u8b80\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 \u5206\u9418\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/\",\"name\":\"Sequence Flow vs Message Flow: Avoid the Mix-Up\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-02-25T10:20:35+00:00\",\"description\":\"Fix common BPMN flow type mistakes: learn when to use sequence flow vs message flow, avoid using sequence flows between pools, and model collaboration correctly for clearer, audit-ready diagrams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Notation Misuse and Semantic Errors\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Sequence Flows vs Message Flows: Mixing Worlds\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-TW\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-TW\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Sequence Flow vs Message Flow: Avoid the Mix-Up","description":"Fix common BPMN flow type mistakes: learn when to use sequence flow vs message flow, avoid using sequence flows between pools, and model collaboration correctly for clearer, audit-ready diagrams.","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\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/","og_locale":"zh_TW","og_type":"article","og_title":"Sequence Flow vs Message Flow: Avoid the Mix-Up","og_description":"Fix common BPMN flow type mistakes: learn when to use sequence flow vs message flow, avoid using sequence flows between pools, and model collaboration correctly for clearer, audit-ready diagrams.","og_url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/","og_site_name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"7 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/","name":"Sequence Flow vs Message Flow: Avoid the Mix-Up","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-02-25T10:20:35+00:00","description":"Fix common BPMN flow type mistakes: learn when to use sequence flow vs message flow, avoid using sequence flows between pools, and model collaboration correctly for clearer, audit-ready diagrams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/sequence-flow-vs-message-flow-mistakes\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/tw\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Notation Misuse and Semantic Errors","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/"},{"@type":"ListItem","position":4,"name":"Sequence Flows vs Message Flows: Mixing Worlds"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website","url":"https:\/\/skills.visual-paradigm.com\/tw\/","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-TW"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/tw\/","logo":{"@type":"ImageObject","inLanguage":"zh-TW","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/574","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/574\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/571"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=574"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}