{"id":1472,"date":"2026-02-25T10:42:05","date_gmt":"2026-02-25T10:42:05","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/"},"modified":"2026-02-25T10:42:05","modified_gmt":"2026-02-25T10:42:05","slug":"soaml-vs-uml-comparison","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/","title":{"rendered":"Comparing SoaML and UML: Where They Overlap and Differ"},"content":{"rendered":"

When I first started modeling services, I defaulted to UML without questioning its suitability. I\u2019d draw class diagrams, sequence diagrams, and component diagrams \u2014 all familiar from past projects. But the moment I tried to model a service contract or define a service\u2019s role in an enterprise ecosystem, something felt off. The tools were right, but the semantics weren\u2019t. That\u2019s when I realized: UML is powerful, but it wasn\u2019t built for service-centric design.<\/p>\n

SoaML was born from that gap. It extends UML\u2019s metamodel but redefines key concepts through a service lens \u2014 focusing on participants, contracts, and capabilities. This chapter will help you understand where UML stops and SoaML begins, and why that distinction matters in real-world architecture.<\/p>\n

If you’re familiar with UML, you\u2019ll find SoaML intuitive in structure but purpose-driven in semantics. This section clarifies how SoaML enhances UML to support service-oriented modeling, with practical comparisons and visual examples.<\/p>\n

Understanding the Core Models: UML vs SoaML<\/h2>\n

UML provides a general-purpose modeling framework. Its components \u2014 classes, objects, components, and relationships \u2014 are excellent for software structure. But in service-oriented design, we need more than classes; we need roles, contracts, and interaction semantics.<\/p>\n

SoaML builds directly on UML\u2019s metamodel but introduces new constructs tailored for services. Instead of focusing only on “classes” and “components,” SoaML emphasizes “participants,” “service contracts,” and “capabilities.” This shift isn\u2019t about replacing UML \u2014 it\u2019s about extending it for better service clarity.<\/p>\n

Key Structural Differences<\/h3>\n

Let\u2019s walk through the most common modeling elements and how their roles differ between UML and SoaML.<\/p>\n\n\n\n\n\n\n\n
Element<\/th>\nUML Meaning<\/th>\nSoaML Meaning<\/th>\nWhy It Matters<\/th>\n<\/tr>\n
Class<\/td>\nStructure of data and behavior<\/td>\nNot directly used \u2014 replaced by Service Interface<\/td>\nSoaML focuses on behavior abstraction through contracts, not data structures.<\/td>\n<\/tr>\n
Component<\/td>\nPhysical or logical module in a system<\/td>\nParticipant \u2014 a provider or consumer of services<\/td>\nSoaML introduces role-based participation, making service roles explicit.<\/td>\n<\/tr>\n
Interface<\/td>\nContract between a client and a service<\/td>\nService Interface \u2014 formalized contract for service operations<\/td>\nSoaML refines this into a standardized, reusable format for inter-service communication.<\/td>\n<\/tr>\n
Sequence Diagram<\/td>\nTemporal interaction flow between objects<\/td>\nService Interaction Diagram \u2014 models service-level collaboration<\/td>\nSoaML shifts from object interaction to service orchestration.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

These differences aren\u2019t just semantic. They reflect a deeper architectural intent: UML models software, while SoaML models service behavior.<\/p>\n

SoaML UML Comparison: Where They Overlap<\/h2>\n

It\u2019s important to recognize that SoaML doesn\u2019t replace UML. It uses UML\u2019s foundation but adds service-specific semantics. Many UML constructs are reused with new meanings.<\/p>\n

For example, the Component<\/code> in UML becomes a Participant<\/code> in SoaML. But both serve a similar purpose: encapsulating functionality. The difference lies in how they\u2019re used. A UML component might be a software module; a SoaML participant is a service provider or consumer in a business ecosystem.<\/p>\n

Similarly, UML Interface<\/code> is a broad term. In SoaML, you\u2019ll see Service Interface<\/code> as a specialized interface that defines operations, data types, and interaction patterns. This makes it far more suitable for API contract definition.<\/p>\n

SoaML UML comparison reveals that the two languages share structure but differ in purpose. UML answers: \u201cHow does this software work?\u201d SoaML answers: \u201cHow do services interact across organizational boundaries?\u201d<\/p>\n

Practical Example: Modeling a Payment Service<\/h3>\n

Consider a payment service. In UML, you might model this as a class with methods like calculateFee()<\/code> and processPayment()<\/code>. But in SoaML, you model it as a Service<\/code> with a Service Interface<\/code> that defines operations like processPayment()<\/code> and refund()<\/code>, with defined input\/output messages and error codes.<\/p>\n

That\u2019s not just a detail \u2014 it\u2019s a fundamental shift. The SoaML model becomes a contract. It\u2019s not just about code; it\u2019s about defining what the service promises to do, who can invoke it, and how it behaves under failure.<\/p>\n

This is where SoaML extension of UML becomes critical. It turns a generic UML component into a service with discoverability, contract, and interoperability baked in.<\/p>\n

When to Use SoaML Instead of UML<\/h2>\n

Not every model needs SoaML. UML remains excellent for system-level design, internal architecture, and component modeling. But when your focus is on services \u2014 especially those that cross organizational or technical boundaries \u2014 SoaML is the right tool.<\/p>\n

Consider these scenarios:<\/p>\n

    \n
  • Designing an API for external partners \u2014 use SoaML for formal contract definition.<\/li>\n
  • Modeling interactions between microservices in a cloud-native platform \u2014 SoaML provides clarity on roles and contracts.<\/li>\n
  • Documenting service capabilities for business teams \u2014 SoaML\u2019s Capability<\/code> and Service Contract<\/code> elements communicate intent clearly.<\/li>\n<\/ul>\n

    When you’re modeling service discovery, contract reuse, or interoperability across teams, SoaML brings precision that UML alone can\u2019t.<\/p>\n

    But when modeling internal data flows, object hierarchies, or software architecture patterns, UML still holds its ground. The key is knowing when to use which.<\/p>\n

    Real-World Trade-offs and Limitations<\/h2>\n

    SoaML isn\u2019t perfect. It introduces complexity for teams new to service modeling. The added concepts \u2014 like Participant<\/code>, Capability<\/code>, and Service Contract<\/code> \u2014 require understanding beyond basic UML.<\/p>\n

    Also, while SoaML integrates well with UML tools, full SoaML support is still limited to a few platforms like Visual Paradigm. You\u2019ll need to ensure your modeling environment supports SoaML-specific diagram types.<\/p>\n

    Another trade-off: SoaML\u2019s focus on contracts may lead to over-engineering in early stages. I\u2019ve seen teams create overly detailed contracts before the service\u2019s actual behavior is stable. The rule of thumb: define contracts once the service\u2019s core behavior is clear.<\/p>\n

    That said, the benefits \u2014 improved clarity, better collaboration, and robust contracts \u2014 outweigh the costs in most enterprise and distributed systems.<\/p>\n

    How SoaML Extends UML: A Summary<\/h2>\n

    SoaML is not a replacement for UML. It\u2019s a specialized extension \u2014 a layer that adds service semantics on top of UML\u2019s general-purpose foundation.<\/p>\n

    Think of it this way: UML gives you the what<\/em> and how<\/em> of software. SoaML gives you the who<\/em> and why<\/em> of service interaction \u2014 who provides, who consumes, and what they agree to do.<\/p>\n

    SoaML extension of UML is best seen in three dimensions:<\/p>\n

      \n
    1. Role Clarity:<\/strong> SoaML explicitly defines participants as providers or consumers \u2014 a concept absent in UML.<\/li>\n
    2. Contract-Driven Design:<\/strong> SoaML enforces service contracts as first-class artifacts. UML may suggest them but doesn\u2019t enforce them.<\/li>\n
    3. Interoperability Focus:<\/strong> SoaML models are designed to be shared, validated, and understood across teams and systems \u2014 a core need in service-oriented architecture.<\/li>\n<\/ol>\n

      These aren\u2019t just syntactic changes. They represent a shift in thinking: from object-centric design to service-centric orchestration.<\/p>\n

      Frequently Asked Questions<\/h2>\n

      What is the difference between UML and SoaML?<\/h3>\n

      UML is a general-purpose modeling language for software systems. SoaML is a specialized extension of UML that adds service-specific semantics \u2014 focusing on participants, service contracts, and capabilities. While UML models components and classes, SoaML models service roles and interactions.<\/p>\n

      Can SoaML be used with UML in the same project?<\/h3>\n

      Absolutely. SoaML is designed to integrate with UML. You can use UML for internal component and class modeling, and SoaML for service contracts and participant roles. Tools like Visual Paradigm support both, allowing seamless integration.<\/p>\n

      Is SoaML better than UML for service design?<\/h3>\n

      It depends on context. SoaML is superior when modeling service contracts, cross-team interactions, or enterprise-level service ecosystems. UML remains better for internal software architecture and object modeling. Use both \u2014 but know when each excels.<\/p>\n

      Why should I learn SoaML if I already know UML?<\/h3>\n

      Because UML doesn\u2019t model service contracts, roles, or capabilities by default. SoaML fills that gap. Learning SoaML helps you design services that are discoverable, reusable, and interoperable \u2014 which is essential for modern enterprise architecture.<\/p>\n

      How does SoaML extend UML?<\/h3>\n

      SoaML extends UML by introducing new metaclasses like Participant<\/code>, Service Contract<\/code>, and Capability<\/code>. It redefines existing UML concepts (like Interface<\/code>) with service-specific semantics. It also adds new diagram types such as Service Interface and Service Contract diagrams.<\/p>\n

      What are the main advantages of the SoaML UML comparison?<\/h3>\n

      Understanding the SoaML UML comparison helps you choose the right modeling language for the right context. It avoids overuse of UML in service modeling and prevents under-use of SoaML in architectural design. It empowers teams to model service contracts with precision and clarity.<\/p>\n","protected":false},"excerpt":{"rendered":"

      When I first started modeling services, I defaulted to UML without questioning its suitability. I\u2019d draw class […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1468,"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-1472","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nSoaML vs UML: Key Differences Explained<\/title>\n<meta name=\"description\" content=\"Discover the difference between UML and SoaML with expert insights on how SoaML extends UML for service-oriented architecture modeling. Learn practical applications, comparison tables, and real-world modeling decisions.\" \/>\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\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SoaML vs UML: Key Differences Explained\" \/>\n<meta property=\"og:description\" content=\"Discover the difference between UML and SoaML with expert insights on how SoaML extends UML for service-oriented architecture modeling. Learn practical applications, comparison tables, and real-world modeling decisions.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/\" \/>\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\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/\",\"name\":\"SoaML vs UML: Key Differences Explained\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:42:05+00:00\",\"description\":\"Discover the difference between UML and SoaML with expert insights on how SoaML extends UML for service-oriented architecture modeling. Learn practical applications, comparison tables, and real-world modeling decisions.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SoaML Diagram Fundamentals: A Beginner\u2019s Guide\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Understanding the Foundations of SoaML\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Comparing SoaML and UML: Where They Overlap and Differ\"}]},{\"@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":"SoaML vs UML: Key Differences Explained","description":"Discover the difference between UML and SoaML with expert insights on how SoaML extends UML for service-oriented architecture modeling. Learn practical applications, comparison tables, and real-world modeling decisions.","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\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/","og_locale":"ja_JP","og_type":"article","og_title":"SoaML vs UML: Key Differences Explained","og_description":"Discover the difference between UML and SoaML with expert insights on how SoaML extends UML for service-oriented architecture modeling. Learn practical applications, comparison tables, and real-world modeling decisions.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/","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\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/","name":"SoaML vs UML: Key Differences Explained","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:42:05+00:00","description":"Discover the difference between UML and SoaML with expert insights on how SoaML extends UML for service-oriented architecture modeling. Learn practical applications, comparison tables, and real-world modeling decisions.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/soaml-vs-uml-comparison\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"SoaML Diagram Fundamentals: A Beginner\u2019s Guide","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/"},{"@type":"ListItem","position":3,"name":"Understanding the Foundations of SoaML","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/soaml-diagram-fundamentals\/introduction-to-soaml\/"},{"@type":"ListItem","position":4,"name":"Comparing SoaML and UML: Where They Overlap and Differ"}]},{"@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\/1472","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\/1472\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1468"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=1472"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=1472"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}