{"id":49467,"date":"2015-04-15T10:37:32","date_gmt":"2015-04-15T09:37:32","guid":{"rendered":"http:\/\/www.corporate-eye.com\/main\/?p=49467"},"modified":"2015-04-15T10:37:32","modified_gmt":"2015-04-15T09:37:32","slug":"compliance-plain-language","status":"publish","type":"post","link":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/","title":{"rendered":"Presenting Compliance Requirements in Plain Language"},"content":{"rendered":"<p><em>Mike Miranda from the Clear Law Institute offered to write a post for us about communicating compliance requirements in plain language. I spend a lot of time reviewing corporate websites, and sometimes the compliance sections are the hardest (and slowest), because of the complexity of the language, and the density of the information. Plain language matters!<\/p>\n<p>Over to you, Mike&#8230;<\/em> <\/p>\n<p><img decoding=\"async\" data-src=\"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg\" alt=\"plain-language\" width=\"580\" height=\"386\" class=\"aligncenter size-full wp-image-49470 lazyload\" data-srcset=\"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg 580w, https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language-150x99.jpg 150w, https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language-300x199.jpg 300w, https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language-100x66.jpg 100w\" data-sizes=\"(max-width: 580px) 100vw, 580px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 580px; --smush-placeholder-aspect-ratio: 580\/386;\" \/><br \/>\nWhen we talk to each other we generally speak in plain language. Have you ever met someone who purposely uses terminology that unnecessarily complicates the point? If you have, you\u2019ll quickly understand the importance of using plain language in conversation. <\/p>\n<p>The same can be said for those in the legal field. Legal jargon is usually meticulously written and confusing to follow, and for good reason: when drafting a contract this practice has purpose, especially for the contractor.<\/p>\n<p>But when dealing with compliance requirements the goal is to make these requirements known and simple to follow. In order for that to happen the point should be expressed clearly and plainly as to avoid any confusion and\/or misconception of the intentions stated. <\/p>\n<p>As a matter of fact, <a href=\"http:\/\/www.plainlanguage.gov\/resources\/\">studies<\/a> show that attorneys took twice as long to translate \u201clegalese\u201d as it took brain surgeons to comprehend medical jargon. <\/p>\n<p>So it\u2019s safe to say simplifying the text will save time, which saves money and improves compliance, which will translate to fewer complaints and less to resolve.<\/p>\n<p>How do we define \u201cplain language\u201d? <\/p>\n<p>It is communication that your audience will understand as soon as they read it or hear it. It will enable them to find what they need, understand what they find, and use what they found to meet their needs. <\/p>\n<p>This streamlines the process of conveying information to your audience. <\/p>\n<p>In a corporate setting, this would allow your company to reach its goals more quickly by eliminating any slack caused by the uninformed. The more someone understands what\u2019s required of them the more efficient they will be. <\/p>\n<p>When you\u2019re dealing with a large company, this difference can be worth millions. For example: every few years the VBA (Veteran Benefit Administration) reaches out to all veterans and asks them to update their beneficiaries. If a veteran dies without doing so the VBA has to identify an eligible beneficiary through extensive research. Each time they do this it costs them thousands of dollars in staff time.  So they decided to rewrite the letter they send to veterans in plain language. <\/p>\n<p>The original outreach yielded a 43% response rate. But the response of the plain language outreach went up to 65% and the VBA saved $5 million in staff time over the course of each mailing period.<\/p>\n<p>These are some things to keep in mind when preparing a compliance presentation in plain language:<\/p>\n<ul>\n<li>Identify and write exclusively for your audience <\/li>\n<li>If you are speaking publicly, make sure to speak clearly and audibly <\/li>\n<li>If you\u2019re writing, keep paragraphs and sentences short and to the point. There is no need for fluff. Also, there is no need for complication of the subject via huge words <\/li>\n<li>Limit jargon, legalese, and acronyms to a minimum. If there is a way to explain yourself in simple terms, do so <\/li>\n<li>Put yourself in the reader\u2019s shoes. Who is my audience? What do they already know about the subject? What kinds of questions will they likely have? Be prepared and you\u2019ll have a much easier time<\/li>\n<li>You should use common words. For example, instead of \u201cprior to\u201d say \u201cbefore\u201d and opposed to \u201ccommence\u201d say \u201cbegin\u201d or \u201cstart\u201d. Keep it simple and your audience will soak up your message. This will create a common understanding, which will greatly increase the adherence to your compliance requirements.<\/li>\n<\/ul>\n<p>Thomas Jefferson once said \u201cThe most valuable of all talents is never using two words where one will do.\u201d Remember this saying, it will serve you well!<\/p>\n<p><em>Thanks Mike!<\/p>\n<p>Mike Miranda is a writer and PR person for <a href=\"http:\/\/clearlawinstitute.com\/compliance-training\/workplace-harassment-prevention\/\" rel=\"nofollow\">Clear Law Institute<\/a>.<\/em> <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Mike Miranda from the Clear Law Institute offered to write a post for us about communicating compliance requirements in plain language. I spend a lot of time reviewing corporate websites, and sometimes the compliance sections are the hardest (and slowest), because of the complexity of the language, and the density of the information. Plain language [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":49470,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[9,29,6443],"tags":[],"class_list":{"0":"post-49467","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-best-practices","8":"category-corporate-governance","9":"category-guest","10":"entry"},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Presenting Compliance Requirements in Plain Language - Corporate Eye<\/title>\n<meta name=\"description\" content=\"Communicating compliance requirements in plain language. Not easy, but important.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Presenting Compliance Requirements in Plain Language - Corporate Eye\" \/>\n<meta property=\"og:description\" content=\"Communicating compliance requirements in plain language. Not easy, but important.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/\" \/>\n<meta property=\"og:site_name\" content=\"Corporate Eye\" \/>\n<meta property=\"article:published_time\" content=\"2015-04-15T09:37:32+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"580\" \/>\n\t<meta property=\"og:image:height\" content=\"386\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Lucy Nixon\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@lucynixon\" \/>\n<meta name=\"twitter:site\" content=\"@lucynixon\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Lucy Nixon\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/\"},\"author\":{\"name\":\"Lucy Nixon\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#\/schema\/person\/d273bf7421dc8f5fec96785876b760e2\"},\"headline\":\"Presenting Compliance Requirements in Plain Language\",\"datePublished\":\"2015-04-15T09:37:32+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/\"},\"wordCount\":663,\"commentCount\":1,\"publisher\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg\",\"articleSection\":[\"Best Practices\",\"Corporate governance\",\"Guest\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/\",\"url\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/\",\"name\":\"Presenting Compliance Requirements in Plain Language - Corporate Eye\",\"isPartOf\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg\",\"datePublished\":\"2015-04-15T09:37:32+00:00\",\"description\":\"Communicating compliance requirements in plain language. Not easy, but important.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#primaryimage\",\"url\":\"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg\",\"contentUrl\":\"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg\",\"width\":580,\"height\":386},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.corporate-eye.com\/main\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Presenting Compliance Requirements in Plain Language\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#website\",\"url\":\"https:\/\/www.corporate-eye.com\/main\/\",\"name\":\"Corporate Eye\",\"description\":\"...compare, compete, excel\",\"publisher\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.corporate-eye.com\/main\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#organization\",\"name\":\"Corporate Eye\",\"url\":\"https:\/\/www.corporate-eye.com\/main\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2019\/11\/corporate-eye-logo.png\",\"contentUrl\":\"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2019\/11\/corporate-eye-logo.png\",\"width\":283,\"height\":42,\"caption\":\"Corporate Eye\"},\"image\":{\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/x.com\/lucynixon\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#\/schema\/person\/d273bf7421dc8f5fec96785876b760e2\",\"name\":\"Lucy Nixon\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.corporate-eye.com\/main\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/538dc739f95aa5a2fd75d054808b18b2afa37a9282a7a8f87001a77dc128d759?s=96&d=identicon&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/538dc739f95aa5a2fd75d054808b18b2afa37a9282a7a8f87001a77dc128d759?s=96&d=identicon&r=g\",\"caption\":\"Lucy Nixon\"},\"description\":\"Lucy is Editor at Corporate Eye\",\"sameAs\":[\"http:\/\/www.corporate-eye.com\",\"https:\/\/x.com\/lucynixon\"],\"url\":\"https:\/\/www.corporate-eye.com\/main\/author\/lucy\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Presenting Compliance Requirements in Plain Language - Corporate Eye","description":"Communicating compliance requirements in plain language. Not easy, but important.","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:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/","og_locale":"en_US","og_type":"article","og_title":"Presenting Compliance Requirements in Plain Language - Corporate Eye","og_description":"Communicating compliance requirements in plain language. Not easy, but important.","og_url":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/","og_site_name":"Corporate Eye","article_published_time":"2015-04-15T09:37:32+00:00","og_image":[{"width":580,"height":386,"url":"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg","type":"image\/jpeg"}],"author":"Lucy Nixon","twitter_card":"summary_large_image","twitter_creator":"@lucynixon","twitter_site":"@lucynixon","twitter_misc":{"Written by":"Lucy Nixon","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#article","isPartOf":{"@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/"},"author":{"name":"Lucy Nixon","@id":"https:\/\/www.corporate-eye.com\/main\/#\/schema\/person\/d273bf7421dc8f5fec96785876b760e2"},"headline":"Presenting Compliance Requirements in Plain Language","datePublished":"2015-04-15T09:37:32+00:00","mainEntityOfPage":{"@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/"},"wordCount":663,"commentCount":1,"publisher":{"@id":"https:\/\/www.corporate-eye.com\/main\/#organization"},"image":{"@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#primaryimage"},"thumbnailUrl":"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg","articleSection":["Best Practices","Corporate governance","Guest"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/","url":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/","name":"Presenting Compliance Requirements in Plain Language - Corporate Eye","isPartOf":{"@id":"https:\/\/www.corporate-eye.com\/main\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#primaryimage"},"image":{"@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#primaryimage"},"thumbnailUrl":"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg","datePublished":"2015-04-15T09:37:32+00:00","description":"Communicating compliance requirements in plain language. Not easy, but important.","breadcrumb":{"@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#primaryimage","url":"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg","contentUrl":"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2015\/04\/plain-language.jpg","width":580,"height":386},{"@type":"BreadcrumbList","@id":"https:\/\/www.corporate-eye.com\/main\/compliance-plain-language\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.corporate-eye.com\/main\/"},{"@type":"ListItem","position":2,"name":"Presenting Compliance Requirements in Plain Language"}]},{"@type":"WebSite","@id":"https:\/\/www.corporate-eye.com\/main\/#website","url":"https:\/\/www.corporate-eye.com\/main\/","name":"Corporate Eye","description":"...compare, compete, excel","publisher":{"@id":"https:\/\/www.corporate-eye.com\/main\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.corporate-eye.com\/main\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.corporate-eye.com\/main\/#organization","name":"Corporate Eye","url":"https:\/\/www.corporate-eye.com\/main\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.corporate-eye.com\/main\/#\/schema\/logo\/image\/","url":"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2019\/11\/corporate-eye-logo.png","contentUrl":"https:\/\/www.corporate-eye.com\/main\/wp-content\/uploads\/2019\/11\/corporate-eye-logo.png","width":283,"height":42,"caption":"Corporate Eye"},"image":{"@id":"https:\/\/www.corporate-eye.com\/main\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/lucynixon"]},{"@type":"Person","@id":"https:\/\/www.corporate-eye.com\/main\/#\/schema\/person\/d273bf7421dc8f5fec96785876b760e2","name":"Lucy Nixon","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.corporate-eye.com\/main\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/538dc739f95aa5a2fd75d054808b18b2afa37a9282a7a8f87001a77dc128d759?s=96&d=identicon&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/538dc739f95aa5a2fd75d054808b18b2afa37a9282a7a8f87001a77dc128d759?s=96&d=identicon&r=g","caption":"Lucy Nixon"},"description":"Lucy is Editor at Corporate Eye","sameAs":["http:\/\/www.corporate-eye.com","https:\/\/x.com\/lucynixon"],"url":"https:\/\/www.corporate-eye.com\/main\/author\/lucy\/"}]}},"modified_by":"Lucy Nixon","_links":{"self":[{"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/posts\/49467","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/comments?post=49467"}],"version-history":[{"count":5,"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/posts\/49467\/revisions"}],"predecessor-version":[{"id":49759,"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/posts\/49467\/revisions\/49759"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/media\/49470"}],"wp:attachment":[{"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/media?parent=49467"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/categories?post=49467"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.corporate-eye.com\/main\/wp-json\/wp\/v2\/tags?post=49467"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}