{"id":1680,"date":"2026-02-25T10:44:48","date_gmt":"2026-02-25T10:44:48","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/"},"modified":"2026-02-25T10:44:48","modified_gmt":"2026-02-25T10:44:48","slug":"uml-class-diagram-mistakes-avoid","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/","title":{"rendered":"Avoiding Beginner Mistakes in Class Diagram Design"},"content":{"rendered":"

When you start building UML class diagrams, it’s tempting to overload them with every possible detail\u2014especially when learning. But that\u2019s where most beginners stumble. The real indicator of progress isn\u2019t how many attributes you\u2019ve added, but how clearly your model communicates intent.<\/p>\n

Over time, you\u2019ll realize that clarity trumps completeness. A well-designed class diagram helps others (and your future self) understand the system\u2019s structure without confusion. This chapter focuses on the most frequent issues that undermine that clarity\u2014mistakes I\u2019ve seen repeated across dozens of beginner projects.<\/p>\n

You\u2019ll learn how to spot these problems early, avoid common pitfalls in UML class modeling, and apply beginner class diagram best practices through real examples. You\u2019ll also get a checklist to audit your own diagrams before sharing or refining them.<\/p>\n

Common Errors in Class Diagrams<\/h2>\n

Over-Modeling Attributes<\/h3>\n

One of the most frequent UML class diagram mistakes is listing too many attributes. It\u2019s tempting to include every data point you can think of\u2014especially when modeling real-world entities like users, orders, or products.<\/p>\n

But not every field needs to be a class attribute. Ask: *Is this value essential to the class\u2019s identity or behavior?* If not, consider it a temporary or derived value, better suited for a separate class or method.<\/p>\n

For example, a Customer<\/code> class should not include fields like fullAddressString<\/code> or combinedTaxAndFees<\/code>. These are better handled through methods or auxiliary classes.<\/p>\n

Use this rule: if the attribute isn\u2019t directly used in operations or state decisions, it\u2019s likely redundant.<\/p>\n

Confusing Aggregation and Composition<\/h3>\n

Many beginners mix up aggregation and composition\u2014both are types of associations but with different semantics.<\/p>\n

Aggregation<\/strong> is a “has-a” relationship where the child can exist independently. For example, a University<\/code> has Departments<\/code>, but departments can survive the university\u2019s closure.<\/p>\n

Composition<\/strong> is a “owns-a” relationship where the child cannot exist without the parent. A House<\/code> owns Doors<\/code>, but doors lose meaning if the house is demolished.<\/p>\n

Use the diamond shape correctly: hollow diamond (\u25c7) for aggregation, filled diamond (\u25c6) for composition. Never assume one over the other based on convenience\u2014your model\u2019s behavior depends on this distinction.<\/p>\n

Poor Naming Practices<\/h3>\n

Vague names like data1<\/code>, obj<\/code>, or info<\/code> destroy readability. Even worse: CustomerData<\/code> or OrderDetails<\/code> may sound meaningful but are ambiguous.<\/p>\n

Use clear, domain-focused names: Customer<\/code>, Order<\/code>, ShippingAddress<\/code>. If you must use a compound name, ensure it reflects a single responsibility.<\/p>\n

Bad: CustomerInfo<\/code> \u2192 implies a mix of data, behavior, and identity.<\/p>\n

Good: Customer<\/code> with name<\/code>, address<\/code>, and email<\/code> as attributes.<\/p>\n

Remember: a class name should reflect a single concept in your domain.<\/p>\n

Checklist: Avoiding Pitfalls in UML Class Modeling<\/h2>\n

Before finalizing any class diagram, run through this quick checklist:<\/p>\n

    \n
  • Do attributes serve a purpose?<\/strong> Remove those that don\u2019t impact behavior or state.<\/li>\n
  • Are relationships correctly typed?<\/strong> Aggregation vs. composition: is the child dependent on the parent?<\/li>\n
  • Are names domain-driven?<\/strong> Avoid generic terms like “Object” or “Data”. Use concrete nouns from your problem domain.<\/li>\n
  • Are operations visible and meaningful?<\/strong> Name methods to reflect actions, not just behavior (e.g., calculateTotal()<\/code>).<\/li>\n
  • Is multiplicity used where needed?<\/strong> 1..*<\/code> for “one or more”, 0..1<\/code> for optional\u2014don\u2019t leave them blank.<\/li>\n
  • Is the diagram scalable?<\/strong> Avoid 100+ classes on one page. Use packages or separate diagrams for clarity.<\/li>\n<\/ul>\n

    Before and After: Real-World Example<\/h2>\n

    Let\u2019s walk through a classic beginner mistake. Consider this flawed Order<\/code> class:<\/p>\n

    \nclass Order {\n  - orderId: String\n  - orderDate: Date\n  - totalPrice: Double\n  - tax: Double\n  - discount: Double\n  - shippingCost: Double\n  - customerName: String\n  - customerEmail: String\n  - customerAddress: String\n  - orderStatus: String\n  - paymentMethod: String\n  - orderItems: List<OrderItem>\n  - orderSummary: String\n  - isProcessed: Boolean\n  - isShipped: Boolean\n}\n<\/code><\/pre>\n
    This list includes redundant data (e.g., orderSummary<\/code>), misused attributes (isProcessed<\/code>), and bundled customer data.<\/p>\n
    Now, here\u2019s the improved version:<\/p>\n
    \nclass Order {\n  - orderId: String\n  - orderDate: Date\n  - status: OrderStatus\n  - items: List<OrderItem>\n  - customer: Customer\n  - total: Money\n  - payment: Payment\n}\n\nclass Customer {\n  - id: String\n  - name: String\n  - email: String\n  - address: Address\n}\n\nclass Address {\n  - street: String\n  - city: String\n  - zipCode: String\n  - country: String\n}\n<\/code><\/pre>\n
    Key changes:<\/p>\n
      \n
    • Customer data is now a separate Customer<\/code> class.<\/li>\n
    • Address is a distinct class.<\/li>\n
    • Price calculations are done via total<\/code> and Money<\/code> type.<\/li>\n
    • Order status is an enum<\/code>, not a string.<\/li>\n
    • Operations like calculateTotal()<\/code> are moved into the class.<\/li>\n<\/ul>\n
      Result: fewer line items, clearer ownership, and better scalability.<\/p>\n
      Beginner Class Diagram Best Practices<\/h2>\n
      Every successful model starts with a focus on intent. Here are the principles I\u2019ve found most effective in real projects:<\/p>\n
        \n
      1. Model the domain, not the database.<\/strong> A class should represent a concept in business logic\u2014not a table. Avoid naming classes after database columns.<\/li>\n
      2. Use composition over inheritance when possible.<\/strong> Inheritance leads to rigid, tightly coupled hierarchies. Composition promotes flexibility and reuse.<\/li>\n
      3. Limit class responsibilities.<\/strong> A class should have one primary job. If you find yourself naming a class \u201cManager\u201d or \u201cHandler,\u201d it\u2019s likely doing too much.<\/li>\n
      4. Apply visibility modifiers consistently.<\/strong> Use +<\/code> for public, -<\/code> for private, #<\/code> for protected. Never leave visibility blank.<\/li>\n
      5. Use stereotypes sparingly.<\/strong> <<entity>><\/code>, <<boundary>><\/code>, <<control>><\/code> have value in some frameworks\u2014but in beginner models, they often add noise.<\/li>\n<\/ol>\n
        These are not rules. They\u2019re guidelines shaped by years of real-world modeling. They help you avoid common errors in class diagrams and build models others can understand.<\/p>\n
        Frequently Asked Questions<\/h2>\n
        What are the most common errors in class diagrams?<\/h3>\n
        Over-attributing classes, confusing aggregation with composition, poor naming, missing multiplicity, and overusing inheritance are the top mistakes. Focus on clarity, not completeness.<\/p>\n
        How can I avoid pitfalls in UML class modeling?<\/h3>\n
        Use the checklist above. Review each class: does it have a single responsibility? Are attributes essential? Are relationships correctly marked? Ask a peer to read the diagram\u2014clarity is the best test.<\/p>\n
        Why do beginner class diagram best practices matter?<\/h3>\n
        They prevent code complexity, support maintainability, and improve communication between developers, analysts, and stakeholders. A good diagram doesn\u2019t just represent code\u2014it guides it.<\/p>\n
        Should I model every database field in a class diagram?<\/h3>\n
        No. Only model fields that represent real attributes in your domain model. Many database fields are implementation details (e.g., timestamps, audit fields) and should be handled in code, not in the class diagram.<\/p>\n
        Can I use inheritance in beginner models?<\/h3>\n
        Yes, but only when the hierarchy is natural (e.g., Vehicle<\/code> \u2192 Car<\/code>, Motorcycle<\/code>). Avoid deep chains or abstract classes unless you have a clear need.<\/p>\n
        How do I know if my class diagram is too complex?<\/h3>\n
        If you have more than 10\u201315 classes in a single diagram, consider splitting it. Use packages, generalization hierarchies, or separate diagrams by subsystems. A clean model is more valuable than a dense one.<\/p>\n","protected":false},"excerpt":{"rendered":"
        When you start building UML class diagrams, it’s tempting to overload them with every possible detail\u2014especially when learning. But that\u2019s where most beginners stumble. The real indicator of progress isn\u2019t how many attributes you\u2019ve added, but how clearly your model communicates intent. Over time, you\u2019ll realize that clarity trumps completeness. A well-designed class diagram helps […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1677,"menu_order":2,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1680","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nUML Class Diagram Mistakes to Avoid<\/title>\n<meta name=\"description\" content=\"Discover common errors in class diagrams and how to avoid pitfalls in UML class modeling with beginner-friendly best practices and real-world fixes.\" \/>\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\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"UML Class Diagram Mistakes to Avoid\" \/>\n<meta property=\"og:description\" content=\"Discover common errors in class diagrams and how to avoid pitfalls in UML class modeling with beginner-friendly best practices and real-world fixes.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/\",\"name\":\"UML Class Diagram Mistakes to Avoid\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:44:48+00:00\",\"description\":\"Discover common errors in class diagrams and how to avoid pitfalls in UML class modeling with beginner-friendly best practices and real-world fixes.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"UML Basics: Diagrams for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Mastering Class Diagrams as a Beginner\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Avoiding Beginner Mistakes in Class Diagram Design\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"UML Class Diagram Mistakes to Avoid","description":"Discover common errors in class diagrams and how to avoid pitfalls in UML class modeling with beginner-friendly best practices and real-world fixes.","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\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/","og_locale":"id_ID","og_type":"article","og_title":"UML Class Diagram Mistakes to Avoid","og_description":"Discover common errors in class diagrams and how to avoid pitfalls in UML class modeling with beginner-friendly best practices and real-world fixes.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"6 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/","name":"UML Class Diagram Mistakes to Avoid","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:44:48+00:00","description":"Discover common errors in class diagrams and how to avoid pitfalls in UML class modeling with beginner-friendly best practices and real-world fixes.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/uml-class-diagram-mistakes-avoid\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"UML Basics: Diagrams for Beginners","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Mastering Class Diagrams as a Beginner","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/uml-basics-diagrams-for-beginners\/mastering-class-diagrams-beginner\/"},{"@type":"ListItem","position":4,"name":"Avoiding Beginner Mistakes in Class Diagram Design"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1680","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1680\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1677"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1680"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1680"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}