{"id":572,"date":"2026-02-25T10:20:34","date_gmt":"2026-02-25T10:20:34","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/"},"modified":"2026-02-25T10:20:34","modified_gmt":"2026-02-25T10:20:34","slug":"bpmn-event-mistakes","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/","title":{"rendered":"Misusing Events: Starts, Ends, and Intermediates"},"content":{"rendered":"<p>Getting event modeling right early saves hours of rework later. A single misused event can change how a process is interpreted by developers, auditors, or business users. I\u2019ve seen teams ship automation based on diagrams where the start event was a generic &#8220;Start&#8221; symbol \u2014 no trigger, no context, no clarity. The result? The system launched processes at random times. That\u2019s not just a modeling flaw. It\u2019s a risk.<\/p>\n<p>Too many practitioners treat events as decorative. But every event defines intent. A start event signals the trigger. An end event defines the conclusion. Misuse here distorts the entire process scope.<\/p>\n<p>This chapter breaks down the most common BPMN event mistakes \u2014 not just how to spot them, but how to fix them with a clear, repeatable method. You\u2019ll learn how to choose the right BPMN event type, assign unambiguous names, and avoid misleading patterns that confuse automation and auditing.<\/p>\n<h2>Start and End Event Errors: The Silent Triggers of Misinterpretation<\/h2>\n<p>Start and end events are not just visual cues. They define the process boundary. A missing start event makes a process ambiguous \u2014 it could trigger from anywhere.<\/p>\n<p>Similarly, an end event with no meaning doesn\u2019t signal completion. It\u2019s like a door with no exit. The process might appear to end, but the system doesn\u2019t know when it\u2019s truly done.<\/p>\n<h3>Common Start Event Mistakes<\/h3>\n<ul>\n<li>Using a generic &#8220;Start&#8221; symbol without specifying a trigger.<\/li>\n<li>Adding multiple start events without clear separation of scenarios.<\/li>\n<li>Using a plain start event for a process that should only begin on message receipt.<\/li>\n<\/ul>\n<p>Here\u2019s a real example: a team modeled a customer onboarding process with a start event labeled &#8220;Start.&#8221; No trigger. No context. The automation tool assumed it was always ready. In reality, it only started when a customer submitted a form. The gap between intent and behavior caused delays and misaligned expectations.<\/p>\n<h3>End Event Confusion: When &#8220;End&#8221; Isn\u2019t Final<\/h3>\n<p>End events aren\u2019t just decorative. They define what \u201cdone\u201d means. A process can end in multiple ways: normally, due to error, or through termination.<\/p>\n<p>Using a terminate end event without clarity creates unintended consequences. Termination doesn&#8217;t mean \u201cfinish.\u201d It means \u201cstop everything immediately.\u201d One such case: a loan approval process used a terminate end event after approval. When the process was terminated, downstream systems had no record of approval \u2014 and no audit trail.<\/p>\n<h2>Choosing the Right BPMN Event Types<\/h2>\n<p>Picking the wrong event type is a silent error. It may pass validation, but it misrepresents business intent. Let\u2019s break down the most common confusions.<\/p>\n<h3>Message vs. Timer vs. Error Events<\/h3>\n<p>Each event type carries a distinct semantic meaning. Confusing them leads to incorrect automation and unpredictable behavior.<\/p>\n<p>Here\u2019s a decision table to guide your choice:<\/p>\n<table>\n<thead>\n<tr>\n<th>Trigger<\/th>\n<th>Recommended Event Type<\/th>\n<th>When to Use<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>A customer submits a form<\/td>\n<td>Message start event<\/td>\n<td>Process begins via external message<\/td>\n<\/tr>\n<tr>\n<td>One hour after submission<\/td>\n<td>Timer event<\/td>\n<td>Process begins after delay<\/td>\n<\/tr>\n<tr>\n<td>An error occurs in a step<\/td>\n<td>Error end event<\/td>\n<td>Process terminates due to exception<\/td>\n<\/tr>\n<tr>\n<td>System failure or shutdown<\/td>\n<td>Terminate end event<\/td>\n<td>Immediate process cancellation<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Rule of thumb: the event type must match the trigger. Not the label. The behavior.<\/p>\n<h3>How to Use BPMN Events Correctly<\/h3>\n<ol>\n<li><strong>Define the trigger first.<\/strong> Ask: What causes this process to start or end?<\/li>\n<li><strong>Match the event type to the trigger.<\/strong> Use message for external signals, timer for time-based triggers, error for exceptions.<\/li>\n<li><strong>Name with intent.<\/strong> Instead of &#8220;Start&#8221; or &#8220;End,&#8221; use &#8220;Customer submits form&#8221; or &#8220;Approval rejected.&#8221;<\/li>\n<li><strong>Use only one start event per scenario.<\/strong> If multiple triggers exist, use multiple processes or separate events with clear labels.<\/li>\n<li><strong>Avoid terminate end events unless necessary.<\/strong> They bypass normal flow and can leave side effects unlogged.<\/li>\n<\/ol>\n<p>Consider this: a process to handle customer complaints. The start event should be \u201cCustomer submits complaint via portal.\u201d Not \u201cStart.\u201d The name is not decorative. It\u2019s a contract.<\/p>\n<h2>Overusing Terminate End Events: The Hidden Risk<\/h2>\n<p>Terminate end events are powerful \u2014 but dangerous. They stop the entire process immediately, skipping all intermediate steps, including cleanup and notifications.<\/p>\n<p>Common mistake: using a terminate end event in a process that handles data reconciliation. When an error occurs, the process terminates \u2014 but the data remains inconsistent, and no one is notified.<\/p>\n<p>Instead, use:<\/p>\n<ul>\n<li><strong>Error end event<\/strong> \u2014 for handling exceptions in a controlled way.<\/li>\n<li><strong>Cancel end event<\/strong> \u2014 for processes that can be canceled gracefully (e.g., a reservation).<\/li>\n<li><strong>Compensation event<\/strong> \u2014 for reversing prior actions.<\/li>\n<\/ul>\n<p>Termination should be reserved for exceptional cases \u2014 like a system shutdown \u2014 where no cleanup is possible.<\/p>\n<h2>Event Naming: Intent Over Convention<\/h2>\n<p>Bad names: \u201cStart,\u201d \u201cEnd,\u201d \u201cEvent 1.\u201d These are meaningless in context.<\/p>\n<p>Good names: \u201cCustomer submits application,\u201d \u201cSystem receives order from partner,\u201d \u201cError in payment validation.\u201d<\/p>\n<p>Use the verb\u2013object format. Be specific. Include the actor if relevant. The goal is to make the event self-explanatory \u2014 even to someone who didn\u2019t create the diagram.<\/p>\n<h3>Do\u2019s and Don\u2019ts of Event Naming<\/h3>\n<ul>\n<li><strong>Do<\/strong> name events with the trigger: \u201cCustomer submits form\u201d<\/li>\n<li><strong>Do<\/strong> include the source: \u201cSystem receives API call from partner\u201d<\/li>\n<li><strong>Don\u2019t<\/strong> use generic terms: \u201cStart,\u201d \u201cEnd,\u201d \u201cEvent\u201d<\/li>\n<li><strong>Don\u2019t<\/strong> name after a system action: \u201cUpdate database\u201d \u2014 that\u2019s a task, not a trigger<\/li>\n<\/ul>\n<p>Naming isn\u2019t just about clarity. It\u2019s about ensuring correct automation. A poorly named event can lead to incorrect process mapping in a workflow engine.<\/p>\n<h2>Practical Checklist: Validating Event Modeling<\/h2>\n<p>Before finalizing any process, run this quick audit:<\/p>\n<ul>\n<li>Does every process have exactly one start event?<\/li>\n<li>Is the start event type correct for the trigger?<\/li>\n<li>Does the end event reflect the actual process conclusion?<\/li>\n<li>Is a terminate end event used only when immediate cancellation is required?<\/li>\n<li>Are all event names clear, specific, and action-based?<\/li>\n<li>Are there multiple start events? If yes, are they clearly separated by scenario?<\/li>\n<\/ul>\n<p>These checks prevent 90% of event-related errors. They\u2019re quick, repeatable, and work in any modeling tool.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What happens if I don\u2019t use a start event in my BPMN process?<\/h3>\n<p>Without a start event, the process has no defined trigger. Most workflow engines will reject it or assume an implicit start \u2014 which leads to unpredictable behavior. Always define the trigger explicitly.<\/p>\n<h3>Can I have multiple start events in one process?<\/h3>\n<p>Yes \u2014 but only if they represent distinct, independent scenarios. For example, \u201cCustomer submits form\u201d and \u201cEmail notification received.\u201d Use separate start events with clear labels. Don\u2019t use multiple starts for the same process.<\/p>\n<h3>When should I use a timer start event instead of a message start event?<\/h3>\n<p>Use a timer start event when the process begins after a delay (e.g., \u201cSend reminder after 48 hours\u201d). Use a message start event when the process is triggered by an external system or user input (e.g., \u201cOrder received via API\u201d). The key is whether the trigger is time-based or event-based.<\/p>\n<h3>Is it a problem to use a message start event for a system-generated process?<\/h3>\n<p>Not inherently. But ensure the message is sent by a recognized external source \u2014 a user, an external system, or a scheduled task. If the system itself initiates the process, use a timer or a call activity. Avoid self-triggering start events.<\/p>\n<h3>Why should I avoid terminate end events?<\/h3>\n<p>Terminate end events bypass normal flow and can leave systems in an inconsistent state. They\u2019re not failure-safe. Use error, cancel, or compensation events instead unless you\u2019re certain immediate termination is correct.<\/p>\n<h3>How do I know which event type to use for a business rule?<\/h3>\n<p>Start events should reflect the trigger: message (external input), timer (time-based), error (exception), or conditional (business rule). The event type must align with the actual cause. Don\u2019t use a timer event just because a rule runs every hour \u2014 that\u2019s a workflow, not a trigger. Use a message or timer event only if the process starts due to that event.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Getting event modeling right early saves hours of rework later. A single misused event can change how a proces [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":571,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-572","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>BPMN Event Mistakes: Fix Start and End Events<\/title>\n<meta name=\"description\" content=\"Avoid start and end event errors in BPMN. Learn how to use BPMN events correctly with real examples, naming best practices, and practical decision rules for message, timer, and error events.\" \/>\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\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Event Mistakes: Fix Start and End Events\" \/>\n<meta property=\"og:description\" content=\"Avoid start and end event errors in BPMN. Learn how to use BPMN events correctly with real examples, naming best practices, and practical decision rules for message, timer, and error events.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills\u65e5\u672c\u8a9e\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/\",\"name\":\"BPMN Event Mistakes: Fix Start and End Events\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:20:34+00:00\",\"description\":\"Avoid start and end event errors in BPMN. Learn how to use BPMN events correctly with real examples, naming best practices, and practical decision rules for message, timer, and error events.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/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\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Misusing Events: Starts, Ends, and Intermediates\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Event Mistakes: Fix Start and End Events","description":"Avoid start and end event errors in BPMN. Learn how to use BPMN events correctly with real examples, naming best practices, and practical decision rules for message, timer, and error events.","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\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/","og_locale":"ja_JP","og_type":"article","og_title":"BPMN Event Mistakes: Fix Start and End Events","og_description":"Avoid start and end event errors in BPMN. Learn how to use BPMN events correctly with real examples, naming best practices, and practical decision rules for message, timer, and error events.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"7\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/","name":"BPMN Event Mistakes: Fix Start and End Events","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:20:34+00:00","description":"Avoid start and end event errors in BPMN. Learn how to use BPMN events correctly with real examples, naming best practices, and practical decision rules for message, timer, and error events.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-event-mistakes\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/ja\/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\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/"},{"@type":"ListItem","position":4,"name":"Misusing Events: Starts, Ends, and Intermediates"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website","url":"https:\/\/skills.visual-paradigm.com\/ja\/","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","url":"https:\/\/skills.visual-paradigm.com\/ja\/","logo":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills\u65e5\u672c\u8a9e"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/572","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/572\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/571"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=572"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=572"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}