{"id":507,"date":"2026-02-25T10:19:23","date_gmt":"2026-02-25T10:19:23","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/"},"modified":"2026-02-25T10:19:23","modified_gmt":"2026-02-25T10:19:23","slug":"cmmn-specification-evolution","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/","title":{"rendered":"The Evolution of the CMMN Standard"},"content":{"rendered":"

When I first sit down with a team who\u2019s struggling to model a complex insurance claim, I often ask: “Is your model built to react to events, or just to follow a script?” The answer reveals everything. If they say \u201cfollow a script,\u201d they\u2019re using a workflow engine with rigid lanes\u2014perfect for BPMN, but not for knowledge-intensive, unpredictable cases. That\u2019s where CMMN steps in. The CMMN specification exists not to replace BPMN, but to expand our modeling toolkit to handle situations where the path isn\u2019t known upfront.<\/p>\n

Over two decades, the CMMN specification has evolved from a bold idea into a mature, industry-recognized standard. It wasn\u2019t born overnight. It was shaped by real-world pain\u2014managing legal disputes, triaging medical records, handling customer escalations\u2014where automation alone fails. The OMG CMMN specification now offers a disciplined yet flexible way to model cases that adapt to context, decisions, and events.<\/p>\n

By the end of this chapter, you\u2019ll understand how the CMMN history unfolded, what drove each major revision, and why today\u2019s best practices are rooted in real engineering, not just theory. You\u2019ll learn to recognize where the standard excels\u2014and where it still demands human judgment.<\/p>\n

The Birth of a Standard: CMMN 1.0 and the OMG Initiative<\/h2>\n

The journey began in 2011, when the Object Management Group (OMG) released the first formal CMMN specification. My first encounter with it was in a public forum\u2014someone asked, \u201cHow do you model a case that might take weeks, with no fixed path?\u201d That question still echoes today.<\/p>\n

CMMN 1.0 introduced a new way of thinking: not a flowchart, but a case plan<\/strong>\u2014a living, dynamic framework that adapts to business events. It centered on three core elements: stages, tasks, and milestones. But the real breakthrough was the event-driven<\/strong> design.<\/p>\n

Before CMMN, most modeling focused on linear, predictable processes. But many real cases\u2014like resolving a compliance violation or reviewing a high-value claim\u2014don\u2019t follow a fixed sequence. They\u2019re context-sensitive, often requiring human judgment. CMMN 1.0 answered that challenge.<\/p>\n

What made it work was the case plan model<\/strong> (CPM), which allowed analysts to define a structure without locking in sequence. Tasks could be open or closed, enabled or disabled, based on events\u2014like a document being uploaded or a deadline passing.<\/p>\n

Why CMMN 1.0 Was a Game-Changer<\/h3>\n
    \n
  • Introduced event-based triggers<\/strong> instead of just sequence flows.<\/li>\n
  • Allowed dynamic task activation<\/strong> based on real-time data.<\/li>\n
  • Provided first-class support for human decision-making<\/strong> in process models.<\/li>\n
  • Enabled adaptive case lifecycle management<\/strong> without predefining every path.<\/li>\n<\/ul>\n

    One of my early projects involved modeling a medical review process. The CMMN 1.0 model allowed us to define the stages\u2014initial intake, documentation review, specialist consultation\u2014without forcing a rigid order. If new evidence appeared, the case could re-enter a prior stage. That flexibility saved us from over-engineering a monolithic workflow.<\/p>\n

    CMMN 1.1 and the Push for Interoperability<\/h2>\n

    Released in 2013, CMMN 1.1 wasn\u2019t a revolution\u2014it was an evolution. The OMG community recognized that while the core model was solid, real-world adoption needed better tooling and clarity.<\/p>\n

    Key updates included:<\/p>\n

      \n
    • Clarified semantics for entry and exit criteria<\/strong>.<\/li>\n
    • Defined the case file<\/strong> as a structured data container for all case-related information.<\/li>\n
    • Improved interoperability with BPMN and DMN through common data and execution semantics.<\/li>\n<\/ul>\n

      What stood out was how this version made it easier to integrate CMMN into existing enterprise architectures. We started seeing CMMN models being used alongside BPMN processes, with the case model managing the adaptive logic and BPMN handling the structured subroutines.<\/p>\n

      I once worked with a financial institution that had separate BPMN models for loan origination and CMMN models for dispute resolution. With CMMN 1.1, they could now link the two: when a dispute arose, a CMMN case would be created, and the relevant BPMN process would be invoked as a sub-case. The integration was seamless, and the model made sense to both IT and business teams.<\/p>\n

      CMMN 1.2: Refining the Core for Real-World Use<\/h2>\n

      By 2015, the community had used CMMN in production for years. Feedback poured in: \u201cToo many edge cases,\u201d \u201cHard to validate,\u201d \u201cNo clear guidance on when to use a nested case.\u201d CMMN 1.2 addressed these directly.<\/p>\n

      Key enhancements:<\/p>\n

        \n
      • Introduced planning<\/strong> and execution<\/strong> modes for case plans.<\/li>\n
      • Clarified task dependencies<\/strong> and execution order rules.<\/li>\n
      • Added support for multiple case files<\/strong> and data binding<\/strong> to tasks.<\/li>\n<\/ul>\n

        One major shift: the introduction of planning mode<\/strong>. In this mode, the model doesn\u2019t execute\u2014instead, it\u2019s used to analyze what tasks *could* be activated based on current data. This became invaluable for scenario simulation and training.<\/p>\n

        I\u2019ve used this feature in a healthcare case model where a patient\u2019s intake triggered a set of potential follow-ups: blood test, consultation, imaging. The planning mode allowed the care team to see all possible next steps *before* any action was taken. It wasn\u2019t about automating decisions\u2014it was about clarifying options.<\/p>\n

        Trade-offs in CMMN 1.2<\/h3>\n

        The trade-off? Increased complexity. More rules meant more to learn, and more opportunities for misinterpretation. But the benefit\u2014greater predictability and auditability\u2014outweighed the cost.<\/p>\n

        For example, in a legal case model, we now had the ability to define that a motion could only be filed once discovery was complete, and that discovery itself was conditional on the court\u2019s order. The model could now reflect both the *logic* and the *constraints*.<\/p>\n

        OMG CMMN and the Role of Community<\/h2>\n

        What sets the CMMN specification apart is how it\u2019s developed\u2014not by a single vendor, but by the OMG community<\/strong>, with contributions from toolmakers, enterprises, and independent experts.<\/p>\n

        Every major revision has been a collaborative effort. Take CMMN 1.3 (2018). It wasn\u2019t about new features\u2014it was about resolving ambiguities. One key change: explicitly defining when a task is \u201cenabled\u201d vs \u201ccompleted\u201d<\/strong>. This small clarification prevented hundreds of misinterpretations in real models.<\/p>\n

        The CMMN history shows a consistent pattern: the standard evolves through practical application<\/strong>, not abstract theory. The community drives it forward by identifying pain points in actual models.<\/p>\n

        Key Milestones in the CMMN History<\/h3>\n\n\n\n\n\n\n\n
        Year<\/th>\nVersion<\/th>\nKey Change<\/th>\nImpact<\/th>\n<\/tr>\n
        2011<\/td>\n1.0<\/td>\nFirst formal CMMN specification<\/td>\nIntroduced event-driven case modeling<\/td>\n<\/tr>\n
        2013<\/td>\n1.1<\/td>\nClarified case file and entry\/exit criteria<\/td>\nImproved interoperability with BPMN\/DMN<\/td>\n<\/tr>\n
        2015<\/td>\n1.2<\/td>\nEnhanced planning execution and data binding<\/td>\nBetter support for simulation and human teams<\/td>\n<\/tr>\n
        2018<\/td>\n1.3<\/td>\nResolved semantic ambiguities<\/td>\nStandardized logic across tools and teams<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

        Why CMMN Specification Still Matters Today<\/h2>\n

        Today\u2019s CMMN specification isn\u2019t just about modeling\u2014it\u2019s about **governance**, **traceability**, and **collaboration**. It\u2019s a language shared across business analysts, IT architects, and frontline staff.<\/p>\n

        But here\u2019s what I\u2019ve learned: you don\u2019t model to please a tool.<\/strong> You model to empower people to make better decisions. The CMMN specification gives you the structure. But the power comes from how you use it\u2014what you leave out, what you emphasize, and when you allow flexibility.<\/p>\n

        For instance, in a case model for a customer dispute, I might define entry criteria like:<\/p>\n

        IF (customer complaint type = \"Billing Error\") AND (document uploaded = TRUE) THEN enable \"Review Billing Record\"\n<\/code><\/pre>\n
        But I\u2019d also allow the case manager to manually override this\u2014because sometimes, the right decision isn\u2019t in the rule, it\u2019s in the context.<\/p>\n
        That\u2019s the heart of CMMN: it\u2019s not about automation. It\u2019s about coordination. About making the unknown visible, the uncertain manageable, and the adaptive, executable.<\/p>\n
        Frequently Asked Questions<\/h2>\n
        What does CMMN history tell us about its evolution?<\/h3>\n
        The CMMN history reflects a shift from theoretical modeling to practical, real-world use. Each version addressed feedback from actual case modeling scenarios\u2014especially around event handling, data binding, and interoperability. The evolution shows that CMMN wasn\u2019t designed for perfection but for adaptability.<\/p>\n
        How has OMG CMMN influenced enterprise modeling?<\/h3>\n
        OMG CMMN has provided a standardized way to model adaptive workflows that no other notation can fully replace. It\u2019s now embedded in enterprise architectures, integrated with BPMN and DMN, and used in sectors like healthcare, legal, and insurance where decisions depend on context, not just sequence.<\/p>\n
        Is CMMN 1.3 still the latest specification?<\/h3>\n
        Yes, CMMN 1.3 is the most recent official version. While some tools support newer features through extensions, the OMG standard remains stable. Any future revisions will likely focus on integration with AI, analytics, and decentralized execution environments.<\/p>\n
        Why should I care about the CMMN specification if I\u2019m not a tool developer?<\/h3>\n
        Because the CMMN specification defines what your model means. It\u2019s not just a diagram\u2014it\u2019s a shared contract. When teams across departments understand the same rules, modeling becomes a conversation, not a chore. You\u2019ll avoid rework, misalignment, and failed implementations.<\/p>\n
        Can CMMN be used without BPMN or DMN?<\/h3>\n
        Absolutely. CMMN is a standalone framework for adaptive case management. While integrating with BPMN and DMN is powerful, it\u2019s not required. Many successful models use only CMMN to handle the dynamic, human-centric parts of a process.<\/p>\n
        How do I know which CMMN version to use in my organization?<\/h3>\n
        Use CMMN 1.3. It\u2019s the most stable, well-documented, and widely supported. If your tooling offers only older versions, plan an upgrade. The differences are minor, but the consistency across systems is worth the effort.<\/p>\n","protected":false},"excerpt":{"rendered":"
        When I first sit down with a team who\u2019s struggling to m […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":503,"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-507","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nCMMN Specification: Evolution & Best Practices<\/title>\n<meta name=\"description\" content=\"Explore the CMMN specification evolution, key milestones, and how OMG CMMN shaped adaptive case management. Learn from real-world modeling challenges and expert insights.\" \/>\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\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CMMN Specification: Evolution & Best Practices\" \/>\n<meta property=\"og:description\" content=\"Explore the CMMN specification evolution, key milestones, and how OMG CMMN shaped adaptive case management. Learn from real-world modeling challenges and expert insights.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/\",\"name\":\"CMMN Specification: Evolution & Best Practices\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:19:23+00:00\",\"description\":\"Explore the CMMN specification evolution, key milestones, and how OMG CMMN shaped adaptive case management. Learn from real-world modeling challenges and expert insights.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CMMN Explained: A Practical Guide for Modelers\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Foundations of Case Management and CMMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"The Evolution of the CMMN Standard\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"CMMN Specification: Evolution & Best Practices","description":"Explore the CMMN specification evolution, key milestones, and how OMG CMMN shaped adaptive case management. Learn from real-world modeling challenges and expert insights.","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\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/","og_locale":"zh_CN","og_type":"article","og_title":"CMMN Specification: Evolution & Best Practices","og_description":"Explore the CMMN specification evolution, key milestones, and how OMG CMMN shaped adaptive case management. Learn from real-world modeling challenges and expert insights.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"8 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/","name":"CMMN Specification: Evolution & Best Practices","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:19:23+00:00","description":"Explore the CMMN specification evolution, key milestones, and how OMG CMMN shaped adaptive case management. Learn from real-world modeling challenges and expert insights.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/cmmn-specification-evolution\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"CMMN Explained: A Practical Guide for Modelers","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/"},{"@type":"ListItem","position":3,"name":"Foundations of Case Management and CMMN","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/cmmn-explained-practical-guide-for-modelers\/foundations-of-case-management-and-cmmn\/"},{"@type":"ListItem","position":4,"name":"The Evolution of the CMMN Standard"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/507","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/507\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/503"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=507"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=507"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}