{"id":15301,"date":"2014-04-08T14:21:58","date_gmt":"2014-04-08T14:21:58","guid":{"rendered":"https:\/\/fortran.uk\/?p=15301"},"modified":"2017-04-28T10:10:48","modified_gmt":"2017-04-28T09:10:48","slug":"plusfort-quality-assurance","status":"publish","type":"page","link":"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/","title":{"rendered":"plusFORT Quality Assurance"},"content":{"rendered":"<p>Many people know <em>plus<\/em><strong>FORT<\/strong> mainly for <a href=\"https:\/\/fortran.uk\/spag-fortran-code-restructuring\/\">SPAG<\/a>, the restructuring tool which unscrambles spaghetti code. However, the <em>plus<\/em><strong>FORT<\/strong> quality assurance facilities are arguably of even greater importance to most users.<\/p>\n<p><em>plus<\/em><strong>FORT<\/strong> Version 7 is unique among QA tools in offering three distinct and complementary approaches to the problem of software quality assurance. Working together these three approaches have far more impact than any one could by itself.<\/p>\n<hr \/>\n<h2><a name=\"gxchk\"><\/a>QA Method 1 &#8211; Global Static Analysis<\/h2>\n<p>GXCHK is the <em>plus<\/em><strong>FORT<\/strong> global static analysis\u00a0tool. GXCHK views data usage from a global perspective, and detects errors and anomalies that compilers and other tools miss. Examples are:<\/p>\n<ul>\n<li>Subprogram argument mismatch or misuse (e.g. constant actual argument is illegally modified by subprogram).<\/li>\n<li>COMMON and\/or MODULE variables assigned a value but never used, or used but never assigned a value.<\/li>\n<li>Globally unused COMMON or MODULE variables, COMMON blocks, PARAMETERs, &amp; INCLUDE files.<\/li>\n<li>Inconsistent COMMON block definitions.<\/li>\n<li>COMMON or MODULE variable name appears in other contexts (e.g. as a local variable, or in a different COMMON).<\/li>\n<\/ul>\n<p>Version 7 of <em>plus<\/em><strong>FORT<\/strong> introduces greatly improved HTML static analysis reports, with comprehensive cross-reference links. These reports are designed to act as a constant companion to coders, providing instant answers to questions like \u201cwhere is this variable set\u201d and \u201cwhere is this routine called from\u201d. A new \u201cmodularization report\u201d shows how a traditional Fortran 77 program can be reorganised using modules and\/or internal subprograms to take full advantage of the modular programming features of Fortran 95 and Fortran 2003.<\/p>\n<p><span style=\"color: #ff0000;\"><a style=\"color: #ff0000; text-decoration: underline;\" href=\"https:\/\/fortran.uk\/AERMOD\/gxchk.htm\"><strong>Try the new GXCHK report interface by clicking here<\/strong>.<\/a><\/span> This report shows an analysis of AERMOD.f90, one of the Polyhedron benchmarks. This file has 50K lines of Fortran 90, but much larger programs (many millions of lines) can be analysed and viewed in this way. Note that most browsers allow you to right-click on links to save particular reports in a separate tab.<em>plus<\/em><strong>FORT<\/strong> also computes complexity metrics for each subprogram. These figures may help to indicate where rationalisation work should be concentrated.<\/p>\n<p>An unusual feature of GXCHK is its ability to analyse local and global data together. For example, if a local variable in subprogram A has the same name as a COMMON variable in subprogram B, it could be that the programmer has omitted the relevant COMMON statement from subprogram A. GXCHK, unlike other static analysers spots this problem. GXCHK also produces a call tree, and concise but comprehensive charts showing where and how each symbol is used. Handy aggregated reports are produced for COMMON blocks and INCLUDE files.<\/p>\n<p>Interface specifications for every subprogram, showing calls in and out, dummy arguments, PARAMETERs, COMMON and MODULE variables usage etc., can also be produced, and, optionally, embedded as comments back into the original source code.<\/p>\n<p>GXCHK operates in a &#8220;compile &amp; link&#8221; style which allows reports to be updated with minimal source code analysis. <a href=\"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/automake-and-qmerge\/\">AUTOMAKE<\/a> can be used to automate the process.<\/p>\n<p>A big advantage of static analysis is that it can check all your code without regard to whether or not it is actually executed in a particular run. On the other hand, static analysis cannot take account of subtleties in program control flow, or the varying nature on input data. Neither can it cannot monitor the status of individual array elements. Arrays are treated as amorphous blobs of data.<\/p>\n<hr \/>\n<div><a href=\"https:\/\/fortran.uk\/plusfort-quality-assurance\/#top\">Top<\/a><\/div>\n<h2><a name=\"dynamic\"><\/a>QA Method 2 &#8211; Dynamic Analysis<\/h2>\n<p>If a bug is defined as &#8220;an incorrect value in a storage location&#8221; then there is a large subset (perhaps 30%) which can be defined as &#8220;an undefined value in a storage location&#8221;, and many of the remainder may cause that condition as a knock-on effect.<\/p>\n<p>The Dynamic Analysis option of <em>plus<\/em><strong>FORT<\/strong> is a tool for diagnosing these errors at run-time. A\u00a0test version of your program is created, which detects any use of an undefined variable or array element, and logs it to a file. In other respects, the test program behaves exactly like the original. This is done by inserting calls to probe routines in the source code before any operation which depends on the value of a data item. \u00a0The program is compiled and linked in the normal way, and the executable code appears to the user to operate in exactly the same way as the original. \u00a0However, if a probe detects an undefined data item, it writes details to a log-file for later analysis. Source code for the probe routines is supplied.<\/p>\n<p>A static analyser such as GXCHK can detect a few of these errors, but the majority can only be detected at run-time. Dynamic analysis takes account of program control flow, works with real data, and can monitor individual bytes if required. However it only validates the code which is executed in a particular run. This makes it an almost precise complement of static analysis &#8211; each excels where the other is deficient.<\/p>\n<div align=\"center\">\n<p>&nbsp;<\/p>\n<table border=\"1\">\n<tbody>\n<tr>\n<th>Feature<\/th>\n<th>Static Analysis<\/th>\n<th>Dynamic Analysis<\/th>\n<\/tr>\n<tr>\n<td>Checks code whether or not it executes<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Checks for unsafe\/questionable source code<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Identifies used before set error<\/td>\n<td>Sometimes<\/td>\n<td>Yes<\/td>\n<\/tr>\n<tr>\n<td>Checks status of individual array elements<\/td>\n<td>No<\/td>\n<td>Yes<\/td>\n<\/tr>\n<tr>\n<td>Handles dependence on external data<\/td>\n<td>No<\/td>\n<td>Yes<\/td>\n<\/tr>\n<tr>\n<td>Effective with dummy args, EQUIVALENCE<\/td>\n<td>poor<\/td>\n<td>Yes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<\/div>\n<p>Dynamic analysis excels at detecting bugs which depend on external data, or on the use of arrays. These characteristics defeat conventional analysers.<\/p>\n<h2>Dynamic Analysis &#8211; Worked Example<\/h2>\n<h3>Original Code<\/h3>\n<pre><tt>      SUBROUTINE QKNUM(Ival,Pos)\r\n      INTEGER Ival , Pos , vals(50) , ios\r\n      READ(11,*,IOSTAT=ios) vals\r\n      IF ( ios.EQ.0 ) THEN\r\n         DO Pos = 1 , 50\r\n            IF ( Ival.EQ.vals(Pos) ) GOTO 100\r\n         ENDDO\r\n      ENDIF\r\n      Pos = 0\r\n 100  END<\/tt><\/pre>\n<p>QKNUM reads 50 numbers, and returns the position (Pos) of the first with value Ival.<\/p>\n<p>If the data file contains &#8220;<tt>2,9,,11,20*44,26*<\/tt>&#8220;, the READ statement leaves some elements of vals undefined, and QKNUM behaves unpredictably.<\/p>\n<hr \/>\n<h3>Code with Dynamic Analysis Probes<\/h3>\n<pre><tt>      SUBROUTINE QKNUM(Ival,Pos)\r\n      INTEGER Ival , Pos , vals(50) , ios\r\n      CALL SB$ENT('QKNUM','DYNBEF.FOR') &lt;-- initialize traceback and timing\r\n      CALL UD$I4(IOS)                   &lt;-- set variable IOS to undefined \r\n      CALL UD$AI4(50,VALS)              &lt;-- set array VALS to undefined\r\n      READ (11,*,IOSTAT=ios) vals\r\n      CALL QD$I4('IOS',IOS,4)  \r\n      IF ( ios.EQ.0 ) THEN \r\n         DO Pos = 1 , 50 \r\n            CALL QD$I4('VALS(POS)',VALS(POS),6)   &lt;-- check that VALS(IPOS) is defined before use\r\n            CALL QD$I4('IVAL',IVAL,6)             &lt;-- check that IVAL is defined before use\r\n            IF ( Ival.EQ.vals(Pos) ) GOTO 99999 \r\n         ENDDO \r\n      ENDIF \r\n      Pos = 0\r\n99999 CALL SB$EXI                       &lt;-- for traceback and timing data \r\n      END<\/tt><\/pre>\n<p>&nbsp;<\/p>\n<hr \/>\n<h3>Sample Log-file<\/h3>\n<pre><tt>XTOP2(I+J) value is undefined\r\n subprogram    FCOMP line    838 file JASO.FOR\r\n subprogram    VSCAN line   4255 file JASO.FOR\r\n subprogram   VUTREE line   1049 file JASO.FOR\r\n\r\nICHR value is undefined\r\n subprogram    VSTOP line   6682 file JASO.FOR\r\n subprogram     JASO line   2241 file JASO.FOR<\/tt><\/pre>\n<hr \/>\n<div><a href=\"https:\/\/fortran.uk\/plusfort-quality-assurance\/#top\">Top<\/a><\/div>\n<h2><a name=\"coverage\"><\/a>QA Method 3 &#8211; Test Coverage and Hot-Spot Analysis.<\/h2>\n<p>A reasonable goal for a software test suite is to ensure that every line of source code is executed at least once. The <em>plus<\/em><strong>FORT<\/strong> coverage analysis facility allows users to monitor progress against this goal, as well as identifying &#8220;hot-spots&#8221; &#8211; the sections of code which are executed most frequently, and which have most effect on program execution time.<\/p>\n<p>The <em>plus<\/em><strong>FORT<\/strong> coverage analysis facility places probes into Fortran source code which allow users to monitor the effectiveness of testing. At the end of each run, the probes update the coverage statistics for each source file. This data may be analysed at any time using the CVRANAL tool. CVRANAL identifies untested code blocks, and execution hot-spots.<\/p>\n<p>In addition, CVRANAL can annotate your source code as shown below. The annotations are comments and do not affect the validity of the source code.<\/p>\n<hr \/>\n<h3>Fragment of CVRANAL Test Coverage Report<\/h3>\n<pre>   4 Untested code blocks in subprogram MOO in file TESTMOO.BEF\r\n     at lines     27    32    33    62\r\nNO   Untested code blocks in subprogram BC in file TESTMOO.BEF\r\nNO   Untested code blocks in subprogram GETNUM in file TESTMOO.BEF\r\nNO   Untested code blocks in subprogram INIT in file TESTMOO.BEF<\/pre>\n<hr \/>\n<h3>Fragment of CVRANAL Execution Hot-spot Report<\/h3>\n<pre>         49682 :       IF(IGUESS(IDIG).NE.IANS(JDIG))GOTO 10\r\n               : in s\/prog BC at line    82 of TESTMOO.BEF\r\n         16336 :       IF(IGUESS(IDIG).EQ.IANS(IDIG))GOTO 40\r\n               : in s\/prog BC at line    80 of TESTMOO.BEF\r\n         14399 :       DO 10 JDIG=1,NDIGIT\r\n               : in s\/prog BC at line    81 of TESTMOO.BEF\r\n         11283 : 10    IF(J.EQ.NUM(JDIG))GOTO 20\r\n               : in s\/prog GETNUM at line   104 of TESTMOO.BEF\r\n          9039 :       GOTO 20\r\n               : in s\/prog BC at line    86 of TESTMOO.BEF<\/pre>\n<hr \/>\n<h3>Annotated Source Code<\/h3>\n<pre>      SUBROUTINE BC(IGUESS,IANS,NBULLS,NCOWS)\r\n      PARAMETER (NDIGIT=4,MINDIG=1,MAXDIG=9)\r\n      DIMENSION IGUESS(NDIGIT),IANS(NDIGIT)\r\n\r\n      NBULLS=0                                           !   4084\r\n      NCOWS=0\r\n      DO 20 IDIG=1,NDIGIT\r\n      IF(IGUESS(IDIG).EQ.IANS(IDIG))GOTO 40              !  16336\r\n      DO 10 JDIG=1,NDIGIT                                !  14399\r\n      IF(IGUESS(IDIG).NE.IANS(JDIG))GOTO 10              !  49682\r\n      NCOWS=NCOWS+1                                      !   5360\r\n      GOTO 20\r\n10    CONTINUE\r\n      GOTO 20                                            !   9039\r\n40    NBULLS=NBULLS+1                                    !   1937\r\n20    CONTINUE\r\n      RETURN                                             !   4084\r\n      END<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>Many people know plusFORT mainly for SPAG, the restructuring tool which unscrambles spaghetti code. However, the plusFORT quality assurance facilities are arguably of even greater importance to most users. plusFORT Version 7 is unique among QA tools in offering three distinct and complementary approaches to the problem of software quality assurance. Working together these three [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":17477,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.6 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>plusFORT Quality Assurance - Fortran UK<\/title>\n<meta name=\"description\" content=\"Many people know plusFORT mainly for SPAG but plusFORT quality assurance facilities are arguably of even greater importance to most users.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"plusFORT Quality Assurance - Fortran UK\" \/>\n<meta property=\"og:description\" content=\"Many people know plusFORT mainly for SPAG but plusFORT quality assurance facilities are arguably of even greater importance to most users.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/\" \/>\n<meta property=\"og:site_name\" content=\"Fortran UK\" \/>\n<meta property=\"article:modified_time\" content=\"2017-04-28T09:10:48+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/\",\"url\":\"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/\",\"name\":\"plusFORT Quality Assurance - Fortran UK\",\"isPartOf\":{\"@id\":\"https:\/\/fortran.uk\/#website\"},\"datePublished\":\"2014-04-08T14:21:58+00:00\",\"dateModified\":\"2017-04-28T09:10:48+00:00\",\"description\":\"Many people know plusFORT mainly for SPAG but plusFORT quality assurance facilities are arguably of even greater importance to most users.\",\"breadcrumb\":{\"@id\":\"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/fortran.uk\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Fortran Analysis &#038; Refactoring with plusFORT V8\",\"item\":\"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"plusFORT Quality Assurance\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fortran.uk\/#website\",\"url\":\"https:\/\/fortran.uk\/\",\"name\":\"Fortran UK\",\"description\":\"All things Fortran\",\"publisher\":{\"@id\":\"https:\/\/fortran.uk\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fortran.uk\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/fortran.uk\/#organization\",\"name\":\"Polyhedron Solutions Ltd.\",\"url\":\"https:\/\/fortran.uk\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/fortran.uk\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/fortran.uk\/wp-content\/uploads\/2018\/03\/Web-logoPolySol.png\",\"contentUrl\":\"https:\/\/fortran.uk\/wp-content\/uploads\/2018\/03\/Web-logoPolySol.png\",\"width\":203,\"height\":113,\"caption\":\"Polyhedron Solutions Ltd.\"},\"image\":{\"@id\":\"https:\/\/fortran.uk\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.youtube.com\/@polyhedronsolutions1405\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"plusFORT Quality Assurance - Fortran UK","description":"Many people know plusFORT mainly for SPAG but plusFORT quality assurance facilities are arguably of even greater importance to most users.","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:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/","og_locale":"en_GB","og_type":"article","og_title":"plusFORT Quality Assurance - Fortran UK","og_description":"Many people know plusFORT mainly for SPAG but plusFORT quality assurance facilities are arguably of even greater importance to most users.","og_url":"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/","og_site_name":"Fortran UK","article_modified_time":"2017-04-28T09:10:48+00:00","twitter_card":"summary_large_image","twitter_misc":{"Estimated reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/","url":"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/","name":"plusFORT Quality Assurance - Fortran UK","isPartOf":{"@id":"https:\/\/fortran.uk\/#website"},"datePublished":"2014-04-08T14:21:58+00:00","dateModified":"2017-04-28T09:10:48+00:00","description":"Many people know plusFORT mainly for SPAG but plusFORT quality assurance facilities are arguably of even greater importance to most users.","breadcrumb":{"@id":"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/plusfort-quality-assurance\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/fortran.uk\/"},{"@type":"ListItem","position":2,"name":"Fortran Analysis &#038; Refactoring with plusFORT V8","item":"https:\/\/fortran.uk\/fortran-analysis-and-refactoring-with-plusfort\/"},{"@type":"ListItem","position":3,"name":"plusFORT Quality Assurance"}]},{"@type":"WebSite","@id":"https:\/\/fortran.uk\/#website","url":"https:\/\/fortran.uk\/","name":"Fortran UK","description":"All things Fortran","publisher":{"@id":"https:\/\/fortran.uk\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fortran.uk\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/fortran.uk\/#organization","name":"Polyhedron Solutions Ltd.","url":"https:\/\/fortran.uk\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/fortran.uk\/#\/schema\/logo\/image\/","url":"https:\/\/fortran.uk\/wp-content\/uploads\/2018\/03\/Web-logoPolySol.png","contentUrl":"https:\/\/fortran.uk\/wp-content\/uploads\/2018\/03\/Web-logoPolySol.png","width":203,"height":113,"caption":"Polyhedron Solutions Ltd."},"image":{"@id":"https:\/\/fortran.uk\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.youtube.com\/@polyhedronsolutions1405"]}]}},"_links":{"self":[{"href":"https:\/\/fortran.uk\/wp-json\/wp\/v2\/pages\/15301"}],"collection":[{"href":"https:\/\/fortran.uk\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/fortran.uk\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/fortran.uk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fortran.uk\/wp-json\/wp\/v2\/comments?post=15301"}],"version-history":[{"count":20,"href":"https:\/\/fortran.uk\/wp-json\/wp\/v2\/pages\/15301\/revisions"}],"predecessor-version":[{"id":18797,"href":"https:\/\/fortran.uk\/wp-json\/wp\/v2\/pages\/15301\/revisions\/18797"}],"up":[{"embeddable":true,"href":"https:\/\/fortran.uk\/wp-json\/wp\/v2\/pages\/17477"}],"wp:attachment":[{"href":"https:\/\/fortran.uk\/wp-json\/wp\/v2\/media?parent=15301"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}