CINXE.COM
Mortality and Other Rate Tables
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head><title> Mortality and Other Rate Tables </title><meta name="description" content="The underlying database for the MORT application is a set of XML files that follow ACORD’s XTbML standards. The Association for Cooperative Operations Research and Development (ACORD) is a non-profit organization dedicated to the electronic exchange of insurance data. The "XTbML Background" screen has information related to the formation of the underlying structure utilized by MORT and summarizes the SOA’s work with ACORD. The SOA and ACORD partnered in 2002 to develop their set of data standards. XML files were chosen as the desired storage format because they provide flexibility and portability for future maintenance of this delivery platform. See the ‘XTbML History’ link to learn more about XTbML." /><link href="Styles/Site.css" rel="stylesheet" type="text/css" /> <!-- Google Tag Manager --> <!--RTRAN 03-30-2022 Update --> <!-- OneTrust Cookies Consent Notice start for soa.org --> <script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js" type="text/javascript" charset="UTF-8" data-domain-script="a99ec4f7-14bc-4efa-9f79-b633c187e043" ></script> <script type="text/javascript"> function OptanonWrapper() { } </script> <!-- OneTrust Cookies Consent Notice end for soa.org --> <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= 'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-M4WCJBM');</script> <!-- End Google Tag Manager --> <script type='text/javascript'> if (typeof jQuery != 'undefined') { var filetypes = /\.(zip|exe|dmg|pdf|doc.*|xls.*|ppt.*|mp3|txt|rar|wma|mov|avi|wmv|flv|wav)$/i; var baseHref = ''; if (jQuery('base').attr('href') != undefined) baseHref = jQuery('base').attr('href'); var hrefRedirect = ''; jQuery('body').on('click', 'a', function(event) { var el = jQuery(this); var track = true; var href = (typeof(el.attr('href')) != 'undefined' ) ? el.attr('href') : ''; var isThisDomain = href.match(document.domain.split('.').reverse()[1] + '.' + document.domain.split('.').reverse()[0]); if (!href.match(/^javascript:/i)) { var elEv = []; elEv.value=0, elEv.non_i=false; if (href.match(/^mailto\:/i)) { elEv.category = 'email'; elEv.action = 'click'; elEv.label = href.replace(/^mailto\:/i, ''); elEv.loc = href; } else if (href.match(filetypes)) { var extension = (/[.]/.exec(href)) ? /[^.]+$/.exec(href) : undefined; elEv.category = 'download'; elEv.action = 'click-' + extension[0]; elEv.label = href.replace(/ /g,'-'); elEv.loc = baseHref + href; } else if (href.match(/^https?\:/i) && !isThisDomain) { elEv.category = 'external'; elEv.action = 'click'; elEv.label = href.replace(/^https?\:\/\//i, ''); elEv.non_i = true; elEv.loc = href; } else if (href.match(/^tel\:/i)) { elEv.category = 'telephone'; elEv.action = 'click'; elEv.label = href.replace(/^tel\:/i, ''); elEv.loc = href; } else track = false; if (track) { var ret = true; if((elEv.category == 'external' || elEv.category == 'download') && (el.attr('target') == undefined || el.attr('target').toLowerCase() != '_blank') ) { hrefRedirect = elEv.loc; ga('send','event', elEv.category.toLowerCase(),elEv.action.toLowerCase(),elEv.label.toLowerCase(),elEv.value,{ 'nonInteraction': elEv.non_i , 'hitCallback':gaHitCallbackHandler }); ret = false; } else { ga('send','event', elEv.category.toLowerCase(),elEv.action.toLowerCase(),elEv.label.toLowerCase(),elEv.value,{ 'nonInteraction': elEv.non_i }); } return ret; } } }); gaHitCallbackHandler = function() { window.location.href = hrefRedirect; } } </script> </head> <body> <form method="post" action="./About.aspx" id="ctl01"> <div class="aspNetHidden"> <input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKMTY1NDU2MTA1MmRkUsOfrF0oJQxlUzfKUGFMamafLZHpn17tzJc6gks21ug=" /> </div> <script src="/WebResource.axd?d=ltwWo5RVObcvndK0MxhCosy4cS4Cl_RlKZJB3I3A36NwQE4NcGJKkYszWFmCwAmk7ieWdEyvy3VxFq8DTtBrZx5rYitDGhZdV3n9eKochWk1&t=638628027619783110" type="text/javascript"></script> <div class="aspNetHidden"> <input type="hidden" name="__VIEWSTATEGENERATOR" id="__VIEWSTATEGENERATOR" value="E809BCA5" /> </div> <!-- Google Tag Manager (noscript) --> <noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M4WCJBM" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript> <!-- End Google Tag Manager (noscript) --> <div class="page"> <div class="header"> <div id="left_jt"> <a href="http://www.SOA.org"> <img border="0" id="logoLeft" name="logoLeft" alt="Actuaries - Risk is Opportunity." src="images/logoLeft.jpg" /></a> </div> <div id="banner"> <a href="../Home.aspx" id="Header1_HeaderHomeLink"> <img alt="Society of Actuaries" src="images/banner.jpg" /></a> </div> <div class="title"> <h1> Mortality and Other Rate Tables </h1> </div> <div class="loginDisplay"> </div> <div class="clear hideSkiplink"> <a href="#NavigationMenu_SkipLink"><img alt="Skip Navigation Links" src="/WebResource.axd?d=HdOYB22iO_0A3BtOI-QChgyEulZ7HjuQIePqtDRX6XsxJgfmzQchDiQg0mvVvAj68PW7msSIv5XcH4TYC_He-jgCVkVGlXEiJKHBwpEi7681&t=638628027619783110" width="0" height="0" style="border-width:0px;" /></a><div class="menu" id="NavigationMenu"> <ul class="level1"> <li><a class="level1" href="Default.aspx">Search</a></li><li><a class="level1" href="ConvertFile.aspx">Convert</a></li><li><a class="level1" href="ViewChangeLog.aspx">Updates</a></li><li><a class="level1" href="About.aspx">Xtbml Background</a></li><li><a class="level1" href="https://www.soa.org/sections/technology/techology-table-manager/">Table Manager</a></li><li><a class="level1" href="AdditionalLinks.aspx" target="_blank">Additional Resources</a></li><li><a class="level1" href="Help.aspx">Help</a></li> </ul> </div><a id="NavigationMenu_SkipLink"></a> </div> </div> <div class="main"> <h2>Background Information</h2> <p> 1998, the Computer Science Council of the Society of Actuaries revisited the task of defining a standard for the interchange of table data. The focus of this work was to be on the format of the data itself and not the tools to maintain or update the data. In 2000, a Data Standards Committee was formed. This Committee was headed by Jacques Rioux (Drake University). Mark Horowitz (Towers Perrin) and Cynthia Jeness (Golden Code Development Corporation) also participated on the Committee. This Committee determined that there was already an open W3C standard, XML, which could be used for actuarial tabular data. Using XML as the standard, the Committee developed a preliminary <i>dialect</i> and presented the results to the Computer Science Council. Subsequent discussions with members of the SOA led to the submission of the XML standard for adoption by ACORD.</p> <p> On March 21-22, 2002, Members of the SOA and other insurance industry professionals met with ACORD in Westwood, MA. At this meeting the original standard was generalized and improved so that it would apply across a range of actuarial tabular data needs. The improved version, <b>XTbML</b>, went through the approval process at the ACORD meeting in June, 2002 and was adopted on a pilot basis by ACORD. The pilot period is intended to provide time for interested parties to use the standard and submit comments before it is officially adopted as a standard in November, 2002.</p> <p> In September, 2002, another ACORD meeting was held to define the transactional interaction for XTbML. Utilizing this transactional standard, tabular data could be stored in a central repository and transferred to a requesting computer utilizing various industry standard protocols such as SOAP and HTTP GET/POST. This should extend the utility of the standard from the realm of human interaction to computer-computer interaction.</p> <h2>ACORD XTbML Standard</h2> <p>The primary documentation of the XTbML standard from ACORD consists of two documents: <ul> <li><a href=XTbML2.7.01.xsd>XML Schema</a> <li>Type Code Definition Document </ul></p> <p> The second document is available from the ACORD site and may be downloaded by anyone who is willing to register. In terms of the XTbML standard, the following type code groups are the most important: <ul> <li>Content Type Codes <li>Nation Type Codes <li>Scale Type Codes </ul></p> <p> Beyond the documents sited above, ACORD does not provide information related to how to successfully implement the standard. They look to the users themselves to provide this type of information. Because the ACORD standard is very general and also because it takes a different approach to storing data than did Table Manager, some more specific standards need to be adopted in order to facilitate the exchange of tabular data.</p> <h3>ACORD Standard: Table Structure</h3> <p>The XML structure underlying the ACORD standard may be represented diagrammatically as follows: <center> <table cellpadding="3" border="1" cellspacing="0"><tr><td> <img src=images/XTbML.jpg border="0"> </td></tr> </table> </center></p> <p> Under this scheme, the<i> XTbML</i> element contains a <i>ContentClassification</i> element and one or more <i>Table</i> elements. Each <i>Table</i> element contains both a <i>Metadata</i> element and a <i>Values</i> element. The <i>Values</i> element contains one or more <i>Axis</i> elements and these elements actually store the values. This assumes that the indexes to the values are number (e.g. age). Non-numeric indexes (e.g. gender) require the use of both <i>KeyDef's</i> and <i>Key's</i>. For the purpose of the SOA table database the use of these elements is deemed unnecessary.</p> <p> The purpose of each of the elements shown in the diagram may be summarized as follows: <ul> <li><b><i>ContentClassification</i></b> - Identifies the tabular data and provides general descriptive information. <li><b><i>Table</i></b>- This is the container for the tabular data. In some cases, it is more convenient to use multiple "tables" to represent a set of tabular data. For example, a select and ultimate table may be best represented by two-dimensional select <i>Table</i> plus a one-dimensional aggregate <i>Table</i>. <li><b><i>Table:MetaData</i></b> - This describes the attributes of the data stored within the <i>Table</i>; e.g., the minimum and maximum values for the indexes, the type of data, etc. <li><b><i>Table:Values</i></b> - This is the top-level container for the data itself. <li><b><i>Table:Values:Axis</i></b> - This is the container for one dimension of the data. A one-dimensional table would have one <i>Axis</i> while a two-dimensional table would have one <i>Axis</i> which contains a second <i>Axis</i>. The lowest level <i>Axis</i> will contain a series of <i>Y</i> elements which actually house the data. </ul></p> <p> For the purpose of the SOA project, the types of tables stored by Table Manager will be structured in XTbML as follows: <ul> <li><b>Aggregate Tables</b> - A single <i>Table</i> element with one <i>Axis</i> element. <li><b>Select and Ultimate Tables</b> - Two <i>Table</i> elements. The select part of the table is represent by one of these. This <i>Table</i> will have two <i>Axis</i> elements. The outermost <i>Axis</i> will be indexed on age and the innermost axis will be indexed based on the duration. The second <i>Table</i> element will contain the ultimate data which will be handled just like an Aggregate Table. </ul></p> <p> Since the ACORD standard is so generic, there are other structures which could be used to represent the SOA data. The proposed scheme is recommended because it is simple and consistent with the pre-cursor to the ACORD standard developed by the Computer Science Council. There was considerable discussion and development around the pre-cursor standard. </p> </div> <div class="clear"> </div> </div> <div class="footer"> <ul> <li><a href="http://www.SOA.org">SOA.org</a> </li> <li>|</li> <li><a href="TermsOfUse.aspx">Terms Of Use</a> </li> <li>|</li> <li><a href="https://www.soa.org/about/contact/contact-customer-service/" id="Footer1_ContactUsLink">Contact Us</a></li> </ul> </div> <script type='text/javascript'>new Sys.WebForms.Menu({ element: 'NavigationMenu', disappearAfter: 500, orientation: 'horizontal', tabIndex: 0, disabled: false });</script></form> </body> </html>