{"id":5861,"date":"2019-04-10T06:24:25","date_gmt":"2019-04-10T06:24:25","guid":{"rendered":"http:\/\/arielsheen.com\/?p=5861"},"modified":"2019-04-10T06:24:25","modified_gmt":"2019-04-10T06:24:25","slug":"establishing-governance-rules-over-data-assets","status":"publish","type":"post","link":"https:\/\/arielsheen.com\/index.php\/2019\/04\/10\/establishing-governance-rules-over-data-assets\/","title":{"rendered":"Establishing Governance Rules Over Data Assets"},"content":{"rendered":"<p><a href=\"https:\/\/www.lens.org\/lens\/patent\/061-414-258-020-133\/fulltext\">LENS source.<\/a><\/p>\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"5\" rowspan=\"1\">\n<hr \/>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<colgroup span=\"1\">\n<col span=\"1\" width=\"3%\" \/>\n<col span=\"1\" width=\"12%\" \/>\n<col span=\"1\" width=\"65%\" \/>\n<col span=\"1\" width=\"15%\" \/><\/colgroup>\n<tbody>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(54)<\/td>\n<td class=\"table_data\" colspan=\"2\" rowspan=\"1\"><span style=\"font-size: xx-small;\"><b>ESTABLISHING <span class=\"highlight\">GOVERNANCE<\/span> RULES OVER DATA ASSETS<\/b><\/span><\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(75)<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\">Inventor:<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><b>International Business Machines Corporation<\/b>, \u00a0Armonk, NY (US)<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(73)<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\">Assignee:<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><b>International Business Machines Corporation<\/b>, \u00a0Armonk, NY (US),\u00a0Type:\u00a0US Company<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(*)<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\">Notice:<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\">Subject to any disclaimer, the term of this patent is extended or adjusted under 35 U.S.C. 154(b) by 0 days.<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(21)<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\">Appl. No.:<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><b>15\/014,329<\/b><\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(22)<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\">Filed:<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><b>Feb. \u00a03, 2016<\/b><\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<colgroup span=\"1\">\n<col span=\"1\" width=\"3%\" \/>\n<col span=\"1\" width=\"90%\" \/>\n<col span=\"1\" width=\"2%\" \/><\/colgroup>\n<tbody>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\" align=\"center\"><b>Related U.S. Patent Documents<\/b><\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\" valign=\"center\">(63)<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\">. Continuation of application No. 14\/929,510, filed on Nov. \u00a02, 2015 .<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Jan. \u00a01, 2013 G 06 F 17 30604 F I Jan. \u00a031, 2017 US B H C Jan. \u00a01, 2013 G 06 F 17 30598 L I Jan. \u00a031, 2017 US B H C<\/p>\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(51)<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><b>Int. Cl.<\/b><\/td>\n<td class=\"separator\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">G06F 007\/00 (20060101); G06F 017\/00 (20060101); G06F 017\/30 (20060101)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(58)<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\"><b>Field of Search <\/b><\/td>\n<td class=\"separator\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">707\/694<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<table border=\"0\" width=\"95%\" rules=\"none\" cellspacing=\"1%\">\n<tbody>\n<tr>\n<td class=\"inid_text\" colspan=\"9\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(56)<\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\" align=\"center\"><b>References Cited<\/b><\/td>\n<\/tr>\n<tr>\n<td colspan=\"9\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\" align=\"center\">U.S. PATENT DOCUMENTS<\/td>\n<\/tr>\n<tr>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">8,700,577<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0B2<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">4\/2014<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0\u00a0\u00a0Yeh et al.<\/td>\n<td class=\"empty_separator\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<\/tr>\n<tr>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">2009\/\/0063534<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0A1<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">3\/2009<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0\u00a0\u00a0Halberstadt<\/td>\n<td class=\"empty_separator\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<\/tr>\n<tr>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">2010\/\/0114628<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0A1<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">5\/2010<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0\u00a0\u00a0Adler et al.<\/td>\n<td class=\"empty_separator\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<\/tr>\n<tr>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">2011\/\/0066602<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0A1<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">3\/2011<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0\u00a0\u00a0Studer et al.<\/td>\n<td class=\"empty_separator\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<\/tr>\n<tr>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">2012\/\/0102007<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0A1<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">4\/2012<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0\u00a0\u00a0Ramasubramanian et al.<\/td>\n<td class=\"empty_separator\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<\/tr>\n<tr>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">2013\/\/0031044<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0A1<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">*<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">1\/2013<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">\u00a0\u00a0\u00a0\u00a0Miranda<\/td>\n<td class=\"separator\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">706\/47<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<table border=\"0\" width=\"95%\" rules=\"none\" cellspacing=\"1%\">\n<tbody>\n<tr>\n<td colspan=\"13\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"11\" rowspan=\"1\" align=\"center\">FOREIGN PATENT DOCUMENTS<\/td>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"table_data\" colspan=\"13\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">WO<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">2007038231<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\">A2<\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"left\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\">4\/2007<\/td>\n<td class=\"empty_separator\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\" align=\"right\"><\/td>\n<td class=\"nowrap_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<table border=\"0\" width=\"95%\" rules=\"none\" cellspacing=\"1%\">\n<tbody>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\" align=\"center\">OTHER PUBLICATIONS<\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\">Chiang et al., \u201cDiscovering Data Quality Rules\u201d, VLDB &#8217;08, Aug. 24-30, 2008, Auckland, New Zealand, Copyright 2008 VLDB Endowment, ACM, 12 pages.<\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\">Appendix P.: List of Patents or Patent Applications Treated as Related, 2 pages.<\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\">U.S. Appl. No. 14\/929,510, Entitled \u201cEstablishing <span class=\"highlight\">Governance<\/span> Rules Over Data Assets\u201d, filed Nov. 2, 2015, IBM.<\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\">List of IBM Patents or Patent Applications Treated as Related, Appendix P, Filed Herewith, 2 pages.<\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\"><\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\">Halberstadt, et al., \u201cEstablishing <span class=\"highlight\">Governance<\/span> Rules Over Data Assets\u201d, U.S. Appl. No. 15\/014,329, filed Feb. 3, 2016.<\/td>\n<\/tr>\n<tr>\n<td class=\"table_data\" colspan=\"9\" rowspan=\"1\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table border=\"0\" width=\"95%\" rules=\"none\" cellspacing=\"1%\">\n<tbody>\n<tr>\n<td class=\"inid_text\" colspan=\"9\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"table_data\" colspan=\"9\" rowspan=\"1\" align=\"left\">\u00a0\u00a0\u00a0\u00a0\u00a0* cited by examiner<\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"9\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"table_data\" colspan=\"9\" rowspan=\"1\" align=\"left\"><i>\u00a0\u00a0\u00a0\u00a0\u00a0Primary Examiner<\/i>\u00a0\u2014Van\u00a0Oberly<\/td>\n<\/tr>\n<tr>\n<td class=\"table_data\" colspan=\"9\" rowspan=\"1\" align=\"left\"><i>\u00a0\u00a0\u00a0\u00a0\u00a0Art Unit<\/i>\u00a0\u2014\u00a02166<\/td>\n<\/tr>\n<tr>\n<td class=\"table_data\" colspan=\"9\" rowspan=\"1\" align=\"left\"><i>\u00a0\u00a0\u00a0\u00a0\u00a0Exemplary claim number<\/i>\u00a0\u2014\u00a01<\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"9\" rowspan=\"1\"><\/td>\n<\/tr>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(74)<\/td>\n<td class=\"table_data\" colspan=\"8\" rowspan=\"1\" align=\"left\"><i>Attorney, Agent, or Firm<\/i>\u00a0\u2014\u00a0Lance I.\u00a0Hochhauser<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<div>\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<colgroup span=\"1\">\n<col span=\"1\" width=\"3%\" \/>\n<col span=\"1\" width=\"92%\" \/><\/colgroup>\n<tbody>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(57)<\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\">\n<h2>Abstract<\/h2>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">Transform <span class=\"highlight\">governance<\/span> rules for a data asset to apply to a set of related data assets. Establishing a <span class=\"highlight\">governance<\/span> rule over a first data asset based on a second <span class=\"highlight\">governance<\/span> rule applied to either an upstream or a downstream data asset.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n<div class=\"table_data\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\" align=\"center\"><b>1 <a href=\"https:\/\/www.lens.org\/lens\/patent\/061-414-258-020-133\/fulltext#claim\" shape=\"rect\">Claim<\/a>, 3 Drawing Sheets, and 5 Figures<\/b><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"break_before\">\n<a name=\"DRAWINGS\" shape=\"rect\"><\/a><\/div>\n<h2>BACKGROUND<\/h2>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0001]\u00a0The present invention relates generally to the field of data processing, and more particularly to data integrity.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0002]\u00a0Data assets are used to run operational systems of businesses. Businesses employ <span class=\"highlight\">governance<\/span> rules to ensure that data assets comply with external and\/or internal regulations. For example, in banking, external regulations come from voluntary agreements (the Third Basel Accord, or Basel III) or <span class=\"highlight\">government<\/span> agencies (FDIC regulations), and internal regulations come from a variety of standards and practices put in place by a management group of a business such as exceeding external regulations or supplementing external regulations (e.g., personnel, physical security). To comply with both internal and external regulations, businesses employ a variety of <span class=\"highlight\">governance<\/span> rules (sometimes also called data rules).<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0003]\u00a0Applying <span class=\"highlight\">governance<\/span> rules to data assets can be manually intensive. Application of <span class=\"highlight\">governance<\/span> rules can also include a variety of errors. To apply a <span class=\"highlight\">governance<\/span> rule, all data assets under the <span class=\"highlight\">governance<\/span> rule must be located, data within the data assets must be understood, and the <span class=\"highlight\">governance<\/span> rule must be applied correctly to the data assets. Generally, these abilities are not centrally located and various knowledge bases must be combined.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2>SUMMARY<\/h2>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0004]\u00a0According to an aspect of the present invention, there is a method, computer program product, and\/or system that performs the following operations (not necessarily in the following order): (i) determining a relationship between a first data asset and a second data asset; (ii) determining a first <span class=\"highlight\">governance<\/span> rule applied to the first data asset; and (iii) transforming the first <span class=\"highlight\">governance<\/span> rule, into a second <span class=\"highlight\">governance<\/span> rule, based on the relationship between the first data asset and the second data asset. At least determining a relationship between a first data asset and a second data asset is performed by computer <span class=\"highlight\">software<\/span> running on computer hardware.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2>BRIEF DESCRIPTION OF THE DRAWINGS<\/h2>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0005]\u00a0<b>FIG. 1<\/b> is a block diagram view of a first embodiment of a system according to the present invention;<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0006]\u00a0<b>FIG. 2<\/b> is a flowchart showing a first embodiment method performed, at least in part, by the first embodiment system;<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0007]\u00a0<b>FIG. 3<\/b> is a block diagram view of a machine logic (e.g., <span class=\"highlight\">software<\/span>) portion of the first embodiment system;<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0008]\u00a0<b>FIG. 4<\/b> is a screenshot showing a data lineage graph according to a second embodiment of a system according to the present invention; and<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0009]\u00a0<b>FIG. 5<\/b> is a screenshot showing a pseudocode according to a third embodiment of a system according to the present invention.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2>DETAILED DESCRIPTION<\/h2>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0010]\u00a0Transform <span class=\"highlight\">governance<\/span> rules for a data asset to apply to a set of related data assets. Establishing a <span class=\"highlight\">governance<\/span> rule over a first data asset based on a second <span class=\"highlight\">governance<\/span> rule applied to either an upstream or a downstream data asset. This Detailed Description section is divided into the following sub-sections: (i) Hardware and <span class=\"highlight\">Software<\/span> Environment; (ii) Example Embodiment; (iii) Further Comments and\/or Embodiments; and (iv) Definitions.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2>I. HARDWARE AND <span class=\"highlight\">SOFTWARE<\/span> ENVIRONMENT<\/h2>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0011]\u00a0The present invention may be a system, a method, and\/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0012]\u00a0The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0013]\u00a0Computer readable program instructions described herein can be downloaded to respective computing\/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and\/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and\/or edge servers. A network adapter card or network interface in each computing\/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing\/processing device.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0014]\u00a0Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the \u201cC\u201d programming language or similar programming languages. The computer readable program instructions may execute entirely on the user&#8217;s computer, partly on the user&#8217;s computer, as a stand-alone <span class=\"highlight\">software<\/span> package, partly on the user&#8217;s computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user&#8217;s computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0015]\u00a0Aspects of the present invention are described herein with reference to flowchart illustrations and\/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and\/or block diagrams, and combinations of blocks in the flowchart illustrations and\/or block diagrams, can be implemented by computer readable program instructions.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0016]\u00a0These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions\/acts specified in the flowchart and\/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and\/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function\/act specified in the flowchart and\/or block diagram block or blocks.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0017]\u00a0The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions\/acts specified in the flowchart and\/or block diagram block or blocks.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0018]\u00a0The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and\/or flowchart illustration, and combinations of blocks in the block diagrams and\/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0019]\u00a0An embodiment of a possible hardware and <span class=\"highlight\">software<\/span> environment for <span class=\"highlight\">software<\/span> and\/or methods according to the present invention will now be described in detail with reference to the Figures. <b>FIG. 1<\/b> is a functional block diagram illustrating various portions of networked computers system <b>100<\/b>, including: <span class=\"highlight\">governance<\/span> relationship sub-system <b>102<\/b>; data asset sub-systems <b>104<\/b>, <b>106<\/b>; rule storage sub-system <b>108<\/b>; and communication network <b>114<\/b>. <span class=\"highlight\">Governance<\/span> relationship sub-system <b>102<\/b> contains: <span class=\"highlight\">governance<\/span> relationship computer <b>200<\/b>; display device <b>212<\/b>; and external devices <b>214<\/b>. <span class=\"highlight\">Governance<\/span> relationship computer <b>200<\/b> contains: communication unit <b>202<\/b>; processor set <b>204<\/b>; input\/output (I\/O) interface set <b>206<\/b>; memory device <b>208<\/b>; and persistent storage device <b>210<\/b>. Memory device <b>208<\/b> contains: random access memory (RAM) devices <b>216<\/b>; and cache memory device <b>218<\/b>. Persistent storage device <b>210<\/b> contains: <span class=\"highlight\">governance<\/span> relationship program <b>300<\/b>. Data asset sub-system <b>104<\/b> contains: first data asset <b>220<\/b>; second data asset <b>222<\/b>; data asset storage <b>224<\/b>; and <span class=\"highlight\">governance<\/span> rule storage <b>226<\/b>.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0020]\u00a0<span class=\"highlight\">Governance<\/span> relationship sub-system <b>102<\/b> is, in many respects, representative of the various computer sub-systems in the present invention. Accordingly, several portions of <span class=\"highlight\">governance<\/span>relationship sub-system <b>102<\/b> will now be discussed in the following paragraphs.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0021]\u00a0<span class=\"highlight\">Governance<\/span> relationship sub-system <b>102<\/b> may be a laptop computer, a tablet computer, a netbook computer, a personal computer (PC), a desktop computer, a personal digital assistant (PDA), a smart phone, or any programmable electronic device capable of communicating with client sub-systems via communication network <b>114<\/b>. <span class=\"highlight\">Governance<\/span> relationship program <b>300<\/b> is a collection of machine readable instructions and\/or data that is used to create, manage, and control certain <span class=\"highlight\">software<\/span> functions that will be discussed in detail, below, in the Example Embodiment sub-section of this Detailed Description section.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0022]\u00a0<span class=\"highlight\">Governance<\/span> relationship sub-system <b>102<\/b> is capable of communicating with other computer sub-systems via communication network <b>114<\/b>. Communication network <b>114<\/b> can be, for example, a local area network (LAN), a wide area network (WAN) such as the Internet, or a combination of the two, and can include wired, wireless, or fiber optic connections. In general, communication network <b>114<\/b> can be any combination of connections and protocols that will support communications between <span class=\"highlight\">governance<\/span> relationship sub-system <b>102<\/b> and client sub-systems.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0023]\u00a0<span class=\"highlight\">Governance<\/span> relationship sub-system <b>102<\/b> is shown as a block diagram with many double arrows. These double arrows (no separate reference numerals) represent a communications fabric, which provides communications between various components of <span class=\"highlight\">governance<\/span> relationship sub-system <b>102<\/b>. This communications fabric can be implemented with any architecture designed for passing data and\/or control information between processors (such as microprocessors, communications processors, and\/or network processors, etc.), system memory, peripheral devices, and any other hardware components within a system. For example, the communications fabric can be implemented, at least in part, with one or more buses.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0024]\u00a0Memory device <b>208<\/b> and persistent storage device <b>210<\/b> are computer readable storage media. In general, memory device <b>208<\/b> can include any suitable volatile or non-volatile computer readable storage media. It is further noted that, now and\/or in the near future: (i) external devices <b>214<\/b> may be able to supply some, or all, memory for <span class=\"highlight\">governance<\/span> relationship sub-system <b>102<\/b>; and\/or (ii) devices external to <span class=\"highlight\">governance<\/span> relationship sub-system <b>102<\/b> may be able to provide memory for <span class=\"highlight\">governance<\/span> relationship sub-system <b>102<\/b>.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0025]\u00a0<span class=\"highlight\">Governance<\/span> relationship program <b>300<\/b> is stored in persistent storage device <b>210<\/b> for access and\/or execution by one or more processors of processor set <b>204<\/b>, usually through memory device <b>208<\/b>. Persistent storage device <b>210<\/b>: (i) is at least more persistent than a signal in transit; (ii) stores the program (including its soft logic and\/or data) on a tangible medium (such as magnetic or optical domains); and (iii) is substantially less persistent than permanent storage. Alternatively, data storage may be more persistent and\/or permanent than the type of storage provided by persistent storage device <b>210<\/b>.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0026]\u00a0<span class=\"highlight\">Governance<\/span> relationship program <b>300<\/b> may include both substantive data (that is, the type of data stored in a database) and\/or machine readable and performable instructions. In this particular embodiment (i.e., <b>FIG. 1<\/b>), persistent storage device <b>210<\/b> includes a magnetic hard disk drive. To name some possible variations, persistent storage device <b>210<\/b> may include a solid-state hard drive, a semiconductor storage device, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, or any other computer readable storage media that is capable of storing program instructions or digital information.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0027]\u00a0The media used by persistent storage device <b>210<\/b> may also be removable. For example, a removable hard drive may be used for persistent storage device <b>210<\/b>. Other examples include optical and magnetic disks, thumb drives, and smart cards that are inserted into a drive for transfer onto another computer readable storage medium that is also part of persistent storage device <b>210<\/b>.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0028]\u00a0Communication unit <b>202<\/b>, in these examples, provides for communications with other data processing systems or devices external to <span class=\"highlight\">governance<\/span> relationship sub-system <b>102<\/b>. In these examples, communication unit <b>202<\/b> includes one or more network interface cards. Communication unit <b>202<\/b> may provide communications through the use of either or both physical and wireless communications links. Any <span class=\"highlight\">software<\/span> modules discussed herein may be downloaded to a persistent storage device (such as persistent storage device <b>210<\/b>) through a communications unit (such as communication unit <b>202<\/b>).<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0029]\u00a0I\/O interface set <b>206<\/b> allows for input and output of data with other devices that may be connected locally in data communication with <span class=\"highlight\">governance<\/span> relationship computer <b>200<\/b>. For example, I\/O interface set <b>206<\/b> provides a connection to external devices <b>214<\/b>. External devices <b>214<\/b>will typically include devices, such as a keyboard, a keypad, a touch screen, and\/or some other suitable input device. External devices <b>214<\/b> can also include portable computer readable storage media, such as, for example, thumb drives, portable optical or magnetic disks, and memory cards. <span class=\"highlight\">Software<\/span> and data used to practice embodiments of the present invention (e.g., <span class=\"highlight\">governance<\/span>relationship program <b>300<\/b>) can be stored on such portable computer readable storage media. In these embodiments, the relevant <span class=\"highlight\">software<\/span> may (or may not) be loaded, in whole or in part, onto persistent storage device <b>210<\/b> via I\/O interface set <b>206<\/b>. I\/O interface set <b>206<\/b> also connects in data communication with display device <b>212<\/b>.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0030]\u00a0Display device <b>212<\/b> provides a mechanism to display data to a user and may be, for example, a computer monitor or a smart phone display screen.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0031]\u00a0The programs described herein are identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature herein is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and\/or implied by such nomenclature.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0032]\u00a0The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2>II. EXAMPLE EMBODIMENT<\/h2>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0033]\u00a0<b>FIG. 2<\/b> shows flowchart <b>250<\/b> depicting a method according to the present invention. <b>FIG. 3<\/b>shows <span class=\"highlight\">governance<\/span> relationship program <b>300<\/b>, which performs at least some of the method operations of flowchart <b>250<\/b>. This method and associated <span class=\"highlight\">software<\/span> will now be discussed, over the course of the following paragraphs, with extensive reference to <b>FIG. 2<\/b> (for the method operation blocks) and <b>FIG. 3<\/b> (for the <span class=\"highlight\">software<\/span> blocks). In this example, John is performing a scientific experiment wherein a thermometer records water temperatures in degrees Fahrenheit, but a later step requires water temperatures in degrees Celsius.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0034]\u00a0Processing begins at operation <b>5255<\/b>, where determine first data asset module (\u201cmod\u201d) <b>302<\/b>determines a first data asset. A data asset is sometimes also called a node or a data set. A first data asset is sometimes also called a current node. A data asset can be a set of related data that is manipulated to determine a result. The use of \u201cfirst\u201d to describe a first data asset does not indicate a relative position of the first data asset in a grouping of data assets; \u201cfirst\u201d is used merely to distinguish a first data asset from other data assets. For example, a \u201cfirst\u201d data asset can be an upstream data asset as compared to a \u201csecond\u201d data asset; however, a \u201cfirst\u201d data asset can also be a downstream data asset as compared to a \u201csecond\u201d data asset. In some embodiments of the present invention, determine first data asset mod <b>302<\/b> determines a first data asset is stored in data asset storage <b>224<\/b>. In this example, determine first data asset mod <b>302<\/b> determines first data asset <b>220<\/b> is a record of water temperatures, recorded in degrees Fahrenheit.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0035]\u00a0Processing proceeds to operation S<b>260<\/b>, where determine rule mod <b>304<\/b> determines a <span class=\"highlight\">governance<\/span> rule for a first data asset. A <span class=\"highlight\">governance<\/span> rule is a restriction of a data asset. A <span class=\"highlight\">governance<\/span> rule is sometimes also called a data quality rule or a first <span class=\"highlight\">governance<\/span> rule. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> rule is a range to which data in a data asset must conform. Alternatively, a <span class=\"highlight\">governance<\/span> rule indicates a different restriction on a data asset including, but not limited to: (i) determining a datum is not null; (ii) determining a datum conforms to a format; (iii) determining a datum is selected from a defined group; (iv) determining a datum is within a range of values; (v) determining a datum contains allowed characters; and\/or (vi) determining a datum conforms to a format requiring special treatment (e.g., a social security number, a credit card number). In some embodiments of the present invention, determine rule mod <b>304<\/b> determines a <span class=\"highlight\">governance<\/span> rule from metadata associated with a first data asset. Alternatively, determine rule mod <b>304<\/b> determines a <span class=\"highlight\">governance<\/span> rule based, at least in part, on a stored <span class=\"highlight\">governance<\/span> rule. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> rule is stored in a location local to a first data asset. Alternatively, a <span class=\"highlight\">governance<\/span> rule is stored in a location remote from a first data asset; for example, a first data asset is stored on data asset sub-system <b>106<\/b>, and a <span class=\"highlight\">governance<\/span> rule is stored on rule storage sub-system <b>108<\/b>. In this example, determine rule mod <b>304<\/b> determines that a data <span class=\"highlight\">governance<\/span> rule is stored in <span class=\"highlight\">governance<\/span> rule storage <b>226<\/b>. Determine rule mod <b>304<\/b> determines that the <span class=\"highlight\">governance<\/span> rule restricts data in the first data asset to values between 32 and 212 (i.e., 32 degrees Fahrenheit and 212 degrees Fahrenheit). This is because the thermometer is measuring the temperature of water.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0036]\u00a0Processing proceeds to operation S<b>265<\/b>, where determine second data asset mod <b>306<\/b>determines a second data asset. The use of \u201csecond\u201d to describe a second data asset does not indicate a relative position of the second data asset in a grouping of data assets; \u201csecond\u201d is used merely to distinguish a second data asset from other data assets. A second data asset is sometimes also called a next node. In some embodiments of the present invention, determine second data asset mod <b>306<\/b> determines a second data asset is stored in data asset storage <b>224<\/b>. In this example, determine second data asset mod <b>306<\/b> determines second data asset <b>222<\/b> is a record of water temperatures, recorded in degrees Celsius.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0037]\u00a0Processing proceeds to operation S<b>270<\/b>, where determine relationship mod <b>308<\/b> determines a relationship between a first data asset and a second data asset. A relationship between two data assets is sometimes also called an edge. In some embodiments of the present invention, a relationship between a first data asset and a second data asset is one of: (i) a direct-write relationship (i.e., the second data asset writes to the first data asset); (ii) an indirect-write relationship (i.e., the second data asset propagates write commands, through one or more intervening data assets, to the first data asset); (iii) a direct-read relationship (i.e., the second data asset reads from the first data asset); or (iv) an indirect-read relationship (i.e., the second data asset propagates read commands, through one or more intervening data assets, to the first data asset). In this example, determine relationship mod <b>308<\/b> determines that second data asset <b>222<\/b> has a direct-read relationship with first data asset <b>220<\/b>.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0038]\u00a0Processing proceeds to operation S<b>275<\/b>, where transform mod <b>310<\/b> transforms a <span class=\"highlight\">governance<\/span>rule. Transform mod <b>310<\/b> transforms a <span class=\"highlight\">governance<\/span> rule into a transformed <span class=\"highlight\">governance<\/span> rule (sometimes also called a second <span class=\"highlight\">governance<\/span> rule) based, at least in part, on a relationship between a first data asset and a second data asset. In some embodiments of the present invention, transform mod <b>310<\/b> determines how a relationship between a first data asset and a second data asset transforms a <span class=\"highlight\">governance<\/span> rule to a transformed <span class=\"highlight\">governance<\/span> rule. In some embodiments of the present invention, transform mod <b>310<\/b> determines how an indirect relationship transforms a <span class=\"highlight\">governance<\/span> rule to a transformed <span class=\"highlight\">governance<\/span> rule. In some embodiments of the present invention, transform mod <b>310<\/b> performs an extract, transform, load process. In some embodiments of the present invention, an extract, transform, load process includes extracting a <span class=\"highlight\">governance<\/span> rule, transforming the <span class=\"highlight\">governance<\/span> rule into a transformed <span class=\"highlight\">governance<\/span> rule, and loading the transformed <span class=\"highlight\">governance<\/span> rule. In some embodiments of the present invention, transform mod <b>310<\/b>extracts a <span class=\"highlight\">governance<\/span> rule from a <span class=\"highlight\">governance<\/span> rule storage. In some embodiments of the present invention, transform mod <b>310<\/b> extracts a <span class=\"highlight\">governance<\/span> rule from a relationship between a first data asset and a second data asset. In some embodiments of the present invention, transform mod <b>310<\/b>extracts a <span class=\"highlight\">governance<\/span> rule from a first data asset. In some embodiments of the present invention, transform mod <b>310<\/b> loads a <span class=\"highlight\">governance<\/span> rule to a <span class=\"highlight\">governance<\/span> rule storage. In some embodiments of the present invention, transform mod <b>310<\/b> loads a <span class=\"highlight\">governance<\/span> rule to a relationship between a first data asset and a second data asset. In some embodiments of the present invention, transform mod <b>310<\/b> loads a <span class=\"highlight\">governance<\/span> rule to a second data asset. In some embodiments of the present invention, transform mod <b>310<\/b> saves a transformed <span class=\"highlight\">governance<\/span> rule to <span class=\"highlight\">governance<\/span> rule storage <b>226<\/b>.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0039]\u00a0In this example, transform mod <b>310<\/b> determines that data in first data asset <b>220<\/b> is converted to data in second data asset <b>222<\/b> by: first, subtracting 32; and, second, dividing by 1.8. Therefore, transform mod <b>310<\/b> transforms the <span class=\"highlight\">governance<\/span> rule, restricting first data asset <b>220<\/b> to a range of 32 to 212, into transformed <span class=\"highlight\">governance<\/span> rule, restricting second data asset <b>222<\/b> to a range of 0 to 100 (i.e., 0 degrees Celsius to 100 degrees Celsius). Alternatively, if a first data asset is in degrees Celsius and a second data asset is in degrees Fahrenheit, transform mod <b>310<\/b> transforms a <span class=\"highlight\">governance<\/span> rule by: first, multiplying by 1.8; and, second, adding 32.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0040]\u00a0In an alternative example, a first data asset is a downstream data asset and a second data asset is an upstream data asset. The second data asset has an indirect-write relationship with the first data asset. Each of the first data asset and second data asset represent dates. The first data asset is a number representing a number of days after a known date; the second data asset is a date in a written format (e.g., Jan. 1, 2016). Data in the second data asset is received as an input and is converted to data in an intermediate data asset, numerical representations of written dates. Data in the intermediate data asset is converted to data in the first data asset. The <span class=\"highlight\">governance<\/span> rule restricts the first data asset to dates after the known date. Therefore, transform mod <b>310<\/b>transforms the <span class=\"highlight\">governance<\/span> rule into the transformed <span class=\"highlight\">governance<\/span> rule by transforming the number representing the known date (e.g., 0) into a numerical representation of the date (e.g., 5845), then transforming the numerical representation of the date into a written date (e.g., Jan. 1, 2016). Therefore, the transformed <span class=\"highlight\">governance<\/span> rule restricts the second data asset to dates after Jan. 1, 2016.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0041]\u00a0Processing terminates at operation <b>5280<\/b>, where apply mod <b>312<\/b> applies a transformed <span class=\"highlight\">governance<\/span> rule to a second data asset. In some embodiments of the present invention, apply mod <b>312<\/b> restricts data in a second data asset based, at least in part, on a transformed <span class=\"highlight\">governance<\/span>rule. In some embodiments of the present invention, restricting data based, at least in part, on a transformed <span class=\"highlight\">governance<\/span> rule includes deleting and\/or eliminating data in a second data asset that violates the transformed <span class=\"highlight\">governance<\/span> rule. In some embodiments of the present invention, restricting data based, at least in part, on a transformed <span class=\"highlight\">governance<\/span> rule includes not permitting new data that violates the transformed <span class=\"highlight\">governance<\/span> rule.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2>III. FURTHER COMMENTS AND\/OR EMBODIMENTS<\/h2>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0042]\u00a0Some embodiments of the present invention recognize the following facts, potential problems, and\/or potential areas for improvement with respect to the current state of the art: (i) data stewards maintaining data assets are prone to mistakes; (ii) maintenance of data assets (sometimes also called data records) is time intensive; and\/or (iii) maintenance of data assets is resource intensive.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0043]\u00a0<b>FIG. 4<\/b> depicts a screenshot of data lineage graph <b>400<\/b>. Data lineage graph <b>400<\/b> contains: production run <b>405<\/b>; staging <b>415<\/b>; and product <b>425<\/b>. Data lineage graph <b>400<\/b> depicts a flow of a datum from a first data asset to a second data asset. The first data asset in data lineage graph <b>400<\/b>is production run <b>405<\/b>. Production run <b>405<\/b> is a table containing various data, including a plant identifications (IDs) <b>410<\/b>, a column in the table. The second data asset in data lineage graph <b>400<\/b> is product <b>425<\/b>. Product <b>425<\/b> is also a table containing various data, including plant <b>430<\/b>, a column in the table. Staging <b>415<\/b> is an export web service that reads data from plant IDs <b>410<\/b> and writes data to plant <b>430<\/b>. Staging <b>415<\/b> also contains lookup table <b>420<\/b>. Lookup table <b>420<\/b> is a table that contains an association between various plant IDs and associated plant names. In this example, plant IDs <b>410<\/b> contains a numerical representation of various plants (e.g., 1, 2, etc.). Staging <b>415<\/b> reads the numerical representation in plant IDs <b>410<\/b>, converts the plant ID to a plant name, and writes the plant name to plant <b>430<\/b>. In this example, plant <b>430<\/b> contains a data quality rule (sometimes also called a data <span class=\"highlight\">governance<\/span> rule) that plant names must be one of: Oregon, Texas, or California. In lookup table <b>420<\/b>: the plant ID for Oregon is 1; the plant ID for Texas is 2; and the plant ID for California is 3. Therefore, staging <b>415<\/b> applies the data quality rule to production run <b>405<\/b> and determines data read from plant IDs <b>410<\/b> must be one of 1, 2, or 3.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0044]\u00a0In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system employs recursive tracing of nodes and\/or edges to determine relationships among various nodes. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system employs computer code based, at least in part, on a pseudo code. One example of pseudo code used by a <span class=\"highlight\">governance<\/span> relationship sub-system is shown in Table 1.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0045]\u00a0<b>FIG. 5<\/b> depicts screenshot <b>500<\/b> showing pseudocode <b>510<\/b>. Pseudocode <b>510<\/b> is pseudocode for traversing edges. In this example, \u201cCurrentNode\u201d is a first data asset, \u201cNextNode\u201d is a related second data asset, and \u201cEdge\u201d is a relationship between \u201cCurrentNode\u201d and \u201cNextNode.\u201d In some embodiments of the present invention, \u201cEdge\u201d is an ETL process. \u201cTraverseEdges\u201d is a recursive process that cascades (sometimes also called propagates) a <span class=\"highlight\">governance<\/span> rule from a first data asset to a second data asset, then determines if the rule should be cascaded to a third data asset. \u201cTraverseEdges\u201d takes a data asset as an argument. First, \u201cTraverseEdges\u201d check if the <span class=\"highlight\">governance<\/span>rule has already been applied to \u201cCurrentNode\u201d using \u201cHasVisited.\u201d \u201cHasVisited\u201d is a process that determines if a data asset has already been processed and takes \u201cCurrentNode\u201d as an argument. If \u201cCurrentNode\u201d has been processed, \u201cTraverseEdges\u201d is completed and processing returns to the process that called \u201cTraverseEdges.\u201d \u201cTraverseEdges\u201d then determines that \u201cCurrentNode\u201d has a set of \u201cEdges\u201d and a set of \u201cNextNodes.\u201d If \u201cCurrentNode\u201d does not have a set of edges or if \u201cCurrentNode\u201d does not have a set of \u201cNextNodes,\u201d \u201cTraverseEdges\u201d is completed and processing returns to the process that called \u201cTraverseEdges.\u201d \u201cTraverseEdges\u201d then checks if \u201cCurrentNode\u201d has a <span class=\"highlight\">governance<\/span> rule using \u201cHasRule.\u201d \u201cHasRule\u201d is a process that determines if a data asset has a <span class=\"highlight\">governance<\/span> rule. If \u201cCurrentNode\u201d does have a <span class=\"highlight\">governance<\/span> rule, \u201cTraverseEdges\u201d calls \u201cApplyRule.\u201d \u201cApplyRule\u201d is a process that applies a <span class=\"highlight\">governance<\/span> rule from a first data asset to a second data asset. In some embodiments of the present invention, \u201cApplyRule\u201d is an ETL process. \u201cApplyRule\u201d takes three arguments: (i) \u201cCurrentNode\u201d; (ii) \u201cEdge\u201d; and (iii) \u201cNextNode.\u201d \u201cApplyRule\u201d takes the <span class=\"highlight\">governance<\/span> rule from \u201cCurrentNode,\u201d transforms the <span class=\"highlight\">governance<\/span> rule using \u201cEdge,\u201d then applies transformed <span class=\"highlight\">governance<\/span> rule to \u201cNextNode.\u201d \u201cTraverseEdges\u201d then calls itself to cascade <span class=\"highlight\">governance<\/span> rules through the set of related data assets.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0046]\u00a0In some embodiments of the present invention, traversing an edge is a recursive manner of checking a set of nodes to determine relationships among the nodes. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system ensures nodes are not processed multiple times. In some embodiments of the present invention, a <span class=\"highlight\">governances<\/span> relationship sub-system applies a rule from a current node to a next node. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system applies a rule recursively over a lineage graph. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system displays a set of nodes as a lineage graph.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0047]\u00a0In some embodiments of the present invention, a data asset has a quality <span class=\"highlight\">governance<\/span> rule regarding format of data. In this example, a <span class=\"highlight\">governance<\/span> rule requires that ninety percent (90%) of data values in a data asset must be of the pattern \u201cx@y,\u201d wherein each of \u201cx\u201d and \u201cy\u201d are non-null strings. A function of this type is sometimes called a concatenation function. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> rule is applied to a concatenation function containing more than two arguments. To achieve the ninety percent quality required, a <span class=\"highlight\">governance<\/span> relationship sub-system applies the <span class=\"highlight\">governance<\/span> rule to the data assets \u201cx\u201d and \u201cy.\u201d Various possible combinations exist for applying <span class=\"highlight\">governance<\/span> rules to \u201cx\u201d and \u201cy,\u201d including, but not limited to: (i) one hundred percent (100%) of data values in data asset \u201cx\u201d must be non-null strings and ninety percent (90%) of data values in data asset \u201cy\u201d must be non-null strings; (ii) ninety percent (90%) of data values in data asset \u201cx\u201d must be non-null strings and one hundred percent (100%) of data values in data asset \u201cy\u201d must be non-null strings; and (iii) ninety-five percent (95%) of data values in data asset \u201cx\u201d must be non-null strings and ninety-five percent (95%) of data values in data asset \u201cy\u201d must be non-null strings. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system applies <span class=\"highlight\">governance<\/span> rules related to various concatenation functions to various data assets.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0048]\u00a0In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> rule relates to unit conversion. In this example, a <span class=\"highlight\">governance<\/span> rule requires temperatures in the range of 0 degrees Celsius to 100 degrees Celsius. To achieve the required data quality, a <span class=\"highlight\">governance<\/span> relationship sub-system applies an ETL process containing a conversion function, converting values from degrees Fahrenheit to degrees Celsius. The <span class=\"highlight\">governance<\/span> relationship sub-system applies the <span class=\"highlight\">governance<\/span> rule to the upstream data asset (the temperatures in degrees Fahrenheit), requiring that each value be in the range of 32 degrees Fahrenheit to 212 degrees Fahrenheit. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system applies <span class=\"highlight\">governance<\/span>rules related to various conversion functions to various data assets.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0049]\u00a0In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> rule relates to a lookup function. In this example, a <span class=\"highlight\">governance<\/span> rule requires a two letter country code selected from a group consisting of: DE, FR, UK, and US. For example, these countries are locations of manufacturing plants for a company. To achieve the required data quality, a <span class=\"highlight\">governance<\/span>relationship sub-system applies an ETL process containing a lookup function, to determine a corresponding numerical representation for each of the two letter country codes (e.g., DE is 1, FR is 2, UK is 3, and US is 4). The <span class=\"highlight\">governance<\/span> relationship sub-system applies the <span class=\"highlight\">governance<\/span> rule to the corresponding data asset, in which the numerical representations for each country are used, requiring that each value be selected from a group consisting of: 1, 2, 3, and 4. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system applies <span class=\"highlight\">governance<\/span>rules related to various lookup functions to various data assets.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0050]\u00a0In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> rule relates to a pivot function. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system uses a pivot function in combination with a conversion function and\/or a lookup function. In this example, a company has employees in various countries around the world. On a data asset containing a list of all employees, the country of each employee, and the salary of each employee, a <span class=\"highlight\">governance<\/span> rule requires a salary to be of the format \u201c$dddd.dd.\u201d Based, at least in part, on the country of the employee, a <span class=\"highlight\">governance<\/span> relationship sub-system applies an ETL function to pivot the salary column from various currencies to U.S. dollars. Additionally, based at least in part, on the country of the employee, a <span class=\"highlight\">governance<\/span> relationship sub-system applies an ETL function to pivot the <span class=\"highlight\">governance<\/span> rule format of \u201c$dddd.dd\u201d to various other currencies (e.g., [see pdf for image] eeee.ee, \u00a3pppp.pp, etc.). In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span>relationship sub-system takes a first data asset and converts it to a second data asset. For example, the first data asset is a table with the columns: name, salary, and country. A <span class=\"highlight\">governance<\/span>relationship sub-system converts this first data asset to a second data asset with the columns: name, salary in Germany, salary in France, salary in the United Kingdom, and salary in the United States.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0051]\u00a0In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> rule relates to a merge and join function. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system uses a merge and join function in combination with a concatenation function. In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> relationship sub-system uses a merge and join function to combine two data assets into a single data asset. For example, a first data asset is a table with the columns: name, age, email, and address; a second data asset is a table with the columns: name, credit rating, and orders. A <span class=\"highlight\">governance<\/span> relationship sub-system would apply a merge and join function to create a single data asset with the columns: name, age, email, address, credit rating, and orders. Additionally, if any of the names in the first data asset and the names in the second data asset match up those entries are combined.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0052]\u00a0In some embodiments of the present invention, a <span class=\"highlight\">governance<\/span> rule employs a combination of one or more of the above functions to apply a <span class=\"highlight\">governance<\/span> rule to a data asset.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0053]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) reducing time required to establish data assets; (ii) reducing resources required to establish data assets; (iii) reducing time required to maintain data assets; (iv) reducing resources required to maintain data assets; and\/or (v) reducing a likelihood of errors in maintaining data assets.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0054]\u00a0In some embodiments of the present invention, a data asset exists within a larger data flow. In some embodiments of the present invention, an upstream process describes an upstream data asset writing information to a downstream data asset. In some embodiments of the present invention, a downstream process describes an downstream data asset reading information from an upstream data asset.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0055]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) an \u201cextract, transform, load\u201d (ETL) job; (ii) an ETL job reading from an operational system; (iii) an ETL job writing to a data warehouse; (iv) a data lifecycle management tool; (v) a data lifecycle management tool reading from a warehouse; and\/or (vi) a data lifecycle management tool creating a set of test data.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0056]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) a reporting cube; (ii) a reporting cube reading from a data mart; (iii) a reporting cube enabling data analytics; (iv) a data lineage graph; (v) a data lineage graph depicting a set of upstream processes; (vi) a data lineage graph depicting a set of upstream data assets; (vii) a data lineage graph depicting a set of downstream processes; (viii) a data lineage graph depicting a set of downstream data asset; (ix) a data lineage graph depicting upstream processes that write to a data asset; and\/or (x) a data lineage graph depicting downstream processes that read from a data asset.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0057]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) locating a data asset within a data lineage graph; (ii) locating a data asset with a <span class=\"highlight\">governance<\/span> rule; (iii) applying a <span class=\"highlight\">governance<\/span> rule to a downstream data asset; (iv) applying a <span class=\"highlight\">governance<\/span> rule to an upstream data asset; (v) examining a relationship between two data assets; (vi) transforming a <span class=\"highlight\">governance<\/span> rule; (vii) transforming a <span class=\"highlight\">governance<\/span> rule based, at least in part, on a relationship between two data assets; (viii) adjusting a <span class=\"highlight\">governance<\/span> rule based, at least in part, on a manipulation of a first data asset into a second data asset; and\/or (ix) recursively applying <span class=\"highlight\">governance<\/span> rules to related data assets. In some embodiments of the present invention, recursive application of a <span class=\"highlight\">governance<\/span> rule involves applying a <span class=\"highlight\">governance<\/span> rule to a set of data assets, wherein each sequential data asset exists in a direct-read relationship with the prior data asset. In some embodiments of the present invention, recursive application of a <span class=\"highlight\">governance<\/span>rule involves applying a <span class=\"highlight\">governance<\/span> rule to a set of data assets, wherein each sequential data asset exists in a direct-write relationship with the prior data asset.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0058]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) analyzing a data lineage; (ii) applying a <span class=\"highlight\">governance<\/span>rule to a data asset; (iii) moving data among a set of data assets; (iv) transforming data among a set of data assets; (v) scaling an ETL platform; (vi) applying a <span class=\"highlight\">governance<\/span> rule to a data asset; (vii) using a set of stages to create jobs; (viii) moving data from a source data asset to a target data asset; (ix) capturing a set of jobs involved in moving data; (x) capturing a set of data assets involved in moving data; and\/or (xi) displaying jobs in a data lineage graph.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0059]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) using a data lineage graph to find an upstream job from a data asset; (ii) using a data lineage graph to find a downstream job from a data asset; (iii) analyzing a set of stages of a job (sometimes also called a process); (iv) analyzing a set of stages of a job to understand a nature of the job; (v) analyzing a <span class=\"highlight\">governance<\/span> rule to understand a meaning of the <span class=\"highlight\">governance<\/span> rule; and\/or (vi) deducing a <span class=\"highlight\">governance<\/span> rule for a related data asset in a data lineage graph.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0060]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) defining a key attribute of a <span class=\"highlight\">governance<\/span> rule; (ii) determining a set of data assets having <span class=\"highlight\">governance<\/span> rules; (iii) invoking a lineage to create a data lineage graph; (iii) applying a pseudo code; and\/or (iv) applying a pseudo code to process a data lineage graph. In some embodiments of the present invention, a key attribute of a <span class=\"highlight\">governance<\/span> rule is a quality rule. Alternatively, a key attribute of a <span class=\"highlight\">governance<\/span> rule includes, but is not limited to: (i) a security rule; and\/or (ii) a lifecycle rule.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0061]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) a data lineage graph consisting of a set of nodes (sometimes also called data assets); (ii) a data lineage graph consisting of a set of edges (sometimes also called relationships among data assets); (iii) a <span class=\"highlight\">governance<\/span> relationship sub-system tracing a data lineage graph; (iv) a <span class=\"highlight\">governance<\/span> relationship sub-system determining an upstream data asset to be <span class=\"highlight\">governed<\/span>; (v) a <span class=\"highlight\">governance<\/span> relationship sub-system determining a downstream data asset to be <span class=\"highlight\">governed<\/span>; (vi) a <span class=\"highlight\">governance<\/span> relationship sub-system determining a <span class=\"highlight\">governance<\/span> rule to be applied to fulfil a set of <span class=\"highlight\">governance<\/span> requirements; (vii) a <span class=\"highlight\">governance<\/span>relationship sub-system invoking a data lineage; and\/or (viii) a <span class=\"highlight\">governance<\/span> relationship sub-system producing a data lineage graph.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0062]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) finding a data lineage graph for a data asset; (ii) applying a <span class=\"highlight\">governance<\/span> rule to a data asset; (iii) applying a <span class=\"highlight\">governance<\/span> rule from a second data asset to a first data asset; (iv) applying a <span class=\"highlight\">governance<\/span> rule from a second data asset to a first data asset, based, at least in part, on a data lineage graph; (v) adapting a <span class=\"highlight\">governance<\/span> rule based, at least in part, on a transformation in a data lineage graph; and\/or (vi) adapting a <span class=\"highlight\">governance<\/span> rule based, at least in part, on a transformation from a first data asset to a second data asset.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0063]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) assigning <span class=\"highlight\">governance<\/span> rules to data assets in a regulatory report; (ii) invoking a data lineage for a data asset in a regulatory report; (iii) finding an ETL process for a data asset in a regulatory report; (iv) finding an upstream data asset in a regulatory report; (v) finding a downstream data asset in a regulatory report; (vi) analyzing an upstream ETL process in a regulatory report; (vii) analyzing a downstream ETL process in a regulatory report; (viii) adjusting a <span class=\"highlight\">governance<\/span> rule of a regulatory report; (ix) assigning an adjusted <span class=\"highlight\">governance<\/span> rule to an upstream asset; and\/or (x) assigning an adjusted <span class=\"highlight\">governance<\/span> rule to an downstream asset.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0064]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) adhering to financial regulations; (ii) adhering to banking regulations (e.g., Basel III); and\/or (iii) reducing effort to adhere to regulations.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0065]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) using data lineage to propagate data quality rules; (ii) using data lineage to transform data quality rules; (iii) using ETL analysis to determine a set of related assets; (iv) using data lineage graph analysis to determine a set of related assets; (v) modifying a set of related assets; (vi) modifying a set of <span class=\"highlight\">governance<\/span> rules; and\/or (vii) determining a set of <span class=\"highlight\">governance<\/span> rules for a business.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0066]\u00a0Some embodiments of the present invention may include one, or more, of the following features, characteristics, and\/or advantages: (i) maintaining a data lineage graph; (ii) maintaining a data lineage graph that identifies a set of related data assets; (iii) identifying a set of related data assets based on an upstream process; (iv) identifying a set of related data assets based on a downstream process; (v) applying a <span class=\"highlight\">governance<\/span> rule to a related data asset; (vi) applying a transformed <span class=\"highlight\">governance<\/span> rule (sometimes also called a modified <span class=\"highlight\">governance<\/span> rule) to a related data asset; (vii) determining a set of <span class=\"highlight\">governance<\/span> rules for a set of related assets; and\/or (viii) determining a set of <span class=\"highlight\">governance<\/span> rules for a set of related assets, wherein each asset in the set of related assets is related to each other asset in the set of related assets.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2>IV. DEFINITIONS<\/h2>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0067]\u00a0\u201cPresent invention\u201d does not create an absolute indication and\/or implication that the described subject matter is covered by the initial set of claims, as filed, by any as-amended set of claims drafted during prosecution, and\/or by the final set of claims allowed through patent prosecution and included in the issued patent. The term \u201cpresent invention\u201d is used to assist in indicating a portion or multiple portions of the disclosure that might possibly include an advancement or multiple advancements over the state of the art. This understanding of the term \u201cpresent invention\u201d and the indications and\/or implications thereof are tentative and provisional and are subject to change during the course of patent prosecution as relevant information is developed and as the claims may be amended.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0068]\u00a0\u201cEmbodiment,\u201d see the definition for \u201cpresent invention.\u201d<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0069]\u00a0\u201cAnd\/or\u201d is the inclusive disjunction, also known as the logical disjunction and commonly known as the \u201cinclusive or.\u201d For example, the phrase \u201cA, B, and\/or C,\u201d means that at least one of A or B or C is true; and \u201cA, B, and\/or C\u201d is only false if each of A and B and C is false.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0070]\u00a0A \u201cset of\u201d items means there exists one or more items; there must exist at least one item, but there can also be two, three, or more items. A \u201csubset of\u201d items means there exists one or more items within a grouping of items that contain a common characteristic.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0071]\u00a0A \u201cplurality of\u201d items means there exists at more than one item; there must exist at least two items, but there can also be three, four, or more items.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0072]\u00a0\u201cIncludes\u201d and any variants (e.g., including, include, etc.) means, unless explicitly noted otherwise, \u201cincludes, but is not necessarily limited to.\u201d<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0073]\u00a0A \u201cuser\u201d or a \u201csubscriber\u201d includes, but is not necessarily limited to: (i) a single individual human; (ii) an artificial intelligence entity with sufficient intelligence to act in the place of a single individual human or more than one human; (iii) a business entity for which actions are being taken by a single individual human or more than one human; and\/or (iv) a combination of any one or more related \u201cusers\u201d or \u201csubscribers\u201d acting as a single \u201cuser\u201d or \u201csubscriber.\u201d<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0074]\u00a0The terms \u201creceive,\u201d \u201cprovide,\u201d \u201csend,\u201d \u201cinput,\u201d \u201coutput,\u201d and \u201creport\u201d should not be taken to indicate or imply, unless otherwise explicitly specified: (i) any particular degree of directness with respect to the relationship between an object and a subject; and\/or (ii) a presence or absence of a set of intermediate components, intermediate actions, and\/or things interposed between an object and a subject.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0075]\u00a0A \u201cmodule\u201d is any set of hardware, firmware, and\/or <span class=\"highlight\">software<\/span> that operatively works to do a function, without regard to whether the module is: (i) in a single local proximity; (ii) distributed over a wide area; (iii) in a single proximity within a larger piece of <span class=\"highlight\">software<\/span> code; (iv) located within a single piece of <span class=\"highlight\">software<\/span> code; (v) located in a single storage device, memory, or medium; (vi) mechanically connected; (vii) electrically connected; and\/or (viii) connected in data communication. A \u201csub-module\u201d is a \u201cmodule\u201d within a \u201cmodule.\u201d<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0076]\u00a0A \u201ccomputer\u201d is any device with significant data processing and\/or machine readable instruction reading capabilities including, but not necessarily limited to: desktop computers; mainframe computers; laptop computers; field-programmable gate array (FPGA) based devices; smart phones; personal digital assistants (PDAs); body-mounted or inserted computers; embedded device style computers; and\/or application-specific integrated circuit (ASIC) based devices.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0077]\u00a0\u201cElectrically connected\u201d means either indirectly electrically connected such that intervening elements are present or directly electrically connected. An \u201celectrical connection\u201d may include, but need not be limited to, elements such as capacitors, inductors, transformers, vacuum tubes, and the like.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0078]\u00a0\u201cMechanically connected\u201d means either indirect mechanical connections made through intermediate components or direct mechanical connections. \u201cMechanically connected\u201d includes rigid mechanical connections as well as mechanical connection that allows for relative motion between the mechanically connected components. \u201cMechanically connected\u201d includes, but is not limited to: welded connections; solder connections; connections by fasteners (e.g., nails, bolts, screws, nuts, hook-and-loop fasteners, knots, rivets, quick-release connections, latches, and\/or magnetic connections); force fit connections; friction fit connections; connections secured by engagement caused by gravitational forces; pivoting or rotatable connections; and\/or slidable mechanical connections.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0079]\u00a0A \u201cdata communication\u201d includes, but is not necessarily limited to, any sort of data communication scheme now known or to be developed in the future. \u201cData communications\u201d include, but are not necessarily limited to: wireless communication; wired communication; and\/or communication routes that have wireless and wired portions. A \u201cdata communication\u201d is not necessarily limited to: (i) direct data communication; (ii) indirect data communication; and\/or (iii) data communication where the format, packetization status, medium, encryption status, and\/or protocol remains constant over the entire course of the data communication.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0080]\u00a0The phrase \u201cwithout substantial human intervention\u201d means a process that occurs automatically (often by operation of machine logic, such as <span class=\"highlight\">software<\/span>) with little or no human input. Some examples that involve \u201cno substantial human intervention\u201d include: (i) a computer is performing complex processing and a human switches the computer to an alternative power supply due to an outage of grid power so that processing continues uninterrupted; (ii) a computer is about to perform resource intensive processing and a human confirms that the resource-intensive processing should indeed be undertaken (in this case, the process of confirmation, considered in isolation, is with substantial human intervention, but the resource intensive processing does not include any substantial human intervention, notwithstanding the simple yes-no style confirmation required to be made by a human); and (iii) using machine logic, a computer has made a weighty decision (for example, a decision to ground all airplanes in anticipation of bad weather), but, before implementing the weighty decision the computer must obtain simple yes-no style confirmation from a human source.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0081]\u00a0\u201cAutomatically\u201d means \u201cwithout any human intervention.\u201d<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" valign=\"top\">\n<div class=\"para_text\">[0082]\u00a0The term \u201creal time\u201d includes any time frame of sufficiently short duration as to provide reasonable response time for information processing as described. Additionally, the term \u201creal time\u201d includes what is commonly termed \u201cnear real time,\u201d generally any time frame of sufficiently short duration as to provide reasonable response time for on-demand information processing as described (e.g., within a portion of a second or within a few seconds). These terms, while difficult to precisely define, are well understood by those skilled in the art.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"para_text\">\n<table border=\"0\" width=\"95%\" rules=\"none\">\n<colgroup span=\"1\">\n<col span=\"1\" width=\"3%\" \/>\n<col span=\"1\" width=\"62%\" \/>\n<col span=\"1\" width=\"30%\" \/><\/colgroup>\n<tbody>\n<tr>\n<td class=\"inid_text\" colspan=\"1\" rowspan=\"1\">(57)<a name=\"claim\" shape=\"rect\"><\/a><\/td>\n<td class=\"table_data\" colspan=\"1\" rowspan=\"1\">\n<h2>Claims<\/h2>\n<\/td>\n<\/tr>\n<tr>\n<td class=\"para_text\" colspan=\"3\" rowspan=\"1\" valign=\"top\"><a name=\"CLM-00001\" shape=\"rect\"><\/a><\/p>\n<div class=\"claim_text\">1. A method comprising:<\/p>\n<div class=\"claim_text\">displaying a plurality of data assets from a data asset storage as a data lineage graph;<\/div>\n<div class=\"claim_text\">determining a first relationship between a first data asset in the plurality of data assets and a second data asset in the plurality of data assets is a direct-read relationship;<\/div>\n<div class=\"claim_text\">determining a first <span class=\"highlight\">governance<\/span> rule applied to the first data asset, wherein the first <span class=\"highlight\">governance<\/span>rule relates to a lookup function;<\/div>\n<div class=\"claim_text\">transforming the first <span class=\"highlight\">governance<\/span> rule into a second <span class=\"highlight\">governance<\/span> rule based, at least in part, on the first relationship, wherein the second <span class=\"highlight\">governance<\/span> rule relates to a pivot function;<\/div>\n<div class=\"claim_text\">applying the second <span class=\"highlight\">governance<\/span> rule to the second data asset;<\/div>\n<div class=\"claim_text\">determining a second relationship between the second data asset and a third data asset in the plurality of data assets is an indirect-write relationship;<\/div>\n<div class=\"claim_text\">transforming the second <span class=\"highlight\">governance<\/span> rule into a third <span class=\"highlight\">governance<\/span> rule based, at least in part, on the second relationship, wherein the third <span class=\"highlight\">governance<\/span> rule relates to a merge and join function;<\/div>\n<div class=\"claim_text\">applying the third <span class=\"highlight\">governance<\/span> rule to the third data asset;<\/div>\n<div class=\"claim_text\">identifying the first data asset, the second data asset, and the third data asset on the data lineage graph; and<\/div>\n<div class=\"claim_text\">storing the first <span class=\"highlight\">governance<\/span> rule, the second <span class=\"highlight\">governance<\/span> rule, and the third <span class=\"highlight\">governance<\/span> rule to a <span class=\"highlight\">governance<\/span> rule storage;<\/div>\n<div class=\"claim_text\">wherein:<\/p>\n<div class=\"claim_text\">at least determining the first relationship between the first data asset and the second data asset is performed by computer <span class=\"highlight\">software<\/span> running on computer hardware.<\/div>\n<\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<table border=\"0\" width=\"40%\" rules=\"none\" align=\"center\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\" align=\"center\" width=\"20%\">*<\/td>\n<td colspan=\"1\" rowspan=\"1\" align=\"center\" width=\"20%\">*<\/td>\n<td colspan=\"1\" rowspan=\"1\" align=\"center\" width=\"20%\">*<\/td>\n<td colspan=\"1\" rowspan=\"1\" align=\"center\" width=\"20%\">*<\/td>\n<td colspan=\"1\" rowspan=\"1\" align=\"center\" width=\"20%\">*<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>LENS source. (54) ESTABLISHING GOVERNANCE RULES OVER DATA ASSETS (75) Inventor: International Business Machines Corporation, \u00a0Armonk, NY (US) (73) Assignee: International Business Machines Corporation, \u00a0Armonk, NY (US),\u00a0Type:\u00a0US Company (*) Notice: Subject to any disclaimer, the term of this patent is extended or adjusted under 35 U.S.C. 154(b) by 0 days. (21) Appl. No.: 15\/014,329 (22) &hellip; <a href=\"https:\/\/arielsheen.com\/index.php\/2019\/04\/10\/establishing-governance-rules-over-data-assets\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Establishing Governance Rules Over Data Assets&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[111,102],"tags":[],"class_list":["post-5861","post","type-post","status-publish","format-standard","hentry","category-legal","category-phd"],"jetpack_publicize_connections":[],"acf":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8e7kf-1wx","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/posts\/5861","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/comments?post=5861"}],"version-history":[{"count":1,"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/posts\/5861\/revisions"}],"predecessor-version":[{"id":5862,"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/posts\/5861\/revisions\/5862"}],"wp:attachment":[{"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/media?parent=5861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/categories?post=5861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arielsheen.com\/index.php\/wp-json\/wp\/v2\/tags?post=5861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}