{"id":25265,"date":"2021-07-26T13:44:04","date_gmt":"2021-07-26T11:44:04","guid":{"rendered":"https:\/\/cesam.community\/?p=25265"},"modified":"2023-01-20T11:38:25","modified_gmt":"2023-01-20T10:38:25","slug":"1-5-the-key-role-of-systems-architects-2","status":"publish","type":"post","link":"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/","title":{"rendered":"1.5 The key Role of Systems Architects"},"content":{"rendered":"<div class=\"wpb-content-wrapper\"><section class=\"vc_row wpb_row vc_row-fluid  vc_custom_1627389518372\"><div class=\"wpb_column vc_column_container vc_col-sm-10 vc_col-md-offset-1 col-xs-mobile-fullwidth\"><div class=\"vc_column-inner \"><div class=\"wpb_wrapper\"><div class=\"vc_row wpb_row vc_inner vc_row-fluid\"><div class=\"wpb_column vc_column_container vc_col-sm-9  col-xs-mobile-fullwidth\"><div class=\"vc_column-inner \"><div class=\"wpb_wrapper\"><h2 id=\"0.1\" class=\"text-medium-gray text-small margin-5px-bottom alt-font text-uppercase heading-style4  heading-1\"  style=\"font-weight: 600; color: #000000;\">1.5 The key Role of Systems Architects<\/h2><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\">Systems architecting would of course not exist without the right key people, i.e. systems architects, to support the architectural process! The systems architect shall indeed fundamentally be the core responsible of the systems integration issues. He\/she shall thus ensure that the interfaces of the subsystems of the target system under design are reasonably robust for the purpose of the system development project<sup class=\"modern-footnotes-footnote \" data-mfn=\"1\" data-mfn-post-scope=\"00000000000019b60000000000000000_25265\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25265-1\">1<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25265-1\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"1\">And possibly beyond, but this is another issue, namely that of the reusability of reference systems architectures and of product lines design, we will not discuss here.<\/span>, or in other terms that they will not be questioned (or as little as possible) by the technical managers in charge of the different subsystems.<\/p>\n<p style=\"text-align: justify;\">To achieve such objectives, it is necessary to play on a different dimension than the purely technical one. A key problem within system design is indeed that it is usually not enough to have the \u00ab\u00a0best\u00a0\u00bb possible system architecture for that it is automatically picked up and used by everybody. The global optimum, typically with respect to quality, cost, delay and performance criteria, for an integrated system is indeed never<sup class=\"modern-footnotes-footnote \" data-mfn=\"2\" data-mfn-post-scope=\"00000000000019b60000000000000000_25265\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25265-2\">2<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25265-2\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"2\">This is true as soon as the system has not a linear behavior with respect to its entries, which is never the case for complex systems. This result can be traced back to Richard Bellman in the 50s (see [13]). <\/span> the union of the local optima of each of subsystems that compose it: the consequence is that each subsystem shall necessary individually be sub-optimal with respect to these criteria, if one wants to reach global optimality at system level.<\/p>\n<p style=\"text-align: justify;\">This fact is unfortunately not easy to accept for the subsystems responsible who will not design their sub-systems with a global vision, as can have the architect of the whole system<sup class=\"modern-footnotes-footnote \" data-mfn=\"3\" data-mfn-post-scope=\"00000000000019b60000000000000000_25265\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25265-3\">3<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25265-3\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"3\">The difficulty of understanding the importance of system architecting comes from this situation. Engineers usually deal with technically homogeneous subsystems of a given system (i.e. the \u201cboxes\u201d of Figure 16) which are clearly visible to all. On the other side, the systems architect takes care of the system interfaces (that is to say the \u00ab\u00a0arrows\u00a0\u00bb in Figure 16) that nobody sees because they are strictly speaking not material. The architecture work is thus done somewhere in the invisible. It is thus difficult to detect for the uninitiated, while fundamental since it fixes the framework in which to do engineering (a bad architectural framework can typically only lead to a \u00ab\u00a0bad\u00a0\u00bb system). <\/span>. To solve this \u00ab\u00a0human\u00a0\u00bb problem, which is intrinsic to the design of integrated systems, one must put stakeholder alignment mechanisms at the heart of any system architecting process. These alignment activities shall in particular ensure that the structuring systems architectural choices will always be shared by their stakeholders. Systemically speaking, such mechanisms will indeed guarantee that the technical interfaces of the product system will always be discussed and accepted at the \u00ab\u00a0human\u00a0\u00bb interfaces to which they are allocated within the project system (see Figure 16).<\/p>\n<\/div>[vc_single_image image=\u00a0\u00bb25320&Prime; img_size=\u00a0\u00bb400&#215;224&Prime; alignment=\u00a0\u00bbcenter\u00a0\u00bb]<div class=\"last-paragraph-no-margin\"><p style=\"text-align: center;\"><strong><span style=\"font-size: 10pt;\">Figure 16 \u2013 The key role of the systems architect\u00a0<\/span><\/strong><\/p>\n<\/div><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\">This quick analysis therefore shows that a systems architect must always be fundamentally capable of converging actors on the architectural choices which he\/she is responsible. This convergence work \u2013 which is a substantial and essential part of the systems architect job<sup class=\"modern-footnotes-footnote \" data-mfn=\"4\" data-mfn-post-scope=\"00000000000019b60000000000000000_25265\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25265-4\">4<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25265-4\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"4\">And that makes a good \u201csystems\u201d architect a kind of 6 feet sheep\u2026<\/span> \u2013 is however not simple at all. It indeed requires mastering, among purely technical competency, a set of completely different soft skills that could be qualified of \u201chuman\u201d architecting and engineering since they are highly involving the \u201chuman\u201d dimension of the project system. At that level, the systems architect shall for instance typically have the following key capability<sup class=\"modern-footnotes-footnote \" data-mfn=\"5\" data-mfn-post-scope=\"00000000000019b60000000000000000_25265\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25265-5\">5<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25265-5\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"5\">Which are typically pre-requisites to achieve the success of any actors\u2019 convergence in a systems architecting context.<\/span>.<\/p>\n<p style=\"text-align: justify;\">\u2022 <em>Identifying all stakeholders<\/em> of a given system architecture: it looks as an apparently simple activity, but it is often terribly difficult to achieve in practice since it requires confronting the complex and changing reality of engineering organizations. Ensuring the completeness and validity of a particular organizational analysis is indeed never easy. It is notably more than classical to forget key players within a given engineering scope and to identify erroneously others<sup class=\"modern-footnotes-footnote \" data-mfn=\"6\" data-mfn-post-scope=\"00000000000019b60000000000000000_25265\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25265-6\">6<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25265-6\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"6\">This can be for instance achieved by badly analysing the role of somebody in a given organization.<\/span>. Moreover, organizations are often changing rapidly. Making a stakeholders mapping should thus always be constantly update if one wants to keep pace with reality.<\/p>\n<p style=\"text-align: justify;\">\u2022 <em>Aligning these stakeholders<\/em> on a same architectural solution: this is a real \u201cfacilitation\u201d skill in the best sense of the term since such a work requires a real difficult technical and human know-how. A systems architect will only succeed to achieve stakeholders\u2019 convergence on given architectural choices if he plays consistently on both the technical side, that he\/she should of course perfectly control to be credible, and the human level, in order to secure strong consensus that will withstand the test of time.<\/p>\n<\/div><a  href=\"https:\/\/cesam.community\/2021\/07\/24\/1-6-how-to-analyze-a-systems-architect-profile\/\" target=\"_self\" class=\"btn pofo-button-1 bg-position-center-center  wow none button-style9  btn-link text-extra-dark-gray text-deep-pink-hover  btn-medium   vc_custom_1668509122628\" >NEXT PAGE<i class=\"ti-arrow-right   margin-5px-left no-margin-right\" aria-hidden=\"true\"><\/i><\/a><\/div><\/div><\/div><div class=\"wpb_column vc_column_container vc_col-sm-3  col-xs-mobile-fullwidth\"><div class=\"vc_column-inner \"><div class=\"wpb_wrapper\"><h2 class=\"text-medium-gray text-small margin-5px-bottom alt-font text-uppercase heading-style4  heading-2\"  style=\"font-size: 10px; font-weight: 600; color: #000000;\" data-fontsize=\"10px\">TABLE OF CONTENTS<\/h2>[vc_wp_custommenu nav_menu=\u00a0\u00bb132&Prime;]<h2 class=\"text-medium-gray text-small margin-5px-bottom alt-font text-uppercase heading-style4  heading-3\"  style=\"font-size: 10px; font-weight: 600; color: #000000;\" data-fontsize=\"10px\">References<\/h2><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\"><span style=\"font-size: 8pt;\">[13] Bellman R.E., Dynamic Programming, Princeton University Press, 1957<\/span><\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Systems architecting would of course not exist without the right key people, i.e. systems architects, to support the architectural process! The systems architect shall indeed fundamentally be the core responsible of the systems integration issues. He\/she shall thus ensure that the interfaces of the subsystems of the target system under design are reasonably robust for the purpose of the system development project, or in other terms that they will not be questioned (or as little as possible) by the technical managers in charge of the different subsystems&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[158],"tags":[157],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.2 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>1.5 The key Role of Systems Architects - Cesam Community<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"1.5 The key Role of Systems Architects - Cesam Community\" \/>\n<meta property=\"og:description\" content=\"Systems architecting would of course not exist without the right key people, i.e. systems architects, to support the architectural process! The systems architect shall indeed fundamentally be the core responsible of the systems integration issues. He\/she shall thus ensure that the interfaces of the subsystems of the target system under design are reasonably robust for the purpose of the system development project, or in other terms that they will not be questioned (or as little as possible) by the technical managers in charge of the different subsystems...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Cesam Community\" \/>\n<meta property=\"article:published_time\" content=\"2021-07-26T11:44:04+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-01-20T10:38:25+00:00\" \/>\n<meta name=\"author\" content=\"admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@cesamcommunity\" \/>\n<meta name=\"twitter:site\" content=\"@cesamcommunity\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\/\/cesam.community\/fr\/#\/schema\/person\/1698618e5539e0eadd3578d29281a505\"},\"headline\":\"1.5 The key Role of Systems Architects\",\"datePublished\":\"2021-07-26T11:44:04+00:00\",\"dateModified\":\"2023-01-20T10:38:25+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/\"},\"wordCount\":1085,\"publisher\":{\"@id\":\"https:\/\/cesam.community\/fr\/#organization\"},\"keywords\":[\"Article\"],\"articleSection\":[\"CESAM Systems Architecting Method\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/\",\"url\":\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/\",\"name\":\"1.5 The key Role of Systems Architects - Cesam Community\",\"isPartOf\":{\"@id\":\"https:\/\/cesam.community\/fr\/#website\"},\"datePublished\":\"2021-07-26T11:44:04+00:00\",\"dateModified\":\"2023-01-20T10:38:25+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/cesam.community\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CESAM Systems Architecting Method\",\"item\":\"https:\/\/cesam.community\/fr\/category\/cesam-systems-architecting-method-en\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"1.5 The key Role of Systems Architects\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/cesam.community\/fr\/#website\",\"url\":\"https:\/\/cesam.community\/fr\/\",\"name\":\"Cesam Community\",\"description\":\"La communaut\u00e9 CESAM\",\"publisher\":{\"@id\":\"https:\/\/cesam.community\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/cesam.community\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/cesam.community\/fr\/#organization\",\"name\":\"CESAM Community\",\"url\":\"https:\/\/cesam.community\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/cesam.community\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/cesam.community\/wp-content\/uploads\/2021\/04\/cesam_community_logo_v4.png\",\"contentUrl\":\"https:\/\/cesam.community\/wp-content\/uploads\/2021\/04\/cesam_community_logo_v4.png\",\"width\":7310,\"height\":1018,\"caption\":\"CESAM Community\"},\"image\":{\"@id\":\"https:\/\/cesam.community\/fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/x.com\/cesamcommunity\",\"https:\/\/www.linkedin.com\/company\/community-cesam\/about\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/cesam.community\/fr\/#\/schema\/person\/1698618e5539e0eadd3578d29281a505\",\"name\":\"admin\",\"sameAs\":[\"https:\/\/cesam.community\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"1.5 The key Role of Systems Architects - Cesam Community","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:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/","og_locale":"fr_FR","og_type":"article","og_title":"1.5 The key Role of Systems Architects - Cesam Community","og_description":"Systems architecting would of course not exist without the right key people, i.e. systems architects, to support the architectural process! The systems architect shall indeed fundamentally be the core responsible of the systems integration issues. He\/she shall thus ensure that the interfaces of the subsystems of the target system under design are reasonably robust for the purpose of the system development project, or in other terms that they will not be questioned (or as little as possible) by the technical managers in charge of the different subsystems...","og_url":"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/","og_site_name":"Cesam Community","article_published_time":"2021-07-26T11:44:04+00:00","article_modified_time":"2023-01-20T10:38:25+00:00","author":"admin","twitter_card":"summary_large_image","twitter_creator":"@cesamcommunity","twitter_site":"@cesamcommunity","twitter_misc":{"\u00c9crit par":"admin","Dur\u00e9e de lecture estim\u00e9e":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/#article","isPartOf":{"@id":"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/"},"author":{"name":"admin","@id":"https:\/\/cesam.community\/fr\/#\/schema\/person\/1698618e5539e0eadd3578d29281a505"},"headline":"1.5 The key Role of Systems Architects","datePublished":"2021-07-26T11:44:04+00:00","dateModified":"2023-01-20T10:38:25+00:00","mainEntityOfPage":{"@id":"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/"},"wordCount":1085,"publisher":{"@id":"https:\/\/cesam.community\/fr\/#organization"},"keywords":["Article"],"articleSection":["CESAM Systems Architecting Method"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/","url":"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/","name":"1.5 The key Role of Systems Architects - Cesam Community","isPartOf":{"@id":"https:\/\/cesam.community\/fr\/#website"},"datePublished":"2021-07-26T11:44:04+00:00","dateModified":"2023-01-20T10:38:25+00:00","breadcrumb":{"@id":"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cesam.community\/fr\/2021\/07\/26\/1-5-the-key-role-of-systems-architects-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/cesam.community\/fr\/"},{"@type":"ListItem","position":2,"name":"CESAM Systems Architecting Method","item":"https:\/\/cesam.community\/fr\/category\/cesam-systems-architecting-method-en\/"},{"@type":"ListItem","position":3,"name":"1.5 The key Role of Systems Architects"}]},{"@type":"WebSite","@id":"https:\/\/cesam.community\/fr\/#website","url":"https:\/\/cesam.community\/fr\/","name":"Cesam Community","description":"La communaut\u00e9 CESAM","publisher":{"@id":"https:\/\/cesam.community\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cesam.community\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/cesam.community\/fr\/#organization","name":"CESAM Community","url":"https:\/\/cesam.community\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/cesam.community\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/cesam.community\/wp-content\/uploads\/2021\/04\/cesam_community_logo_v4.png","contentUrl":"https:\/\/cesam.community\/wp-content\/uploads\/2021\/04\/cesam_community_logo_v4.png","width":7310,"height":1018,"caption":"CESAM Community"},"image":{"@id":"https:\/\/cesam.community\/fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/cesamcommunity","https:\/\/www.linkedin.com\/company\/community-cesam\/about\/"]},{"@type":"Person","@id":"https:\/\/cesam.community\/fr\/#\/schema\/person\/1698618e5539e0eadd3578d29281a505","name":"admin","sameAs":["https:\/\/cesam.community"]}]}},"_links":{"self":[{"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/posts\/25265"}],"collection":[{"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/comments?post=25265"}],"version-history":[{"count":7,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/posts\/25265\/revisions"}],"predecessor-version":[{"id":33365,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/posts\/25265\/revisions\/33365"}],"wp:attachment":[{"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/media?parent=25265"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/categories?post=25265"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/tags?post=25265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}