{"id":941,"date":"2026-02-25T10:32:34","date_gmt":"2026-02-25T10:32:34","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/"},"modified":"2026-02-25T10:32:34","modified_gmt":"2026-02-25T10:32:34","slug":"crc-sketch-to-uml","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/","title":{"rendered":"From Informal Sketch to Formal Structure"},"content":{"rendered":"

Never rush the transition from CRC cards to UML. That\u2019s the single most important rule I\u2019ve seen teams break\u2014often at great cost. I\u2019ve watched entire development cycles unravel because a team skipped validation and jumped straight into formalizing a sketch that wasn\u2019t ready. The result? Overly complex diagrams, missing relationships, and poor cohesion\u2014just because the foundational intent wasn\u2019t solid.<\/p>\n

Formalizing class diagrams isn\u2019t about making something look better. It\u2019s about ensuring every element you draw reflects real, agreed-upon behavior and structure. This chapter walks you through the critical steps to evolve your informal CRC sketch into a precise, maintainable UML class diagram\u2014step by step, with real design trade-offs and clarity.<\/p>\n

Why the Transition Matters<\/h2>\n

Turning CRC cards into UML isn’t just a mechanical conversion. It\u2019s a shift from exploration to specification. CRC cards are ideal for team brainstorming\u2014lightweight, collaborative, and fast. But they lack structure, consistency, and persistence.<\/p>\n

UML, on the other hand, provides a standardized language for documentation, communication, and implementation. When you formalize class diagrams, you\u2019re not just drawing boxes and lines. You’re creating a shared reference for developers, testers, and architects.<\/p>\n

Think of it like this: CRC cards help you discover<\/strong> the design. UML helps you communicate<\/strong> it.<\/p>\n

Design Transition Steps: Your Practical Roadmap<\/h2>\n

Let\u2019s walk through a proven workflow\u2014tested in real-world projects and team workshops. These steps are not rigid. They reflect the evolution of thought, not a checklist to check off.<\/p>\n

    \n
  1. Review and Consolidate CRC Cards<\/strong> \u2013 Gather all cards. Look for duplicates, vague roles, and unclear responsibilities. Merge similar concepts. This step prevents fragmentation in the final model.<\/li>\n
  2. Extract Core Concepts into Classes<\/strong> \u2013 Each card becomes a class. Name it using noun phrases. Keep names consistent with your domain language. Avoid abbreviations unless widely understood.<\/li>\n
  3. Map Responsibilities to Methods and Attributes<\/strong> \u2013 Every responsibility on a card translates into either a method (behavior) or attribute (data). Be explicit. If a responsibility says \u201ccalculate total,\u201d it\u2019s a method. If it says \u201ctrack amount,\u201d it\u2019s an attribute.<\/li>\n
  4. Convert Collaborations into Associations<\/strong> \u2013 Identify who a class works with. These are associations. Use arrows to show direction, and label them with role names. Consider multiplicity early\u2014e.g., \u201ca Library has many Books.\u201d<\/li>\n
  5. Define Visibility and Encapsulation<\/strong> \u2013 Use +<\/code> (public), -<\/code> (private), #<\/code> (protected) to clarify access. Decide what belongs inside the class and what should be hidden.<\/li>\n
  6. Validate for Completeness and Consistency<\/strong> \u2013 Check that every method has a clear purpose, every attribute is used, and no class is isolated or redundant.<\/li>\n<\/ol>\n

    Common Pitfalls in CRC to UML Workflow<\/h3>\n

    Even experienced teams stumble. Here are the most frequent missteps\u2014and how to fix them:<\/p>\n

      \n
    • Confusing responsibilities with methods<\/strong> \u2013 Not every action is a method. Some are constraints or rules. Ask: \u201cIs this a behavior, or is it a rule governing behavior?\u201d<\/li>\n
    • Overloading associations<\/strong> \u2013 Don\u2019t draw every possible link. Focus on essential, meaningful relationships. You can add more later if needed.<\/li>\n
    • Ignoring multiplicity<\/strong> \u2013 \u201cMany\u201d doesn\u2019t mean \u201cunlimited.\u201d Be specific: 0..1, 1..*, etc. This impacts how code is structured, especially in ORM or persistence layers.<\/li>\n
    • Missing abstraction<\/strong> \u2013 If several classes share behavior, ask: \u201cCan this be extracted into a parent class or interface?\u201d You\u2019ll save code and improve reusability.<\/li>\n<\/ul>\n

      Formalizing Class Diagrams: A Side-by-Side Comparison<\/h2>\n\n\n\n\n\n\n\n
      CRC Element<\/th>\nUML Equivalent<\/th>\nKey Considerations<\/th>\n<\/tr>\n
      Class name (e.g., \u201cBook\u201d)<\/td>\nClass box with name<\/td>\nUse PascalCase. Avoid verbs. Use domain terms.<\/td>\n<\/tr>\n
      Responsibility: \u201ctrack due date\u201d<\/td>\nAttribute: dueDate: Date<\/code><\/td>\nEnsure data type matches expected format.<\/td>\n<\/tr>\n
      Responsibility: \u201cissue loan\u201d<\/td>\nMethod: issueLoan(): boolean<\/code><\/td>\nReturn type matters. Use boolean<\/code> for success\/failure.<\/td>\n<\/tr>\n
      Collaboration: \u201cBorrower\u201d<\/td>\nAssociation: Borrower<\/code> \u2014 Book<\/code><\/td>\nLabel with role. Add multiplicity: 1..* for Borrower to Book.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Refining the Model Through Feedback<\/h2>\n

      I\u2019ve seen teams create perfect-looking class diagrams\u2014only to realize they don\u2019t match how the system behaves. That\u2019s why iteration is not optional. You must loop back.<\/p>\n

      After drafting your UML, run a simple validation check:<\/p>\n

        \n
      • Can the system\u2019s behavior be modeled from the class diagram alone?<\/li>\n
      • Are all responsibilities accounted for in methods or attributes?<\/li>\n
      • Do associations reflect real business rules, or are they just assumptions?<\/li>\n
      • Are there any orphaned classes or redundant relationships?<\/li>\n<\/ul>\n

        If the answer to any of these is \u201cno,\u201d go back to the CRC cards. Re-clarify. Re-interpret. Don\u2019t force the model to fit the diagram. Let the diagram grow from the idea.<\/p>\n

        Using Visual Paradigm to Streamline the CRC-to-UML Workflow<\/h2>\n

        Tools like Visual Paradigm make this transition smoother\u2014but they don\u2019t replace thought. You still must understand the model.<\/p>\n

        Start by creating a new class diagram. Then, use the CRC card features to import or map your cards. Visual Paradigm allows you to:<\/p>\n

          \n
        • Import CRC elements directly into a class diagram<\/li>\n
        • Auto-generate methods and attributes from responsibilities<\/li>\n
        • Apply UML standards (naming, visibility, multiplicity) with one click<\/li>\n
        • Generate code skeletons automatically<\/li>\n<\/ul>\n

          But remember: automation doesn\u2019t eliminate the need for judgment. It reduces tedium\u2014but you must still validate every step.<\/p>\n

          Frequently Asked Questions<\/h2>\n

          How do I know when my CRC sketch is ready for formalizing class diagrams?<\/h3>\n

          When your team agrees on all class names, responsibilities, and collaborations\u2014and you can explain the system\u2019s behavior without hesitation. If you\u2019re still arguing over a single role or responsibility, it\u2019s not ready. Go back to the CRC cards.<\/p>\n

          Can one CRC card become multiple classes in UML?<\/h3>\n

          Yes. If a CRC card describes a role that involves multiple responsibilities or spans several domain concepts, it may split. For example, a card named \u201cCustomer\u201d might include responsibilities like \u201cplace order\u201d and \u201ctrack delivery,\u201d which could become separate classes: Customer<\/code>, Order<\/code>, Delivery<\/code>.<\/p>\n

          What\u2019s the best way to handle inheritance during the CRC-to-UML transition?<\/h3>\n

          Look for shared behavior. If two classes both \u201ccalculate fees\u201d or \u201cvalidate eligibility,\u201d ask: \u201cIs there a common base?\u201d If yes, extract it into an abstract class or interface. Don\u2019t force inheritance\u2014let it emerge from shared intent.<\/p>\n

          Should I use attributes or methods for state tracking?<\/h3>\n

          Use attributes for data. Use methods for actions that affect or retrieve that data. \u201cTrack due date\u201d is a responsibility best represented as an attribute. \u201cCheck if overdue\u201d is a method.<\/p>\n

          How do I ensure consistency across multiple team members’ CRC cards?<\/h3>\n

          Hold a CRC alignment session. Use a shared whiteboard or digital tool like Visual Paradigm. Review each card together. Define naming conventions and role definitions. This isn\u2019t just documentation\u2014it\u2019s team alignment.<\/p>\n

          What if my CRC card has conflicting responsibilities?<\/h3>\n

          That\u2019s a red flag. Conflicting responsibilities mean the class has too many roles. Split it. For example, a \u201cPaymentProcessor\u201d that both \u201cvalidate card\u201d and \u201csend email receipt\u201d should be two classes: PaymentValidator<\/code> and EmailNotifier<\/code>. One class, one responsibility.<\/p>\n","protected":false},"excerpt":{"rendered":"

          Never rush the transition from CRC cards to UML. That\u2019s the single most important rule I\u2019ve seen teams break\u2014often at great cost. I\u2019ve watched entire development cycles unravel because a team skipped validation and jumped straight into formalizing a sketch that wasn\u2019t ready. The result? Overly complex diagrams, missing relationships, and poor cohesion\u2014just because the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":940,"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-941","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nCRC Sketch to UML: From Informal to Formal<\/title>\n<meta name=\"description\" content=\"Transform your CRC brainstorming notes into clean, consistent UML class diagrams. Learn proven steps to formalize class diagrams with confidence and clarity.\" \/>\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\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CRC Sketch to UML: From Informal to Formal\" \/>\n<meta property=\"og:description\" content=\"Transform your CRC brainstorming notes into clean, consistent UML class diagrams. Learn proven steps to formalize class diagrams with confidence and clarity.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/\",\"name\":\"CRC Sketch to UML: From Informal to Formal\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:32:34+00:00\",\"description\":\"Transform your CRC brainstorming notes into clean, consistent UML class diagrams. Learn proven steps to formalize class diagrams with confidence and clarity.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"From CRC Cards to Class Diagrams\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Refining and Validating the Design\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"From Informal Sketch to Formal Structure\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"CRC Sketch to UML: From Informal to Formal","description":"Transform your CRC brainstorming notes into clean, consistent UML class diagrams. Learn proven steps to formalize class diagrams with confidence and clarity.","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\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/","og_locale":"pl_PL","og_type":"article","og_title":"CRC Sketch to UML: From Informal to Formal","og_description":"Transform your CRC brainstorming notes into clean, consistent UML class diagrams. Learn proven steps to formalize class diagrams with confidence and clarity.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/","name":"CRC Sketch to UML: From Informal to Formal","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:32:34+00:00","description":"Transform your CRC brainstorming notes into clean, consistent UML class diagrams. Learn proven steps to formalize class diagrams with confidence and clarity.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/crc-sketch-to-uml\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"From CRC Cards to Class Diagrams","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/"},{"@type":"ListItem","position":3,"name":"Refining and Validating the Design","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/"},{"@type":"ListItem","position":4,"name":"From Informal Sketch to Formal Structure"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/941","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/941\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/940"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=941"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=941"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}