Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 8.702278137207031e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 10.594100713729858s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.6172723770141602s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00037598609924316406s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.2636184692382812e-05s
INFO | --- Analysis for 0080-3626 took 114.94330859184265s
Availability | SPARQL endpoint availability check for 土地利用图 took 8.606910705566406e-05s
Availability | VoID file availability check for 土地利用图 took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for 土地利用图 took 10.099939107894897s
Reputation | Calculation of the PageRank for 土地利用图 took 0.022168874740600586s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 2.6702880859375e-05s
Believability | Calculation of trust value for 土地利用图 took 1.239776611328125e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 112.66832566261292s
Availability | SPARQL endpoint availability check for 113322 took 4.1484832763671875e-05s
Availability | VoID file availability check for 113322 took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for 113322 took 10.101838827133179s
Reputation | Calculation of the PageRank for 113322 took 0.020247697830200195s
Interlinking | Calculation of Degree of Connection for 113322 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.7179718017578125e-05s
Believability | Calculation of trust value for 113322 took 1.2636184692382812e-05s
INFO | --- Analysis for 11 took 112.87161993980408s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.0531158447265625e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.00030159950256347656s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 10.092620134353638s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.361701965332031e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.2874603271484375e-05s
INFO | --- Analysis for 12323 took 112.67249703407288s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 8.654594421386719e-05s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 10.097049713134766s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.940696716308594e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 7.867813110351562e-06s
INFO | --- Analysis for 2000-us-census-rdf took 111.37443995475769s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 8.344650268554688e-05s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 10.095021724700928s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.4809112548828125e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 1.239776611328125e-05s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 111.7658531665802s
Availability | SPARQL endpoint availability check for Open Data Web took 6.628036499023438e-05s
Availability | VoID file availability check for Open Data Web took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Open Data Web took 10.10321044921875s
Reputation | Calculation of the PageRank for Open Data Web took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.123283386230469e-05s
Believability | Calculation of trust value for Open Data Web took 1.2636184692382812e-05s
INFO | --- Analysis for _data.odw.tw took 112.17715311050415s
Availability | SPARQL endpoint availability check for 土地利用 took 4.267692565917969e-05s
Availability | VoID file availability check for 土地利用 took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for 土地利用 took 10.601158380508423s
Reputation | Calculation of the PageRank for 土地利用 took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.7670135498046875e-05s
Believability | Calculation of trust value for 土地利用 took 7.62939453125e-06s
INFO | --- Analysis for _data1.odw.tw took 111.97021484375s
Availability | SPARQL endpoint availability check for 土地利用模型 took 6.771087646484375e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 10.085727214813232s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020153284072875977s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.86102294921875e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.2636184692382812e-05s
INFO | --- Analysis for _data2.odw.tw took 111.40445637702942s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.172325134277344e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0011069774627685547s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 10.096341371536255s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.3909759521484375e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 112.84231781959534s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 8.511543273925781e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.00127410888671875s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 10.090717315673828s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.0040740966796875e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.239776611328125e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 112.46890640258789s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.1961669921875e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 10.094042778015137s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.021360397338867188s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.4809112548828125e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 1.2636184692382812e-05s
INFO | --- Analysis for A1 took 111.26982021331787s
Availability | SPARQL endpoint availability check for SummerOlympics took 7.390975952148438e-05s
Availability | VoID file availability check for SummerOlympics took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for SummerOlympics took 10.094964027404785s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 7.081031799316406e-05s
Believability | Calculation of trust value for SummerOlympics took 1.1920928955078125e-05s
INFO | --- Analysis for abc took 111.3354115486145s
Availability | SPARQL endpoint availability check for Test_m took 4.1961669921875e-05s
Availability | VoID file availability check for Test_m took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Test_m took 10.092217445373535s
Reputation | Calculation of the PageRank for Test_m took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for Test_m took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.314018249511719e-05s
Believability | Calculation of trust value for Test_m took 1.3113021850585938e-05s
INFO | --- Analysis for ABC took 111.97823119163513s
Availability | SPARQL endpoint availability check for my intro took 8.606910705566406e-05s
Availability | VoID file availability check for my intro took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for my intro took 10.092186212539673s
Reputation | Calculation of the PageRank for my intro took 0.020056486129760742s
Interlinking | Calculation of Degree of Connection for my intro took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for my intro took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for my intro took 2.6226043701171875e-05s
Believability | Calculation of trust value for my intro took 1.2159347534179688e-05s
INFO | --- Analysis for abhay_intro took 111.26163053512573s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 4.220008850097656e-05s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 10.20264196395874s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010442733764648438s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for abs-linked-data took 111.47580218315125s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 4.38690185546875e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 10.195799112319946s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.7894973754882812e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.1444091796875e-05s
INFO | --- Analysis for academic-offer-of-unl took 112.13985466957092s
Availability | SPARQL endpoint availability check for AcadOnto took 6.580352783203125e-05s
Availability | VoID file availability check for AcadOnto took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for AcadOnto took 10.101464986801147s
Reputation | Calculation of the PageRank for AcadOnto took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.86102294921875e-05s
Believability | Calculation of trust value for AcadOnto took 1.33514404296875e-05s
INFO | --- Analysis for acadonto took 111.33985209465027s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.298324584960938e-05s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 10.100252151489258s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.021409988403320312s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.315376281738281e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for acorn-sat took 111.27859258651733s
Availability | SPARQL endpoint availability check for Addgene took 8.606910705566406e-05s
Availability | VoID file availability check for Addgene took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Addgene took 10.104152917861938s
Reputation | Calculation of the PageRank for Addgene took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for Addgene took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0009322166442871094s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.291534423828125e-05s
Believability | Calculation of trust value for Addgene took 1.1920928955078125e-05s
INFO | --- Analysis for addgene took 111.26506638526917s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 6.699562072753906e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 10.10649847984314s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 3.62396240234375e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 0.00010061264038085938s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.1920928955078125e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 111.67138624191284s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 8.58306884765625e-05s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 10.102036476135254s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.0226132869720459s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0008859634399414062s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.719329833984375e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.2874603271484375e-05s
INFO | --- Analysis for aemet took 111.43934726715088s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 6.556510925292969e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 10.103443384170532s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.020061254501342773s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.218650817871094e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 1.2636184692382812e-05s
INFO | --- Analysis for agenda-de-zaragoza took 111.66896176338196s
Availability | SPARQL endpoint availability check for AgriNepalData took 4.4345855712890625e-05s
Availability | VoID file availability check for AgriNepalData took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for AgriNepalData took 10.09965467453003s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020071029663085938s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.510185241699219e-05s
Believability | Calculation of trust value for AgriNepalData took 1.4066696166992188e-05s
INFO | --- Analysis for agrinepaldata took 111.4757227897644s
Availability | SPARQL endpoint availability check for AGRIS took 8.702278137207031e-05s
Availability | VoID file availability check for AGRIS took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for AGRIS took 10.201130628585815s
Reputation | Calculation of the PageRank for AGRIS took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.058547973632812e-05s
Believability | Calculation of trust value for AGRIS took 1.33514404296875e-05s
INFO | --- Analysis for agris took 111.43871974945068s
Availability | SPARQL endpoint availability check for AGROVOC took 5.221366882324219e-05s
Availability | VoID file availability check for AGROVOC took 0.004014492034912109s
Completeness | Calculation of interlinking completeness for AGROVOC took 10.096839904785156s
Reputation | Calculation of the PageRank for AGROVOC took 0.022437095642089844s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011014938354492188s
Believability | Calculation of trust value for AGROVOC took 1.1920928955078125e-05s
INFO | --- Analysis for agrovoc took 111.27359509468079s
Availability | SPARQL endpoint availability check for AGROVOC took 7.104873657226562e-05s
Availability | VoID file availability check for AGROVOC took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for AGROVOC took 10.095566511154175s
Reputation | Calculation of the PageRank for AGROVOC took 0.022504329681396484s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.9604644775390625e-05s
Believability | Calculation of trust value for AGROVOC took 1.2874603271484375e-05s
INFO | --- Analysis for agrovoc-skos took 111.53066945075989s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 4.00543212890625e-05s
Availability | VoID file availability check for Analytics India Magazine took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 10.100773096084595s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.457069396972656e-05s
Believability | Calculation of trust value for Analytics India Magazine took 1.2874603271484375e-05s
INFO | --- Analysis for AIM took 111.37151908874512s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.220008850097656e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0003135204315185547s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 10.093662738800049s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.3855438232421875e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.1920928955078125e-05s
INFO | --- Analysis for AISHE took 111.3420078754425s
Availability | SPARQL endpoint availability check for  equipment ontology took 8.845329284667969e-05s
Availability | VoID file availability check for  equipment ontology took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for  equipment ontology took 10.094758033752441s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for  equipment ontology took 1.3113021850585938e-05s
INFO | --- Analysis for akash took 111.36943483352661s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 8.678436279296875e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 10.101424217224121s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.02249312400817871s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 1.239776611328125e-05s
INFO | --- Analysis for aksworg took 111.27347254753113s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.267692565917969e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 10.102297306060791s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.9325485229492188e-05s
Believability | Calculation of trust value for AlchemyAPI took 8.106231689453125e-06s
INFO | --- Analysis for alchemyapi took 111.37023854255676s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 8.869171142578125e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 10.097484588623047s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.6941299438476562e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 6.9141387939453125e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 111.54408144950867s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.8532474040985107s
Availability | VoID file availability check for aliada-scanbit-net took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 10.088886022567749s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02188396453857422s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.0001049041748046875s
Believability | Calculation of trust value for aliada-scanbit-net took 1.33514404296875e-05s
INFO | --- Analysis for aliada-scanbit-net took 113.78182554244995s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.5299530029296875e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 10.179624795913696s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.020072460174560547s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.0994415283203125e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 8.344650268554688e-06s
INFO | --- Analysis for allen-brain-atlas took 115.92538619041443s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 8.654594421386719e-05s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 10.107195615768433s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02018570899963379s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 6.0558319091796875e-05s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 8.344650268554688e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 314.77474188804626s
Availability | SPARQL endpoint availability check for Alojamientos took 0.00011038780212402344s
Availability | VoID file availability check for Alojamientos took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for Alojamientos took 125.52808785438538s
Reputation | Calculation of the PageRank for Alojamientos took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.695487976074219e-05s
Believability | Calculation of trust value for Alojamientos took 1.33514404296875e-05s
INFO | --- Analysis for alojamientos-zaragoza took 308.3642826080322s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 8.726119995117188e-05s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 10.175772905349731s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.600120544433594e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.3828277587890625e-05s
INFO | --- Analysis for alpino-rdf took 112.54863834381104s
Availability | SPARQL endpoint availability check for AAT-atawil took 0.00013017654418945312s
Availability | VoID file availability check for AAT-atawil took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for AAT-atawil took 10.547713279724121s
Reputation | Calculation of the PageRank for AAT-atawil took 0.021164894104003906s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 2.8848648071289062e-05s
Believability | Calculation of trust value for AAT-atawil took 1.239776611328125e-05s
INFO | --- Analysis for Altawil took 112.96659898757935s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 8.702278137207031e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 10.104955434799194s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020173311233520508s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 2.6464462280273438e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 1.2874603271484375e-05s
INFO | --- Analysis for am-collections-online took 112.46826720237732s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.315376281738281e-05s
Availability | VoID file availability check for Amer Nejma took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for Amer Nejma took 10.592381715774536s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.6716461181640625e-05s
Believability | Calculation of trust value for Amer Nejma took 8.821487426757812e-06s
INFO | --- Analysis for Amer_Nejma took 112.94785475730896s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 10.094613552093506s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 2.8133392333984375e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for amon took 111.56723022460938s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.717745304107666s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 10.107192754745483s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 8.273124694824219e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.3113021850585938e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 113.88009142875671s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 8.988380432128906e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 10.283498048782349s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.647804260253906e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 8.106231689453125e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 111.73192191123962s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 8.511543273925781e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.001115560531616211s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 10.098313808441162s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0006811618804931641s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 2.765655517578125e-05s
Believability | Calculation of trust value for Animal Diversity Web took 1.3113021850585938e-05s
INFO | --- Analysis for animal-diversity-web took 111.96707391738892s
Availability | SPARQL endpoint availability check for Anime Dataset took 8.678436279296875e-05s
Availability | VoID file availability check for Anime Dataset took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Anime Dataset took 10.097712993621826s
Reputation | Calculation of the PageRank for Anime Dataset took 0.02261948585510254s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 2.765655517578125e-05s
Believability | Calculation of trust value for Anime Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for Anime took 111.3722550868988s
Availability | SPARQL endpoint availability check for ANNO took 5.173683166503906e-05s
Availability | VoID file availability check for ANNO took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for ANNO took 10.092437267303467s
Reputation | Calculation of the PageRank for ANNO took 0.020518064498901367s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.647804260253906e-05s
Believability | Calculation of trust value for ANNO took 1.239776611328125e-05s
INFO | --- Analysis for anno took 111.36365175247192s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 7.295608520507812e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 10.09805154800415s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.200241088867188e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.2874603271484375e-05s
INFO | --- Analysis for AntiqueCarsCollection took 112.67439937591553s
Availability | SPARQL endpoint availability check for apache took 0.00017452239990234375s
Availability | VoID file availability check for apache took 0.0037736892700195312s
Completeness | Calculation of interlinking completeness for apache took 10.098515033721924s
Reputation | Calculation of the PageRank for apache took 0.02239394187927246s
Interlinking | Calculation of Degree of Connection for apache took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for apache took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for apache took 5.173683166503906e-05s
Believability | Calculation of trust value for apache took 1.239776611328125e-05s
INFO | --- Analysis for apache took 111.54390239715576s
Availability | SPARQL endpoint availability check for Apertium RDF took 8.940696716308594e-05s
Availability | VoID file availability check for Apertium RDF took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Apertium RDF took 10.138053178787231s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf took 111.96747207641602s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 10.201883316040039s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.839897155761719e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.4781951904296875e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 111.53388261795044s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 8.678436279296875e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 10.10834550857544s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.022850513458251953s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 112.24546694755554s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 8.654594421386719e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 10.093028545379639s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.1961669921875e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-en-es took 112.46824502944946s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 10.10395860671997s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 112.04770135879517s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.601478576660156e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 10.10462474822998s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.887580871582031e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.52587890625e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 111.34089183807373s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 10.59632134437561s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 111.94122433662415s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 10.204358577728271s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.021252155303955078s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 111.37519454956055s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 10.15386438369751s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 111.64079570770264s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 7.843971252441406e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 10.10515832901001s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-es-an took 111.93774819374084s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 10.098308801651001s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02028489112854004s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 112.24534821510315s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.100799560546875e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 10.09822678565979s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.021852731704711914s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 111.83376955986023s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 10.09716272354126s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020342111587524414s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 111.47214484214783s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 8.606910705566406e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 10.093870878219604s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.02032756805419922s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 112.04589319229126s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 8.726119995117188e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 10.598059892654419s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.9114227294921875e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 111.83514857292175s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 0.00010204315185546875s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 10.107165336608887s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.021619796752929688s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 111.47255682945251s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 9.226799011230469e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 10.603541851043701s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 8.249282836914062e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 113.74366593360901s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 6.651878356933594e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 10.151396036148071s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020025253295898438s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.124641418457031e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.7404556274414062e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 111.97089695930481s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.029273986816406e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 10.095283031463623s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.02009725570678711s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 3.910064697265625e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 112.36896181106567s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 10.101418018341064s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.021939516067504883s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.076957702636719e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 111.56188130378723s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 7.963180541992188e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0011458396911621094s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 10.099761009216309s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 5.221366882324219e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 111.25146579742432s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.124641418457031e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 10.09541630744934s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 113.03028726577759s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.124641418457031e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0003769397735595703s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 10.096595048904419s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.022959232330322266s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 111.94038081169128s
Availability | SPARQL endpoint availability check for AragoDBPedia took 4.0531158447265625e-05s
Availability | VoID file availability check for AragoDBPedia took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 10.101149320602417s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.02200603485107422s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 3.647804260253906e-05s
Believability | Calculation of trust value for AragoDBPedia took 1.1920928955078125e-05s
INFO | --- Analysis for aragodbpedia took 112.13996839523315s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 4.38690185546875e-05s
Availability | VoID file availability check for Archives Hub Linked Data took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 10.099000930786133s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.078315734863281e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for archiveshub-linkeddata took 111.34567666053772s
Availability | SPARQL endpoint availability check for Archivi ISMA took 3.981590270996094e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 10.098425149917603s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.0202176570892334s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.123283386230469e-05s
Believability | Calculation of trust value for Archivi ISMA took 7.62939453125e-06s
INFO | --- Analysis for archivio-isma took 111.73446822166443s
Availability | SPARQL endpoint availability check for ARIADNE took 8.58306884765625e-05s
Availability | VoID file availability check for ARIADNE took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for ARIADNE took 10.096922874450684s
Reputation | Calculation of the PageRank for ARIADNE took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for ARIADNE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.0279159545898438e-05s
Believability | Calculation of trust value for ARIADNE took 1.1920928955078125e-05s
INFO | --- Analysis for ariadne took 111.53602313995361s
Availability | SPARQL endpoint availability check for Aristotle University took 8.511543273925781e-05s
Availability | VoID file availability check for Aristotle University took 0.0010671615600585938s
Completeness | Calculation of interlinking completeness for Aristotle University took 10.093054056167603s
Reputation | Calculation of the PageRank for Aristotle University took 0.02021479606628418s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 2.9802322387695312e-05s
Believability | Calculation of trust value for Aristotle University took 1.2874603271484375e-05s
INFO | --- Analysis for aristotle-university took 111.93944931030273s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.4345855712890625e-05s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 10.19373607635498s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02183246612548828s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.457069396972656e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 8.106231689453125e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 111.44477605819702s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.512901306152344e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 10.095195293426514s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.4332275390625e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.3589859008789062e-05s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 112.24069547653198s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.5367431640625e-05s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 10.194314956665039s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02211284637451172s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.552436828613281e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.2874603271484375e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 111.66995859146118s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.100799560546875e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 10.0989830493927s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020049333572387695s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0001049041748046875s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.2636184692382812e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 111.6464912891388s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.124641418457031e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 10.19991683959961s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02225661277770996s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 9.894371032714844e-05s
Believability | Calculation of trust value for Arthroscopy community took 1.7642974853515625e-05s
INFO | --- Analysis for arthroscopy took 111.94856119155884s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 8.7738037109375e-05s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 10.136461973190308s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.2636184692382812e-05s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 7.62939453125e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 111.53982615470886s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 4.095565319061279s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 10.09756088256836s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006780624389648438s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.843971252441406e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 115.46704840660095s
Availability | SPARQL endpoint availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 2.4581801891326904s
Availability | VoID file availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 10.106439590454102s
Reputation | Calculation of the PageRank for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.319450378417969e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 114.04228091239929s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.4223251342773438s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 10.6016526222229s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.797645568847656e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.3113021850585938e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 115.15043568611145s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.455779790878296s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 10.101606369018555s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02217578887939453s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.2636184692382812e-05s
INFO | --- Analysis for ASCDC-CRB took 113.94071865081787s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.4241843223571777s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 10.20339822769165s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0203096866607666s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.465217590332031e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.3113021850585938e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 114.44693613052368s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.4606337547302246s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 10.095738410949707s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.021029233932495117s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.337860107421875e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-DQOT took 113.83465790748596s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.418508768081665s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 10.205337762832642s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.106231689453125e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.3589859008789062e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 114.44329476356506s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.238950252532959s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 10.102203845977783s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.511543273925781e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 115.04274249076843s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.4553682804107666s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 10.10093092918396s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02164316177368164s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 113.84469509124756s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.4468894004821777s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 10.100104331970215s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 4.982948303222656e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 114.0306224822998s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.270442962646484s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 10.595491409301758s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.02155613899230957s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.14984130859375e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.5497207641601562e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 116.3384017944336s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.437695026397705s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 10.097238779067993s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.367134094238281e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 114.84033441543579s
Availability | SPARQL endpoint availability check for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 2.432711601257324s
Availability | VoID file availability check for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 10.200473546981812s
Reputation | Calculation of the PageRank for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.677078247070312e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.3113021850585938e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 115.24537467956543s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.4223246574401855s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 10.198432922363281s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.100799560546875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC_-_DNB took 113.73410058021545s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.1961669921875e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 10.099316120147705s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020371437072753906s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.318092346191406e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.2159347534179688e-05s
INFO | --- Analysis for asit took 111.94295120239258s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.172325134277344e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 10.098024606704712s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.022162675857543945s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.7670135498046875e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.33514404296875e-05s
INFO | --- Analysis for asjp took 111.47519183158875s
Availability | SPARQL endpoint availability check for ASN:US took 4.076957702636719e-05s
Availability | VoID file availability check for ASN:US took 0.0011551380157470703s
Completeness | Calculation of interlinking completeness for ASN:US took 10.098857641220093s
Reputation | Calculation of the PageRank for ASN:US took 0.020817279815673828s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0009121894836425781s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.842613220214844e-05s
Believability | Calculation of trust value for ASN:US took 1.3113021850585938e-05s
INFO | --- Analysis for asn-us took 112.34234833717346s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 8.511543273925781e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 10.096187829971313s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.504753112792969e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 1.2636184692382812e-05s
INFO | --- Analysis for aspire-mmu took 112.02985167503357s
Availability | SPARQL endpoint availability check for associations took 4.029273986816406e-05s
Availability | VoID file availability check for associations took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for associations took 10.100703954696655s
Reputation | Calculation of the PageRank for associations took 0.021941423416137695s
Interlinking | Calculation of Degree of Connection for associations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for associations took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for associations took 6.103515625e-05s
Believability | Calculation of trust value for associations took 1.3589859008789062e-05s
INFO | --- Analysis for associations took 112.56503820419312s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 9.846687316894531e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 10.189634799957275s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.02218317985534668s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.7894973754882812e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 1.2159347534179688e-05s
INFO | --- Analysis for atc-publikovan--s-kl took 111.97773003578186s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.00543212890625e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 10.204792737960815s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.298324584960938e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.3113021850585938e-05s
INFO | --- Analysis for athelia-rfid took 111.74563884735107s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 8.654594421386719e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 10.094981670379639s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.743171691894531e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.3113021850585938e-05s
INFO | --- Analysis for aueb-linked-open-data took 111.5393340587616s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 8.797645568847656e-05s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 10.097485303878784s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.7697296142578125e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.3589859008789062e-05s
INFO | --- Analysis for AugustiniConfessiones took 112.63239693641663s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 4.076957702636719e-05s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 10.097703695297241s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.749961853027344e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.2874603271484375e-05s
INFO | --- Analysis for austrian_ski_racers took 112.35915875434875s
Availability | SPARQL endpoint availability check for AVsOnto took 4.076957702636719e-05s
Availability | VoID file availability check for AVsOnto took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for AVsOnto took 10.603228092193604s
Reputation | Calculation of the PageRank for AVsOnto took 0.020097732543945312s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.0040740966796875e-05s
Believability | Calculation of trust value for AVsOnto took 1.3589859008789062e-05s
INFO | --- Analysis for AVsOnto took 112.2773699760437s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5284650325775146s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007054805755615234s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 222.95492243766785s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5248324871063232s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0062618255615s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 263.4401364326477s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.01334738731384s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.03162002563477s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23661136627197266s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4457235336303711s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12049460411071777s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.08727383613586426s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 44.54009532928467s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1046006679535s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15376710891723633s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0656147003174s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3308274745941162s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10079455375671387s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19913935661315918s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09304928779602051s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.66044306755066s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.414817810058594e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09528398513793945s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.05897998809814s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13959097862243652s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1172037124633789s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11040067672729492s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.32269835472106934s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22562742233276367s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1087.2189519405365s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1749424934387207s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.173759460449219s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1698079109191895s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.793990850448608s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14448070526123047s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.19425773620605s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 23.893595457077026s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.221618175506592s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.4695518016815s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.781428098678589s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18171215057373047s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0615739822387695s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.701324701309204s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021454572677612305s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.867813110351562e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.9073486328125e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.5367431640625e-06s
INFO | --- Analysis for b3kat took 4820.516749620438s
Availability | SPARQL endpoint availability check for BabelNet took 6.747245788574219e-05s
Availability | VoID file availability check for BabelNet took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for BabelNet took 10.098092317581177s
Reputation | Calculation of the PageRank for BabelNet took 0.02120375633239746s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00015997886657714844s
Believability | Calculation of trust value for BabelNet took 8.58306884765625e-06s
INFO | --- Analysis for babelnet took 112.77100968360901s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 8.678436279296875e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 10.090516567230225s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.62396240234375e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.2874603271484375e-05s
INFO | --- Analysis for Bacevicius.lt took 112.31990599632263s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 4.267692565917969e-05s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 10.112153768539429s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.0201413631439209s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.6253204345703125e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.1920928955078125e-05s
INFO | --- Analysis for bag took 112.3333351612091s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.172325134277344e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 10.098414897918701s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.8133392333984375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.3909759521484375e-06s
INFO | --- Analysis for baixue took 112.27100110054016s
Availability | SPARQL endpoint availability check for baixue composer took 4.172325134277344e-05s
Availability | VoID file availability check for baixue composer took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for baixue composer took 10.098434686660767s
Reputation | Calculation of the PageRank for baixue composer took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for baixue composer took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for baixue composer took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for baixue composer took 2.765655517578125e-05s
Believability | Calculation of trust value for baixue composer took 1.239776611328125e-05s
INFO | --- Analysis for baixue_composer took 111.67132377624512s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.267692565917969e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 10.100223064422607s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0009980201721191406s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.8623809814453125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.3589859008789062e-05s
INFO | --- Analysis for baixue_imagery took 111.6430606842041s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.100799560546875e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 10.096431255340576s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 4.124641418457031e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.867813110351562e-06s
INFO | --- Analysis for baixue_imagery1 took 111.86299920082092s
Availability | SPARQL endpoint availability check for BAMS took 6.508827209472656e-05s
Availability | VoID file availability check for BAMS took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for BAMS took 10.094883918762207s
Reputation | Calculation of the PageRank for BAMS took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for BAMS took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.266334533691406e-05s
Believability | Calculation of trust value for BAMS took 1.3113021850585938e-05s
INFO | --- Analysis for bams took 112.73629713058472s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.1484832763671875e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 10.096031427383423s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020433664321899414s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.506111145019531e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 2.09808349609375e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 111.34512686729431s
Availability | SPARQL endpoint availability check for BBC Music took 0.5138821601867676s
Availability | VoID file availability check for BBC Music took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for BBC Music took 10.183246612548828s
Reputation | Calculation of the PageRank for BBC Music took 0.02144789695739746s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013375282287597656s
Believability | Calculation of trust value for BBC Music took 1.33514404296875e-05s
INFO | --- Analysis for bbc-music took 112.44847631454468s
Availability | SPARQL endpoint availability check for BBC Programmes took 9.34600830078125e-05s
Availability | VoID file availability check for BBC Programmes took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for BBC Programmes took 10.100922107696533s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010609626770019531s
Believability | Calculation of trust value for BBC Programmes took 9.298324584960938e-06s
INFO | --- Analysis for bbc-programmes took 111.4320752620697s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.28444409370422363s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0012307167053222656s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 10.100084781646729s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 9.942054748535156e-05s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-wildlife-finder took 111.94878387451172s
Availability | SPARQL endpoint availability check for BBOP took 0.00010824203491210938s
Availability | VoID file availability check for BBOP took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for BBOP took 10.097650289535522s
Reputation | Calculation of the PageRank for BBOP took 0.02193737030029297s
Interlinking | Calculation of Degree of Connection for BBOP took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.86102294921875e-05s
Believability | Calculation of trust value for BBOP took 1.33514404296875e-05s
INFO | --- Analysis for bbop took 108.86049342155457s
Availability | SPARQL endpoint availability check for BBOP took 8.678436279296875e-05s
Availability | VoID file availability check for BBOP took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for BBOP took 10.1935875415802s
Reputation | Calculation of the PageRank for BBOP took 0.020221233367919922s
Interlinking | Calculation of Degree of Connection for BBOP took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.765655517578125e-05s
Believability | Calculation of trust value for BBOP took 7.3909759521484375e-06s
INFO | --- Analysis for bbop-selected took 112.67132186889648s
Availability | SPARQL endpoint availability check for Bdgp took 8.344650268554688e-05s
Availability | VoID file availability check for Bdgp took 0.0003120899200439453s
Completeness | Calculation of interlinking completeness for Bdgp took 10.090558290481567s
Reputation | Calculation of the PageRank for Bdgp took 0.020787954330444336s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bdgp took 5.698204040527344e-05s
INFO | --- Analysis for bdgp took 112.06639885902405s
Availability | SPARQL endpoint availability check for Bendev Junior took 3.9577484130859375e-05s
Availability | VoID file availability check for Bendev Junior took 0.017018556594848633s
Completeness | Calculation of interlinking completeness for Bendev Junior took 10.178125858306885s
Reputation | Calculation of the PageRank for Bendev Junior took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 4.124641418457031e-05s
Believability | Calculation of trust value for Bendev Junior took 1.4543533325195312e-05s
INFO | --- Analysis for bendevoficial took 112.53830647468567s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.124641418457031e-05s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 10.095892190933228s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.200241088867188e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 1.4543533325195312e-05s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 111.43689632415771s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 8.58306884765625e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 10.102831602096558s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.8623809814453125e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 8.344650268554688e-06s
INFO | --- Analysis for berlin-offener-haushalt took 111.24400234222412s
Availability | SPARQL endpoint availability check for berlios took 4.00543212890625e-05s
Availability | VoID file availability check for berlios took 0.0012285709381103516s
Completeness | Calculation of interlinking completeness for berlios took 10.101581811904907s
Reputation | Calculation of the PageRank for berlios took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for berlios took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for berlios took 8.893013000488281e-05s
Believability | Calculation of trust value for berlios took 1.239776611328125e-05s
INFO | --- Analysis for berlios took 111.44257950782776s
Availability | SPARQL endpoint availability check for Between Our Worlds took 8.392333984375e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 10.194085359573364s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.022217512130737305s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0008578300476074219s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.843971252441406e-05s
Believability | Calculation of trust value for Between Our Worlds took 7.867813110351562e-06s
INFO | --- Analysis for betweenourworlds took 112.17114281654358s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 4.410743713378906e-05s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 10.101012468338013s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.02234935760498047s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.416175842285156e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for bfs-linked-data took 112.0666651725769s
Availability | SPARQL endpoint availability check for BibBase took 4.506111145019531e-05s
Availability | VoID file availability check for BibBase took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for BibBase took 10.098819494247437s
Reputation | Calculation of the PageRank for BibBase took 0.02131032943725586s
Interlinking | Calculation of Degree of Connection for BibBase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.465217590332031e-05s
Believability | Calculation of trust value for BibBase took 1.3113021850585938e-05s
INFO | --- Analysis for bibbase took 111.66572332382202s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 5.14984130859375e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 10.092739343643188s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.0001068115234375s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.2159347534179688e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 111.53321290016174s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.1484832763671875e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 10.594379663467407s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010037422180175781s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.2874603271484375e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 111.87983584403992s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.076957702636719e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 10.102271318435669s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.743171691894531e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.3828277587890625e-05s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 111.43082857131958s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.029273986816406e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 10.099587440490723s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.504753112792969e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.33514404296875e-05s
INFO | --- Analysis for BibSonomy took 111.34297275543213s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.029273986816406e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 10.098276615142822s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.022962093353271484s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.24249267578125e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.3828277587890625e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 112.3711609840393s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 7.081031799316406e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 10.101385593414307s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.022352933883666992s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.86102294921875e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.3113021850585938e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 111.43893933296204s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 9.083747863769531e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 10.100965976715088s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.02177572250366211s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.765655517578125e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-acfsid took 112.07022070884705s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 9.679794311523438e-05s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 10.097965002059937s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.02017354965209961s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.5367431640625e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 112.57212424278259s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 3.910064697265625e-05s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0004112720489501953s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 10.200088500976562s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011205673217773438s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-biomodels took 111.76597952842712s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 7.2479248046875e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00032711029052734375s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 10.097269773483276s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.02260613441467285s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 111.76585125923157s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 8.249282836914062e-05s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 10.088134527206421s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.022639036178588867s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004096031188964844s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-bioportal took 111.53843307495117s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 10.101171255111694s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.221366882324219e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.4543533325195312e-05s
INFO | --- Analysis for bio2rdf-chembl took 111.74102425575256s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 10.09732437133789s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.601478576660156e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 111.23865699768066s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 7.772445678710938e-05s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0011322498321533203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 10.103528261184692s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.022065401077270508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.628036499023438e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-ctd took 111.54725646972656s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 8.153915405273438e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 10.099482774734497s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.221366882324219e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.52587890625e-05s
INFO | --- Analysis for bio2rdf-dataset took 111.342458486557s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 3.886222839355469e-05s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 10.17650032043457s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.022434473037719727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.008148193359375e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 112.66119408607483s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 8.368492126464844e-05s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 10.09582805633545s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010442733764648438s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-drugbank took 111.37751245498657s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 7.843971252441406e-05s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 10.094617128372192s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.022893190383911133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.817413330078125e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-genage took 112.04058623313904s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 8.916854858398438e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 10.20237946510315s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.021445274353027344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.817413330078125e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-genbank took 111.67117881774902s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 8.0108642578125e-05s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 10.099796295166016s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 4.673004150390625e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-gendr took 112.068612575531s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 4.410743713378906e-05s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 10.101388216018677s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.02034163475036621s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0009036064147949219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.914138793945312e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-goa took 111.67332363128662s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 6.4849853515625e-05s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 10.198046207427979s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.0001087188720703125s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-hgnc took 111.86144161224365s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.00116729736328125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 10.104359865188599s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02179098129272461s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 4.839897155761719e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-homologene took 111.37640953063965s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 7.271766662597656e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 10.599283695220947s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.02028036117553711s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 2.7179718017578125e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-inoh took 112.37083578109741s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 8.463859558105469e-05s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 10.587378740310669s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010132789611816406s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-interpro took 112.74908256530762s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 8.416175842285156e-05s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 10.098777770996094s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.224082946777344e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-iproclass took 111.77008485794067s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 6.651878356933594e-05s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 10.09878158569336s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.963180541992188e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-irefindex took 112.44080471992493s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 10.102985620498657s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.437301635742188e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-kegg took 111.76446580886841s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 10.108359336853027s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.020233154296875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.504753112792969e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-kegg-biopax took 111.24813294410706s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0011017322540283203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 10.494554281234741s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.910064697265625e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 111.86276197433472s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 10.090705156326294s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02132248878479004s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.4345855712890625e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-lsr took 112.2404191493988s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 9.632110595703125e-05s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 10.09800934791565s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 6.985664367675781e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-mesh took 111.37161898612976s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 10.092702865600586s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.022536039352416992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 8.511543273925781e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-mgi took 113.33653378486633s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 9.870529174804688e-05s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 10.597309350967407s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020055770874023438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012564659118652344s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 113.44793272018433s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 8.606910705566406e-05s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 10.201358556747437s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.02141427993774414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.506111145019531e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.4781951904296875e-05s
INFO | --- Analysis for bio2rdf-ndc took 111.53403282165527s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 10.095663785934448s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.02207207679748535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-netpath took 111.54112315177917s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 10.093556880950928s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-nextprot took 112.13681983947754s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::Omim took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 10.097606182098389s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00012803077697753906s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-omim took 112.33865094184875s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 8.368492126464844e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 10.107707738876343s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.022116422653198242s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.695487976074219e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 112.44082951545715s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 6.222724914550781e-05s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 10.203657627105713s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.022703886032104492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 7.152557373046875e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-orphanet took 111.94453191757202s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 10.092736959457397s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.022397518157958984s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 112.54055166244507s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 10.197602987289429s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 6.556510925292969e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 113.05759716033936s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 10.199069261550903s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.02208566665649414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 2.765655517578125e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 112.07759213447571s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 8.535385131835938e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 10.099325180053711s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.457069396972656e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-pid took 111.94025707244873s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 8.416175842285156e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 10.093961715698242s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-pubchem-2 took 111.23707675933838s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 10.595951795578003s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.021930456161499023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0010619163513183594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00015878677368164062s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-pubmed took 111.77098989486694s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 5.125999450683594e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 10.094727754592896s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.461143493652344e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-reactome took 111.36818265914917s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 9.489059448242188e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 10.202923774719238s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.054473876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-rhea took 111.50026774406433s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 9.703636169433594e-05s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 11.179112434387207s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.653236389160156e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-sabiork took 116.51334834098816s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 10.099437713623047s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020371198654174805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 9.72747802734375e-05s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-sgd took 113.9394633769989s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 8.797645568847656e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 10.19920825958252s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.02021503448486328s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.3855438232421875e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 112.44590878486633s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 8.320808410644531e-05s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 10.607202291488647s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.021879196166992188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.647804260253906e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-sider took 113.4626681804657s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 10.095365047454834s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.021239280700683594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-spike took 111.77372860908508s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.029273986816406e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 10.097844123840332s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.0215761661529541s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 3.695487976074219e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-taxon took 111.25029826164246s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 6.604194641113281e-05s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 10.19342851638794s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00011372566223144531s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 111.63918828964233s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 6.461143493652344e-05s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 10.229149341583252s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 111.44087934494019s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 8.225440979003906e-05s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 10.193788051605225s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.796287536621094e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-wormbase took 111.30970501899719s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.9114227294921875e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 10.588852405548096s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020810842514038086s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.33514404296875e-05s
Believability | Calculation of trust value for Biografías y Vidas took 1.3589859008789062e-05s
INFO | --- Analysis for biografiasyvidas took 111.8714554309845s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 4.124641418457031e-05s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 10.096156120300293s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020144224166870117s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.225440979003906e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.3113021850585938e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 111.56639504432678s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.534027099609375e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 10.10004186630249s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.021483182907104492s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.1948089599609375e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for biolit took 112.63116645812988s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 8.20159912109375e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 10.216647624969482s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.029273986816406e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.3828277587890625e-05s
INFO | --- Analysis for biolod-pdb took 112.4369387626648s
Availability | SPARQL endpoint availability check for BioModels RDF took 4.029273986816406e-05s
Availability | VoID file availability check for BioModels RDF took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for BioModels RDF took 10.100725412368774s
Reputation | Calculation of the PageRank for BioModels RDF took 0.021053314208984375s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.1484832763671875e-05s
Believability | Calculation of trust value for BioModels RDF took 8.344650268554688e-06s
INFO | --- Analysis for biomodels-rdf took 112.13263535499573s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.273124694824219e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 10.196774244308472s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.743171691894531e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.867813110351562e-06s
INFO | --- Analysis for Biop took 111.53377175331116s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 6.4849853515625e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 10.100707292556763s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 5.125999450683594e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.3113021850585938e-05s
INFO | --- Analysis for Bioportal took 111.44461560249329s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.38690185546875e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 10.095457315444946s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006148815155029297s
Believability | Calculation of trust value for Amphibian gross anatomy took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-aao took 111.7316963672638s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.1484832763671875e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 10.204100608825684s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020386457443237305s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002963542938232422s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-aba took 111.63698720932007s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 10.094048500061035s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.022249937057495117s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0014634132385253906s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-acgt took 111.36879515647888s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 9.679794311523438e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 10.09803557395935s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.000370025634765625s
Believability | Calculation of trust value for Animal natural history and life history took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-adw took 112.45931911468506s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 10.094300031661987s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004458427429199219s
Believability | Calculation of trust value for Anatomical Entity Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-aeo took 111.73745012283325s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 10.10269045829773s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02225804328918457s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009217262268066406s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-aero took 111.4351544380188s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.029273986816406e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 10.606239795684814s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.022336483001708984s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0003974437713623047s
Believability | Calculation of trust value for AI/RHEUM took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-air took 112.44747257232666s
Availability | SPARQL endpoint availability check for Amino Acid took 3.9577484130859375e-05s
Availability | VoID file availability check for Amino Acid took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Amino Acid took 10.09394645690918s
Reputation | Calculation of the PageRank for Amino Acid took 0.02140498161315918s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002582073211669922s
Believability | Calculation of trust value for Amino Acid took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-amino-acid took 112.34005904197693s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 8.249282836914062e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 10.102556228637695s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.021448612213134766s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00029468536376953125s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-apo took 112.44441413879395s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 6.556510925292969e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 10.094721794128418s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.02082085609436035s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 4.0531158447265625e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00022745132446289062s
Believability | Calculation of trust value for African Traditional Medicine took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-atmo took 112.33973574638367s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 8.320808410644531e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 10.091922044754028s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 0.0001895427703857422s
Believability | Calculation of trust value for Amphibian taxonomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ato took 111.43440890312195s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 10.10313105583191s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0012798309326171875s
Believability | Calculation of trust value for BioAssay Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-bao took 111.23554944992065s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 8.153915405273438e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 10.101078510284424s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.025623321533203125s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.002153158187866211s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0008423328399658203s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 112.14569902420044s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 10.097115993499756s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003132820129394531s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-bcgo took 111.7416455745697s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 10.100741386413574s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02169060707092285s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013682842254638672s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-bdo took 112.13482117652893s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 10.098626613616943s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004761219024658203s
Believability | Calculation of trust value for Basic Formal Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bfo took 111.83093023300171s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.00543212890625e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 10.099031925201416s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007238388061523438s
Believability | Calculation of trust value for Bleeding History Phenotype took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-bho took 111.77199697494507s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 5.054473876953125e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 10.106249570846558s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.02134394645690918s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004143714904785156s
Believability | Calculation of trust value for Bilateria anatomy took 1.5020370483398438e-05s
INFO | --- Analysis for bioportal-bila took 111.53663635253906s
Availability | SPARQL endpoint availability check for BIRNLex took 6.246566772460938e-05s
Availability | VoID file availability check for BIRNLex took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for BIRNLex took 10.101491689682007s
Reputation | Calculation of the PageRank for BIRNLex took 0.021584272384643555s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014297962188720703s
Believability | Calculation of trust value for BIRNLex took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-birnlex took 111.64779829978943s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 10.107813596725464s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02155923843383789s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.000732421875s
Believability | Calculation of trust value for Gene Regulation Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-bootstrep took 112.0348448753357s
Availability | SPARQL endpoint availability check for BioPAX took 4.100799560546875e-05s
Availability | VoID file availability check for BioPAX took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for BioPAX took 10.098643064498901s
Reputation | Calculation of the PageRank for BioPAX took 0.021939516067504883s
Interlinking | Calculation of Degree of Connection for BioPAX took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00010085105895996094s
Believability | Calculation of trust value for BioPAX took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bp took 111.43592119216919s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 10.19978642463684s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00032067298889160156s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 111.83883357048035s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 10.097468852996826s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02214980125427246s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002079010009765625s
Believability | Calculation of trust value for Spatial Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-bspo took 111.85347247123718s
Availability | SPARQL endpoint availability check for BioTop took 4.100799560546875e-05s
Availability | VoID file availability check for BioTop took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for BioTop took 10.0997314453125s
Reputation | Calculation of the PageRank for BioTop took 0.021796226501464844s
Interlinking | Calculation of Degree of Connection for BioTop took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006325244903564453s
Believability | Calculation of trust value for BioTop took 5.459785461425781e-05s
INFO | --- Analysis for bioportal-bt took 112.3295111656189s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 7.05718994140625e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 10.08677077293396s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.022158145904541016s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008623600006103516s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-bto took 111.82057785987854s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 7.104873657226562e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 10.108307123184204s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0017902851104736328s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 9.036064147949219e-05s
INFO | --- Analysis for bioportal-canco took 111.74055767059326s
Availability | SPARQL endpoint availability check for CAO took 7.987022399902344e-05s
Availability | VoID file availability check for CAO took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for CAO took 10.093384504318237s
Reputation | Calculation of the PageRank for CAO took 0.021833419799804688s
Interlinking | Calculation of Degree of Connection for CAO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for CAO took 0.000583648681640625s
Believability | Calculation of trust value for CAO took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-cao took 111.77069067955017s
Availability | SPARQL endpoint availability check for CareLex took 8.440017700195312e-05s
Availability | VoID file availability check for CareLex took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for CareLex took 10.195194959640503s
Reputation | Calculation of the PageRank for CareLex took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.507469177246094e-05s
Believability | Calculation of trust value for CareLex took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-carelex took 111.94769620895386s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00030159950256347656s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 10.105968475341797s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008590221405029297s
Believability | Calculation of trust value for Cell Cycle Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-cco took 112.44038486480713s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 10.102256298065186s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025463104248046875s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-cdao took 111.43515634536743s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.1961669921875e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 10.192627191543579s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02028679847717285s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007717609405517578s
Believability | Calculation of trust value for Chemical entities of biological interest took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-chebi took 111.84330081939697s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.076957702636719e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 10.092881441116333s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00023889541625976562s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 112.54258298873901s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 8.344650268554688e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 10.095877885818481s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007448196411132812s
Believability | Calculation of trust value for Chemical Information Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-cheminf took 111.77173328399658s
Availability | SPARQL endpoint availability check for Cell type took 5.793571472167969e-05s
Availability | VoID file availability check for Cell type took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Cell type took 10.597683429718018s
Reputation | Calculation of the PageRank for Cell type took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Cell type took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003712177276611328s
Believability | Calculation of trust value for Cell type took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-cl took 112.24445962905884s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 10.096503973007202s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020293235778808594s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008080005645751953s
Believability | Calculation of trust value for Cell Line Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-clo took 112.25462079048157s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 10.100421905517578s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02683091163635254s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00016880035400390625s
Believability | Calculation of trust value for Clinical Measurement Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-cmo took 111.34353995323181s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.00038695335388183594s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 10.103365659713745s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00021529197692871094s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-cno took 111.73259735107422s
Availability | SPARQL endpoint availability check for Wheat trait took 0.0001049041748046875s
Availability | VoID file availability check for Wheat trait took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Wheat trait took 10.599552631378174s
Reputation | Calculation of the PageRank for Wheat trait took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for Wheat trait took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 4.9114227294921875e-05s
Believability | Calculation of trust value for Wheat trait took 7.62939453125e-06s
INFO | --- Analysis for bioportal-co_wheat took 111.87275266647339s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.076957702636719e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 10.10373044013977s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02019786834716797s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003447532653808594s
Believability | Calculation of trust value for Cognitive Atlas took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-cogat took 111.96934819221497s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 10.206025123596191s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.022397518157958984s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007045269012451172s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-cogpo took 111.96322774887085s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.315376281738281e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 10.101856470108032s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.022436141967773438s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00039386749267578125s
Believability | Calculation of trust value for Current Procedural Terminology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-cpt took 111.87154269218445s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 3.9577484130859375e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.03894639015197754s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 10.163339853286743s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017726421356201172s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-csp took 112.97027087211609s
Availability | SPARQL endpoint availability check for COSTART took 4.220008850097656e-05s
Availability | VoID file availability check for COSTART took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for COSTART took 10.198215007781982s
Reputation | Calculation of the PageRank for COSTART took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009522438049316406s
Believability | Calculation of trust value for COSTART took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-cst took 112.770512342453s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.153915405273438e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 10.10040283203125s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.02070307731628418s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.00047588348388671875s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-ctcae took 111.5379409790039s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.029273986816406e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 10.202491998672485s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.022669553756713867s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004315376281738281s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-ctx took 111.26945853233337s
Availability | SPARQL endpoint availability check for Dendritic cell took 8.058547973632812e-05s
Availability | VoID file availability check for Dendritic cell took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Dendritic cell took 10.09760046005249s
Reputation | Calculation of the PageRank for Dendritic cell took 0.0223388671875s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0003032684326171875s
Believability | Calculation of trust value for Dendritic cell took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-dc_cl took 111.44643974304199s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.320808410644531e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 10.103851556777954s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.022224903106689453s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.320808410644531e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-ddanat took 111.74114179611206s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 8.797645568847656e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.012709617614746094s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 10.091453075408936s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009031295776367188s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-ddi took 111.74011087417603s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 0.00010180473327636719s
Availability | VoID file availability check for Diagnostic Ontology took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 10.59524917602539s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.021160364151000977s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 0.0001010894775390625s
Believability | Calculation of trust value for Diagnostic Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-diagnosticont took 113.05011582374573s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 10.099638223648071s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.021587371826171875s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00015211105346679688s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-dikb-evidence took 112.4419469833374s
Availability | SPARQL endpoint availability check for Human disease ontology took 6.365776062011719e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Human disease ontology took 10.099568367004395s
Reputation | Calculation of the PageRank for Human disease ontology took 0.02055501937866211s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006103515625s
Believability | Calculation of trust value for Human disease ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-doid took 111.83641362190247s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 8.296966552734375e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 10.098587036132812s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020348310470581055s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007598400115966797s
Believability | Calculation of trust value for Electrocardiography Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-ecg took 111.73844408988953s
Availability | SPARQL endpoint availability check for Evidence codes took 8.320808410644531e-05s
Availability | VoID file availability check for Evidence codes took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Evidence codes took 10.204442501068115s
Reputation | Calculation of the PageRank for Evidence codes took 0.021682262420654297s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.457069396972656e-05s
Believability | Calculation of trust value for Evidence codes took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-eco took 112.37276530265808s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 6.4849853515625e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 10.098967790603638s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020766496658325195s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.001711130142211914s
Believability | Calculation of trust value for Experimental Factor Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-efo took 111.34426259994507s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.172325134277344e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 10.093468427658081s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011332035064697266s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-ehda took 111.62930727005005s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.2438507080078125e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 10.100321054458618s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007061958312988281s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-ehdaa took 111.34756684303284s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.458427429199219e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 10.101239442825317s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.021966218948364258s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005106925964355469s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-ehdaa2 took 111.95908188819885s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 6.937980651855469e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 10.088818073272705s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.0279159545898438e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-emap took 112.46824383735657s
Availability | SPARQL endpoint availability check for Environment Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Environment Ontology took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Environment Ontology took 10.101937055587769s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0003845691680908203s
Believability | Calculation of trust value for Environment Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-envo took 111.3812050819397s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 8.726119995117188e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 10.09738564491272s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.021718978881835938s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0002880096435546875s
Believability | Calculation of trust value for Plant environmental conditions took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-eo took 111.80331420898438s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 10.592193603515625s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012056827545166016s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ep took 112.36994504928589s
Availability | SPARQL endpoint availability check for Epilepsy took 8.416175842285156e-05s
Availability | VoID file availability check for Epilepsy took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Epilepsy took 10.189401626586914s
Reputation | Calculation of the PageRank for Epilepsy took 0.02240777015686035s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00011968612670898438s
Believability | Calculation of trust value for Epilepsy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-epileponto took 112.93574643135071s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.029273986816406e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 10.598731517791748s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.021466732025146484s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011532306671142578s
Believability | Calculation of trust value for eagle-i research resource ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ero took 112.94346213340759s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.029273986816406e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 10.099040508270264s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020891904830932617s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011548995971679688s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ev took 111.27287864685059s
Availability | SPARQL endpoint availability check for ExO took 5.91278076171875e-05s
Availability | VoID file availability check for ExO took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for ExO took 10.198131084442139s
Reputation | Calculation of the PageRank for ExO took 0.02248525619506836s
Interlinking | Calculation of Degree of Connection for ExO took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ExO took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00025391578674316406s
Believability | Calculation of trust value for ExO took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-exo took 111.66991591453552s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 0.0001266002655029297s
Availability | VoID file availability check for Fungal gross anatomy took 0.0003345012664794922s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 10.099039077758789s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02120661735534668s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00012254714965820312s
Believability | Calculation of trust value for Fungal gross anatomy took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-fao took 111.87515926361084s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.0531158447265625e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 10.093808889389038s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.02069377899169922s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.0001838207244873047s
Believability | Calculation of trust value for Biological imaging methods took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-fbbi took 111.26402163505554s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.1961669921875e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 10.605982065200806s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006866455078125s
Believability | Calculation of trust value for Drosophila gross anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-fbbt took 111.87276124954224s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.029273986816406e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 10.106074571609497s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02026844024658203s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0003998279571533203s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-fbcv took 111.6658444404602s
Availability | SPARQL endpoint availability check for Drosophila development took 8.344650268554688e-05s
Availability | VoID file availability check for Drosophila development took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Drosophila development took 10.101995468139648s
Reputation | Calculation of the PageRank for Drosophila development took 0.020272493362426758s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.076957702636719e-05s
Believability | Calculation of trust value for Drosophila development took 7.62939453125e-06s
INFO | --- Analysis for bioportal-fbdv took 113.27057576179504s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.267692565917969e-05s
Availability | VoID file availability check for Fly taxonomy took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 10.094878435134888s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003490447998046875s
Believability | Calculation of trust value for Fly taxonomy took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-fbsp took 112.1408121585846s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.124641418457031e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 10.202605485916138s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002148151397705078s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 111.83903861045837s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 10.60433030128479s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00047135353088378906s
Believability | Calculation of trust value for Family Health History Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-fhho took 111.96579766273499s
Availability | SPARQL endpoint availability check for Influenza Ontology took 8.20159912109375e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 10.091338634490967s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020236730575561523s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.00102996826171875s
Believability | Calculation of trust value for Influenza Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-flu took 112.36628198623657s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 10.196930885314941s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.580352783203125e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-fma took 112.43721437454224s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 10.100167512893677s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00012540817260742188s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-fypo took 112.03731799125671s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0012083053588867188s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 10.094008445739746s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.022029399871826172s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.58306884765625e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-geospecies took 111.83901190757751s
Availability | SPARQL endpoint availability check for General Formal Ontology took 0.00010204315185546875s
Availability | VoID file availability check for General Formal Ontology took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 10.094415664672852s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00015282630920410156s
Believability | Calculation of trust value for General Formal Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-gfo took 111.7359459400177s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 5.030632019042969e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 10.095457077026367s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005774497985839844s
Believability | Calculation of trust value for General Formal Ontology: Biology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-gfo-bio took 112.04802012443542s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 0.0001227855682373047s
Availability | VoID file availability check for Gene Ontology Extension took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 10.200519323348999s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008494853973388672s
Believability | Calculation of trust value for Gene Ontology Extension took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-go_x1 took 112.03720283508301s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Gene Ontology took 10.094028949737549s
Reputation | Calculation of the PageRank for Gene Ontology took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008337497711181641s
Believability | Calculation of trust value for Gene Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-go_x2 took 112.03510165214539s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 8.20159912109375e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 10.090715169906616s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 2.956390380859375e-05s
Believability | Calculation of trust value for Cereal Plant Development took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-gro took 112.03951478004456s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.029273986816406e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0003712177276611328s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 10.096189260482788s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.021783113479614258s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004286766052246094s
Believability | Calculation of trust value for Cereal plant gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-gro_x1 took 111.45089626312256s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 10.103729248046875s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007195472717285156s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-gro_x2 took 111.43764162063599s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 10.098182439804077s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005602836608886719s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-hao took 112.04040551185608s
Availability | SPARQL endpoint availability check for HCPCS took 6.461143493652344e-05s
Availability | VoID file availability check for HCPCS took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for HCPCS took 10.116015195846558s
Reputation | Calculation of the PageRank for HCPCS took 0.02168416976928711s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002167224884033203s
Believability | Calculation of trust value for HCPCS took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-hcpcs took 113.14233756065369s
Availability | SPARQL endpoint availability check for Health Level Seven took 8.58306884765625e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Health Level Seven took 10.19697117805481s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020122766494750977s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012269020080566406s
Believability | Calculation of trust value for Health Level Seven took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-hl7 took 111.57482433319092s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 0.00010204315185546875s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0003731250762939453s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 10.108465194702148s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.02086782455444336s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00033736228942871094s
Believability | Calculation of trust value for HEALTH_INDICATORS took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-hlth_indics took 111.47282385826111s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 7.081031799316406e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0003046989440917969s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 10.102285146713257s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.021370649337768555s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0009860992431640625s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 9.942054748535156e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 1.430511474609375e-05s
INFO | --- Analysis for bioportal-hom took 111.31047534942627s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 0.00010061264038085938s
Availability | VoID file availability check for HOM-HARVARD took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 10.084849119186401s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 2.9325485229492188e-05s
Believability | Calculation of trust value for HOM-HARVARD took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-hom_harvard took 111.45142269134521s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 6.532669067382812e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 10.092124223709106s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006170272827148438s
Believability | Calculation of trust value for Human Phenotype Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-hp_x1 took 111.33908867835999s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 6.341934204101562e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 10.101508378982544s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.022652387619018555s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0009839534759521484s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-hpio took 111.16709995269775s
Availability | SPARQL endpoint availability check for HUGO took 4.076957702636719e-05s
Availability | VoID file availability check for HUGO took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for HUGO took 10.097672462463379s
Reputation | Calculation of the PageRank for HUGO took 0.02135753631591797s
Interlinking | Calculation of Degree of Connection for HUGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.510185241699219e-05s
Believability | Calculation of trust value for HUGO took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-hugo took 111.34955477714539s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 6.628036499023438e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 10.095208644866943s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0007009506225585938s
Believability | Calculation of trust value for Information Artifact Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for bioportal-iao took 111.34875321388245s
Availability | SPARQL endpoint availability check for ICD10 took 4.458427429199219e-05s
Availability | VoID file availability check for ICD10 took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for ICD10 took 10.089453935623169s
Reputation | Calculation of the PageRank for ICD10 took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007817745208740234s
Believability | Calculation of trust value for ICD10 took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-icd10 took 111.76081728935242s
Availability | SPARQL endpoint availability check for ICD10CM took 6.580352783203125e-05s
Availability | VoID file availability check for ICD10CM took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for ICD10CM took 10.093610286712646s
Reputation | Calculation of the PageRank for ICD10CM took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006234645843505859s
Believability | Calculation of trust value for ICD10CM took 7.62939453125e-06s
INFO | --- Analysis for bioportal-icd10cm took 111.54342722892761s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.076957702636719e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 10.100112438201904s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015854835510253906s
Believability | Calculation of trust value for ICD-10-PCS took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-icd10pcs took 111.3408875465393s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 9.989738464355469e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 10.099571228027344s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020204782485961914s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006694793701171875s
Believability | Calculation of trust value for International Classification of Diseases took 7.62939453125e-06s
INFO | --- Analysis for bioportal-icd9cm took 111.56778979301453s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 6.556510925292969e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 10.101093292236328s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.02185678482055664s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004513263702392578s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 1.5735626220703125e-05s
INFO | --- Analysis for bioportal-icf_x1 took 111.66943073272705s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 5.245208740234375e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 10.100473642349243s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0013165473937988281s
Believability | Calculation of trust value for International Classification for Nursing Practice took 7.62939453125e-06s
INFO | --- Analysis for bioportal-icnp took 111.9456434249878s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 9.036064147949219e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 10.093727350234985s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0005033016204833984s
Believability | Calculation of trust value for International Classification of Primary Care took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-icpc took 111.57291173934937s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 8.559226989746094e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 10.504659414291382s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020394086837768555s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008318424224853516s
Believability | Calculation of trust value for ICPC-2 PLUS took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-icpc2p took 111.66625785827637s
Availability | SPARQL endpoint availability check for ICPS Network took 4.124641418457031e-05s
Availability | VoID file availability check for ICPS Network took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for ICPS Network took 10.09620451927185s
Reputation | Calculation of the PageRank for ICPS Network took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00024175643920898438s
Believability | Calculation of trust value for ICPS Network took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-icps took 111.16677951812744s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 10.104465007781982s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008394718170166016s
Believability | Calculation of trust value for Infectious Disease Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ido took 111.64293456077576s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 10.099874019622803s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020135879516601562s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011243820190429688s
Believability | Calculation of trust value for Brucellosis Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-idobru took 111.47214221954346s
Availability | SPARQL endpoint availability check for Malaria Ontology took 8.106231689453125e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 10.082821369171143s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.021964073181152344s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012569427490234375s
Believability | Calculation of trust value for Malaria Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-idomal took 112.76527953147888s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 6.890296936035156e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 10.103316307067871s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02217864990234375s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0002906322479248047s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-iev took 111.75000882148743s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.458427429199219e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 10.592293500900269s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020250320434570312s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00014495849609375s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-imgt took 112.7368974685669s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.6253204345703125e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 10.099729299545288s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.021420001983642578s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005254745483398438s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-imr took 111.93798875808716s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 10.097750663757324s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007522106170654297s
Believability | Calculation of trust value for Interaction Network Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-ino took 111.96855759620667s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.744529724121094e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0011882781982421875s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 10.093807697296143s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.02030158042907715s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.075599670410156e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-invertebrata took 113.27099275588989s
Availability | SPARQL endpoint availability check for IxnO took 4.100799560546875e-05s
Availability | VoID file availability check for IxnO took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for IxnO took 10.099355220794678s
Reputation | Calculation of the PageRank for IxnO took 0.02024698257446289s
Interlinking | Calculation of Degree of Connection for IxnO took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0001823902130126953s
Believability | Calculation of trust value for IxnO took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ixno took 112.24474143981934s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.124641418457031e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 10.099504470825195s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020159006118774414s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00037288665771484375s
Believability | Calculation of trust value for SysMO-JERM took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-jerm took 111.57049489021301s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 10.098541259765625s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.62396240234375e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-kisao took 111.17571520805359s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 8.368492126464844e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 10.096204996109009s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020911693572998047s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0001914501190185547s
Believability | Calculation of trust value for Loggerhead nesting took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-lhn took 111.9417142868042s
Availability | SPARQL endpoint availability check for Lipid Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 10.100016117095947s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020313262939453125s
Believability | Calculation of trust value for Lipid Ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-lipro took 111.43475818634033s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.553794860839844e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 10.59912896156311s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0017774105072021484s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-lnc took 112.3470938205719s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.100799560546875e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 10.097821474075317s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006968975067138672s
Believability | Calculation of trust value for Mouse adult gross anatomy took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-ma took 112.43192791938782s
Availability | SPARQL endpoint availability check for Multiple alignment took 3.9577484130859375e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Multiple alignment took 10.496922731399536s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00019860267639160156s
Believability | Calculation of trust value for Multiple alignment took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mao took 112.84546828269958s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 8.273124694824219e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 10.100403308868408s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006914138793945312s
Believability | Calculation of trust value for Minimal anatomical terminology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mat took 111.96643137931824s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.1484832763671875e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 10.102426528930664s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00040841102600097656s
Believability | Calculation of trust value for Breast tissue cell lines took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-mcbcc took 111.44956684112549s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for Cell line ontology took 10.100579261779785s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007293224334716797s
Believability | Calculation of trust value for Cell line ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mccl took 112.16139960289001s
Availability | SPARQL endpoint availability check for Cell line ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Cell line ontology took 10.091816902160645s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02228999137878418s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0013813972473144531s
Believability | Calculation of trust value for Cell line ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-mccl_x1 took 112.66340517997742s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.172325134277344e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 10.096888065338135s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.022081613540649414s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00023245811462402344s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-mcv took 112.54347610473633s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 8.797645568847656e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 10.0981924533844s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017762184143066406s
Believability | Calculation of trust value for Master Drug Data Base took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mddb took 112.24493908882141s
Availability | SPARQL endpoint availability check for MedDRA took 8.559226989746094e-05s
Availability | VoID file availability check for MedDRA took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for MedDRA took 10.09991455078125s
Reputation | Calculation of the PageRank for MedDRA took 0.022225379943847656s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0008366107940673828s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0012972354888916016s
Believability | Calculation of trust value for MedDRA took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-mdr took 112.24190974235535s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 8.416175842285156e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 10.196402549743652s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02010941505432129s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008559226989746094s
Believability | Calculation of trust value for MedlinePlus Health Topics took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-medlineplus took 111.84774041175842s
Availability | SPARQL endpoint availability check for MeGO took 4.029273986816406e-05s
Availability | VoID file availability check for MeGO took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for MeGO took 10.109424352645874s
Reputation | Calculation of the PageRank for MeGO took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MeGO took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001404285430908203s
Believability | Calculation of trust value for MeGO took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-mego took 112.44698667526245s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 7.200241088867188e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 10.099721193313599s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02131199836730957s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0017790794372558594s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mesh-owl took 111.74522948265076s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 10.09743618965149s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020984888076782227s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006463527679443359s
Believability | Calculation of trust value for Mental Functioning Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-mf took 111.33655524253845s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.38690185546875e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0011594295501708984s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 10.095107793807983s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005292892456054688s
Believability | Calculation of trust value for Medaka fish anatomy and development took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-mfo took 112.0353090763092s
Availability | SPARQL endpoint availability check for Emotion Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 10.194602489471436s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.022720813751220703s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007202625274658203s
Believability | Calculation of trust value for Emotion Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-mfoem took 113.34439873695374s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.00034880638122558594s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 10.097585678100586s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02109813690185547s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 9.822845458984375e-05s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-mhc took 111.54167366027832s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.029273986816406e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 10.09975814819336s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020388126373291016s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006685256958007812s
Believability | Calculation of trust value for Protein-protein interaction took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mi took 112.22946405410767s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 3.910064697265625e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 10.196633338928223s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0006721019744873047s
Believability | Calculation of trust value for Mosquito insecticide resistance took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-miro took 111.94021368026733s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 7.43865966796875e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0003726482391357422s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 10.496795892715454s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.02266716957092285s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013589859008789062s
Believability | Calculation of trust value for Measurement Method Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-mmo took 111.84320569038391s
Availability | SPARQL endpoint availability check for MGED Ontology took 8.153915405273438e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for MGED Ontology took 10.094244241714478s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021695613861083984s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003733634948730469s
Believability | Calculation of trust value for MGED Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-mo took 112.77948355674744s
Availability | SPARQL endpoint availability check for Protein modification took 4.029273986816406e-05s
Availability | VoID file availability check for Protein modification took 0.2086772918701172s
Completeness | Calculation of interlinking completeness for Protein modification took 10.588510274887085s
Reputation | Calculation of the PageRank for Protein modification took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for Protein modification took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021266937255859375s
Believability | Calculation of trust value for Protein modification took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-mod took 112.83683586120605s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 8.96453857421875e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 10.095465183258057s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006563663482666016s
Believability | Calculation of trust value for Mammalian phenotype took 7.62939453125e-06s
INFO | --- Analysis for bioportal-mp took 111.97571349143982s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.863739013671875e-05s
Availability | VoID file availability check for Mouse pathology took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Mouse pathology took 10.096665620803833s
Reputation | Calculation of the PageRank for Mouse pathology took 0.022579431533813477s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004553794860839844s
Believability | Calculation of trust value for Mouse pathology took 1.52587890625e-05s
INFO | --- Analysis for bioportal-mpath took 111.3302686214447s
Availability | SPARQL endpoint availability check for Mass spectrometry took 7.581710815429688e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 10.100924015045166s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00033664703369140625s
Believability | Calculation of trust value for Mass spectrometry took 1.4781951904296875e-05s
INFO | --- Analysis for bioportal-ms took 111.64759397506714s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 8.392333984375e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 10.19877290725708s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.02032327651977539s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018031597137451172s
Believability | Calculation of trust value for Medical Subject Headings took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-msh took 112.33585405349731s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 8.082389831542969e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 10.105918169021606s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02037978172302246s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00016570091247558594s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-mthch took 111.24244570732117s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 10.5898118019104s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007734298706054688s
Believability | Calculation of trust value for Natural Products Ontology took 2.002716064453125e-05s
INFO | --- Analysis for bioportal-natpro took 111.8455274105072s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.076957702636719e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 10.09426736831665s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.021356821060180664s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0007708072662353516s
Believability | Calculation of trust value for NCBI organismal classification took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ncbitaxon took 111.56582975387573s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 9.1552734375e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 10.204522132873535s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02030324935913086s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.001920461654663086s
Believability | Calculation of trust value for NCI Thesaurus took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-ncit took 111.94100451469421s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.029273986816406e-05s
Availability | VoID file availability check for National Drug Data File took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for National Drug Data File took 10.10643219947815s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.000598907470703125s
Believability | Calculation of trust value for National Drug Data File took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-nddf took 112.24491548538208s
Availability | SPARQL endpoint availability check for National Drug File took 4.4345855712890625e-05s
Availability | VoID file availability check for National Drug File took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for National Drug File took 10.099235773086548s
Reputation | Calculation of the PageRank for National Drug File took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012371540069580078s
Believability | Calculation of trust value for National Drug File took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-ndfrt took 111.95026731491089s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.00543212890625e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 10.100454330444336s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02016758918762207s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011255741119384766s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-nemo_x1 took 112.26997995376587s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 9.512901306152344e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 10.199697017669678s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006611347198486328s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-neomark took 112.47012639045715s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 8.320808410644531e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 10.203377723693848s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02040863037109375s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012421607971191406s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-neomarkontology took 111.37458848953247s
Availability | SPARQL endpoint availability check for NIFSTD took 4.172325134277344e-05s
Availability | VoID file availability check for NIFSTD took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for NIFSTD took 10.199025869369507s
Reputation | Calculation of the PageRank for NIFSTD took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0009615421295166016s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019767284393310547s
Believability | Calculation of trust value for NIFSTD took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-nif took 111.66734862327576s
Availability | SPARQL endpoint availability check for NIF Cell took 8.296966552734375e-05s
Availability | VoID file availability check for NIF Cell took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for NIF Cell took 10.198297262191772s
Reputation | Calculation of the PageRank for NIF Cell took 0.020221710205078125s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.001287698745727539s
Believability | Calculation of trust value for NIF Cell took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-nif_cell took 111.557701587677s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 8.511543273925781e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 10.095070838928223s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0013728141784667969s
Believability | Calculation of trust value for NIF Dysfunction took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-nif_dysfunction took 111.76597309112549s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 10.100436210632324s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005502700805664062s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-nigo took 112.77559423446655s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 5.745887756347656e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 10.097560405731201s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005390644073486328s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-nmr took 111.44024467468262s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 6.556510925292969e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 10.103169679641724s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011587142944335938s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 112.67302632331848s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 8.344650268554688e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.00033092498779296875s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 10.09505844116211s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.02112865447998047s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012814998626708984s
Believability | Calculation of trust value for NanoParticle Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-npo took 111.2644100189209s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0010836124420166016s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 10.199314594268799s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0006847381591796875s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-oae took 112.4775619506836s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 5.245208740234375e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 10.102277517318726s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014171600341796875s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-obi took 111.26778078079224s
Availability | SPARQL endpoint availability check for OBOE took 4.029273986816406e-05s
Availability | VoID file availability check for OBOE took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for OBOE took 10.098052978515625s
Reputation | Calculation of the PageRank for OBOE took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for OBOE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.0001227855682373047s
Believability | Calculation of trust value for OBOE took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-oboe took 112.57150411605835s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.291534423828125e-05s
Availability | VoID file availability check for OBOE SBC took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for OBOE SBC took 10.098779201507568s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020824432373046875s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007913112640380859s
Believability | Calculation of trust value for OBOE SBC took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 112.26861476898193s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 8.416175842285156e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 10.095323324203491s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005629062652587891s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 1.430511474609375e-05s
INFO | --- Analysis for bioportal-ocre took 111.67922067642212s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.601478576660156e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 10.09886884689331s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0007989406585693359s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-odgi took 112.34402537345886s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 6.4849853515625e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 10.104694604873657s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.022421598434448242s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008628368377685547s
Believability | Calculation of trust value for Ontology for Genetic Interval took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ogi took 112.24229907989502s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.029273986816406e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 10.08969497680664s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002944469451904297s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-ogmd took 112.73626804351807s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 9.846687316894531e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 10.10319209098816s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006783008575439453s
Believability | Calculation of trust value for Ontology for General Medical Science took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ogms took 111.97425651550293s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.100799560546875e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 10.597322702407837s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011649131774902344s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-omim took 111.86843729019165s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0003197193145751953s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 10.100131750106812s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020696640014648438s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003943443298339844s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-omit took 111.86913275718689s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 10.107415676116943s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005700588226318359s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-omrse took 112.07827353477478s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 7.224082946777344e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 10.108583927154541s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007545948028564453s
Believability | Calculation of trust value for Ontology of Data Mining took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ontodm took 112.06199097633362s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 3.933906555175781e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 10.096730470657349s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.022843599319458008s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00025081634521484375s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-ontodt took 112.76477694511414s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 8.630752563476562e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 10.100061655044556s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020200490951538086s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006158351898193359s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ontoorpha took 111.34651803970337s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 10.09677529335022s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0008733272552490234s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 7.62939453125e-06s
INFO | --- Analysis for bioportal-opl took 111.87287592887878s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.00543212890625e-05s
Availability | VoID file availability check for Phenotypic quality took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 10.102923154830933s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.021990299224853516s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0008273124694824219s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0009002685546875s
Believability | Calculation of trust value for Phenotypic quality took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pato took 112.67101383209229s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.76837158203125e-05s
Availability | VoID file availability check for Physician Data Query took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Physician Data Query took 10.10085391998291s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.000820159912109375s
Believability | Calculation of trust value for Physician Data Query took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-pdq took 111.67252779006958s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.00543212890625e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 10.112304449081421s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020994186401367188s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0009596347808837891s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.00095367431640625s
Believability | Calculation of trust value for Pediatric Terminology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-pedterm took 111.96724390983582s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 10.0968017578125s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.02063608169555664s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00022482872009277344s
Believability | Calculation of trust value for Parasite Experiment Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-peo took 112.9766731262207s
Availability | SPARQL endpoint availability check for PHARE took 8.893013000488281e-05s
Availability | VoID file availability check for PHARE took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for PHARE took 10.102069854736328s
Reputation | Calculation of the PageRank for PHARE took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for PHARE took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for PHARE took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006177425384521484s
Believability | Calculation of trust value for PHARE took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-phare took 111.87006664276123s
Availability | SPARQL endpoint availability check for PKO_Re took 5.316734313964844e-05s
Availability | VoID file availability check for PKO_Re took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for PKO_Re took 10.101654767990112s
Reputation | Calculation of the PageRank for PKO_Re took 0.02177119255065918s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001804828643798828s
Believability | Calculation of trust value for PKO_Re took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-pko took 111.74181771278381s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.029273986816406e-05s
Availability | VoID file availability check for PMA 2010 took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for PMA 2010 took 10.101956367492676s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008840560913085938s
Believability | Calculation of trust value for PMA 2010 took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-pma took 112.44009852409363s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 3.910064697265625e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 10.098854780197144s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.022182464599609375s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.000186920166015625s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-pmr took 111.77488112449646s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Plant Anatomy took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 10.195460557937622s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.021902799606323242s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.000370025634765625s
Believability | Calculation of trust value for Plant Anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-po took 111.57241654396057s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.00543212890625e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 10.198220252990723s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.914138793945312e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-po_x1 took 112.24397921562195s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Plant Ontology took 10.10279369354248s
Reputation | Calculation of the PageRank for Plant Ontology took 0.02106451988220215s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004277229309082031s
Believability | Calculation of trust value for Plant Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-po_x2 took 111.26031279563904s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 9.012222290039062e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 10.198325157165527s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006353855133056641s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-pr took 111.63537049293518s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 8.177757263183594e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 10.108776330947876s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00026106834411621094s
Believability | Calculation of trust value for Proteomics data and process provenance took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-propreo took 111.36900472640991s
Availability | SPARQL endpoint availability check for Pathway ontology took 6.532669067382812e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for Pathway ontology took 10.094820261001587s
Reputation | Calculation of the PageRank for Pathway ontology took 0.0202786922454834s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.000125885009765625s
Believability | Calculation of trust value for Pathway ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-pw took 111.93648338317871s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 10.205091953277588s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-qibo took 111.4750988483429s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.029273986816406e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 10.171737432479858s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017328262329101562s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-rcd took 112.86460733413696s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 10.59533429145813s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02206254005432129s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012063980102539062s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-rctontology took 112.27757215499878s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 10.09166407585144s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.441375732421875e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-repo took 111.2442843914032s
Availability | SPARQL endpoint availability check for Physico-chemical process took 3.9577484130859375e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 10.098008155822754s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00018167495727539062s
Believability | Calculation of trust value for Physico-chemical process took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-rex took 111.94226908683777s
Availability | SPARQL endpoint availability check for RadLex took 8.630752563476562e-05s
Availability | VoID file availability check for RadLex took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for RadLex took 10.093738555908203s
Reputation | Calculation of the PageRank for RadLex took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0014774799346923828s
Believability | Calculation of trust value for RadLex took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-rid took 111.66591596603394s
Availability | SPARQL endpoint availability check for RNA ontology took 3.981590270996094e-05s
Availability | VoID file availability check for RNA ontology took 0.0003120899200439453s
Completeness | Calculation of interlinking completeness for RNA ontology took 10.100877523422241s
Reputation | Calculation of the PageRank for RNA ontology took 0.022096633911132812s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005497932434082031s
Believability | Calculation of trust value for RNA ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-rnao took 112.13926672935486s
Availability | SPARQL endpoint availability check for Role Ontology took 8.177757263183594e-05s
Availability | VoID file availability check for Role Ontology took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Role Ontology took 10.206624031066895s
Reputation | Calculation of the PageRank for Role Ontology took 0.0226747989654541s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018596649169921875s
Believability | Calculation of trust value for Role Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-roleo took 112.33531475067139s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 6.508827209472656e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 10.093130111694336s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001742839813232422s
Believability | Calculation of trust value for Rat Strain Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-rs took 111.97079682350159s
Availability | SPARQL endpoint availability check for RxNORM took 3.981590270996094e-05s
Availability | VoID file availability check for RxNORM took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for RxNORM took 10.100619077682495s
Reputation | Calculation of the PageRank for RxNORM took 0.02122783660888672s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006268024444580078s
Believability | Calculation of trust value for RxNORM took 2.956390380859375e-05s
INFO | --- Analysis for bioportal-rxnorm took 111.66942310333252s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.100799560546875e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 10.095870971679688s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.022437572479248047s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.001032114028930664s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-sao took 111.47577452659607s
Availability | SPARQL endpoint availability check for Systems Biology took 9.369850158691406e-05s
Availability | VoID file availability check for Systems Biology took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for Systems Biology took 10.598725318908691s
Reputation | Calculation of the PageRank for Systems Biology took 0.022164106369018555s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00045013427734375s
Believability | Calculation of trust value for Systems Biology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-sbo took 112.54154562950134s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 10.101207256317139s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.0001087188720703125s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-sbro took 111.24426364898682s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 8.130073547363281e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 10.205527305603027s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.021329641342163086s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0009925365447998047s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0015261173248291016s
Believability | Calculation of trust value for Sleep Domain Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-sdo took 111.43804788589478s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 8.678436279296875e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 10.100232362747192s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0009763240814208984s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0004448890686035156s
Believability | Calculation of trust value for Sample processing and separation techniques took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-sep took 112.34556102752686s
Availability | SPARQL endpoint availability check for Student Health Record took 3.981590270996094e-05s
Availability | VoID file availability check for Student Health Record took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Student Health Record took 10.100376605987549s
Reputation | Calculation of the PageRank for Student Health Record took 0.021629810333251953s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.00042247772216796875s
Believability | Calculation of trust value for Student Health Record took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-shr took 111.66658401489258s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 10.097543001174927s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0011866092681884766s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 3.886222839355469e-05s
INFO | --- Analysis for bioportal-sio took 111.370854139328s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 8.368492126464844e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 10.10293459892273s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02091503143310547s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00019669532775878906s
Believability | Calculation of trust value for Situation-Based Access Control took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-sitbac took 112.77012085914612s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.1484832763671875e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 10.207256317138672s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.02129840850830078s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019202232360839844s
Believability | Calculation of trust value for SNOMED Clinical Terms took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-snomedct took 111.74302911758423s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 10.094283819198608s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020140886306762695s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006511211395263672s
Believability | Calculation of trust value for SNP-Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-snpo took 112.37096071243286s
Availability | SPARQL endpoint availability check for Sequence types and features took 7.009506225585938e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Sequence types and features took 10.099251747131348s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005857944488525391s
Believability | Calculation of trust value for Sequence types and features took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-so_x1 took 112.26929807662964s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 5.364418029785156e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 10.096952199935913s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015482902526855469s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-sopharm took 112.74513483047485s
Availability | SPARQL endpoint availability check for SoyOntology took 4.00543212890625e-05s
Availability | VoID file availability check for SoyOntology took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for SoyOntology took 10.106876134872437s
Reputation | Calculation of the PageRank for SoyOntology took 0.02173018455505371s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00013303756713867188s
Believability | Calculation of trust value for SoyOntology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-soy took 112.66982889175415s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Spider Ontology took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for Spider Ontology took 10.099962949752808s
Reputation | Calculation of the PageRank for Spider Ontology took 0.021617412567138672s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003178119659423828s
Believability | Calculation of trust value for Spider Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-spd took 112.24157309532166s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 10.096372127532959s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0008082389831542969s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0003082752227783203s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 1.7881393432617188e-05s
INFO | --- Analysis for bioportal-spto took 111.36788964271545s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 10.093932390213013s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00042366981506347656s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-sso took 113.33980560302734s
Availability | SPARQL endpoint availability check for Software Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Software Ontology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Software Ontology took 10.10006046295166s
Reputation | Calculation of the PageRank for Software Ontology took 0.020255565643310547s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00039887428283691406s
Believability | Calculation of trust value for Software Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-swo took 111.34879231452942s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.458427429199219e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 10.10325288772583s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.023149728775024414s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002396106719970703s
Believability | Calculation of trust value for Tick gross anatomy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-tads took 112.24351596832275s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 10.104030847549438s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02050161361694336s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008509159088134766s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 1.5497207641601562e-05s
INFO | --- Analysis for bioportal-tao took 111.73156189918518s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 8.0108642578125e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 10.088429927825928s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020274639129638672s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.7738037109375e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-taxrank took 112.32718777656555s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 6.4849853515625e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 10.20431137084961s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 6.771087646484375e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-teddy took 112.2315936088562s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 10.106637001037598s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0007817745208740234s
Believability | Calculation of trust value for Time Event Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-teo took 112.67657732963562s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 10.101146459579468s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00037407875061035156s
Believability | Calculation of trust value for Mosquito gross anatomy took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-tgma took 111.33381223678589s
Availability | SPARQL endpoint availability check for thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for thesaurus took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for thesaurus took 10.090370655059814s
Reputation | Calculation of the PageRank for thesaurus took 0.021404504776000977s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.389617919921875e-05s
Believability | Calculation of trust value for thesaurus took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-thesaurus took 112.8417809009552s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 5.602836608886719e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 10.594623327255249s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003314018249511719s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 113.13741111755371s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 0.0001068115234375s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 10.599802017211914s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020158767700195312s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0007801055908203125s
Believability | Calculation of trust value for Translational Medicine Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-tmo took 112.33938980102539s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 10.101171493530273s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.022291183471679688s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.000156402587890625s
Believability | Calculation of trust value for Plant Trait Ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-to took 112.43869543075562s
Availability | SPARQL endpoint availability check for TOK_Ontology took 3.8623809814453125e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 10.097486972808838s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001800060272216797s
Believability | Calculation of trust value for TOK_Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-tok took 111.55037879943848s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 3.910064697265625e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0007698535919189453s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 10.594018459320068s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0001971721649169922s
Believability | Calculation of trust value for Teleost taxonomy took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-tto took 112.43827676773071s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 8.320808410644531e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 10.605550050735474s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02031254768371582s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0009829998016357422s
Believability | Calculation of trust value for Uber anatomy ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-uberon took 113.13309335708618s
Availability | SPARQL endpoint availability check for Units Ontology took 8.344650268554688e-05s
Availability | VoID file availability check for Units Ontology took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Units Ontology took 10.099945068359375s
Reputation | Calculation of the PageRank for Units Ontology took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00021314620971679688s
Believability | Calculation of trust value for Units Ontology took 1.7404556274414062e-05s
INFO | --- Analysis for bioportal-unitsontology took 111.74429702758789s
Availability | SPARQL endpoint availability check for Units of measurement took 9.703636169433594e-05s
Availability | VoID file availability check for Units of measurement took 0.0010869503021240234s
Completeness | Calculation of interlinking completeness for Units of measurement took 10.100653886795044s
Reputation | Calculation of the PageRank for Units of measurement took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002789497375488281s
Believability | Calculation of trust value for Units of measurement took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-uo took 111.49046039581299s
Availability | SPARQL endpoint availability check for VANDF took 4.0531158447265625e-05s
Availability | VoID file availability check for VANDF took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for VANDF took 10.595202207565308s
Reputation | Calculation of the PageRank for VANDF took 0.0213773250579834s
Interlinking | Calculation of Degree of Connection for VANDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VANDF took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.000659942626953125s
Believability | Calculation of trust value for VANDF took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-vandf took 112.54071688652039s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0003223419189453125s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 10.096563816070557s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02291250228881836s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004165172576904297s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-vao took 111.73627305030823s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 6.532669067382812e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0003273487091064453s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 10.098661661148071s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0010180473327636719s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006330013275146484s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-vhog took 111.94314360618591s
Availability | SPARQL endpoint availability check for VIVO took 4.220008850097656e-05s
Availability | VoID file availability check for VIVO took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for VIVO took 10.099475860595703s
Reputation | Calculation of the PageRank for VIVO took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for VIVO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003376007080078125s
Believability | Calculation of trust value for VIVO took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-vivo took 112.94559240341187s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 0.00012063980102539062s
Availability | VoID file availability check for Vaccine Ontology took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 10.092912435531616s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02054119110107422s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.001249074935913086s
Believability | Calculation of trust value for Vaccine Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-vo took 111.74310183525085s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 10.1932692527771s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.021104812622070312s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00019478797912597656s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-vt took 111.5484230518341s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 9.465217590332031e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.00030875205993652344s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 10.099191188812256s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.0212099552154541s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.00047850608825683594s
Believability | Calculation of trust value for C. elegans gross anatomy took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-wbbt took 111.24662685394287s
Availability | SPARQL endpoint availability check for C. elegans development took 3.933906555175781e-05s
Availability | VoID file availability check for C. elegans development took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for C. elegans development took 10.192488431930542s
Reputation | Calculation of the PageRank for C. elegans development took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.887580871582031e-05s
Believability | Calculation of trust value for C. elegans development took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-wbls took 112.4439480304718s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 0.00010848045349121094s
Availability | VoID file availability check for C. elegans phenotype took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 10.101180791854858s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.021425962448120117s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.678436279296875e-05s
Believability | Calculation of trust value for C. elegans phenotype took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-wbphenotype took 112.64767837524414s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 5.245208740234375e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 10.102195739746094s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.02106928825378418s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005898475646972656s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-who took 112.37131667137146s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.029273986816406e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.12928080558776855s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 10.168351888656616s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020642995834350586s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006501674652099609s
Believability | Calculation of trust value for Xenopus anatomy and development took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-xao took 111.84040451049805s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 8.153915405273438e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 10.094940900802612s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00022339820861816406s
Believability | Calculation of trust value for Experimental Conditions Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-xco took 111.93074297904968s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 7.2479248046875e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 10.098261594772339s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.02246713638305664s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.000255584716796875s
Believability | Calculation of trust value for Yeast phenotypes took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-ypo took 112.7442274093628s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 7.581710815429688e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 10.090511798858643s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02070307731628418s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007481575012207031s
Believability | Calculation of trust value for Zebrafish anatomy and development took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-zfa took 112.46723127365112s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 9.179115295410156e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 10.0841646194458s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.022427082061767578s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.765655517578125e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.2874603271484375e-05s
INFO | --- Analysis for Bioportal_link took 111.64403915405273s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.00011944770812988281s
Availability | VoID file availability check for BioSamples RDF took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 10.098978757858276s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02235865592956543s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.0517578125e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.3113021850585938e-05s
INFO | --- Analysis for biosamples-rdf took 111.67521405220032s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 4.315376281738281e-05s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 10.105599880218506s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011110305786132812s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for bis-linked-data took 112.76657938957214s
Availability | SPARQL endpoint availability check for Bitzi took 4.863739013671875e-05s
Availability | VoID file availability check for Bitzi took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Bitzi took 10.0944664478302s
Reputation | Calculation of the PageRank for Bitzi took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for Bitzi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bitzi took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bitzi took 1.2636184692382812e-05s
INFO | --- Analysis for bitzi took 112.16919684410095s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.0531158447265625e-05s
Availability | VoID file availability check for BizkaiSense took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for BizkaiSense took 10.102659702301025s
Reputation | Calculation of the PageRank for BizkaiSense took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 2.8371810913085938e-05s
Believability | Calculation of trust value for BizkaiSense took 1.3828277587890625e-05s
INFO | --- Analysis for bizkaisense took 111.96271300315857s
Availability | SPARQL endpoint availability check for blabla.itemlist took 8.392333984375e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 10.595033407211304s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02077937126159668s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0040740966796875e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.2874603271484375e-05s
INFO | --- Analysis for blabla-itemlist took 112.44535040855408s
Availability | SPARQL endpoint availability check for blabla.itemlist took 7.009506225585938e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 10.197860479354858s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.021015167236328125s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0279159545898438e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.3589859008789062e-05s
INFO | --- Analysis for blabla_itemlist took 111.94372582435608s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.630752563476562e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 10.098562240600586s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02246832847595215s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.076957702636719e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for bll-thesaurus took 111.36890697479248s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.3387341499328613s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 10.100449562072754s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.175041198730469e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for bluk-bnb took 112.9419813156128s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.3179199695587158s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006914138793945312s
Extra | Recovery of all triples for Thesaurus BNCF took 111.77819299697876s
Performance | Total latancy measurement for Thesaurus BNCF took 1.4765920639038086s
Amount of data | Number of triples check for Thesaurus BNCF took 1.0866098403930664s
Interoperability | New terms check for Thesaurus BNCF took 1.749124526977539s
Versatility | Languages check for Thesaurus BNCF took 7.255928993225098s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 1.2660729885101318s
Security | Check HTTPS for Thesaurus BNCF took 0.278226375579834s
Interpretability | RDF structures check for Thesaurus BNCF took 0.4095616340637207s
Versatility | Serialization formats check for Thesaurus BNCF took 0.42122435569763184s
Availability | RDF dump link check for Thesaurus BNCF took 0.4345715045928955s
License | MR license check for Thesaurus BNCF took 0.42066526412963867s
License | HR license check for Thesaurus BNCF took 0.3113679885864258s
Amount of data | Number of property check for Thesaurus BNCF took 0.17970585823059082s
Understandability | Number of label check for Thesaurus BNCF took 0.38877034187316895s
Understandability | URI regex check for Thesaurus BNCF took 0.5285828113555908s
Understandability | Vocabs check for Thesaurus BNCF took 0.24557948112487793s
Verifiability | Authors check for Thesaurus BNCF took 0.21606135368347168s
Verifiability | Publishers check for Thesaurus BNCF took 0.23513317108154297s
Performance | Throughput check for Thesaurus BNCF took 11.801132440567017s
Amount of data | Check the number of entities for Thesaurus BNCF took 3.0279159545898438e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.5742676258087158s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.6046323776245117s
Interlinking | skos check for Thesaurus BNCF took 0.6244146823883057s
Interlinking | skos check for Thesaurus BNCF took 0.6113073825836182s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.4799981117248535s
Currency | Creation date check for Thesaurus BNCF took 1.1115398406982422s
Currency | Modification date check for Thesaurus BNCF took 1.1895999908447266s
Rep.Conc. | URIs length for Thesaurus BNCF took 26.544353485107422s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.2343888282775879s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.27437424659729004s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.23484253883361816s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 13.36100697517395s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5008785724639893s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.909310817718506s
Consistency | Disjoint class check for Thesaurus BNCF took 0.36061787605285645s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.9700429439544678s
Consistency | Misplaced classes for Thesaurus BNCF took 6.986435413360596s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 9.299371004104614s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4932291507720947s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.4461183547973633s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.391685962677002s
Security | Sign check for Thesaurus BNCF took 0.24237275123596191s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 22.088122606277466s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 10.143064975738525s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.021678686141967773s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 6.842613220214844e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.384185791015625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.239776611328125e-05s
INFO | --- Analysis for bncf-ns took 372.25201869010925s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.678436279296875e-05s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0010476112365722656s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.206045389175415s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02253437042236328s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.647804260253906e-05s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.58306884765625e-06s
INFO | --- Analysis for bpr took 111.4123182296753s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 8.630752563476562e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0011789798736572266s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 10.198946714401245s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020605802536010742s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.556510925292969e-05s
Believability | Calculation of trust value for Brazilian Politicians took 1.239776611328125e-05s
INFO | --- Analysis for brazilian-politicians took 112.27744388580322s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.00543212890625e-05s
Availability | VoID file availability check for BrazilianCities took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for BrazilianCities took 10.09698486328125s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.695487976074219e-05s
Believability | Calculation of trust value for BrazilianCities took 8.58306884765625e-06s
INFO | --- Analysis for braziliancities took 111.4424045085907s
Availability | SPARQL endpoint availability check for Bricklink took 8.678436279296875e-05s
Availability | VoID file availability check for Bricklink took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Bricklink took 10.100563049316406s
Reputation | Calculation of the PageRank for Bricklink took 0.02180624008178711s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.009506225585938e-05s
Believability | Calculation of trust value for Bricklink took 1.3589859008789062e-05s
INFO | --- Analysis for bricklink took 112.73562526702881s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.094257831573486s
Availability | VoID file availability check for British Museum Collection took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for British Museum Collection took 10.200263977050781s
Reputation | Calculation of the PageRank for British Museum Collection took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.123283386230469e-05s
Believability | Calculation of trust value for British Museum Collection took 1.3113021850585938e-05s
INFO | --- Analysis for british-museum-collection took 172.05083203315735s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 8.511543273925781e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 10.100725412368774s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.021775245666503906s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.649162292480469e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.4066696166992188e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 112.23153877258301s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.029273986816406e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 10.104946613311768s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 3.4332275390625e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 1.2159347534179688e-05s
INFO | --- Analysis for bsv took 111.5403254032135s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 8.535385131835938e-05s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.192677736282349s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.021175861358642578s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3589859008789062e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3113021850585938e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 111.44430375099182s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 3.981590270996094e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 10.100106000900269s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.3113021850585938e-05s
INFO | --- Analysis for bund-offener-haushalt took 111.43844771385193s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 8.487701416015625e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 10.093092203140259s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020804166793823242s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.266334533691406e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 1.33514404296875e-05s
INFO | --- Analysis for bundestagnebeneinkuenfte took 111.53139543533325s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 8.392333984375e-05s
Availability | VoID file availability check for business.data.gov.uk took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 10.099316120147705s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02174520492553711s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.173683166503906e-05s
Believability | Calculation of trust value for business.data.gov.uk took 7.867813110351562e-06s
INFO | --- Analysis for business-data-gov-uk took 111.84650611877441s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.567650318145752s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0005450248718261719s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 4.151451110839844s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.6513049602508545s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.6166572570800781s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.8379592895507812s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 44.041815757751465s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.3090333938598633s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.3282439708709717s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5415966510772705s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3758554458618164s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.440946102142334s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.6426317691802979s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 21.16830086708069s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.5262651443481445s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.8702266216278076s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.9306585788726807s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.5492489337921143s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.43720412254333496s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.4773085117340088s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 12.394882678985596s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 6.842613220214844e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.2820765972137451s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.28841710090637207s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.46475815773010254s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.5565812587738037s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.40407633781433105s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 1.3127539157867432s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.855708122253418s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.881942987442017s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.3871903419494629s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5956871509552002s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5359833240509033s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.5869860649108887s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.034017324447631836s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.027986526489257812s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.5872178077697754s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.8508634567260742s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.42305588722229004s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.643498182296753s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2619421482086182s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.485079288482666s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.030931949615478516s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.27457451820373535s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.2654838562011719s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1343.1936604976654s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 10.832676649093628s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021357297897338867s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.9073486328125e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 8.58306884765625e-06s
INFO | --- Analysis for BVMC took 1603.4420731067657s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 8.630752563476562e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 10.50113844871521s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.021560192108154297s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.814697265625e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.152557373046875e-06s
INFO | --- Analysis for cabbage took 114.55760931968689s
Availability | SPARQL endpoint availability check for cablegate took 4.076957702636719e-05s
Availability | VoID file availability check for cablegate took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for cablegate took 10.104059934616089s
Reputation | Calculation of the PageRank for cablegate took 0.020390987396240234s
Interlinking | Calculation of Degree of Connection for cablegate took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.508827209472656e-05s
Believability | Calculation of trust value for cablegate took 1.33514404296875e-05s
INFO | --- Analysis for cablegate took 112.46453189849854s
Availability | SPARQL endpoint availability check for Calames took 8.916854858398438e-05s
Availability | VoID file availability check for Calames took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Calames took 10.10278844833374s
Reputation | Calculation of the PageRank for Calames took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for Calames took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Calames took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Calames took 3.24249267578125e-05s
Believability | Calculation of trust value for Calames took 1.2159347534179688e-05s
INFO | --- Analysis for calames took 111.54387283325195s
Availability | SPARQL endpoint availability check for CaLiGraph took 8.511543273925781e-05s
Availability | VoID file availability check for CaLiGraph took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for CaLiGraph took 10.13175106048584s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021986007690429688s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.123283386230469e-05s
Believability | Calculation of trust value for CaLiGraph took 1.239776611328125e-05s
INFO | --- Analysis for CaLiGraph took 111.7474799156189s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.00010561943054199219s
Availability | VoID file availability check for CaLiGraph took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for CaLiGraph took 10.100419044494629s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021875381469726562s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 8.20159912109375e-05s
Believability | Calculation of trust value for CaLiGraph took 1.33514404296875e-05s
INFO | --- Analysis for caligraph took 111.46819806098938s
Availability | SPARQL endpoint availability check for can-link took 4.076957702636719e-05s
Availability | VoID file availability check for can-link took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for can-link took 10.105445384979248s
Reputation | Calculation of the PageRank for can-link took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for can-link took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for can-link took 4.0531158447265625e-05s
Believability | Calculation of trust value for can-link took 8.344650268554688e-06s
INFO | --- Analysis for can-link took 111.66911745071411s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 8.702278137207031e-05s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 10.095884084701538s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.266334533691406e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.430511474609375e-05s
INFO | --- Analysis for cap-italy-rdf took 111.86856889724731s
Availability | SPARQL endpoint availability check for person took 8.630752563476562e-05s
Availability | VoID file availability check for person took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for person took 10.09401273727417s
Reputation | Calculation of the PageRank for person took 0.021911144256591797s
Interlinking | Calculation of Degree of Connection for person took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for person took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for person took 2.7894973754882812e-05s
Believability | Calculation of trust value for person took 1.2874603271484375e-05s
INFO | --- Analysis for card took 111.3674247264862s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 8.249282836914062e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 10.100435018539429s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.981590270996094e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.4781951904296875e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 111.85365104675293s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.124641418457031e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0010983943939208984s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 10.098891496658325s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 2.8371810913085938e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.3589859008789062e-05s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 112.33229279518127s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 6.031990051269531e-05s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 10.102789402008057s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.076957702636719e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 7.62939453125e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 111.94608759880066s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 8.559226989746094e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 10.103326082229614s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.021429777145385742s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00011014938354492188s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2636184692382812e-05s
INFO | --- Analysis for ce4r took 111.84879779815674s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4999403953552246s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005335807800292969s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.101818561553955s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.8658382892608643s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4199330806732178s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.690793514251709s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.142359495162964s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16168808937072754s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.27950143814086914s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16773033142089844s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15367746353149414s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24900054931640625s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2989358901977539s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16419386863708496s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24962949752807617s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3263707160949707s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17474937438964844s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19488525390625s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1740114688873291s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 11.135507106781006s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 6.866455078125e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26891589164733887s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16350769996643066s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.679349422454834s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16358470916748047s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1657116413116455s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5913112163543701s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.456864595413208s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.0017385482788086s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16349339485168457s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.24215459823608398s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.24873685836791992s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6216938495635986s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028865575790405273s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.028873682022094727s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.33851027488708496s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.1864063739776611s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9869818687438965s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.3024702072143555s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.520596981048584s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03222966194152832s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.28938794136047363s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16351914405822754s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2913.896516561508s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 11.331606149673462s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0015745162963867188s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 2.6226043701171875e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.3589859008789062e-05s
INFO | --- Analysis for ceo took 3151.1874680519104s
Availability | SPARQL endpoint availability check for Charging Stations took 4.124641418457031e-05s
Availability | VoID file availability check for Charging Stations took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Charging Stations took 10.098226308822632s
Reputation | Calculation of the PageRank for Charging Stations took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.1948089599609375e-05s
Believability | Calculation of trust value for Charging Stations took 1.430511474609375e-05s
INFO | --- Analysis for charging-stations took 113.101567029953s
Availability | SPARQL endpoint availability check for Chat Game corpus took 8.726119995117188e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 10.096004724502563s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02220630645751953s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.075599670410156e-05s
Believability | Calculation of trust value for Chat Game corpus took 7.867813110351562e-06s
INFO | --- Analysis for chat-game-corpus took 112.94493913650513s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 3.9577484130859375e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 10.103737354278564s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.022490262985229492s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.337860107421875e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 3.695487976074219e-05s
INFO | --- Analysis for chebi took 111.84427881240845s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 9.083747863769531e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.007184505462646484s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 10.589455366134644s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02118086814880371s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.507469177246094e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.3828277587890625e-05s
INFO | --- Analysis for chem2bio2rdf took 113.1688985824585s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 8.630752563476562e-05s
Availability | VoID file availability check for ChEMBL RDF took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 10.10384464263916s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.0219876766204834s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.982948303222656e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.3589859008789062e-05s
INFO | --- Analysis for chembl-rdf took 112.04662084579468s
Availability | SPARQL endpoint availability check for chemdb  dataset took 4.553794860839844e-05s
Availability | VoID file availability check for chemdb  dataset took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 10.095059633255005s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.020770549774169922s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 6.127357482910156e-05s
Believability | Calculation of trust value for chemdb  dataset took 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-basicInfo took 112.7377998828888s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 4.00543212890625e-05s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0002982616424560547s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 10.104235410690308s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.363059997558594e-05s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.33514404296875e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 111.65076732635498s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 9.059906005859375e-05s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 10.10098934173584s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.2874603271484375e-05s
INFO | --- Analysis for chemdb-phaseTransition took 111.97179746627808s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 5.3882598876953125e-05s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 10.102313756942749s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0008757114410400391s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.0558319091796875e-05s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.2874603271484375e-05s
INFO | --- Analysis for chemdb-thermochemistry took 111.56902742385864s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.029273986816406e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 10.10545563697815s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020157575607299805s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 2.6702880859375e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.3113021850585938e-05s
INFO | --- Analysis for chempedia-rdf took 112.56936717033386s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.1961669921875e-05s
Availability | VoID file availability check for Chiman Maru took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Chiman Maru took 10.097034692764282s
Reputation | Calculation of the PageRank for Chiman Maru took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.695487976074219e-05s
Believability | Calculation of trust value for Chiman Maru took 8.58306884765625e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 112.26970744132996s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 393.3520567417145s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 10.599592685699463s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.743171691894531e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.239776611328125e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 776.5851905345917s
Availability | SPARQL endpoint availability check for Chronicling America took 4.673004150390625e-05s
Availability | VoID file availability check for Chronicling America took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Chronicling America took 10.096372604370117s
Reputation | Calculation of the PageRank for Chronicling America took 0.020869016647338867s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0009906291961669922s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00013446807861328125s
Believability | Calculation of trust value for Chronicling America took 1.2636184692382812e-05s
INFO | --- Analysis for chronicling-america took 114.19645476341248s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.9187538623809814s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0005102157592773438s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 75.4160578250885s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.3586750030517578s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.7132735252380371s
Interoperability | New terms check for Cultural Heritage Thesaurus took 15.493658542633057s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.5258781909942627s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5069589614868164s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.26611995697021484s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.28798532485961914s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 10.639528751373291s
License | MR license check for Cultural Heritage Thesaurus took 0.3311440944671631s
License | HR license check for Cultural Heritage Thesaurus took 0.4415583610534668s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.29572248458862305s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3208291530609131s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5527505874633789s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.25391721725463867s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.2698967456817627s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.2929801940917969s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.206613302230835s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 3.814697265625e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.3225290775299072s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.27136659622192383s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.2888023853302002s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.289233922958374s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.2977166175842285s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5879209041595459s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5527868270874023s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 24.24161171913147s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 0.9733288288116455s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.29725050926208496s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.25847744941711426s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.274888277053833s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 5.066840648651123s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21634888648986816s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.26610827445983887s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.1028227806091309s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2590010166168213s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 8.98626160621643s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 1.9886600971221924s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.000133514404296875s
Security | Sign check for Cultural Heritage Thesaurus took 0.2570838928222656s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 278.7335922718048s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 10.297369718551636s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.025418758392333984s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0006811618804931641s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.0001475811004638672s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.4416236877441406s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for cht took 582.6423761844635s
Availability | SPARQL endpoint availability check for ciard-ring took 4.029273986816406e-05s
Availability | VoID file availability check for ciard-ring took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for ciard-ring took 10.50824522972107s
Reputation | Calculation of the PageRank for ciard-ring took 0.02077198028564453s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.38690185546875e-05s
Believability | Calculation of trust value for ciard-ring took 8.106231689453125e-06s
INFO | --- Analysis for ciard-ring took 113.53897547721863s
Availability | SPARQL endpoint availability check for Cine Figure took 5.650520324707031e-05s
Availability | VoID file availability check for Cine Figure took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Cine Figure took 10.593369245529175s
Reputation | Calculation of the PageRank for Cine Figure took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.76837158203125e-05s
Believability | Calculation of trust value for Cine Figure took 8.344650268554688e-06s
INFO | --- Analysis for Cine_Figure took 113.36015915870667s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 6.689911127090454s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 10.505646467208862s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020976543426513672s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.291534423828125e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 123.27809882164001s
Availability | SPARQL endpoint availability check for CIPFA took 4.00543212890625e-05s
Availability | VoID file availability check for CIPFA took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for CIPFA took 10.10509204864502s
Reputation | Calculation of the PageRank for CIPFA took 0.020700931549072266s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.457069396972656e-05s
Believability | Calculation of trust value for CIPFA took 7.867813110351562e-06s
INFO | --- Analysis for cipfa took 111.66592168807983s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 4.1961669921875e-05s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 10.597752332687378s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003871917724609375s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 7.3909759521484375e-06s
INFO | --- Analysis for ckan took 112.05959343910217s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.00543212890625e-05s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 10.093802452087402s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.02085089683532715s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 7.62939453125e-06s
INFO | --- Analysis for CLaSSES took 112.17597317695618s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.553794860839844e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 10.093863248825073s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.170967102050781e-05s
Believability | Calculation of trust value for Temples of the Classical World took 7.152557373046875e-06s
INFO | --- Analysis for classical_temples took 112.36429643630981s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 8.249282836914062e-05s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 10.096952199935913s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.0207064151763916s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.821487426757812e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 1.33514404296875e-05s
INFO | --- Analysis for clean-energy-data-reegle took 111.54787254333496s
Availability | SPARQL endpoint availability check for CLLD-afbo took 9.34600830078125e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0013210773468017578s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 10.199578046798706s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02080392837524414s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.510185241699219e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.2636184692382812e-05s
INFO | --- Analysis for clld-afbo took 111.93659400939941s
Availability | SPARQL endpoint availability check for CLLD-APICS took 8.606910705566406e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 10.597144603729248s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.022331953048706055s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.343292236328125e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.3589859008789062e-05s
INFO | --- Analysis for clld-apics took 112.44454526901245s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.00543212890625e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 10.103425979614258s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.021803617477416992s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.719329833984375e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.2159347534179688e-05s
INFO | --- Analysis for clld-ewave took 112.36776375770569s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 6.29425048828125e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 10.096696376800537s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.632110595703125e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.1920928955078125e-05s
INFO | --- Analysis for clld-glottolog took 111.73900532722473s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.392333984375e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 10.170000553131104s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.106231689453125e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.1444091796875e-05s
INFO | --- Analysis for clld-phoible took 112.34140133857727s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.368492126464844e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 10.091734647750854s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.2479248046875e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.2874603271484375e-05s
INFO | --- Analysis for clld-sails took 112.37455487251282s
Availability | SPARQL endpoint availability check for CLLD-WALS took 9.059906005859375e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 10.099255800247192s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020580530166625977s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.273124694824219e-05s
Believability | Calculation of trust value for CLLD-WALS took 1.33514404296875e-05s
INFO | --- Analysis for clld-wals took 111.77268409729004s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.506111145019531e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 10.179781436920166s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.022148847579956055s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.557868957519531e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.33514404296875e-05s
INFO | --- Analysis for clld-wold took 112.86572933197021s
Availability | SPARQL endpoint availability check for COD inventory took 6.389617919921875e-05s
Availability | VoID file availability check for COD inventory took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for COD inventory took 10.097961902618408s
Reputation | Calculation of the PageRank for COD inventory took 0.0208282470703125s
Interlinking | Calculation of Degree of Connection for COD inventory took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COD inventory took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.5762786865234375e-05s
Believability | Calculation of trust value for COD inventory took 1.3828277587890625e-05s
INFO | --- Analysis for cod-inventory took 111.24401950836182s
Availability | SPARQL endpoint availability check for Cooperation Databank took 9.632110595703125e-05s
Availability | VoID file availability check for Cooperation Databank took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 10.139549970626831s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.600120544433594e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.2874603271484375e-05s
INFO | --- Analysis for CoDa took 112.03918051719666s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.00543212890625e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 10.096091270446777s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.814697265625e-05s
Believability | Calculation of trust value for CODE Endpoint took 1.2636184692382812e-05s
INFO | --- Analysis for code-endpoint took 112.03906035423279s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 4.00543212890625e-05s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 10.60127854347229s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020684003829956055s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 1.3113021850585938e-05s
INFO | --- Analysis for coins-openuplabs took 112.84211850166321s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 4.792213439941406e-05s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 10.092503547668457s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.021849632263183594s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.225440979003906e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.4066696166992188e-05s
INFO | --- Analysis for CoLChina_sp2000 took 112.34278154373169s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 3.981590270996094e-05s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 10.195999145507812s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.021616458892822266s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.814697265625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for colinda took 111.94328331947327s
Availability | SPARQL endpoint availability check for CN  2012 took 0.00011420249938964844s
Availability | VoID file availability check for CN  2012 took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for CN  2012 took 10.105578184127808s
Reputation | Calculation of the PageRank for CN  2012 took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.076957702636719e-05s
Believability | Calculation of trust value for CN  2012 took 1.2874603271484375e-05s
INFO | --- Analysis for combined-nomenclature-2012 took 111.24507188796997s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.124641418457031e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 10.108935356140137s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.022437334060668945s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.504753112792969e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 1.3113021850585938e-05s
INFO | --- Analysis for comments-on-literature-in-literature took 112.67286539077759s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 8.702278137207031e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0010101795196533203s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 10.102543592453003s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02025318145751953s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 2.7418136596679688e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 1.3589859008789062e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 111.36025023460388s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.0531158447265625e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 10.598791599273682s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.020957231521606445s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.337860107421875e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 1.3828277587890625e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 112.76887059211731s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.124641418457031e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 10.10102367401123s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 3.3855438232421875e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 7.152557373046875e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 112.37214422225952s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 8.821487426757812e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.011140823364257812s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 10.196304082870483s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 2.7179718017578125e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 1.33514404296875e-05s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 111.66441249847412s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 8.273124694824219e-05s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 10.100445747375488s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.33514404296875e-05s
INFO | --- Analysis for CompHistSem took 111.74141693115234s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 8.58306884765625e-05s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 10.099104642868042s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.814697265625e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.2874603271484375e-05s
INFO | --- Analysis for comsode-d3-2 took 111.54849863052368s
Availability | SPARQL endpoint availability check for ConceptNet took 5.5789947509765625e-05s
Availability | VoID file availability check for ConceptNet took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for ConceptNet took 10.59167218208313s
Reputation | Calculation of the PageRank for ConceptNet took 0.02202749252319336s
Interlinking | Calculation of Degree of Connection for ConceptNet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.86102294921875e-05s
Believability | Calculation of trust value for ConceptNet took 1.4066696166992188e-05s
INFO | --- Analysis for conceptnet took 112.65128374099731s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.00543212890625e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 10.597274780273438s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.20159912109375e-05s
Believability | Calculation of trust value for 2011 US Congress People took 7.3909759521484375e-06s
INFO | --- Analysis for congresspeople took 112.02542233467102s
Availability | SPARQL endpoint availability check for MIMO took 5.1975250244140625e-05s
Availability | VoID file availability check for MIMO took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for MIMO took 10.10042405128479s
Reputation | Calculation of the PageRank for MIMO took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for MIMO took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.4066696166992188e-05s
Believability | Calculation of trust value for MIMO took 8.106231689453125e-06s
INFO | --- Analysis for CONNECTED took 112.07443165779114s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 8.130073547363281e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 10.197256088256836s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 2.7418136596679688e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 111.84019684791565s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.124641418457031e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 10.088444232940674s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.021403789520263672s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.0517578125e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 8.344650268554688e-06s
INFO | --- Analysis for copac-library-catalogue took 112.36895799636841s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.2438507080078125e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 10.073235034942627s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.6941299438476562e-05s
Believability | Calculation of trust value for Copyright Free Music took 6.9141387939453125e-06s
INFO | --- Analysis for Copyright_Free_Music took 112.17019271850586s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 3.886222839355469e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 10.091659307479858s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.62939453125e-05s
Believability | Calculation of trust value for CopyrightTermBank took 8.106231689453125e-06s
INFO | --- Analysis for copyrighttermbank took 112.16567516326904s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 3.9577484130859375e-05s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 10.204039096832275s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.022241830825805664s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.76837158203125e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.3589859008789062e-05s
INFO | --- Analysis for core took 113.07793831825256s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 4.410743713378906e-05s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 10.19723892211914s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.123283386230469e-05s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Corine_linked_dataset took 112.54162812232971s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.00015091896057128906s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 10.200519323348999s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.314018249511719e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.106231689453125e-06s
INFO | --- Analysis for corn took 111.53174376487732s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 8.463859558105469e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 10.10465955734253s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 2.8848648071289062e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 1.33514404296875e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 112.07419204711914s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.00543212890625e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 10.101521015167236s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0221102237701416s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.574920654296875e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.33514404296875e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 111.74310350418091s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.100799560546875e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 10.097031831741333s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.29425048828125e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.3828277587890625e-05s
INFO | --- Analysis for cornetto took 112.4344322681427s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 5.888938903808594e-05s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 10.093743562698364s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 4.673004150390625e-05s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 8.106231689453125e-06s
INFO | --- Analysis for corporate-body took 111.64930295944214s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 3.814697265625e-05s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 10.100870609283447s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for CorpusFibonacci took 112.16296815872192s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 9.465217590332031e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 10.097572803497314s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.022436857223510742s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 3.218650817871094e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 1.3113021850585938e-05s
INFO | --- Analysis for corscheck took 112.87898564338684s
Availability | SPARQL endpoint availability check for Country Name Authority List took 7.152557373046875e-05s
Availability | VoID file availability check for Country Name Authority List took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 10.095228672027588s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.021548032760620117s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 4.482269287109375e-05s
Believability | Calculation of trust value for Country Name Authority List took 7.3909759521484375e-06s
INFO | --- Analysis for country-authority-list took 112.44038224220276s
Availability | SPARQL endpoint availability check for Courts thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for Courts thesaurus took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 10.098661184310913s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.022029638290405273s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.508827209472656e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.52587890625e-05s
INFO | --- Analysis for courts-thesaurus took 111.86920881271362s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 8.320808410644531e-05s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 10.200765371322632s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.022539615631103516s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.177757263183594e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.3589859008789062e-05s
INFO | --- Analysis for Covid-on-the-Web took 111.4650456905365s
Availability | SPARQL endpoint availability check for CPA 2008 took 8.225440979003906e-05s
Availability | VoID file availability check for CPA 2008 took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for CPA 2008 took 10.096970558166504s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.3855438232421875e-05s
Believability | Calculation of trust value for CPA 2008 took 1.3828277587890625e-05s
INFO | --- Analysis for cpa-2008 took 111.83232259750366s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 4.124641418457031e-05s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 10.092210531234741s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.020808935165405273s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 3.552436828613281e-05s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.33514404296875e-05s
INFO | --- Analysis for CPC took 112.74447393417358s
Availability | SPARQL endpoint availability check for CPC 2008 took 3.910064697265625e-05s
Availability | VoID file availability check for CPC 2008 took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for CPC 2008 took 10.193328619003296s
Reputation | Calculation of the PageRank for CPC 2008 took 0.02121567726135254s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.314018249511719e-05s
Believability | Calculation of trust value for CPC 2008 took 7.867813110351562e-06s
INFO | --- Analysis for cpc-2008 took 111.43240094184875s
Availability | SPARQL endpoint availability check for CPV  2003 took 3.910064697265625e-05s
Availability | VoID file availability check for CPV  2003 took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for CPV  2003 took 10.189491748809814s
Reputation | Calculation of the PageRank for CPV  2003 took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.076957702636719e-05s
Believability | Calculation of trust value for CPV  2003 took 9.298324584960938e-06s
INFO | --- Analysis for cpv-2003 took 112.35332703590393s
Availability | SPARQL endpoint availability check for CPV 2008 took 8.273124694824219e-05s
Availability | VoID file availability check for CPV 2008 took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for CPV 2008 took 10.19576120376587s
Reputation | Calculation of the PageRank for CPV 2008 took 0.02252364158630371s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.3392181396484375e-05s
Believability | Calculation of trust value for CPV 2008 took 1.0013580322265625e-05s
INFO | --- Analysis for cpv-2008 took 111.83773589134216s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 4.0531158447265625e-05s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 10.20639443397522s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 3.886222839355469e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.1920928955078125e-05s
INFO | --- Analysis for crowdsourcing-fb took 111.96465802192688s
Availability | SPARQL endpoint availability check for CRTM took 6.246566772460938e-05s
Availability | VoID file availability check for CRTM took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for CRTM took 10.200488328933716s
Reputation | Calculation of the PageRank for CRTM took 0.023089885711669922s
Interlinking | Calculation of Degree of Connection for CRTM took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0008604526519775391s
Interlinking | Calculation of Clustering coefficient for CRTM took 4.57763671875e-05s
Believability | Calculation of trust value for CRTM took 1.2636184692382812e-05s
INFO | --- Analysis for crtm took 113.24347829818726s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 6.175041198730469e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 10.101049184799194s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020814895629882812s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 1.3113021850585938e-05s
INFO | --- Analysis for crystal-eye took 111.84451174736023s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 8.678436279296875e-05s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 10.104409217834473s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.022116899490356445s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 5.507469177246094e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 7.867813110351562e-06s
INFO | --- Analysis for ctic-public-dataset took 111.67083811759949s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.029273986816406e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 10.104496002197266s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.022162199020385742s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.9802322387695312e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 8.821487426757812e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 111.54230499267578s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.43773555755615234s
Availability | VoID file availability check for CulturaLinkedData took 0.0005238056182861328s
Extra | Recovery of all triples for CulturaLinkedData took 140.53696990013123s
Performance | Total latancy measurement for CulturaLinkedData took 2.767401933670044s
Amount of data | Number of triples check for CulturaLinkedData took 2.5403213500976562s
Interoperability | New terms check for CulturaLinkedData took 4.086621522903442s
Versatility | Languages check for CulturaLinkedData took 61.29852747917175s
Interpretability | Number of blank nodes check for CulturaLinkedData took 1.9924101829528809s
Interpretability | RDF structures check for CulturaLinkedData took 0.35921669006347656s
Versatility | Serialization formats check for CulturaLinkedData took 0.3863849639892578s
Availability | RDF dump link check for CulturaLinkedData took 0.23644495010375977s
License | MR license check for CulturaLinkedData took 0.5060083866119385s
License | HR license check for CulturaLinkedData took 60.51128888130188s
Amount of data | Number of property check for CulturaLinkedData took 0.004713535308837891s
Understandability | Number of label check for CulturaLinkedData took 2.9217002391815186s
Understandability | URI regex check for CulturaLinkedData took 4.179378509521484s
Understandability | Vocabs check for CulturaLinkedData took 0.2589707374572754s
Verifiability | Authors check for CulturaLinkedData took 0.3045921325683594s
Verifiability | Publishers check for CulturaLinkedData took 2.0752830505371094s
Performance | Throughput check for CulturaLinkedData took 24.089491844177246s
Amount of data | Check the number of entities for CulturaLinkedData took 8.344650268554688e-05s
Verifiability | Contribs. check for CulturaLinkedData took 1.9960923194885254s
Interlinking | sameAs chians check for CulturaLinkedData took 0.3082244396209717s
Interlinking | skos check for CulturaLinkedData took 0.4013206958770752s
Interlinking | skos check for CulturaLinkedData took 1.9697275161743164s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.2741544246673584s
Currency | Creation date check for CulturaLinkedData took 3.8499317169189453s
Currency | Modification date check for CulturaLinkedData took 2.2059319019317627s
Rep.Conc. | URIs length for CulturaLinkedData took 54.84835624694824s
Interoperability | New vocabularies check for CulturaLinkedData took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.18100309371948242s
Accuracy | Check Functional Property for CulturaLinkedData took 1.9232633113861084s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 1.9290351867675781s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 44.550788164138794s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6014258861541748s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.300349473953247s
Consistency | Disjoint class check for CulturaLinkedData took 0.20366597175598145s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.004279613494873s
Consistency | Misplaced classes for CulturaLinkedData took 4.18346905708313s
Consistency | Check Ontology hijacking for CulturaLinkedData took 40.52189540863037s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.359534502029419s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 11.111074924468994s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3590731620788574s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 2.0706827640533447s
Security | Sign check for CulturaLinkedData took 0.8407928943634033s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 19.71754240989685s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 10.230216026306152s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021480083465576172s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.3855438232421875e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.1457672119140625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.33514404296875e-05s
INFO | --- Analysis for culturalinkeddata took 738.3750288486481s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 8.535385131835938e-05s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 10.599242448806763s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.021347522735595703s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.2438507080078125e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-ares-or took 113.35816097259521s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 7.081031799316406e-05s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 10.105538606643677s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0218050479888916s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.361701965332031e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.3113021850585938e-05s
INFO | --- Analysis for cz-ares-rzp took 114.31338667869568s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 4.00543212890625e-05s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 10.541828155517578s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.1948089599609375e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 8.58306884765625e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 111.77164602279663s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 3.9577484130859375e-05s
Availability | VoID file availability check for Integrated pollution registry took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 10.103010654449463s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02106022834777832s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 4.124641418457031e-05s
Believability | Calculation of trust value for Integrated pollution registry took 1.2874603271484375e-05s
INFO | --- Analysis for cz-cenia-pollution took 111.36475253105164s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 8.535385131835938e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 10.098809957504272s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020756959915161133s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 4.100799560546875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 1.5974044799804688e-05s
INFO | --- Analysis for cz-contracts took 112.04529643058777s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 6.270408630371094e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 10.100117206573486s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.021013736724853516s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.2901763916015625e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 1.33514404296875e-05s
INFO | --- Analysis for cz-courts took 111.44010257720947s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 8.320808410644531e-05s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 10.102933406829834s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02051401138305664s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.7670135498046875e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 1.3113021850585938e-05s
INFO | --- Analysis for cz-ctia-bans took 113.14866948127747s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 8.058547973632812e-05s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 10.196542501449585s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.021547317504882812s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.24249267578125e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 1.4066696166992188e-05s
INFO | --- Analysis for cz-ctia-confiscations took 112.03792595863342s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 8.320808410644531e-05s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 10.096394777297974s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.8623809814453125e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 7.3909759521484375e-06s
INFO | --- Analysis for cz-ctia-focus took 112.7379834651947s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 4.0531158447265625e-05s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 10.10576057434082s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 3.814697265625e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 1.3589859008789062e-05s
INFO | --- Analysis for cz-ctia-inspections took 112.47003412246704s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 3.790855407714844e-05s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 10.49939489364624s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.02106499671936035s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.361701965332031e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 7.3909759521484375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 113.37288570404053s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 4.029273986816406e-05s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 10.10267686843872s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.4809112548828125e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 1.2159347534179688e-05s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 111.37112855911255s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 8.296966552734375e-05s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 10.498107194900513s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.0040740966796875e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 1.3113021850585938e-05s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 112.46968483924866s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 4.363059997558594e-05s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.00033354759216308594s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 10.102423429489136s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 1.2636184692382812e-05s
INFO | --- Analysis for cz-czso-average-salaries took 111.54926300048828s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 3.933906555175781e-05s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 10.10196304321289s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020605087280273438s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.933906555175781e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 1.4543533325195312e-05s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 111.26643204689026s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.910064697265625e-05s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 10.094726324081421s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.022694110870361328s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.7670135498046875e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0023458003997802734s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 9.5367431640625e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0013580322265625e-05s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 112.73838138580322s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 3.981590270996094e-05s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 10.203563213348389s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020831823348999023s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.291534423828125e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 1.2159347534179688e-05s
INFO | --- Analysis for cz-czso-job-applicants took 112.17800545692444s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 3.9577484130859375e-05s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 10.101647138595581s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 1.1682510375976562e-05s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 111.76527214050293s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 4.00543212890625e-05s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 10.60158085823059s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.528594970703125e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 7.62939453125e-06s
INFO | --- Analysis for cz-czso-regions took 111.873952627182s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 4.00543212890625e-05s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 10.100430727005005s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.021017789840698242s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.5299530029296875e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 7.62939453125e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 112.04382157325745s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 4.553794860839844e-05s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0003058910369873047s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 10.099682807922363s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020763635635375977s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.315376281738281e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 111.86696076393127s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 3.9577484130859375e-05s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 10.107078075408936s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.022566556930541992s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.100799560546875e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 1.3113021850585938e-05s
INFO | --- Analysis for cz-czso-unemployment-rate took 111.66783690452576s
Availability | SPARQL endpoint availability check for ATC groups took 3.9577484130859375e-05s
Availability | VoID file availability check for ATC groups took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for ATC groups took 10.093080282211304s
Reputation | Calculation of the PageRank for ATC groups took 0.020845413208007812s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.699562072753906e-05s
Believability | Calculation of trust value for ATC groups took 1.2874603271484375e-05s
INFO | --- Analysis for cz-eh-1-atc took 112.64260625839233s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 8.20159912109375e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 10.099827527999878s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 4.458427429199219e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 1.2874603271484375e-05s
INFO | --- Analysis for cz-fulfillments took 112.47699666023254s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 4.076957702636719e-05s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 10.501111507415771s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.022292613983154297s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.673004150390625e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 1.3828277587890625e-05s
INFO | --- Analysis for cz-ic took 112.6361825466156s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 4.00543212890625e-05s
Availability | VoID file availability check for List of Czech data boxes took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 10.095148086547852s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 2.9325485229492188e-05s
Believability | Calculation of trust value for List of Czech data boxes took 1.33514404296875e-05s
INFO | --- Analysis for cz-list-of-databoxes took 111.76631236076355s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.9577484130859375e-05s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0011305809020996094s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.099023818969727s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6464462280273438e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.2636184692382812e-05s
INFO | --- Analysis for cz-nace took 111.88052606582642s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.1484832763671875e-05s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.100956678390503s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.021840572357177734s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.600120544433594e-05s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.1920928955078125e-05s
INFO | --- Analysis for cz-nkod took 111.36668086051941s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 3.9577484130859375e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 10.201358318328857s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.6716461181640625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 1.1920928955078125e-05s
INFO | --- Analysis for cz-orders took 112.3660261631012s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 8.678436279296875e-05s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 10.088980197906494s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.1961669921875e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 5.269050598144531e-05s
INFO | --- Analysis for cz-ovm took 111.63113451004028s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 3.9577484130859375e-05s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 10.093780517578125s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 4.57763671875e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-ovm-agendas took 112.2621533870697s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 4.172325134277344e-05s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.095449686050415s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.02187204360961914s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.723403930664062e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.239776611328125e-05s
INFO | --- Analysis for cz-ruian took 111.44424438476562s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 3.886222839355469e-05s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 10.099669218063354s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 6.961822509765625e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 112.26217150688171s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 3.9577484130859375e-05s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 10.59753680229187s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.02077651023864746s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.4809112548828125e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sao-check-actions took 112.36948823928833s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 4.220008850097656e-05s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 10.097525119781494s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.5762786865234375e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 7.62939453125e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 111.67280101776123s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 4.291534423828125e-05s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 10.09426736831665s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.022966861724853516s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0010862350463867188s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 4.458427429199219e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.33514404296875e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 111.57411336898804s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 8.344650268554688e-05s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 10.09642243385315s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.52587890625e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.0040740966796875e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 111.74047231674194s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 4.00543212890625e-05s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0003075599670410156s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 10.106471300125122s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.021117448806762695s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 4.792213439941406e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-sidc-drugs took 111.8734278678894s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 4.100799560546875e-05s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 10.1053946018219s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.361701965332031e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 1.3589859008789062e-05s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 112.0725839138031s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 8.463859558105469e-05s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 10.100694179534912s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.4332275390625e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 1.3589859008789062e-05s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 112.94773507118225s
Availability | SPARQL endpoint availability check for State funding providers took 4.410743713378906e-05s
Availability | VoID file availability check for State funding providers took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for State funding providers took 10.104947566986084s
Reputation | Calculation of the PageRank for State funding providers took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.8623809814453125e-05s
Believability | Calculation of trust value for State funding providers took 1.3589859008789062e-05s
INFO | --- Analysis for cz-vavai-funding-providers took 112.43756198883057s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 3.9577484130859375e-05s
Availability | VoID file availability check for Organizations active in R&D took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 10.098471641540527s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.022828340530395508s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0009453296661376953s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.076957702636719e-05s
Believability | Calculation of trust value for Organizations active in R&D took 7.3909759521484375e-06s
INFO | --- Analysis for cz-vavai-organizations took 111.97115731239319s
Availability | SPARQL endpoint availability check for R&D Programmes took 4.00543212890625e-05s
Availability | VoID file availability check for R&D Programmes took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for R&D Programmes took 10.103643894195557s
Reputation | Calculation of the PageRank for R&D Programmes took 0.022835493087768555s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.001050710678100586s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.5299530029296875e-05s
Believability | Calculation of trust value for R&D Programmes took 1.1920928955078125e-05s
INFO | --- Analysis for cz-vavai-programmes took 112.37506699562073s
Availability | SPARQL endpoint availability check for R&D Projects took 3.933906555175781e-05s
Availability | VoID file availability check for R&D Projects took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for R&D Projects took 10.599541664123535s
Reputation | Calculation of the PageRank for R&D Projects took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.838539123535156e-05s
Believability | Calculation of trust value for R&D Projects took 7.3909759521484375e-06s
INFO | --- Analysis for cz-vavai-projects took 112.66875576972961s
Availability | SPARQL endpoint availability check for Institutional research plans took 4.76837158203125e-05s
Availability | VoID file availability check for Institutional research plans took 0.00030517578125s
Completeness | Calculation of interlinking completeness for Institutional research plans took 10.090039014816284s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 5.364418029785156e-05s
Believability | Calculation of trust value for Institutional research plans took 1.33514404296875e-05s
INFO | --- Analysis for cz-vavai-research-plans took 111.67343592643738s
Availability | SPARQL endpoint availability check for Results of R&D took 8.440017700195312e-05s
Availability | VoID file availability check for Results of R&D took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Results of R&D took 10.099775552749634s
Reputation | Calculation of the PageRank for Results of R&D took 0.023722410202026367s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0009877681732177734s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.744529724121094e-05s
Believability | Calculation of trust value for Results of R&D took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-results took 112.74601578712463s
Availability | SPARQL endpoint availability check for Tenders in R&D took 8.535385131835938e-05s
Availability | VoID file availability check for Tenders in R&D took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 10.099763870239258s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02087116241455078s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.4345855712890625e-05s
Believability | Calculation of trust value for Tenders in R&D took 1.2636184692382812e-05s
INFO | --- Analysis for cz-vavai-tenders took 111.24135136604309s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.4345855712890625e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 10.097703695297241s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.0994415283203125e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.239776611328125e-05s
INFO | --- Analysis for czech_addresses took 111.44482040405273s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 5.9604644775390625e-05s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0003228187561035156s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 10.097477674484253s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020867347717285156s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 8.58306884765625e-06s
INFO | --- Analysis for DanteLatinLoanwords took 111.97220730781555s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3360610008239746s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.00032258033752441406s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 150.57723712921143s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.238032341003418s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 10.213316679000854s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.3715574741363525s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.27893161773682s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.2252814769744873s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.11810898780822754s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.36231207847595215s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.41747188568115234s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.19795584678649902s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 2.0318496227264404s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.27459764480591s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.20898032188415527s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.896998643875122s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.410449743270874s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.20278120040893555s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.5430524349212646s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.19515514373779297s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.545007228851318s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.295608520507812e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.20380949974060059s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.6363344192504883s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 3.319960832595825s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.29742431640625s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.7781312465667725s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.415510892868042s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.3773488998413086s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 84.8799409866333s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.22077608108520508s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.39001011848449707s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.36734867095947266s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 39.929665327072144s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2024264335632324s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.569627046585083s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.2181229591369629s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 22.31133246421814s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.357329368591309s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 49.58167004585266s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.474799633026123s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.603156328201294s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.793940305709839s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2086796760559082s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.9656984806060791s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 12.788025856018066s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 10.292770624160767s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02187514305114746s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.0001399517059326172s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 2.1457672119140625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.33514404296875e-05s
INFO | --- Analysis for data-bnf-fr took 964.4757332801819s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 8.344650268554688e-05s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 10.103167057037354s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.699562072753906e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 7.152557373046875e-06s
INFO | --- Analysis for data-cnr-it took 111.73185634613037s
Availability | SPARQL endpoint availability check for Data.gov took 4.100799560546875e-05s
Availability | VoID file availability check for Data.gov took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Data.gov took 10.590501308441162s
Reputation | Calculation of the PageRank for Data.gov took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.1948089599609375e-05s
Believability | Calculation of trust value for Data.gov took 8.106231689453125e-06s
INFO | --- Analysis for data-gov took 114.44340658187866s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 8.392333984375e-05s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 10.093704223632812s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.021243810653686523s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.866455078125e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 1.2636184692382812e-05s
INFO | --- Analysis for data-gov-ie took 111.36976361274719s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 3.9577484130859375e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 10.19327187538147s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02169966697692871s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.295608520507812e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 1.2636184692382812e-05s
INFO | --- Analysis for data-gov-uk-time-intervals took 111.75301885604858s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 20.526593446731567s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 10.097128868103027s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.628036499023438e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for data-hnm-hu took 161.86266827583313s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.32084059715270996s
Availability | VoID file availability check for Climb Dataincubator took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 10.086623191833496s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.557868957519531e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-climb took 112.33939719200134s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 10.114753246307373s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 8.96453857421875e-05s
Believability | Calculation of trust value for Discogs in RDF took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-discogs took 113.43552255630493s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 8.535385131835938e-05s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 10.100137948989868s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.6743621826171875e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 1.4781951904296875e-05s
INFO | --- Analysis for data-incubator-metoffice took 112.24357724189758s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.05757927894592285s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 10.088659048080444s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.021100282669067383s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.511543273925781e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-moseley took 113.45392727851868s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.05284833908081055s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 10.199215412139893s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.463859558105469e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.33514404296875e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 112.2371814250946s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 5.340576171875e-05s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 10.102821826934814s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02247333526611328s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 9.083747863769531e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 1.33514404296875e-05s
INFO | --- Analysis for data-incubator-nasa took 111.33323812484741s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 4.076957702636719e-05s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 10.092235565185547s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.700920104980469e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 8.58306884765625e-06s
INFO | --- Analysis for data-incubator-our-airports took 111.9469153881073s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 3.933906555175781e-05s
Availability | VoID file availability check for Pokedex data in RDF took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 10.103951930999756s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 8.654594421386719e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-pokedex took 113.17042899131775s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 4.9591064453125e-05s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 10.193367958068848s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.630752563476562e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.2874603271484375e-05s
INFO | --- Analysis for data-incubator-smcjournals took 111.94362020492554s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 7.987022399902344e-05s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 10.59459638595581s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.02031421661376953s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.723403930664062e-05s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 8.106231689453125e-06s
INFO | --- Analysis for data-open-ac-uk took 113.14922904968262s
Availability | SPARQL endpoint availability check for Persée in RDF took 8.58306884765625e-05s
Availability | VoID file availability check for Persée in RDF took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for Persée in RDF took 10.101484537124634s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00012683868408203125s
Believability | Calculation of trust value for Persée in RDF took 1.4781951904296875e-05s
INFO | --- Analysis for data-persee-fr took 113.36006999015808s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 5.078315734863281e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 10.503973484039307s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 2.8848648071289062e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 6.9141387939453125e-06s
INFO | --- Analysis for data-southampton-ac-uk took 111.77587509155273s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.1331923007965088s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 10.093801259994507s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.021962404251098633s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011157989501953125s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.2874603271484375e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 113.51804327964783s
Availability | SPARQL endpoint availability check for Open Data Web took 8.726119995117188e-05s
Availability | VoID file availability check for Open Data Web took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Open Data Web took 10.195952892303467s
Reputation | Calculation of the PageRank for Open Data Web took 0.026145458221435547s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0010666847229003906s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.886222839355469e-05s
Believability | Calculation of trust value for Open Data Web took 1.2874603271484375e-05s
INFO | --- Analysis for data.odw.tw took 111.39607429504395s
Availability | SPARQL endpoint availability check for DataFAQs took 4.100799560546875e-05s
Availability | VoID file availability check for DataFAQs took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for DataFAQs took 10.09583067893982s
Reputation | Calculation of the PageRank for DataFAQs took 0.021135807037353516s
Interlinking | Calculation of Degree of Connection for DataFAQs took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.743171691894531e-05s
Believability | Calculation of trust value for DataFAQs took 1.2636184692382812e-05s
INFO | --- Analysis for datafaqs took 111.36920213699341s
Availability | SPARQL endpoint availability check for datahub took 0.00015211105346679688s
Availability | VoID file availability check for datahub took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for datahub took 10.175951480865479s
Reputation | Calculation of the PageRank for datahub took 0.02313828468322754s
Interlinking | Calculation of Degree of Connection for datahub took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for datahub took 0.0009539127349853516s
Interlinking | Calculation of Clustering coefficient for datahub took 6.246566772460938e-05s
Believability | Calculation of trust value for datahub took 7.867813110351562e-06s
INFO | --- Analysis for datahub took 112.15832996368408s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.00543212890625e-05s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 10.097983837127686s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020323991775512695s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 2.9325485229492188e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.2874603271484375e-05s
INFO | --- Analysis for datahub-kr-datamap took 112.34805393218994s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 4.076957702636719e-05s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 10.589128255844116s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020505905151367188s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.104873657226562e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.3909759521484375e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 111.94651508331299s
Availability | SPARQL endpoint availability check for datos-artium-org took 20.946340084075928s
Availability | VoID file availability check for datos-artium-org took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for datos-artium-org took 10.099792957305908s
Reputation | Calculation of the PageRank for datos-artium-org took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00010752677917480469s
Believability | Calculation of trust value for datos-artium-org took 1.4543533325195312e-05s
INFO | --- Analysis for datos-artium-org took 163.16452550888062s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 7.462501525878906e-05s
Availability | VoID file availability check for Datos.bcn.cl took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 10.19508981704712s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.022758007049560547s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.581710815429688e-05s
Believability | Calculation of trust value for Datos.bcn.cl took 1.3589859008789062e-05s
INFO | --- Analysis for datos-bcn-cl took 111.95029520988464s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.503469705581665s
Availability | VoID file availability check for datos.bne.es took 0.0005230903625488281s
Extra | Recovery of all triples for datos.bne.es took 128.02109909057617s
Performance | Total latancy measurement for datos.bne.es took 1.3796288967132568s
Amount of data | Number of triples check for datos.bne.es took 0.8291103839874268s
Interoperability | New terms check for datos.bne.es took 4.163597106933594s
Versatility | Languages check for datos.bne.es took 61.92250657081604s
Interpretability | Number of blank nodes check for datos.bne.es took 0.27054929733276367s
Security | Check HTTPS for datos.bne.es took 0.18054866790771484s
Interpretability | RDF structures check for datos.bne.es took 0.5743353366851807s
Versatility | Serialization formats check for datos.bne.es took 0.5827970504760742s
Availability | RDF dump link check for datos.bne.es took 2.127638339996338s
License | MR license check for datos.bne.es took 0.767378568649292s
License | HR license check for datos.bne.es took 61.253411054611206s
Amount of data | Number of property check for datos.bne.es took 0.27022838592529297s
Understandability | Number of label check for datos.bne.es took 3.0159645080566406s
Understandability | URI regex check for datos.bne.es took 2.684319496154785s
Understandability | Vocabs check for datos.bne.es took 2.184176445007324s
Verifiability | Authors check for datos.bne.es took 2.2315218448638916s
Verifiability | Publishers check for datos.bne.es took 0.36551523208618164s
Performance | Throughput check for datos.bne.es took 23.49530529975891s
Amount of data | Check the number of entities for datos.bne.es took 7.295608520507812e-05s
Verifiability | Contribs. check for datos.bne.es took 0.35457730293273926s
Interlinking | sameAs chians check for datos.bne.es took 0.45399951934814453s
Interlinking | skos check for datos.bne.es took 2.3973228931427s
Interlinking | skos check for datos.bne.es took 2.0607750415802s
Timeliness | dataset update frequency check for datos.bne.es took 0.4370858669281006s
Currency | Creation date check for datos.bne.es took 0.618828535079956s
Currency | Modification date check for datos.bne.es took 2.4525842666625977s
Rep.Conc. | URIs length for datos.bne.es took 54.57158374786377s
Interoperability | New vocabularies check for datos.bne.es took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.25489354133605957s
Accuracy | Check Functional Property for datos.bne.es took 0.2742595672607422s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.30017971992492676s
Accuracy | Check Empty annotation labels for datos.bne.es took 44.6363639831543s
Accuracy | Check White space in annotation for datos.bne.es took 1.602330207824707s
Accuracy | Check Datatype consistency for datos.bne.es took 1.2595875263214111s
Consistency | Disjoint class check for datos.bne.es took 0.31297945976257324s
Consistency | Check Misplaced properties for datos.bne.es took 10.379886627197266s
Consistency | Misplaced classes for datos.bne.es took 4.235182046890259s
Consistency | Check Ontology hijacking for datos.bne.es took 42.31755757331848s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.3050825595855713s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 9.673829555511475s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.3580853939056396s
Conciseness | Check Intensional conciseness for datos.bne.es took 2.17657208442688s
Security | Sign check for datos.bne.es took 1.0704548358917236s
Availability | Check URIs Dereferenciability for datos.bne.es took 16.28142786026001s
Completeness | Calculation of interlinking completeness for datos.bne.es took 10.626168489456177s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020998716354370117s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011277198791503906s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 1.9073486328125e-06s
Believability | Calculation of trust value for datos.bne.es took 1.2636184692382812e-05s
INFO | --- Analysis for datos-bne-es took 729.3557636737823s
Availability | SPARQL endpoint availability check for dbacademic took 8.535385131835938e-05s
Availability | VoID file availability check for dbacademic took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for dbacademic took 10.097517490386963s
Reputation | Calculation of the PageRank for dbacademic took 0.02208232879638672s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.4332275390625e-05s
Believability | Calculation of trust value for dbacademic took 1.3113021850585938e-05s
INFO | --- Analysis for dbacademic took 112.62141394615173s
Availability | SPARQL endpoint availability check for DBkWik took 3.933906555175781e-05s
Availability | VoID file availability check for DBkWik took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for DBkWik took 10.097817420959473s
Reputation | Calculation of the PageRank for DBkWik took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for DBkWik took 6.771087646484375e-05s
Believability | Calculation of trust value for DBkWik took 1.3828277587890625e-05s
INFO | --- Analysis for dbkwik took 112.90242743492126s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.076957702636719e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 10.105530977249146s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.022591114044189453s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0010023117065429688s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001289844512939453s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 113.25281023979187s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 8.630752563476562e-05s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 10.209290742874146s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.1205673217773438e-05s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for dblp-kg took 112.34873008728027s
Availability | SPARQL endpoint availability check for dbnary took 8.082389831542969e-05s
Availability | VoID file availability check for dbnary took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for dbnary took 10.091773509979248s
Reputation | Calculation of the PageRank for dbnary took 0.02216362953186035s
Interlinking | Calculation of Degree of Connection for dbnary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0006814002990722656s
Interlinking | Calculation of Clustering coefficient for dbnary took 4.5299530029296875e-05s
Believability | Calculation of trust value for dbnary took 1.2874603271484375e-05s
INFO | --- Analysis for dbnary took 111.56925320625305s
Availability | SPARQL endpoint availability check for DBpedia took 3.981590270996094e-05s
Availability | VoID file availability check for DBpedia took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for DBpedia took 10.090270042419434s
Reputation | Calculation of the PageRank for DBpedia took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008709430694580078s
Believability | Calculation of trust value for DBpedia took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia took 112.57250595092773s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 8.249282836914062e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 10.200812101364136s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.198883056640625e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.239776611328125e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 112.36615037918091s
Availability | SPARQL endpoint availability check for DBpedia Commons took 3.9577484130859375e-05s
Availability | VoID file availability check for DBpedia Commons took 0.0008518695831298828s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 10.095729351043701s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.02237844467163086s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0009450912475585938s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 8.654594421386719e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.2874603271484375e-05s
INFO | --- Analysis for dbpedia-commons took 112.5739073753357s
Availability | SPARQL endpoint availability check for DBpedia in German took 9.274482727050781e-05s
Availability | VoID file availability check for DBpedia in German took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for DBpedia in German took 10.09682846069336s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.031990051269531e-05s
Believability | Calculation of trust value for DBpedia in German took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-de took 111.46756649017334s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 3.933906555175781e-05s
Availability | VoID file availability check for DBpedia in Greek took 0.00032520294189453125s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 10.10652494430542s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0001888275146484375s
Believability | Calculation of trust value for DBpedia in Greek took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-el took 112.24125528335571s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 8.153915405273438e-05s
Availability | VoID file availability check for DBpedia in Spanish took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 10.090340614318848s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021113872528076172s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 9.751319885253906e-05s
Believability | Calculation of trust value for DBpedia in Spanish took 1.239776611328125e-05s
INFO | --- Analysis for dbpedia-es took 112.35656118392944s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 3.933906555175781e-05s
Availability | VoID file availability check for DBpedia in Basque took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 10.10352087020874s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 2.5987625122070312e-05s
Believability | Calculation of trust value for DBpedia in Basque took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-eu took 112.17625021934509s
Availability | SPARQL endpoint availability check for DBpedia in French took 4.100799560546875e-05s
Availability | VoID file availability check for DBpedia in French took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for DBpedia in French took 10.577484607696533s
Reputation | Calculation of the PageRank for DBpedia in French took 0.023622512817382812s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0009601116180419922s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00012803077697753906s
Believability | Calculation of trust value for DBpedia in French took 1.3113021850585938e-05s
INFO | --- Analysis for dbpedia-fr took 112.94405674934387s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 3.910064697265625e-05s
Availability | VoID file availability check for DBpedia in Japanese took 0.0004036426544189453s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 10.604501485824585s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 9.322166442871094e-05s
Believability | Calculation of trust value for DBpedia in Japanese took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-ja took 112.24379086494446s
Availability | SPARQL endpoint availability check for dbpedia lite took 7.796287536621094e-05s
Availability | VoID file availability check for dbpedia lite took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for dbpedia lite took 10.201754808425903s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.72747802734375e-05s
Believability | Calculation of trust value for dbpedia lite took 1.3589859008789062e-05s
INFO | --- Analysis for dbpedia-lite took 111.56516003608704s
Availability | SPARQL endpoint availability check for DBpedia-Live took 8.893013000488281e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 10.196860313415527s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.910064697265625e-05s
Believability | Calculation of trust value for DBpedia-Live took 1.2874603271484375e-05s
INFO | --- Analysis for dbpedia-live took 112.75075078010559s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 7.200241088867188e-05s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 10.104322910308838s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016927719116210938s
Believability | Calculation of trust value for DBpedia in Dutch took 1.33514404296875e-05s
INFO | --- Analysis for dbpedia-nl took 112.7364194393158s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 4.4345855712890625e-05s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 10.095128536224365s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.034706115722656e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.3113021850585938e-05s
INFO | --- Analysis for dbpedia-pt took 112.17695617675781s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 8.511543273925781e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 10.10241413116455s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.02071356773376465s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.790855407714844e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 1.3113021850585938e-05s
INFO | --- Analysis for dbpedia-spotlight took 117.3668315410614s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 8.463859558105469e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 10.10055923461914s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 7.176399230957031e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.33514404296875e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 112.0418438911438s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.029273986816406e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 10.092546939849854s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.021636962890625s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 4.100799560546875e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 1.239776611328125e-05s
INFO | --- Analysis for dbpedia-wikidata took 111.84190464019775s
Availability | SPARQL endpoint availability check for DBpedia took 8.559226989746094e-05s
Availability | VoID file availability check for DBpedia took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for DBpedia took 10.194634437561035s
Reputation | Calculation of the PageRank for DBpedia took 0.022144317626953125s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for DBpedia took 2.7894973754882812e-05s
Believability | Calculation of trust value for DBpedia took 7.62939453125e-06s
INFO | --- Analysis for dbpedia_ took 111.77376651763916s
Availability | SPARQL endpoint availability check for DBTropes took 8.678436279296875e-05s
Availability | VoID file availability check for DBTropes took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for DBTropes took 10.137561798095703s
Reputation | Calculation of the PageRank for DBTropes took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for DBTropes took 8.96453857421875e-05s
Believability | Calculation of trust value for DBTropes took 1.1920928955078125e-05s
INFO | --- Analysis for dbtropes took 113.06216406822205s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.029273986816406e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 10.102410554885864s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 4.124641418457031e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 1.2636184692382812e-05s
INFO | --- Analysis for dbtune took 111.94549822807312s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 9.274482727050781e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 10.199546337127686s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 6.222724914550781e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.239776611328125e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 112.0724527835846s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.935264587402344e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 10.099391222000122s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 4.0531158447265625e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.3113021850585938e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 111.34106516838074s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.635589838027954s
Availability | VoID file availability check for DBTune.org/classical took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 10.199098825454712s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020231962203979492s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 8.058547973632812e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.2636184692382812e-05s
INFO | --- Analysis for dbtune-classical took 118.30233883857727s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.517388582229614s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 10.204148769378662s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.437301635742188e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 117.32546925544739s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.608958721160889s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 10.597534418106079s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.365776062011719e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.2874603271484375e-05s
INFO | --- Analysis for dbtune-magnatune took 118.38431787490845s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 1.2510795593261719s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005652904510498047s
Extra | Recovery of all triples for DBTune.org Musicbrainz D2R Server took 0.22373652458190918s
Amount of data | Number of triples check for DBTune.org Musicbrainz D2R Server took 2.5274124145507812s
Versatility | Languages check for DBTune.org Musicbrainz D2R Server took 0.31084251403808594s
Interpretability | Number of blank nodes check for DBTune.org Musicbrainz D2R Server took 2.768710136413574s
Interpretability | RDF structures check for DBTune.org Musicbrainz D2R Server took 0.13685846328735352s
Versatility | Serialization formats check for DBTune.org Musicbrainz D2R Server took 0.1141502857208252s
Availability | RDF dump link check for DBTune.org Musicbrainz D2R Server took 0.09989714622497559s
License | MR license check for DBTune.org Musicbrainz D2R Server took 0.09194350242614746s
License | HR license check for DBTune.org Musicbrainz D2R Server took 2.6310739517211914s
Amount of data | Number of property check for DBTune.org Musicbrainz D2R Server took 0.09261465072631836s
Understandability | Number of label check for DBTune.org Musicbrainz D2R Server took 2.6167666912078857s
Understandability | URI regex check for DBTune.org Musicbrainz D2R Server took 0.18367218971252441s
Understandability | Vocabs check for DBTune.org Musicbrainz D2R Server took 0.09044456481933594s
Verifiability | Authors check for DBTune.org Musicbrainz D2R Server took 0.10053491592407227s
Verifiability | Publishers check for DBTune.org Musicbrainz D2R Server took 0.10023760795593262s
Amount of data | Check the number of entities for DBTune.org Musicbrainz D2R Server took 7.05718994140625e-05s
Verifiability | Contribs. check for DBTune.org Musicbrainz D2R Server took 0.09255433082580566s
Interlinking | sameAs chians check for DBTune.org Musicbrainz D2R Server took 0.1656169891357422s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.09211611747741699s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.09885025024414062s
Timeliness | dataset update frequency check for DBTune.org Musicbrainz D2R Server took 0.09132790565490723s
Currency | Creation date check for DBTune.org Musicbrainz D2R Server took 0.17952585220336914s
Currency | Modification date check for DBTune.org Musicbrainz D2R Server took 0.17635059356689453s
Rep.Conc. | URIs length for DBTune.org Musicbrainz D2R Server took 4.266537427902222s
Interoperability | New vocabularies check for DBTune.org Musicbrainz D2R Server took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for DBTune.org Musicbrainz D2R Server took 0.0859220027923584s
Consistency | Disjoint class check for DBTune.org Musicbrainz D2R Server took 0.09214496612548828s
Consistency | Check Misplaced properties for DBTune.org Musicbrainz D2R Server took 2.35603928565979s
Consistency | Check Ontology hijacking for DBTune.org Musicbrainz D2R Server took 5.003917455673218s
Consistency | Check Invalid usage of undefined properties for DBTune.org Musicbrainz D2R Server took 1.4251246452331543s
Conciseness | Check Extensional conciseness for DBTune.org Musicbrainz D2R Server took 0.0001323223114013672s
Security | Sign check for DBTune.org Musicbrainz D2R Server took 0.09964704513549805s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 10.135237216949463s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010848045349121094s
Interoperability | Check the re-using of existing vocabs for DBTune.org Musicbrainz D2R Server took 1.9073486328125e-06s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.3113021850585938e-05s
INFO | --- Analysis for dbtune-musicbrainz took 165.45934987068176s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.29232311248779297s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0010285377502441406s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 10.197656393051147s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0009808540344238281s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 6.508827209472656e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.4066696166992188e-05s
INFO | --- Analysis for dbtune-myspace took 112.78126835823059s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 7.295608520507812e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.0024788379669189453s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 10.202008962631226s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.02101755142211914s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.52587890625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 2.956390380859375e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 1.3589859008789062e-05s
INFO | --- Analysis for dclg-openuplabs took 112.03636598587036s
Availability | SPARQL endpoint availability check for data.dcs took 9.369850158691406e-05s
Availability | VoID file availability check for data.dcs took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for data.dcs took 10.595927000045776s
Reputation | Calculation of the PageRank for data.dcs took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.842613220214844e-05s
Believability | Calculation of trust value for data.dcs took 8.106231689453125e-06s
INFO | --- Analysis for dcs-sheffield took 111.84478378295898s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 7.033348083496094e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00040221214294433594s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 10.095701456069946s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.023000001907348633s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 2.9802322387695312e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 1.33514404296875e-05s
INFO | --- Analysis for de-budget took 112.33257293701172s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 9.5367431640625e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 10.106060028076172s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020296335220336914s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.9577484130859375e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.2636184692382812e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 112.33912587165833s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 6.389617919921875e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 10.10151481628418s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.887580871582031e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.3113021850585938e-05s
INFO | --- Analysis for debian-package-tracking-system took 111.26678419113159s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0001049041748046875s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.00033974647521972656s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 10.104048013687134s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.457069396972656e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.3589859008789062e-05s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 111.9374303817749s
Availability | SPARQL endpoint availability check for Demografie took 4.1484832763671875e-05s
Availability | VoID file availability check for Demografie took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Demografie took 10.1924467086792s
Reputation | Calculation of the PageRank for Demografie took 0.02278590202331543s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.0040740966796875e-05s
Believability | Calculation of trust value for Demografie took 1.621246337890625e-05s
INFO | --- Analysis for demografie took 112.13388276100159s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 8.559226989746094e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 10.100096940994263s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.457069396972656e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 7.62939453125e-06s
INFO | --- Analysis for desaparecidos took 112.34125185012817s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.076957702636719e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 10.596903800964355s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.775161743164062e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.239776611328125e-05s
INFO | --- Analysis for deustoentrepreneurship took 111.94186878204346s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.076957702636719e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 10.593352794647217s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.022621870040893555s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00011110305786132812s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.2874603271484375e-05s
INFO | --- Analysis for deustotech took 112.34520363807678s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3763067722320557s
Availability | VoID file availability check for Deutsche Biographie took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 10.10140061378479s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02169322967529297s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.743171691894531e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.239776611328125e-05s
INFO | --- Analysis for deutsche-biographie took 103.22958588600159s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 8.368492126464844e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 10.097949028015137s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020961284637451172s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.936622619628906e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.0251998901367188e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 111.21306228637695s
Availability | SPARQL endpoint availability check for dev8d took 4.38690185546875e-05s
Availability | VoID file availability check for dev8d took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for dev8d took 10.092771530151367s
Reputation | Calculation of the PageRank for dev8d took 0.02162313461303711s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.534027099609375e-05s
Believability | Calculation of trust value for dev8d took 1.1920928955078125e-05s
INFO | --- Analysis for dev8d took 111.94335269927979s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 8.463859558105469e-05s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 10.09868836402893s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.221366882324219e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.2636184692382812e-05s
INFO | --- Analysis for dewey_decimal_classification took 111.84795641899109s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.267692565917969e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 10.103507041931152s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.0279159545898438e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 6.9141387939453125e-06s
INFO | --- Analysis for DHSVM took 111.6438672542572s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.100799560546875e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 10.503499507904053s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020641565322875977s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.361701965332031e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 1.239776611328125e-05s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 111.86958599090576s
Availability | SPARQL endpoint availability check for Diavgeia took 8.368492126464844e-05s
Availability | VoID file availability check for Diavgeia took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Diavgeia took 10.59883713722229s
Reputation | Calculation of the PageRank for Diavgeia took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.749961853027344e-05s
Believability | Calculation of trust value for Diavgeia took 1.33514404296875e-05s
INFO | --- Analysis for diavgeia took 111.94053506851196s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 7.05718994140625e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 10.59309196472168s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02031111717224121s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011157989501953125s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.33514404296875e-05s
INFO | --- Analysis for didactalia took 112.94643974304199s
Availability | SPARQL endpoint availability check for diigo.feed took 4.124641418457031e-05s
Availability | VoID file availability check for diigo.feed took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for diigo.feed took 10.103465795516968s
Reputation | Calculation of the PageRank for diigo.feed took 0.021020889282226562s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 3.600120544433594e-05s
Believability | Calculation of trust value for diigo.feed took 1.2874603271484375e-05s
INFO | --- Analysis for diigo-feed took 112.73856210708618s
Availability | SPARQL endpoint availability check for DisGeNET took 8.559226989746094e-05s
Availability | VoID file availability check for DisGeNET took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for DisGeNET took 10.100038766860962s
Reputation | Calculation of the PageRank for DisGeNET took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015354156494140625s
Believability | Calculation of trust value for DisGeNET took 1.5020370483398438e-05s
INFO | --- Analysis for disgenet took 111.46424508094788s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 8.249282836914062e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 10.100296020507812s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.0209047794342041s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.123283386230469e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 1.4066696166992188e-05s
INFO | --- Analysis for disk took 112.3427267074585s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 5.1021575927734375e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 10.194106817245483s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 2.86102294921875e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 1.3589859008789062e-05s
INFO | --- Analysis for distritos-zaragoza took 112.75184535980225s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 3.981590270996094e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 10.094589233398438s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.0517578125e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.3113021850585938e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 112.54011583328247s
Availability | SPARQL endpoint availability check for DM2E took 4.3392181396484375e-05s
Availability | VoID file availability check for DM2E took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for DM2E took 10.17229962348938s
Reputation | Calculation of the PageRank for DM2E took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.0001087188720703125s
Believability | Calculation of trust value for DM2E took 1.2159347534179688e-05s
INFO | --- Analysis for dm2e took 112.15033459663391s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 3.981590270996094e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 10.099207162857056s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.020919322967529297s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.8623809814453125e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 1.239776611328125e-05s
INFO | --- Analysis for dmoz_rdf_dump took 111.53838729858398s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 9.417533874511719e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 10.105366706848145s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.000148773193359375s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.3113021850585938e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 112.23514604568481s
Availability | SPARQL endpoint availability check for DOAP Store took 8.988380432128906e-05s
Availability | VoID file availability check for DOAP Store took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for DOAP Store took 10.19661545753479s
Reputation | Calculation of the PageRank for DOAP Store took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.4809112548828125e-05s
Believability | Calculation of trust value for DOAP Store took 1.3113021850585938e-05s
INFO | --- Analysis for doap_store took 111.67098546028137s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.100799560546875e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 10.09472393989563s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.022864103317260742s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 7.271766662597656e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 1.4781951904296875e-05s
INFO | --- Analysis for doi took 112.12760734558105s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.076957702636719e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 10.09009838104248s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.956390380859375e-05s
Believability | Calculation of trust value for Driggu Florentino took 2.4318695068359375e-05s
INFO | --- Analysis for Driggu took 111.63700819015503s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 3.9577484130859375e-05s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 10.104177713394165s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.62396240234375e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.1682510375976562e-05s
INFO | --- Analysis for drug-data-hifm took 112.26937770843506s
Availability | SPARQL endpoint availability check for dspace took 0.00011014938354492188s
Availability | VoID file availability check for dspace took 0.00036644935607910156s
Completeness | Calculation of interlinking completeness for dspace took 10.597188949584961s
Reputation | Calculation of the PageRank for dspace took 0.02035379409790039s
Interlinking | Calculation of Degree of Connection for dspace took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for dspace took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for dspace took 2.7894973754882812e-05s
Believability | Calculation of trust value for dspace took 7.867813110351562e-06s
INFO | --- Analysis for dspace took 111.86953544616699s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 8.273124694824219e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 10.198503255844116s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 5.507469177246094e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 8.821487426757812e-06s
INFO | --- Analysis for duraark-linked-building-data took 112.14026308059692s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 4.7206878662109375e-05s
Availability | VoID file availability check for MetaLex Document Server took 0.00035858154296875s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 10.094107389450073s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.62396240234375e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.33514404296875e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 112.64525198936462s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.8332383632659912s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 10.102629661560059s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020883560180664062s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 6.198883056640625e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.2874603271484375e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 105.63710069656372s
Availability | SPARQL endpoint availability check for DWS-Group took 3.933906555175781e-05s
Availability | VoID file availability check for DWS-Group took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for DWS-Group took 10.098320722579956s
Reputation | Calculation of the PageRank for DWS-Group took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010323524475097656s
Believability | Calculation of trust value for DWS-Group took 1.430511474609375e-05s
INFO | --- Analysis for dws-group took 111.95146298408508s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.124641418457031e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 10.09072494506836s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.021853923797607422s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.8848648071289062e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.3828277587890625e-05s
INFO | --- Analysis for E1 took 111.43904995918274s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 4.029273986816406e-05s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 10.199748754501343s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02054905891418457s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00010919570922851562s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i-alaska took 112.44964575767517s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 8.726119995117188e-05s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 10.094710111618042s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.340576171875e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-cau took 111.34620785713196s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.0001544952392578125s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 10.096687078475952s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.022504568099975586s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.4849853515625e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 112.4429247379303s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 4.601478576660156e-05s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 10.197021961212158s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.023142337799072266s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.751319885253906e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-cdrewu took 111.36759853363037s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 4.00543212890625e-05s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 10.0946364402771s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00012826919555664062s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-dartmouth took 112.37259674072266s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 7.62939453125e-05s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 10.100801467895508s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 9.5367431640625e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-famu took 111.8675172328949s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 8.273124694824219e-05s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 10.096117973327637s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.002000570297241211s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.0003123283386230469s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-harvard took 111.34607148170471s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.00010347366333007812s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 10.097394466400146s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020241975784301758s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012803077697753906s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i-hawaii took 111.63770031929016s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 5.125999450683594e-05s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 10.09570050239563s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.127357482910156e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-howard took 112.03950309753418s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 6.175041198730469e-05s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 10.19512391090393s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.128715515136719e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 112.8694384098053s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 8.296966552734375e-05s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 10.091416597366333s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020931005477905273s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.0001327991485595703s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-jsu took 112.44598770141602s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 3.910064697265625e-05s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 10.102152347564697s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.021693706512451172s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.839897155761719e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-meharry took 111.26150393486023s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 8.368492126464844e-05s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 10.197151184082031s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020897865295410156s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010156631469726562s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-montana took 111.54492139816284s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 8.320808410644531e-05s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 10.093729019165039s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.584426879882812e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-msm took 112.06632542610168s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 4.458427429199219e-05s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 10.598681926727295s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02031874656677246s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00012874603271484375s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.430511474609375e-05s
INFO | --- Analysis for eagle-i-ohsu took 112.17435622215271s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 4.124641418457031e-05s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00039839744567871094s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 10.101382970809937s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.02244400978088379s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.246566772460938e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-psm took 112.16585898399353s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 4.076957702636719e-05s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 10.103030920028687s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020685434341430664s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.67572021484375e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-tsu took 111.5674831867218s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 9.703636169433594e-05s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 10.09526014328003s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.079673767089844e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-tuskegee took 111.37618732452393s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 3.9577484130859375e-05s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 10.105648040771484s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02213287353515625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.846687316894531e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 9.775161743164062e-06s
INFO | --- Analysis for eagle-i-uccaribe took 111.34196472167969s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 9.250640869140625e-05s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 10.091776371002197s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02227473258972168s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012755393981933594s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-upr took 112.76627731323242s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 4.00543212890625e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0011878013610839844s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 10.0958571434021s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.437301635742188e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-utep took 111.367600440979s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 4.029273986816406e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 10.199675559997559s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.02115797996520996s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.009506225585938e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-utsa took 112.47024416923523s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 3.886222839355469e-05s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 10.101006746292114s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.021136045455932617s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 8.96453857421875e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 8.821487426757812e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 111.32084226608276s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 4.076957702636719e-05s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 10.098310947418213s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.867813110351562e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-xula took 111.34347653388977s
Availability | SPARQL endpoint availability check for Emergency situation took 4.029273986816406e-05s
Availability | VoID file availability check for Emergency situation took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Emergency situation took 10.09905743598938s
Reputation | Calculation of the PageRank for Emergency situation took 0.025624513626098633s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.001013040542602539s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 7.367134094238281e-05s
Believability | Calculation of trust value for Emergency situation took 7.867813110351562e-06s
INFO | --- Analysis for Earthquake took 111.27500200271606s
Availability | SPARQL endpoint availability check for ESO took 3.9577484130859375e-05s
Availability | VoID file availability check for ESO took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for ESO took 10.103137731552124s
Reputation | Calculation of the PageRank for ESO took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for ESO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for ESO took 7.843971252441406e-05s
Believability | Calculation of trust value for ESO took 7.867813110351562e-06s
INFO | --- Analysis for Earthquake_case took 111.2715528011322s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 5.245208740234375e-05s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 10.102038145065308s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 9.655952453613281e-05s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for ecb-linked-data took 111.57259106636047s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 6.4849853515625e-05s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 10.107330799102783s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.022330045700073242s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.029273986816406e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 1.3113021850585938e-05s
INFO | --- Analysis for ecb-statistics-linked-data took 111.55964827537537s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0974578857421875s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 10.104748725891113s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 7.104873657226562e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 113.38006544113159s
Availability | SPARQL endpoint availability check for ECLAP took 20.92316508293152s
Availability | VoID file availability check for ECLAP took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for ECLAP took 10.10254693031311s
Reputation | Calculation of the PageRank for ECLAP took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.6253204345703125e-05s
Believability | Calculation of trust value for ECLAP took 1.2874603271484375e-05s
INFO | --- Analysis for eclap took 163.56304502487183s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.315376281738281e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0003447532653808594s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 10.19955587387085s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.021730899810791016s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.0967254638671875e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.2636184692382812e-05s
INFO | --- Analysis for ECNU-GISer took 111.8685839176178s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.1484832763671875e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 10.097511053085327s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.888938903808594e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.2636184692382812e-05s
INFO | --- Analysis for ecs took 111.75338578224182s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.076957702636719e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 10.100819110870361s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.123283386230469e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 8.106231689453125e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 112.33218622207642s
Availability | SPARQL endpoint availability check for Edublogs took 8.940696716308594e-05s
Availability | VoID file availability check for Edublogs took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Edublogs took 10.103036403656006s
Reputation | Calculation of the PageRank for Edublogs took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0008280277252197266s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00011515617370605469s
Believability | Calculation of trust value for Edublogs took 1.33514404296875e-05s
INFO | --- Analysis for edublogs took 111.57468056678772s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 3.9577484130859375e-05s
Availability | VoID file availability check for education.data.gov.uk took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 10.09088945388794s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.083747863769531e-05s
Believability | Calculation of trust value for education.data.gov.uk took 1.3828277587890625e-05s
INFO | --- Analysis for education-data-gov-uk took 111.93839359283447s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 10.098991394042969s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.867813110351562e-06s
INFO | --- Analysis for education-openuplabs took 111.7336368560791s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 3.981590270996094e-05s
Availability | VoID file availability check for Educational programs - SISVU took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 10.10166597366333s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.1021575927734375e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.621246337890625e-05s
INFO | --- Analysis for educationalprograms_sisvu took 111.83795380592346s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 5.14984130859375e-05s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 10.098411321640015s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.022513866424560547s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.886222839355469e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 1.3113021850585938e-05s
INFO | --- Analysis for eea took 111.93808197975159s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 9.226799011230469e-05s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0027642250061035156s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 10.107587575912476s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 6.031990051269531e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 1.3589859008789062e-05s
INFO | --- Analysis for eea-rod took 111.75171661376953s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 4.124641418457031e-05s
Availability | VoID file availability check for EEA Vocabularies took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 10.094258308410645s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 7.891654968261719e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.2636184692382812e-05s
INFO | --- Analysis for eea-vocabularies took 111.364901304245s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 8.368492126464844e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 10.107676029205322s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.552436828613281e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for ege-university-linked-open-data took 113.8691987991333s
Availability | SPARQL endpoint availability check for E-Government Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for E-Government Ontology took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 10.098770380020142s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 2.6702880859375e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.33514404296875e-05s
INFO | --- Analysis for EGovOntology took 111.76588654518127s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.0531158447265625e-05s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0003428459167480469s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 10.099543571472168s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0202484130859375s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 4.9114227294921875e-05s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2874603271484375e-05s
INFO | --- Analysis for ei2a took 111.6692750453949s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.482269287109375e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 10.096505165100098s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.021231889724731445s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010609626770019531s
Believability | Calculation of trust value for EIONET RDF Data took 8.58306884765625e-06s
INFO | --- Analysis for eionet-rdf took 111.8715500831604s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 8.535385131835938e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 10.096195697784424s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.021366119384765625s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 2.765655517578125e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.2636184692382812e-05s
INFO | --- Analysis for ElgooG_ took 111.97521686553955s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 8.487701416015625e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 10.122107028961182s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.02135300636291504s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.956390380859375e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 1.3589859008789062e-05s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 111.43786692619324s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.608268737792969e-05s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 10.101415395736694s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.021126985549926758s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 9.942054748535156e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 8.344650268554688e-06s
INFO | --- Analysis for elviajero took 112.33352780342102s
Availability | SPARQL endpoint availability check for EMN took 7.05718994140625e-05s
Availability | VoID file availability check for EMN took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for EMN took 10.190788745880127s
Reputation | Calculation of the PageRank for EMN took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for EMN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for EMN took 3.647804260253906e-05s
Believability | Calculation of trust value for EMN took 1.2874603271484375e-05s
INFO | --- Analysis for emn took 111.86941862106323s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 3.9577484130859375e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 10.102771997451782s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.412101745605469e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for enakting-co2emission took 111.9732358455658s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 8.20159912109375e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 10.09624171257019s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.506111145019531e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for enakting-crime took 111.66038513183594s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.029273986816406e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00031113624572753906s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 10.100565910339355s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.020519733428955078s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.410743713378906e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for enakting-energy took 111.44452285766602s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 6.413459777832031e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 10.098251342773438s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.131431579589844e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 7.867813110351562e-06s
INFO | --- Analysis for enakting-mortality took 111.52988362312317s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 10.196595668792725s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020639657974243164s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.267692565917969e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 1.52587890625e-05s
INFO | --- Analysis for enakting-nhs took 112.04735565185547s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.00543212890625e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 10.100136756896973s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.245208740234375e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 1.3828277587890625e-05s
INFO | --- Analysis for enakting-population took 112.77005076408386s
Availability | SPARQL endpoint availability check for Enel Shops took 8.606910705566406e-05s
Availability | VoID file availability check for Enel Shops took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for Enel Shops took 10.094464302062988s
Reputation | Calculation of the PageRank for Enel Shops took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.170967102050781e-05s
Believability | Calculation of trust value for Enel Shops took 1.2636184692382812e-05s
INFO | --- Analysis for enel-shops took 111.76561689376831s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 8.58306884765625e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 10.098754405975342s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020792007446289062s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.7670135498046875e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 8.106231689453125e-06s
INFO | --- Analysis for energy-efficiency took 111.84358644485474s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 9.870529174804688e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0011289119720458984s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 10.097896814346313s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 111.23954629898071s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 8.511543273925781e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 10.601014375686646s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.3855438232421875e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 112.34495615959167s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 8.463859558105469e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 10.094995737075806s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020220041275024414s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 2.7894973754882812e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for english-heritage-components-thesaurus took 112.363942861557s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.76837158203125e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 10.103537797927856s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.552436828613281e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 111.97048330307007s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.482269287109375e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 10.092598915100098s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020632266998291016s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.504753112792969e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 1.4543533325195312e-05s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 111.44318699836731s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 8.58306884765625e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 10.591127872467041s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.02282404899597168s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.266334533691406e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 111.93580222129822s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.38690185546875e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 10.09934401512146s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.021718263626098633s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.5762786865234375e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 111.27397131919861s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.604790210723877s
Availability | VoID file availability check for English Heritage Periods List took 0.0002701282501220703s
Extra | Recovery of all triples for English Heritage Periods List took 0.302889347076416s
Performance | Total latancy measurement for English Heritage Periods List took 1.5147535800933838s
Amount of data | Number of triples check for English Heritage Periods List took 0.4897725582122803s
Versatility | Languages check for English Heritage Periods List took 0.2719709873199463s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.4930298328399658s
Security | Check HTTPS for English Heritage Periods List took 0.21748924255371094s
Interpretability | RDF structures check for English Heritage Periods List took 0.2570168972015381s
Versatility | Serialization formats check for English Heritage Periods List took 0.43747591972351074s
Availability | RDF dump link check for English Heritage Periods List took 0.289020299911499s
License | MR license check for English Heritage Periods List took 0.3655562400817871s
License | HR license check for English Heritage Periods List took 0.3622293472290039s
Amount of data | Number of property check for English Heritage Periods List took 0.40788888931274414s
Understandability | Number of label check for English Heritage Periods List took 0.43321681022644043s
Understandability | URI regex check for English Heritage Periods List took 0.6312911510467529s
Understandability | Vocabs check for English Heritage Periods List took 0.3382883071899414s
Verifiability | Authors check for English Heritage Periods List took 0.37590980529785156s
Verifiability | Publishers check for English Heritage Periods List took 0.3735208511352539s
Performance | Throughput check for English Heritage Periods List took 13.921253681182861s
Amount of data | Check the number of entities for English Heritage Periods List took 6.914138793945312e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.3913421630859375s
Interlinking | sameAs chians check for English Heritage Periods List took 0.30933165550231934s
Interlinking | skos check for English Heritage Periods List took 0.3065183162689209s
Interlinking | skos check for English Heritage Periods List took 0.36221861839294434s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.3753230571746826s
Currency | Creation date check for English Heritage Periods List took 0.6659786701202393s
Currency | Modification date check for English Heritage Periods List took 0.7463593482971191s
Rep.Conc. | URIs length for English Heritage Periods List took 0.5913538932800293s
Interoperability | New vocabularies check for English Heritage Periods List took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.35717129707336426s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3002135753631592s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3053905963897705s
Consistency | Disjoint class check for English Heritage Periods List took 0.32582664489746094s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3728451728820801s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.664534568786621s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001468658447265625s
Security | Sign check for English Heritage Periods List took 0.29802799224853516s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 10.574511051177979s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 1.2636184692382812e-05s
INFO | --- Analysis for english-heritage-periods-list took 159.85109424591064s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 8.535385131835938e-05s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 10.194885015487671s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.0214841365814209s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.075599670410156e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 1.3828277587890625e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 111.62884449958801s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.00031113624572753906s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 10.098539113998413s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.337860107421875e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 7.3909759521484375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 111.16807961463928s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.267692565917969e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 10.112427711486816s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.790855407714844e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 1.3589859008789062e-05s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 111.842698097229s
Availability | SPARQL endpoint availability check for English WordNet took 4.3392181396484375e-05s
Availability | VoID file availability check for English WordNet took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for English WordNet took 10.11224627494812s
Reputation | Calculation of the PageRank for English WordNet took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.910064697265625e-05s
Believability | Calculation of trust value for English WordNet took 1.3589859008789062e-05s
INFO | --- Analysis for english-wordnet took 112.0361602306366s
Availability | SPARQL endpoint availability check for English Heritage Places took 9.036064147949219e-05s
Availability | VoID file availability check for English Heritage Places took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for English Heritage Places took 10.094226121902466s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.0279159545898438e-05s
Believability | Calculation of trust value for English Heritage Places took 1.3113021850585938e-05s
INFO | --- Analysis for englishheritage_places took 111.35272741317749s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 8.630752563476562e-05s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 10.101154804229736s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.000985860824584961s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 0.00010991096496582031s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.33514404296875e-05s
INFO | --- Analysis for enipedia took 111.66183185577393s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.1484832763671875e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Enslaved.org took 10.17845630645752s
Reputation | Calculation of the PageRank for Enslaved.org took 0.022482633590698242s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.552436828613281e-05s
Believability | Calculation of trust value for Enslaved.org took 1.1920928955078125e-05s
INFO | --- Analysis for enslaved.org took 113.34525442123413s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 8.368492126464844e-05s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 10.09601378440857s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.021598100662231445s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 4.792213439941406e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.2874603271484375e-05s
INFO | --- Analysis for entice-graph took 112.14763641357422s
Availability | SPARQL endpoint availability check for Entrez Gene took 8.7738037109375e-05s
Availability | VoID file availability check for Entrez Gene took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Entrez Gene took 10.104274272918701s
Reputation | Calculation of the PageRank for Entrez Gene took 0.021219253540039062s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.5762786865234375e-05s
Believability | Calculation of trust value for Entrez Gene took 8.344650268554688e-06s
INFO | --- Analysis for entrez_gene took 111.24106645584106s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.291534423828125e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 10.701436519622803s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.02231764793395996s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.24249267578125e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 1.430511474609375e-05s
INFO | --- Analysis for entrez_gene_extract took 112.14105772972107s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 4.1484832763671875e-05s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 10.101576089859009s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.021854162216186523s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0009424686431884766s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.5789947509765625e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 1.5020370483398438e-05s
INFO | --- Analysis for environment-agency-bathing-water-quality took 111.93033194541931s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 4.100799560546875e-05s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 10.198428392410278s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020355701446533203s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 5.030632019042969e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 1.239776611328125e-05s
INFO | --- Analysis for environment-data-gov-uk took 111.64058113098145s
Availability | SPARQL endpoint availability check for EARTh took 8.630752563476562e-05s
Availability | VoID file availability check for EARTh took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for EARTh took 10.590357065200806s
Reputation | Calculation of the PageRank for EARTh took 0.021913766860961914s
Interlinking | Calculation of Degree of Connection for EARTh took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.608268737792969e-05s
Believability | Calculation of trust value for EARTh took 8.106231689453125e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 112.57095122337341s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 8.273124694824219e-05s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 10.095401525497437s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.022429466247558594s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.2901763916015625e-05s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for EO_metadata took 111.27009916305542s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 6.508827209472656e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 10.591684341430664s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.022797584533691406s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.600120544433594e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 8.344650268554688e-06s
INFO | --- Analysis for EOKP-Datasets took 112.86952137947083s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.0531158447265625e-05s
Availability | VoID file availability check for EPA-CDR took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for EPA-CDR took 10.202786684036255s
Reputation | Calculation of the PageRank for EPA-CDR took 0.021404027938842773s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 4.1961669921875e-05s
Believability | Calculation of trust value for EPA-CDR took 1.33514404296875e-05s
INFO | --- Analysis for epa-cdr took 111.36376285552979s
Availability | SPARQL endpoint availability check for EPA-FRS took 9.799003601074219e-05s
Availability | VoID file availability check for EPA-FRS took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for EPA-FRS took 10.19190526008606s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020479679107666016s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.152557373046875e-05s
Believability | Calculation of trust value for EPA-FRS took 7.3909759521484375e-06s
INFO | --- Analysis for epa-frs took 111.46195864677429s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.029273986816406e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 10.095733404159546s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.504753112792969e-05s
Believability | Calculation of trust value for EPA-RCRA took 8.106231689453125e-06s
INFO | --- Analysis for epa-rcra took 111.30282998085022s
Availability | SPARQL endpoint availability check for EPA-SRS took 8.344650268554688e-05s
Availability | VoID file availability check for EPA-SRS took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for EPA-SRS took 10.099722385406494s
Reputation | Calculation of the PageRank for EPA-SRS took 0.022721052169799805s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.176399230957031e-05s
Believability | Calculation of trust value for EPA-SRS took 7.3909759521484375e-06s
INFO | --- Analysis for epa-srs took 111.36624956130981s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.696846008300781e-05s
Availability | VoID file availability check for EPA-TRI took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for EPA-TRI took 10.095222234725952s
Reputation | Calculation of the PageRank for EPA-TRI took 0.02230358123779297s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.4809112548828125e-05s
Believability | Calculation of trust value for EPA-TRI took 1.33514404296875e-05s
INFO | --- Analysis for epa-tri took 112.14104342460632s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 8.392333984375e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0003077983856201172s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 10.1062912940979s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.796287536621094e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 8.58306884765625e-06s
INFO | --- Analysis for epo took 111.87143588066101s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 7.367134094238281e-05s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 10.198634386062622s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.02031874656677246s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00012826919555664062s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 111.27644348144531s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 4.124641418457031e-05s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 10.093693494796753s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0009763240814208984s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 9.632110595703125e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 8.58306884765625e-06s
INFO | --- Analysis for eprtr took 112.36146473884583s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 4.00543212890625e-05s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 10.105869054794312s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 2.8133392333984375e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.239776611328125e-05s
INFO | --- Analysis for ERAKG took 111.34846591949463s
Availability | SPARQL endpoint availability check for reg took 4.673004150390625e-05s
Availability | VoID file availability check for reg took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for reg took 10.604998350143433s
Reputation | Calculation of the PageRank for reg took 0.020501136779785156s
Interlinking | Calculation of Degree of Connection for reg took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for reg took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for reg took 2.09808349609375e-05s
Believability | Calculation of trust value for reg took 7.867813110351562e-06s
INFO | --- Analysis for erg took 112.37559080123901s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 5.221366882324219e-05s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 10.597930908203125s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.075599670410156e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 9.298324584960938e-06s
INFO | --- Analysis for es-msssi-drug-prices took 112.03993797302246s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 5.1975250244140625e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 10.103164672851562s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.059906005859375e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 1.33514404296875e-05s
INFO | --- Analysis for esd-standards took 111.53566431999207s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.1484832763671875e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 10.103512287139893s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 6.771087646484375e-05s
Believability | Calculation of trust value for ESD-Toolkit took 7.3909759521484375e-06s
INFO | --- Analysis for esd-toolkit took 111.33306527137756s
Availability | SPARQL endpoint availability check for Dataset Esis took 3.981590270996094e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Dataset Esis took 10.197844982147217s
Reputation | Calculation of the PageRank for Dataset Esis took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.695487976074219e-05s
Believability | Calculation of trust value for Dataset Esis took 7.3909759521484375e-06s
INFO | --- Analysis for esislearning took 112.0713791847229s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 8.416175842285156e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 10.196219444274902s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.02233433723449707s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 2.765655517578125e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 8.344650268554688e-06s
INFO | --- Analysis for ESV took 111.86604762077332s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 8.058547973632812e-05s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 10.099745273590088s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02049994468688965s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.3113021850585938e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 111.7758674621582s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 8.20159912109375e-05s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 10.194251775741577s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.021465063095092773s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 6.818771362304688e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.33514404296875e-05s
INFO | --- Analysis for eu-agencies-bodies took 111.34104776382446s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 7.2479248046875e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 10.107986450195312s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.022430419921875s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.4332275390625e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 7.62939453125e-06s
INFO | --- Analysis for eu-dgt-tm took 111.33491826057434s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.00543212890625e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 10.197984457015991s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.02115654945373535s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.295608520507812e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 1.2636184692382812e-05s
INFO | --- Analysis for eu-institutions took 111.47733688354492s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 4.2438507080078125e-05s
Availability | VoID file availability check for EU Parliament Media Library took 0.00036597251892089844s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 10.09774661064148s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02279520034790039s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.600120544433594e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 1.3828277587890625e-05s
INFO | --- Analysis for eu-parliament-media took 111.64211869239807s
Availability | SPARQL endpoint availability check for EU Who Is Who took 6.365776062011719e-05s
Availability | VoID file availability check for EU Who Is Who took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 10.106066942214966s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.022257566452026367s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.552436828613281e-05s
Believability | Calculation of trust value for EU Who Is Who took 1.1920928955078125e-05s
INFO | --- Analysis for eu-who-is-who took 112.24151968955994s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 8.463859558105469e-05s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.000850677490234375s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 10.090312957763672s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.022937297821044922s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.719329833984375e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for eumida-linked-data took 111.53294897079468s
Availability | SPARQL endpoint availability check for European Nature Information System took 4.00543212890625e-05s
Availability | VoID file availability check for European Nature Information System took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for European Nature Information System took 10.096424102783203s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 9.870529174804688e-05s
Believability | Calculation of trust value for European Nature Information System took 8.821487426757812e-06s
INFO | --- Analysis for eunis took 111.27067041397095s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 6.937980651855469e-05s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 10.208791255950928s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 6.461143493652344e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for eur-lex-rdf took 112.0768301486969s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 7.128715515136719e-05s
Availability | VoID file availability check for Standard Eurobarometer took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 10.096540927886963s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.02139449119567871s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.7206878662109375e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 1.3589859008789062e-05s
INFO | --- Analysis for eurobarometer-standard took 111.26797389984131s
Availability | SPARQL endpoint availability check for European Election Results took 3.981590270996094e-05s
Availability | VoID file availability check for European Election Results took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for European Election Results took 10.099338054656982s
Reputation | Calculation of the PageRank for European Election Results took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.1948089599609375e-05s
Believability | Calculation of trust value for European Election Results took 1.2159347534179688e-05s
INFO | --- Analysis for european-election-results took 111.46926760673523s
Availability | SPARQL endpoint availability check for EPO patents took 5.1021575927734375e-05s
Availability | VoID file availability check for EPO patents took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for EPO patents took 10.09806489944458s
Reputation | Calculation of the PageRank for EPO patents took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for EPO patents took 3.647804260253906e-05s
Believability | Calculation of trust value for EPO patents took 1.3589859008789062e-05s
INFO | --- Analysis for European_Patent_Information took 111.76429343223572s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.100799560546875e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 10.096352815628052s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020990371704101562s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.123283386230469e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 1.3828277587890625e-05s
INFO | --- Analysis for europeana-lod took 111.83938384056091s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.649162292480469e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 10.101900815963745s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.465217590332031e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 1.3113021850585938e-05s
INFO | --- Analysis for europeana-lod-v1 took 111.6679961681366s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.11881661415100098s
Availability | VoID file availability check for Europeana SPARQL took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 10.098542928695679s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.054473876953125e-05s
Believability | Calculation of trust value for Europeana SPARQL took 7.62939453125e-06s
INFO | --- Analysis for europeana-sparql took 111.68567943572998s
Availability | SPARQL endpoint availability check for EuroSentiment took 4.1961669921875e-05s
Availability | VoID file availability check for EuroSentiment took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for EuroSentiment took 10.09783387184143s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.62396240234375e-05s
Believability | Calculation of trust value for EuroSentiment took 1.3113021850585938e-05s
INFO | --- Analysis for eurosentiment took 111.75989055633545s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 8.940696716308594e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 10.097208976745605s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.0108642578125e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 1.2636184692382812e-05s
INFO | --- Analysis for eurostat-rdf took 112.16802334785461s
Availability | SPARQL endpoint availability check for EuroVoc took 8.559226989746094e-05s
Availability | VoID file availability check for EuroVoc took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for EuroVoc took 10.096944332122803s
Reputation | Calculation of the PageRank for EuroVoc took 0.022912263870239258s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 6.985664367675781e-05s
Believability | Calculation of trust value for EuroVoc took 1.3828277587890625e-05s
INFO | --- Analysis for eurovoc took 112.4377453327179s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 6.270408630371094e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 10.098614692687988s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0008602142333984375s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.696846008300781e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 1.3828277587890625e-05s
INFO | --- Analysis for eurovoc-in-skos took 111.74560809135437s
Availability | SPARQL endpoint availability check for European Television Heritage took 8.130073547363281e-05s
Availability | VoID file availability check for European Television Heritage took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for European Television Heritage took 10.193651676177979s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.7894973754882812e-05s
Believability | Calculation of trust value for European Television Heritage took 7.62939453125e-06s
INFO | --- Analysis for euscreen took 111.79286789894104s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 3.981590270996094e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 10.102892637252808s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.021445274353027344s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.8160552978515625e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 1.3113021850585938e-05s
INFO | --- Analysis for euskadi-farmacias took 111.57659935951233s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 8.320808410644531e-05s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 10.102104663848877s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 2.9087066650390625e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.3589859008789062e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 112.26491451263428s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 4.291534423828125e-05s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 10.196855068206787s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 6.866455078125e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.2636184692382812e-05s
INFO | --- Analysis for eutc-productions took 112.06402206420898s
Availability | SPARQL endpoint availability check for EventMedia took 0.3221862316131592s
Availability | VoID file availability check for EventMedia took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for EventMedia took 10.103256940841675s
Reputation | Calculation of the PageRank for EventMedia took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00011420249938964844s
Believability | Calculation of trust value for EventMedia took 1.2636184692382812e-05s
INFO | --- Analysis for event-media took 112.02023673057556s
Availability | SPARQL endpoint availability check for EventKG took 4.1484832763671875e-05s
Availability | VoID file availability check for EventKG took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for EventKG took 10.60172414779663s
Reputation | Calculation of the PageRank for EventKG took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for EventKG took 9.036064147949219e-05s
Believability | Calculation of trust value for EventKG took 1.2159347534179688e-05s
INFO | --- Analysis for eventkg took 113.32521390914917s
Availability | SPARQL endpoint availability check for Eventseer took 8.606910705566406e-05s
Availability | VoID file availability check for Eventseer took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Eventseer took 10.099990606307983s
Reputation | Calculation of the PageRank for Eventseer took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for Eventseer took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Eventseer took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for Eventseer took 5.2928924560546875e-05s
Believability | Calculation of trust value for Eventseer took 7.867813110351562e-06s
INFO | --- Analysis for eventseer took 112.35760593414307s
Availability | SPARQL endpoint availability check for Face Link took 7.343292236328125e-05s
Availability | VoID file availability check for Face Link took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Face Link took 10.096973419189453s
Reputation | Calculation of the PageRank for Face Link took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for Face Link took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.838539123535156e-05s
Believability | Calculation of trust value for Face Link took 7.867813110351562e-06s
INFO | --- Analysis for Face_Link took 111.43619847297668s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 8.177757263183594e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 10.203402519226074s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.022073745727539062s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 3.528594970703125e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 8.821487426757812e-06s
INFO | --- Analysis for facebook-lids took 111.54172849655151s
Availability | SPARQL endpoint availability check for Fact Forge took 4.029273986816406e-05s
Availability | VoID file availability check for Fact Forge took 0.0003864765167236328s
Completeness | Calculation of interlinking completeness for Fact Forge took 10.100616931915283s
Reputation | Calculation of the PageRank for Fact Forge took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.552436828613281e-05s
Believability | Calculation of trust value for Fact Forge took 1.33514404296875e-05s
INFO | --- Analysis for fact-forge took 112.34133672714233s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.0531158447265625e-05s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.102807760238647s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.647804260253906e-05s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for FADN_(2019) took 111.94029521942139s
Availability | SPARQL endpoint availability check for FAMEData took 8.034706115722656e-05s
Availability | VoID file availability check for FAMEData took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for FAMEData took 10.102225303649902s
Reputation | Calculation of the PageRank for FAMEData took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for FAMEData took 2.9087066650390625e-05s
Believability | Calculation of trust value for FAMEData took 7.62939453125e-06s
INFO | --- Analysis for famedata took 111.9719877243042s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.00543212890625e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 10.099599361419678s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 8.893013000488281e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 1.3113021850585938e-05s
INFO | --- Analysis for fao-geopolitical-ontology took 112.16505265235901s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 4.76837158203125e-05s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 10.595317840576172s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0001010894775390625s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for fao-linked-data took 111.85770010948181s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 8.463859558105469e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 10.108721733093262s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.0218198299407959s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 2.7894973754882812e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for FAO_species took 111.3388261795044s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 4.0531158447265625e-05s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 10.108423471450806s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02169036865234375s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 5.0067901611328125e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.2874603271484375e-05s
INFO | --- Analysis for farmbio-chembl took 112.5332899093628s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 8.630752563476562e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.0011479854583740234s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 10.099149465560913s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.02252364158630371s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 2.956390380859375e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 1.3589859008789062e-05s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 112.3297028541565s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 5.221366882324219e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 10.09713625907898s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.02085113525390625s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for farolapp-dataset took 111.53997564315796s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 3.981590270996094e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 10.199350118637085s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020513296127319336s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 3.0517578125e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 1.3113021850585938e-05s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 111.54135990142822s
Availability | SPARQL endpoint availability check for I4.0-Onto took 7.271766662597656e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 10.107759952545166s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020282983779907227s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.600120544433594e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.4781951904296875e-05s
INFO | --- Analysis for fatimazahra took 111.37456130981445s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 9.965896606445312e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 10.092628002166748s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.3855438232421875e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 1.430511474609375e-05s
INFO | --- Analysis for federal-economic-rdf took 111.66920590400696s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.0531158447265625e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 10.092397928237915s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.695487976074219e-05s
Believability | Calculation of trust value for Feed Wrapper took 7.3909759521484375e-06s
INFO | --- Analysis for feedwrapper-lids took 111.36472725868225s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.029273986816406e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 10.09673547744751s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.8848648071289062e-05s
Believability | Calculation of trust value for FHIR STU3 took 8.106231689453125e-06s
INFO | --- Analysis for FHIR_STU3 took 111.868239402771s
Availability | SPARQL endpoint availability check for FiESTA took 4.220008850097656e-05s
Availability | VoID file availability check for FiESTA took 0.000518798828125s
Completeness | Calculation of interlinking completeness for FiESTA took 10.09993577003479s
Reputation | Calculation of the PageRank for FiESTA took 0.021444320678710938s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for FiESTA took 4.1484832763671875e-05s
Believability | Calculation of trust value for FiESTA took 7.152557373046875e-06s
INFO | --- Analysis for fiesta took 111.76988816261292s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.1484832763671875e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 10.087118864059448s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02227044105529785s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.528594970703125e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 6.9141387939453125e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 112.37058424949646s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 8.416175842285156e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 10.10666036605835s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.604194641113281e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 7.3909759521484375e-06s
INFO | --- Analysis for finnish-municipalities took 111.3704776763916s
Availability | SPARQL endpoint availability check for firmao took 8.559226989746094e-05s
Availability | VoID file availability check for firmao took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for firmao took 10.10353970527649s
Reputation | Calculation of the PageRank for firmao took 0.022933244705200195s
Interlinking | Calculation of Degree of Connection for firmao took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for firmao took 2.956390380859375e-05s
Believability | Calculation of trust value for firmao took 1.3828277587890625e-05s
INFO | --- Analysis for firmao took 112.43978714942932s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 9.298324584960938e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 10.09371542930603s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 111.64496326446533s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 8.130073547363281e-05s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 10.19827675819397s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.600120544433594e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.2636184692382812e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 112.47389674186707s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.00543212890625e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 10.193941354751587s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02244400978088379s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.726119995117188e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.2159347534179688e-05s
INFO | --- Analysis for fishes-of-texas took 111.43536853790283s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.172325134277344e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 10.604068994522095s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.1552734375e-05s
Believability | Calculation of trust value for flickr? wrappr took 1.3113021850585938e-05s
INFO | --- Analysis for flickr-wrappr took 111.8546826839447s
Availability | SPARQL endpoint availability check for flickr.person took 8.678436279296875e-05s
Availability | VoID file availability check for flickr.person took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for flickr.person took 10.100091934204102s
Reputation | Calculation of the PageRank for flickr.person took 0.021164417266845703s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for flickr.person took 4.0531158447265625e-05s
Believability | Calculation of trust value for flickr.person took 1.430511474609375e-05s
INFO | --- Analysis for flickr_person took 111.34119439125061s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.029273986816406e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 10.106407165527344s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.0517578125e-05s
Believability | Calculation of trust value for flickr.videoobject took 1.33514404296875e-05s
INFO | --- Analysis for flickr_videoobject took 111.43495392799377s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.601478576660156e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 10.096089839935303s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.022010326385498047s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 2.8371810913085938e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.2636184692382812e-05s
INFO | --- Analysis for FLUS took 111.66973805427551s
Availability | SPARQL endpoint availability check for Fly-TED took 4.076957702636719e-05s
Availability | VoID file availability check for Fly-TED took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Fly-TED took 10.095124244689941s
Reputation | Calculation of the PageRank for Fly-TED took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.361701965332031e-05s
Believability | Calculation of trust value for Fly-TED took 1.3113021850585938e-05s
INFO | --- Analysis for fly-ted took 111.47855401039124s
Availability | SPARQL endpoint availability check for FlyAtlas took 8.487701416015625e-05s
Availability | VoID file availability check for FlyAtlas took 0.001146078109741211s
Completeness | Calculation of interlinking completeness for FlyAtlas took 10.097672462463379s
Reputation | Calculation of the PageRank for FlyAtlas took 0.020830154418945312s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.218650817871094e-05s
Believability | Calculation of trust value for FlyAtlas took 1.33514404296875e-05s
INFO | --- Analysis for flyatlas took 113.03474926948547s
Availability | SPARQL endpoint availability check for Flybase took 9.584426879882812e-05s
Availability | VoID file availability check for Flybase took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Flybase took 10.097985982894897s
Reputation | Calculation of the PageRank for Flybase took 0.02206873893737793s
Interlinking | Calculation of Degree of Connection for Flybase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Flybase took 4.1961669921875e-05s
Believability | Calculation of trust value for Flybase took 1.33514404296875e-05s
INFO | --- Analysis for flybase took 111.63850998878479s
Availability | SPARQL endpoint availability check for Flyted took 9.1552734375e-05s
Availability | VoID file availability check for Flyted took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Flyted took 10.103815793991089s
Reputation | Calculation of the PageRank for Flyted took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for Flyted took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.0040740966796875e-05s
Believability | Calculation of trust value for Flyted took 1.3589859008789062e-05s
INFO | --- Analysis for flyted took 111.34861707687378s
Availability | SPARQL endpoint availability check for Foodista took 4.029273986816406e-05s
Availability | VoID file availability check for Foodista took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for Foodista took 10.202426195144653s
Reputation | Calculation of the PageRank for Foodista took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for Foodista took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.3855438232421875e-05s
Believability | Calculation of trust value for Foodista took 1.33514404296875e-05s
INFO | --- Analysis for foodista took 111.74357271194458s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.939338684082031e-05s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 10.101595401763916s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 8.106231689453125e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.3113021850585938e-05s
INFO | --- Analysis for foodpedia took 111.53834271430969s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.506111145019531e-05s
Availability | VoID file availability check for FORGE Course information took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for FORGE Course information took 10.091862678527832s
Reputation | Calculation of the PageRank for FORGE Course information took 0.0203397274017334s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.075599670410156e-05s
Believability | Calculation of trust value for FORGE Course information took 1.8596649169921875e-05s
INFO | --- Analysis for forge-course-information took 111.94880366325378s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.124641418457031e-05s
Availability | VoID file availability check for FrameBase schema took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for FrameBase schema took 10.09125566482544s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.5299530029296875e-05s
Believability | Calculation of trust value for FrameBase schema took 1.3113021850585938e-05s
INFO | --- Analysis for framebase-schema took 111.5424792766571s
Availability | SPARQL endpoint availability check for FrameNet took 4.00543212890625e-05s
Availability | VoID file availability check for FrameNet took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for FrameNet took 10.098185062408447s
Reputation | Calculation of the PageRank for FrameNet took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.00087738037109375s
Interlinking | Calculation of Clustering coefficient for FrameNet took 4.029273986816406e-05s
Believability | Calculation of trust value for FrameNet took 1.33514404296875e-05s
INFO | --- Analysis for framenet took 112.54834079742432s
Availability | SPARQL endpoint availability check for Framester took 4.1961669921875e-05s
Availability | VoID file availability check for Framester took 0.007375001907348633s
Completeness | Calculation of interlinking completeness for Framester took 10.093230485916138s
Reputation | Calculation of the PageRank for Framester took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for Framester took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Framester took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Framester took 7.152557373046875e-05s
Believability | Calculation of trust value for Framester took 1.3828277587890625e-05s
INFO | --- Analysis for framester took 111.6439483165741s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 8.463859558105469e-05s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 10.202753782272339s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.535385131835938e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.3113021850585938e-05s
INFO | --- Analysis for frb-linked-data took 112.44235849380493s
Availability | SPARQL endpoint availability check for Freebase took 4.3392181396484375e-05s
Availability | VoID file availability check for Freebase took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Freebase took 10.093334197998047s
Reputation | Calculation of the PageRank for Freebase took 0.021219491958618164s
Interlinking | Calculation of Degree of Connection for Freebase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.0002739429473876953s
Believability | Calculation of trust value for Freebase took 1.4066696166992188e-05s
INFO | --- Analysis for freebase took 111.93473100662231s
Availability | SPARQL endpoint availability check for Freeyork took 8.58306884765625e-05s
Availability | VoID file availability check for Freeyork took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Freeyork took 10.107874870300293s
Reputation | Calculation of the PageRank for Freeyork took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010704994201660156s
Believability | Calculation of trust value for Freeyork took 7.867813110351562e-06s
INFO | --- Analysis for freeyork-org took 111.93070101737976s
Availability | SPARQL endpoint availability check for French School Program took 4.0531158447265625e-05s
Availability | VoID file availability check for French School Program took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for French School Program took 10.099613189697266s
Reputation | Calculation of the PageRank for French School Program took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for French School Program took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.0517578125e-05s
Believability | Calculation of trust value for French School Program took 1.3589859008789062e-05s
INFO | --- Analysis for french-school-program took 111.32343292236328s
Availability | SPARQL endpoint availability check for French School System took 6.628036499023438e-05s
Availability | VoID file availability check for French School System took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for French School System took 10.101836919784546s
Reputation | Calculation of the PageRank for French School System took 0.02092456817626953s
Interlinking | Calculation of Degree of Connection for French School System took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for French School System took 2.9802322387695312e-05s
Believability | Calculation of trust value for French School System took 8.344650268554688e-06s
INFO | --- Analysis for french-school-system took 112.83931994438171s
Availability | SPARQL endpoint availability check for French TimeBank took 4.0531158447265625e-05s
Availability | VoID file availability check for French TimeBank took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for French TimeBank took 10.093757390975952s
Reputation | Calculation of the PageRank for French TimeBank took 0.02064800262451172s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.0040740966796875e-05s
Believability | Calculation of trust value for French TimeBank took 1.1920928955078125e-05s
INFO | --- Analysis for french-timebank took 111.44725394248962s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 4.076957702636719e-05s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 10.599073886871338s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.021086692810058594s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 9.608268737792969e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 1.2874603271484375e-05s
INFO | --- Analysis for fu-berlin-cordis took 112.16767597198486s
Availability | SPARQL endpoint availability check for DailyMed took 9.1552734375e-05s
Availability | VoID file availability check for DailyMed took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for DailyMed took 10.095071792602539s
Reputation | Calculation of the PageRank for DailyMed took 0.022089004516601562s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00010061264038085938s
Believability | Calculation of trust value for DailyMed took 1.3828277587890625e-05s
INFO | --- Analysis for fu-berlin-dailymed took 111.74563980102539s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 9.274482727050781e-05s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 10.096976041793823s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 0.00010967254638671875s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.3828277587890625e-05s
INFO | --- Analysis for fu-berlin-dblp took 111.3651065826416s
Availability | SPARQL endpoint availability check for Diseasome took 4.076957702636719e-05s
Availability | VoID file availability check for Diseasome took 0.00031566619873046875s
Completeness | Calculation of interlinking completeness for Diseasome took 10.097700119018555s
Reputation | Calculation of the PageRank for Diseasome took 0.02119588851928711s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011873245239257812s
Believability | Calculation of trust value for Diseasome took 1.2636184692382812e-05s
INFO | --- Analysis for fu-berlin-diseasome took 111.76700925827026s
Availability | SPARQL endpoint availability check for DrugBank took 4.2438507080078125e-05s
Availability | VoID file availability check for DrugBank took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for DrugBank took 10.100815296173096s
Reputation | Calculation of the PageRank for DrugBank took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011587142944335938s
Believability | Calculation of trust value for DrugBank took 1.4066696166992188e-05s
INFO | --- Analysis for fu-berlin-drugbank took 112.04572296142578s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 8.225440979003906e-05s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 10.595376253128052s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.0208585262298584s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.4809112548828125e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 112.84648704528809s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 9.799003601074219e-05s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0010824203491210938s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 10.093042135238647s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.05718994140625e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 1.2874603271484375e-05s
INFO | --- Analysis for fu-berlin-euraxess took 111.9629373550415s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 8.749961853027344e-05s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 10.10108208656311s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.486343383789062e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 8.58306884765625e-06s
INFO | --- Analysis for fu-berlin-eures took 112.24453020095825s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 4.5299530029296875e-05s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 10.14811372756958s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.34600830078125e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 1.5020370483398438e-05s
INFO | --- Analysis for fu-berlin-eurostat took 111.74786710739136s
Availability | SPARQL endpoint availability check for MediCare took 4.172325134277344e-05s
Availability | VoID file availability check for MediCare took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for MediCare took 10.205613851547241s
Reputation | Calculation of the PageRank for MediCare took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for MediCare took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.76837158203125e-05s
Believability | Calculation of trust value for MediCare took 1.33514404296875e-05s
INFO | --- Analysis for fu-berlin-medicare took 111.5476393699646s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 3.838539123535156e-05s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 10.092550992965698s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 8.082389831542969e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.2636184692382812e-05s
INFO | --- Analysis for fu-berlin-project-gutenberg took 111.53711295127869s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 3.7670135498046875e-05s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 10.104944705963135s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.560585021972656e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.2874603271484375e-05s
INFO | --- Analysis for fu-berlin-sider took 111.96758079528809s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 4.076957702636719e-05s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 10.09581732749939s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.52587890625e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 8.106231689453125e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.2874603271484375e-05s
INFO | --- Analysis for fu-berlin-stitch took 112.7711193561554s
Availability | SPARQL endpoint availability check for fvdb took 8.821487426757812e-05s
Availability | VoID file availability check for fvdb took 0.000579833984375s
Completeness | Calculation of interlinking completeness for fvdb took 10.110986709594727s
Reputation | Calculation of the PageRank for fvdb took 0.02040863037109375s
Interlinking | Calculation of Degree of Connection for fvdb took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.765655517578125e-05s
Believability | Calculation of trust value for fvdb took 1.239776611328125e-05s
INFO | --- Analysis for fv took 112.57208585739136s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.601478576660156e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 10.09830379486084s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.86102294921875e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 7.62939453125e-06s
INFO | --- Analysis for GACS took 111.4711503982544s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 9.512901306152344e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 10.601431131362915s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.02109217643737793s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.0994415283203125e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 8.106231689453125e-06s
INFO | --- Analysis for galen_from_co-odeorg took 111.8660957813263s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.029273986816406e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 10.099090814590454s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.647804260253906e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.3589859008789062e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 111.67344284057617s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 5.3882598876953125e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 10.1013503074646s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02115035057067871s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0009477138519287109s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00011563301086425781s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 7.62939453125e-06s
INFO | --- Analysis for garnicaplywood took 112.47392725944519s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.0531158447265625e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 10.08993124961853s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00011348724365234375s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.2636184692382812e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 111.87318801879883s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 8.654594421386719e-05s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 10.09923505783081s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020812034606933594s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 8.940696716308594e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for gemet took 111.23445224761963s
Availability | SPARQL endpoint availability check for gemet-annotated took 8.368492126464844e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for gemet-annotated took 10.095009565353394s
Reputation | Calculation of the PageRank for gemet-annotated took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.4809112548828125e-05s
Believability | Calculation of trust value for gemet-annotated took 7.867813110351562e-06s
INFO | --- Analysis for gemet-annotated took 113.7358968257904s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 8.630752563476562e-05s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 10.19727349281311s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020177364349365234s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 9.059906005859375e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 113.84001541137695s
Availability | SPARQL endpoint availability check for Super Ontology took 6.365776062011719e-05s
Availability | VoID file availability check for Super Ontology took 0.00038051605224609375s
Completeness | Calculation of interlinking completeness for Super Ontology took 10.406684160232544s
Reputation | Calculation of the PageRank for Super Ontology took 0.02302718162536621s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0008337497711181641s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 5.245208740234375e-05s
Believability | Calculation of trust value for Super Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 115.0215220451355s
Availability | SPARQL endpoint availability check for geo.place took 5.221366882324219e-05s
Availability | VoID file availability check for geo.place took 0.00040078163146972656s
Completeness | Calculation of interlinking completeness for geo.place took 10.214057683944702s
Reputation | Calculation of the PageRank for geo.place took 0.027971982955932617s
Interlinking | Calculation of Degree of Connection for geo.place took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0018038749694824219s
Interlinking | Calculation of Clustering coefficient for geo.place took 8.344650268554688e-05s
Believability | Calculation of trust value for geo.place took 1.1682510375976562e-05s
INFO | --- Analysis for geo_place took 112.40486574172974s
Availability | SPARQL endpoint availability check for Geographic detector model took 0.00013637542724609375s
Availability | VoID file availability check for Geographic detector model took 0.0003628730773925781s
Completeness | Calculation of interlinking completeness for Geographic detector model took 10.58355188369751s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.24249267578125e-05s
Believability | Calculation of trust value for Geographic detector model took 7.3909759521484375e-06s
INFO | --- Analysis for GeoDetector took 113.60863399505615s
Availability | SPARQL endpoint availability check for geodomainwn took 3.981590270996094e-05s
Availability | VoID file availability check for geodomainwn took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for geodomainwn took 10.224772691726685s
Reputation | Calculation of the PageRank for geodomainwn took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for geodomainwn took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for geodomainwn took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.1021575927734375e-05s
Believability | Calculation of trust value for geodomainwn took 1.1444091796875e-05s
INFO | --- Analysis for geodomainwn took 112.3656587600708s
Availability | SPARQL endpoint availability check for GeoEcuador took 6.580352783203125e-05s
Availability | VoID file availability check for GeoEcuador took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for GeoEcuador took 10.108839988708496s
Reputation | Calculation of the PageRank for GeoEcuador took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.05718994140625e-05s
Believability | Calculation of trust value for GeoEcuador took 1.5020370483398438e-05s
INFO | --- Analysis for geoecuador took 112.47259640693665s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.271439790725708s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 10.09181833267212s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.604194641113281e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.1682510375976562e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 107.08968472480774s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 8.368492126464844e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 10.10022258758545s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.022822141647338867s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 2.7179718017578125e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 1.2636184692382812e-05s
INFO | --- Analysis for geographic-openuplabs took 111.34024310112s
Availability | SPARQL endpoint availability check for GeoLinkedData took 8.535385131835938e-05s
Availability | VoID file availability check for GeoLinkedData took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 10.604882955551147s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.416175842285156e-05s
Believability | Calculation of trust value for GeoLinkedData took 1.2874603271484375e-05s
INFO | --- Analysis for geolinkeddata took 111.76798605918884s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 6.389617919921875e-05s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 10.096501111984253s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.034706115722656e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 111.67112565040588s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 0.0001518726348876953s
Availability | VoID file availability check for GeoNames Semantic Web took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 10.095953702926636s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00046181678771972656s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.62939453125e-06s
INFO | --- Analysis for geonames-semantic-web took 112.46605110168457s
Availability | SPARQL endpoint availability check for Geospatial World  took 0.00010991096496582031s
Availability | VoID file availability check for Geospatial World  took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Geospatial World  took 10.09796953201294s
Reputation | Calculation of the PageRank for Geospatial World  took 0.021065473556518555s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010347366333007812s
Believability | Calculation of trust value for Geospatial World  took 1.3589859008789062e-05s
INFO | --- Analysis for geospatialworld-net took 111.76703310012817s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 6.628036499023438e-05s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 10.10489559173584s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00014138221740722656s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.430511474609375e-05s
INFO | --- Analysis for geospecies took 112.84008526802063s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.0531158447265625e-05s
Availability | VoID file availability check for GeoWordNet took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for GeoWordNet took 10.109411001205444s
Reputation | Calculation of the PageRank for GeoWordNet took 0.0223696231842041s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.459785461425781e-05s
Believability | Calculation of trust value for GeoWordNet took 1.33514404296875e-05s
INFO | --- Analysis for geowordnet took 111.9420006275177s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 7.772445678710938e-05s
Availability | VoID file availability check for German labor law thesaurus took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 10.203622579574585s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.021846294403076172s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.487701416015625e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 112.07080459594727s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 8.153915405273438e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 10.60165810585022s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02199864387512207s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.315376281738281e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.3828277587890625e-05s
INFO | --- Analysis for germlex took 112.45002818107605s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.416175842285156e-05s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 10.107113361358643s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.012222290039062e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.3589859008789062e-05s
INFO | --- Analysis for gesis-thesoz took 112.76459956169128s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.850139617919922s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 10.194082021713257s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 0.00011181831359863281s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for getty-aat took 118.17102670669556s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.2778522968292236s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 10.203304767608643s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020654678344726562s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.745887756347656e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.2159347534179688e-05s
INFO | --- Analysis for getty-tgn took 115.01633667945862s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 7.581710815429688e-05s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 10.199037551879883s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.021458148956298828s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 2.8371810913085938e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 7.3909759521484375e-06s
INFO | --- Analysis for gipuzkoademografia took 111.42521500587463s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.792213439941406e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 10.194969415664673s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02081131935119629s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.314018249511719e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.33514404296875e-05s
INFO | --- Analysis for glastonbury-2011 took 111.84485340118408s
Availability | SPARQL endpoint availability check for Global Change Information System took 8.630752563476562e-05s
Availability | VoID file availability check for Global Change Information System took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for Global Change Information System took 10.093651056289673s
Reputation | Calculation of the PageRank for Global Change Information System took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.504753112792969e-05s
Believability | Calculation of trust value for Global Change Information System took 1.3589859008789062e-05s
INFO | --- Analysis for global-change-information-system took 111.33285522460938s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 8.416175842285156e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 10.104726314544678s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.022488117218017578s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.459785461425781e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.2636184692382812e-05s
INFO | --- Analysis for global-hunger-index-2011 took 111.43725633621216s
Availability | SPARQL endpoint availability check for Glottolog took 8.535385131835938e-05s
Availability | VoID file availability check for Glottolog took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Glottolog took 10.094491243362427s
Reputation | Calculation of the PageRank for Glottolog took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Glottolog took 4.744529724121094e-05s
Believability | Calculation of trust value for Glottolog took 1.3589859008789062e-05s
INFO | --- Analysis for glottolog took 111.96585035324097s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 5.14984130859375e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 10.098643779754639s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010085105895996094s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.3589859008789062e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 111.84557890892029s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.601478576660156e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 10.098044395446777s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.956390380859375e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 1.33514404296875e-05s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 111.33652472496033s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.981590270996094e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 10.197336196899414s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.021887779235839844s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 2.8848648071289062e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.2874603271484375e-05s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 111.54560852050781s
Availability | SPARQL endpoint availability check for 1121 took 8.082389831542969e-05s
Availability | VoID file availability check for 1121 took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for 1121 took 10.093923807144165s
Reputation | Calculation of the PageRank for 1121 took 0.020249366760253906s
Interlinking | Calculation of Degree of Connection for 1121 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.4332275390625e-05s
Believability | Calculation of trust value for 1121 took 1.3589859008789062e-05s
INFO | --- Analysis for God_ took 111.73602676391602s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 8.535385131835938e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 10.196075916290283s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.412101745605469e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.1920928955078125e-05s
INFO | --- Analysis for gold took 111.36457395553589s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.2438507080078125e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 10.102401494979858s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.270408630371094e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.1682510375976562e-05s
INFO | --- Analysis for googleart-wrapper took 112.93520784378052s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 4.00543212890625e-05s
Availability | VoID file availability check for GovAgriBus Denmark took 0.00033092498779296875s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 10.10160779953003s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 4.100799560546875e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.2636184692382812e-05s
INFO | --- Analysis for govagribus-denmark took 111.96728277206421s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 8.535385131835938e-05s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 10.098550081253052s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020827531814575195s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.082389831542969e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 1.4066696166992188e-05s
INFO | --- Analysis for government-web-integration-for-linked-data took 111.77209687232971s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 3.981590270996094e-05s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 10.102270603179932s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.021233797073364258s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.463859558105469e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 1.4066696166992188e-05s
INFO | --- Analysis for govtrack took 112.5372576713562s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.00543212890625e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 10.09670877456665s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.023005008697509766s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.079673767089844e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.2874603271484375e-05s
INFO | --- Analysis for greek-administrative-geography took 112.67493796348572s
Availability | SPARQL endpoint availability check for Greek Wordnet took 8.606910705566406e-05s
Availability | VoID file availability check for Greek Wordnet took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 10.091646432876587s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.02188396453857422s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.4345855712890625e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.3113021850585938e-05s
INFO | --- Analysis for greek-wordnet took 112.06689286231995s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 4.124641418457031e-05s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 10.099298000335693s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.023401260375976562s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.8358230590820312e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 9.059906005859375e-06s
INFO | --- Analysis for greek_prisons_releases took 113.13427186012268s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.773733377456665s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 10.098166227340698s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.130073547363281e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.2874603271484375e-05s
INFO | --- Analysis for greekchildrensartmuseum took 112.97946214675903s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.172325134277344e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 10.086893081665039s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02055525779724121s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010585784912109375s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.3113021850585938e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 111.29794573783875s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 8.392333984375e-05s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 10.09984278678894s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.021365642547607422s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.76837158203125e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 8.821487426757812e-06s
INFO | --- Analysis for grrp took 112.04248380661011s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 4.0531158447265625e-05s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 10.597519397735596s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02214217185974121s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.604194641113281e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 1.3113021850585938e-05s
INFO | --- Analysis for grrt took 113.82867217063904s
Availability | SPARQL endpoint availability check for Geological Timescale took 4.172325134277344e-05s
Availability | VoID file availability check for Geological Timescale took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Geological Timescale took 10.098680019378662s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.104873657226562e-05s
Believability | Calculation of trust value for Geological Timescale took 8.106231689453125e-06s
INFO | --- Analysis for GTS took 112.62830638885498s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 10.100488662719727s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02090001106262207s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for GTS-ont took 112.84016227722168s
Availability | SPARQL endpoint availability check for GUTSTOK  took 8.869171142578125e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 10.094799041748047s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.0208737850189209s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.600120544433594e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.2874603271484375e-05s
INFO | --- Analysis for Guillaume_Forget took 112.34683108329773s
Availability | SPARQL endpoint availability check for Project Gutenberg took 8.821487426757812e-05s
Availability | VoID file availability check for Project Gutenberg took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 10.129858493804932s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02071070671081543s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.43865966796875e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.1682510375976562e-05s
INFO | --- Analysis for gutenberg took 113.04630208015442s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 0.00010538101196289062s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 10.098496437072754s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.022624969482421875s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.8623809814453125e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.3113021850585938e-05s
INFO | --- Analysis for gwa-ili took 111.343501329422s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.0531158447265625e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 10.198419332504272s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.021343708038330078s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.933906555175781e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 8.344650268554688e-06s
INFO | --- Analysis for GWR took 112.66972947120667s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.029273986816406e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 10.09961748123169s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.7670135498046875e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.2636184692382812e-05s
INFO | --- Analysis for HASM took 112.76986241340637s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.100799560546875e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 10.090236902236938s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 2.956390380859375e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 1.3113021850585938e-05s
INFO | --- Analysis for hcls-knowledge-base took 111.87493968009949s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for HealthCare Ontology took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 10.600397109985352s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 5.2928924560546875e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.239776611328125e-05s
INFO | --- Analysis for HealthCare_Ontology took 112.05863690376282s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.0531158447265625e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 10.085331916809082s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.022538185119628906s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 8.106231689453125e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 7.867813110351562e-06s
INFO | --- Analysis for heartfailure took 111.77326321601868s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.463279247283936s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 10.098761796951294s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.8623809814453125e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 9.5367431640625e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 163.34394311904907s
Availability | SPARQL endpoint availability check for Hedatuz took 0.35364603996276855s
Availability | VoID file availability check for Hedatuz took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Hedatuz took 10.099214553833008s
Reputation | Calculation of the PageRank for Hedatuz took 0.02191758155822754s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.744529724121094e-05s
Believability | Calculation of trust value for Hedatuz took 1.3113021850585938e-05s
INFO | --- Analysis for hedatuz took 112.93722319602966s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 8.344650268554688e-05s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 10.100069046020508s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00013184547424316406s
Believability | Calculation of trust value for Hellenic Fire Brigade took 8.106231689453125e-06s
INFO | --- Analysis for hellenic-fire-brigade took 111.63865375518799s
Availability | SPARQL endpoint availability check for Hellenic Police took 3.933906555175781e-05s
Availability | VoID file availability check for Hellenic Police took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for Hellenic Police took 10.098185539245605s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012969970703125s
Believability | Calculation of trust value for Hellenic Police took 9.298324584960938e-06s
INFO | --- Analysis for hellenic-police took 111.77418828010559s
Availability | SPARQL endpoint availability check for Hermos took 9.250640869140625e-05s
Availability | VoID file availability check for Hermos took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Hermos took 10.100728750228882s
Reputation | Calculation of the PageRank for Hermos took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.9087066650390625e-05s
Believability | Calculation of trust value for Hermos took 1.33514404296875e-05s
INFO | --- Analysis for Hermos took 111.44800543785095s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 3.981590270996094e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 10.101759195327759s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.0205996036529541s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.765655517578125e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 7.152557373046875e-06s
INFO | --- Analysis for Himanshu_Mahawar took 111.7595374584198s
Availability | SPARQL endpoint availability check for HITO took 8.7738037109375e-05s
Availability | VoID file availability check for HITO took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for HITO took 10.188362121582031s
Reputation | Calculation of the PageRank for HITO took 0.02096390724182129s
Interlinking | Calculation of Degree of Connection for HITO took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for HITO took 7.224082946777344e-05s
Believability | Calculation of trust value for HITO took 1.2636184692382812e-05s
INFO | --- Analysis for hito took 111.5773253440857s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 4.124641418457031e-05s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 10.101600646972656s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.337860107421875e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.33514404296875e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 111.23520398139954s
Availability | SPARQL endpoint availability check for Homologene took 8.487701416015625e-05s
Availability | VoID file availability check for Homologene took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for Homologene took 10.195487022399902s
Reputation | Calculation of the PageRank for Homologene took 0.020392656326293945s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.504753112792969e-05s
Believability | Calculation of trust value for Homologene took 7.62939453125e-06s
INFO | --- Analysis for homologene took 111.97000789642334s
Availability | SPARQL endpoint availability check for gseg took 4.0531158447265625e-05s
Availability | VoID file availability check for gseg took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for gseg took 10.106671810150146s
Reputation | Calculation of the PageRank for gseg took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for gseg took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for gseg took 2.8133392333984375e-05s
Believability | Calculation of trust value for gseg took 1.3113021850585938e-05s
INFO | --- Analysis for hongse took 111.26864123344421s
Availability | SPARQL endpoint availability check for Noticias Universia took 0.00013017654418945312s
Availability | VoID file availability check for Noticias Universia took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Noticias Universia took 10.09636116027832s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020183801651000977s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 2.8371810913085938e-05s
Believability | Calculation of trust value for Noticias Universia took 1.239776611328125e-05s
INFO | --- Analysis for http-data-noticias-universia-net took 111.5780417919159s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 8.535385131835938e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 10.097628831863403s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.02043890953063965s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 2.765655517578125e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 7.152557373046875e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 112.15944457054138s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.8008511066436768s
Availability | VoID file availability check for COURAGE Dataset took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 10.135415077209473s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.62396240234375e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.33514404296875e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 115.71123361587524s
Availability | SPARQL endpoint availability check for RoadTrb took 7.081031799316406e-05s
Availability | VoID file availability check for RoadTrb took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for RoadTrb took 10.10029411315918s
Reputation | Calculation of the PageRank for RoadTrb took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0009753704071044922s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.552436828613281e-05s
Believability | Calculation of trust value for RoadTrb took 1.3113021850585938e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 111.77074432373047s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 10.101075649261475s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.6941299438476562e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.867813110351562e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 111.56840658187866s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.100799560546875e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 10.11393117904663s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.86102294921875e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.239776611328125e-05s
INFO | --- Analysis for http:pakistan.com took 111.26711702346802s
Availability | SPARQL endpoint availability check for CEDICT took 8.487701416015625e-05s
Availability | VoID file availability check for CEDICT took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for CEDICT took 10.097536325454712s
Reputation | Calculation of the PageRank for CEDICT took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.0040740966796875e-05s
Believability | Calculation of trust value for CEDICT took 1.3589859008789062e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 112.2411642074585s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 3.981590270996094e-05s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.002070188522338867s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 10.188305854797363s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.4849853515625e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.3113021850585938e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 112.84714651107788s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 6.890296936035156e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 10.099425554275513s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.4781951904296875e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 111.83242988586426s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 6.151199340820312e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 10.19947361946106s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020661592483520508s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.075599670410156e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.239776611328125e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 112.44216179847717s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.124641418457031e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 10.104858875274658s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.022719383239746094s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.528594970703125e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for http:www.msm.com took 111.17452073097229s
Availability | SPARQL endpoint availability check for Game Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Game Ontology took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Game Ontology took 10.101231813430786s
Reputation | Calculation of the PageRank for Game Ontology took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.695487976074219e-05s
Believability | Calculation of trust value for Game Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 111.24682140350342s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.076957702636719e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 10.103066205978394s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020949125289916992s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2636184692382812e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 111.96686506271362s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.749961853027344e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 10.100923538208008s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02141547203063965s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0011930465698242188s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 5.555152893066406e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.430511474609375e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 112.77421593666077s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.606910705566406e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 10.093073844909668s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8371810913085938e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2874603271484375e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 111.83999729156494s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 6.4849853515625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 10.095678806304932s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020834684371948242s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.86102294921875e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.4066696166992188e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 111.66574788093567s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.0001246929168701172s
Availability | VoID file availability check for Indian Biodiversity took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 10.188331127166748s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.0225522518157959s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.5735626220703125e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 111.93722319602966s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 6.914138793945312e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 10.10024642944336s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.3828277587890625e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 112.2429575920105s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.100799560546875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 10.196855545043945s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9087066650390625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.867813110351562e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 111.44304776191711s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.887580871582031e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 10.099254131317139s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.02223515510559082s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.5762786865234375e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 8.344650268554688e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 113.13969540596008s
Availability | SPARQL endpoint availability check for Bookkeeping took 0.00010967254638671875s
Availability | VoID file availability check for Bookkeeping took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Bookkeeping took 10.099419116973877s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bookkeeping took 1.33514404296875e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 112.53636574745178s
Availability | SPARQL endpoint availability check for Legal Ontology took 8.320808410644531e-05s
Availability | VoID file availability check for Legal Ontology took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Legal Ontology took 10.091217041015625s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020627975463867188s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.62396240234375e-05s
Believability | Calculation of trust value for Legal Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 111.6386022567749s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 10.098168849945068s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020586252212524414s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.797645568847656e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.2636184692382812e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 111.34061098098755s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.482269287109375e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 10.099134683609009s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.02127814292907715s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 2.9802322387695312e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 8.58306884765625e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 112.3669204711914s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 8.7738037109375e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 10.195430278778076s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.022608518600463867s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 2.86102294921875e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 7.62939453125e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 112.44304585456848s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.029273986816406e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 10.098987817764282s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.02182769775390625s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 1.2874603271484375e-05s
INFO | --- Analysis for hud-library-usagedata took 111.86705017089844s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.339582920074463s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 10.198338031768799s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00011086463928222656s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.2874603271484375e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 103.92659211158752s
Availability | SPARQL endpoint availability check for IATE RDF took 3.9577484130859375e-05s
Availability | VoID file availability check for IATE RDF took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for IATE RDF took 10.598767280578613s
Reputation | Calculation of the PageRank for IATE RDF took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.52587890625e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 4.0531158447265625e-05s
Believability | Calculation of trust value for IATE RDF took 1.2636184692382812e-05s
INFO | --- Analysis for iate-rdf took 112.75539636611938s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 7.152557373046875e-05s
Availability | VoID file availability check for IATI as Linked Data took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 10.097245931625366s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0009045600891113281s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 9.632110595703125e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for iati-as-linked-data took 112.37157249450684s
Availability | SPARQL endpoint availability check for ICANE took 4.029273986816406e-05s
Availability | VoID file availability check for ICANE took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for ICANE took 10.100765466690063s
Reputation | Calculation of the PageRank for ICANE took 0.020809173583984375s
Interlinking | Calculation of Degree of Connection for ICANE took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.821487426757812e-05s
Believability | Calculation of trust value for ICANE took 1.3828277587890625e-05s
INFO | --- Analysis for icane took 111.76833295822144s
Availability | SPARQL endpoint availability check for ichoose took 8.58306884765625e-05s
Availability | VoID file availability check for ichoose took 0.0007648468017578125s
Completeness | Calculation of interlinking completeness for ichoose took 10.124008417129517s
Reputation | Calculation of the PageRank for ichoose took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for ichoose took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.176399230957031e-05s
Believability | Calculation of trust value for ichoose took 7.867813110351562e-06s
INFO | --- Analysis for ichoose took 111.86676383018494s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 4.0531158447265625e-05s
Availability | VoID file availability check for The Iconology Dataset took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 10.097341299057007s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.1205673217773438e-05s
Believability | Calculation of trust value for The Iconology Dataset took 1.239776611328125e-05s
INFO | --- Analysis for iconology-dataset took 112.46862936019897s
Availability | SPARQL endpoint availability check for Identifiers.org took 5.245208740234375e-05s
Availability | VoID file availability check for Identifiers.org took 0.001081228256225586s
Completeness | Calculation of interlinking completeness for Identifiers.org took 10.091351509094238s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.8623809814453125e-05s
Believability | Calculation of trust value for Identifiers.org took 1.4066696166992188e-05s
INFO | --- Analysis for identifiers-org took 112.26522159576416s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.1484832763671875e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 10.099039793014526s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.867813110351562e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.33514404296875e-05s
INFO | --- Analysis for idreffr took 112.36736679077148s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.00011396408081054688s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 10.096238374710083s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.602836608886719e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.3113021850585938e-05s
INFO | --- Analysis for ids took 110.51017355918884s
Availability | SPARQL endpoint availability check for ietflang took 8.96453857421875e-05s
Availability | VoID file availability check for ietflang took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for ietflang took 0.25357627868652344s
Reputation | Calculation of the PageRank for ietflang took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for ietflang took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.673004150390625e-05s
Believability | Calculation of trust value for ietflang took 1.1444091796875e-05s
INFO | --- Analysis for ietflang took 2.5139269828796387s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6649436950683594s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.06620478630065918s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.30252861976623535s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.022165298461914062s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for IGVLL took 4.2474775314331055s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 9.882928609848022s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.27974605560302734s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.430511474609375e-05s
INFO | --- Analysis for IHE took 40.983835220336914s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.6840484142303467s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0007081031799316406s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 9.545806169509888s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 8.26665186882019s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 20.05418872833252s
Interoperability | New terms check for Test Site, LOD Lab 317 took 20.38036298751831s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.636204957962036s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.9349918365478516s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.100541114807129s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 1.7220814228057861s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.8249118328094482s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.6715099811553955s
License | MR license check for Test Site, LOD Lab 317 took 1.7602572441101074s
License | HR license check for Test Site, LOD Lab 317 took 2.099430561065674s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.7611544132232666s
Understandability | Number of label check for Test Site, LOD Lab 317 took 2.4224586486816406s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.414905309677124s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.6707980632781982s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.735501766204834s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.6685941219329834s
Performance | Throughput check for Test Site, LOD Lab 317 took 16.53351354598999s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 6.842613220214844e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.7626659870147705s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.662945032119751s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.7162423133850098s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.6869664192199707s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.6978957653045654s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.4004180431365967s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.3330025672912598s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 32.33484244346619s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.6686744689941406s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.6809399127960205s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.7147247791290283s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 3.8822264671325684s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.02973771095275879s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.027436494827270508s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.675098180770874s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 24.860801696777344s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 2.00547456741333s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 4.594445705413818s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.2665164470672607s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 24.872706413269043s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.031020402908325195s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.251479148864746s
Security | Sign check for Test Site, LOD Lab 317 took 1.7028286457061768s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 16.82942032814026s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.3814101219177246s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021847963333129883s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.9073486328125e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.2159347534179688e-05s
INFO | --- Analysis for iislod-test took 544.8360509872437s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.291534423828125e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0003762245178222656s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.25515103340148926s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020133495330810547s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.075599670410156e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 8.106231689453125e-06s
INFO | --- Analysis for ILUSOC took 19.713191509246826s
Availability | SPARQL endpoint availability check for im@sparql took 7.148514986038208s
Availability | VoID file availability check for im@sparql took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for im@sparql took 0.2702004909515381s
Reputation | Calculation of the PageRank for im@sparql took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.337860107421875e-05s
Believability | Calculation of trust value for im@sparql took 1.1205673217773438e-05s
INFO | --- Analysis for im@sparql took 15.15260362625122s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.0531158447265625e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.267545223236084s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.021643877029418945s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.0994415283203125e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.0013580322265625e-05s
INFO | --- Analysis for imagery_bailingniao took 6.392544269561768s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.076798677444458s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0005762577056884766s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 20.214937686920166s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.5116803646087646s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.993269205093384s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.508741855621338s
Versatility | Languages check for Imagesnippets Image Descriptions took 20.229591846466064s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.846577167510986s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.7174520492553711s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7583210468292236s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.6513986587524414s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7100720405578613s
License | MR license check for Imagesnippets Image Descriptions took 0.7069575786590576s
License | HR license check for Imagesnippets Image Descriptions took 30.728420734405518s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.6773810386657715s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.601868152618408s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.3792738914489746s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.6607270240783691s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7230687141418457s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7068362236022949s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.775484800338745s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.2479248046875e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.6767578125s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.6835589408874512s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6946673393249512s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6658484935760498s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6903772354125977s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.397223711013794s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.3919923305511475s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 32.32788419723511s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.6816756725311279s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6799302101135254s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.6827082633972168s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 11.011346817016602s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.2724111080169678s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.257158517837524s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.6978504657745361s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 8.157349824905396s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 5.075169801712036s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.4507684707641602s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.911042213439941s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.8140335083007812s
Security | Sign check for Imagesnippets Image Descriptions took 0.6631143093109131s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 14.696298837661743s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.3694479465484619s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.021152973175048828s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.322166442871094e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 2.1457672119140625e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.049041748046875e-05s
INFO | --- Analysis for imagesnippets took 376.7890737056732s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.16657638549804688s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.7395992279052734s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.678436279296875e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for imf-linked-data took 4.001792907714844s
Availability | SPARQL endpoint availability check for IMGpedia took 3.933906555175781e-05s
Availability | VoID file availability check for IMGpedia took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.25692248344421387s
Reputation | Calculation of the PageRank for IMGpedia took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 2.8848648071289062e-05s
Believability | Calculation of trust value for IMGpedia took 1.3113021850585938e-05s
INFO | --- Analysis for imgpedia took 3.8797566890716553s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 6.508827209472656e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.2551908493041992s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.86102294921875e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 1.049041748046875e-05s
INFO | --- Analysis for import-status-of-gmo-crops took 2.86142635345459s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.315376281738281e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.24294114112854004s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.1920928955078125e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 8.58306884765625e-06s
INFO | --- Analysis for Imtiaz took 2.333552837371826s
Availability | SPARQL endpoint availability check for Royalty Free Music took 8.821487426757812e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2527801990509033s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.9802322387695312e-05s
Believability | Calculation of trust value for Royalty Free Music took 7.867813110351562e-06s
INFO | --- Analysis for inaudio.org took 3.588958501815796s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 6.246566772460938e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2566192150115967s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.170967102050781e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 1.2159347534179688e-05s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.93684458732605s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 8.153915405273438e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.2751948833465576s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.0517578125e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 1.33514404296875e-05s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.934004068374634s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.513901948928833s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.2656383514404297s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02051401138305664s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 4.646296501159668s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.1484832763671875e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.037381887435913086s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2502100467681885s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.147125244140625e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.2636184692382812e-05s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.792236804962158s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 8.559226989746094e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.27558016777038574s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010323524475097656s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.239776611328125e-05s
INFO | --- Analysis for ineverycrea took 31.66309118270874s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.487701416015625e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2518332004547119s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.916854858398438e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.1682510375976562e-05s
INFO | --- Analysis for ineverycrea-argentina took 10.942547798156738s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 272.32671761512756s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007817745208740234s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.25350332260131836s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.022111177444458008s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.128715515136719e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for influence-tracker-dataset took 567.8854851722717s
Availability | SPARQL endpoint availability check for INSEMTIVES took 8.535385131835938e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.2525763511657715s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 2.956390380859375e-05s
Believability | Calculation of trust value for INSEMTIVES took 1.1920928955078125e-05s
INFO | --- Analysis for insemtives took 5.007917881011963s
Availability | SPARQL endpoint availability check for instagram.person took 8.320808410644531e-05s
Availability | VoID file availability check for instagram.person took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for instagram.person took 0.2806556224822998s
Reputation | Calculation of the PageRank for instagram.person took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.0279159545898438e-05s
Believability | Calculation of trust value for instagram.person took 1.3589859008789062e-05s
INFO | --- Analysis for instagram_person took 4.635448217391968s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.029273986816406e-05s
Availability | VoID file availability check for instagram.videoobject took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.6897692680358887s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.023505449295043945s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 2.7894973754882812e-05s
Believability | Calculation of trust value for instagram.videoobject took 1.2636184692382812e-05s
INFO | --- Analysis for instagram_videoobject took 3.340541124343872s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2698338031768799s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.022244691848754883s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 2.765655517578125e-05s
Believability | Calculation of trust value for Instance Hub Countries took 1.1920928955078125e-05s
INFO | --- Analysis for instance-hub-countries took 3.390899181365967s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 9.131431579589844e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2551448345184326s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0009088516235351562s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.218650817871094e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.1682510375976562e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 2.692188262939453s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.0531158447265625e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.26734328269958496s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 2.7418136596679688e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 1.1682510375976562e-05s
INFO | --- Analysis for instance-hub-organizations took 2.921820640563965s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.0531158447265625e-05s
Availability | VoID file availability check for Instance Hub People took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.24954915046691895s
Reputation | Calculation of the PageRank for Instance Hub People took 0.021145343780517578s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub People took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-people took 2.895171642303467s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 8.368492126464844e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.26087427139282227s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.02127528190612793s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 2.7418136596679688e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 7.295608520507812e-05s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.9639158248901367s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.00543212890625e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.25408506393432617s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 2.8133392333984375e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 1.239776611328125e-05s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.8822808265686035s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 3.981590270996094e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2777881622314453s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.02193903923034668s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 2.765655517578125e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 2.0265579223632812e-05s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.9395933151245117s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 8.20159912109375e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.28069210052490234s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.022075653076171875s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.075599670410156e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 1.0967254638671875e-05s
INFO | --- Analysis for instance-hub-us-crops took 2.8921360969543457s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.4345855712890625e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.23548436164855957s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.02145528793334961s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.1948089599609375e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 1.1682510375976562e-05s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.915830135345459s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 8.416175842285156e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.26711297035217285s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.023304462432861328s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 1.2874603271484375e-05s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.941495180130005s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.24829339981079102s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 2.956390380859375e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 1.1920928955078125e-05s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.988384246826172s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.076957702636719e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.2512941360473633s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020848751068115234s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 2.956390380859375e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.1444091796875e-05s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.8911497592926025s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.00543212890625e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.2618985176086426s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020338773727416992s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.489059448242188e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.1682510375976562e-05s
INFO | --- Analysis for interactivemaps-gnoss took 9.188789367675781s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.029273986816406e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2516183853149414s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.022847890853881836s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 2.8848648071289062e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 1.2159347534179688e-05s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 3.0342838764190674s
Availability | SPARQL endpoint availability check for intervalue took 0.28311586380004883s
Availability | VoID file availability check for intervalue took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for intervalue took 0.24797749519348145s
Reputation | Calculation of the PageRank for intervalue took 0.020989418029785156s
Interlinking | Calculation of Degree of Connection for intervalue took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.556510925292969e-05s
Believability | Calculation of trust value for intervalue took 1.2159347534179688e-05s
INFO | --- Analysis for intervalue took 2.7070000171661377s
Availability | SPARQL endpoint availability check for Inztrow took 5.269050598144531e-05s
Availability | VoID file availability check for Inztrow took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for Inztrow took 0.26572179794311523s
Reputation | Calculation of the PageRank for Inztrow took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for Inztrow took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Inztrow took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.9087066650390625e-05s
Believability | Calculation of trust value for Inztrow took 1.1444091796875e-05s
INFO | --- Analysis for Inztrow took 3.324881076812744s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2548635005950928s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.02093815803527832s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 8.106231689453125e-06s
INFO | --- Analysis for ipbes took 3.7068824768066406s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.4345855712890625e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2628133296966553s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02106165885925293s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.38690185546875e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 8.106231689453125e-06s
INFO | --- Analysis for iptc-newscodes took 3.4575698375701904s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.315376281738281e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.25035810470581055s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.0040740966796875e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.239776611328125e-05s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.9229378700256348s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.664632558822632s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.001180410385131836s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.24367856979370117s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.72747802734375e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.3589859008789062e-05s
INFO | --- Analysis for iserve took 9.440699338912964s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.96047282218933s
Availability | VoID file availability check for ISIC V4 took 0.0007946491241455078s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.3773229122161865s
Reputation | Calculation of the PageRank for ISIC V4 took 0.021263599395751953s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.528594970703125e-05s
Believability | Calculation of trust value for ISIC V4 took 8.821487426757812e-06s
INFO | --- Analysis for isic-v4 took 114.9975917339325s
Availability | SPARQL endpoint availability check for Isidore took 8.177757263183594e-05s
Availability | VoID file availability check for Isidore took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Isidore took 0.30425524711608887s
Reputation | Calculation of the PageRank for Isidore took 0.021091938018798828s
Interlinking | Calculation of Degree of Connection for Isidore took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Isidore took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Isidore took 3.147125244140625e-05s
Believability | Calculation of trust value for Isidore took 3.4332275390625e-05s
INFO | --- Analysis for isidore took 2.9426698684692383s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.220008850097656e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2714977264404297s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.104873657226562e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 4.76837158203125e-06s
INFO | --- Analysis for isil-dbpedia took 4.292689800262451s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.26665496826171875s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.02080082893371582s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 7.3909759521484375e-06s
INFO | --- Analysis for iso-3166-2-data took 3.3658857345581055s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.267692565917969e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.2402043342590332s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.02104806900024414s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.600120544433594e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 7.3909759521484375e-06s
INFO | --- Analysis for iso-639-oasis took 3.0681889057159424s
Availability | SPARQL endpoint availability check for ISOcat took 4.982948303222656e-05s
Availability | VoID file availability check for ISOcat took 0.0003764629364013672s
Completeness | Calculation of interlinking completeness for ISOcat took 0.2461848258972168s
Reputation | Calculation of the PageRank for ISOcat took 0.021008014678955078s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for ISOcat took 7.05718994140625e-05s
Believability | Calculation of trust value for ISOcat took 7.152557373046875e-06s
INFO | --- Analysis for isocat took 33.190845251083374s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.172325134277344e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.00033783912658691406s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.24437308311462402s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020755290985107422s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.361701965332031e-05s
Believability | Calculation of trust value for ISOcat-metadata took 7.867813110351562e-06s
INFO | --- Analysis for isocat-metadata took 4.748053312301636s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.1484832763671875e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.2782297134399414s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.020581960678100586s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 2.7179718017578125e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.947211265563965s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08716464042663574s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0005881786346435547s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.236231327056885s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2639181613922119s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11586236953735352s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.979518175125122s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.5989899635315s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.054830312728881836s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.03274035453796387s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08212995529174805s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07245397567749023s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.06344151496887207s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1181344985961914s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.48428893089294s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.054894447326660156s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1447784900665283s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20765256881713867s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08597946166992188s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0915684700012207s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05167794227600098s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.374264240264893s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.104873657226562e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08833003044128418s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14868640899658203s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.33374547958374023s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.34006619453430176s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10332107543945312s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13947057723999023s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05421280860900879s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.467671632766724s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.055289268493652344s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05559182167053223s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05562901496887207s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.669301986694336s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.30516982078552246s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2634866237640381s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05591440200805664s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.533684968948364s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8658952713012695s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.668959617614746s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2695860862731934s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.750662565231323s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2867913246154785s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.06838560104370117s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0803992748260498s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 15.081261396408081s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8472716808319092s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.02102494239807129s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010180473327636719s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.4781951904296875e-05s
INFO | --- Analysis for ispra-lod-place took 460.63939666748047s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.172325134277344e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.24274492263793945s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 2.956390380859375e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.3589859008789062e-05s
INFO | --- Analysis for ispra-lod-rmn took 4.1440441608428955s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.05206441879272461s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.00052642822265625s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.208057403564453s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.2577519416809082s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.1291654109954834s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.967388391494751s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 91.62831974029541s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.06262993812561035s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.03188371658325195s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.0828239917755127s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.0688314437866211s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.06038379669189453s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.11342096328735352s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.4985191822052s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.08183026313781738s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.2603275775909424s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.21205639839172363s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.0900273323059082s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.12705206871032715s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.05318617820739746s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.28651475906372s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.033348083496094e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.09714746475219727s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.15361833572387695s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.3647429943084717s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.34354472160339355s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.09203195571899414s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.13919448852539062s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.06885838508605957s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 13.663622856140137s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.05532240867614746s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.0574193000793457s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.05414843559265137s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.6782562732696533s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.30721020698547363s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.2629992961883545s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.05509305000305176s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.538280010223389s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.8550198078155518s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.768359661102295s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.3039815425872803s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.862576484680176s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2829599380493164s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.05422258377075195s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.0836782455444336s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 11.648908615112305s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.3776063919067383s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021390199661254883s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.0531158447265625e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 4.76837158203125e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.0728836059570312e-05s
INFO | --- Analysis for ispra-lod-ron took 454.19907879829407s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 3.9577484130859375e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.26798248291015625s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.02104806900024414s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.0517578125e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 6.67572021484375e-06s
INFO | --- Analysis for ispra-lod-sc took 3.859564781188965s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6992542743682861s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0074520111083984375s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2642958164215088s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.179115295410156e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.239776611328125e-05s
INFO | --- Analysis for issa-agritrop took 5.983154058456421s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.2438507080078125e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2704341411590576s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02102065086364746s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.9087066650390625e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.239776611328125e-05s
INFO | --- Analysis for ISSN:0080-3626 took 2.3514373302459717s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.172325134277344e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.6942739486694336s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.8371810913085938e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 5.936622619628906e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 3.6691107749938965s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.315376281738281e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.25742459297180176s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.023153305053710938s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0008356571197509766s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.314018249511719e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.239776611328125e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 2.6641838550567627s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 0.33279967308044434s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.268341064453125s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.440017700195312e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 9.5367431640625e-06s
INFO | --- Analysis for istat-immigration took 2.9527649879455566s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.100799560546875e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.28099560737609863s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020754575729370117s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.0517578125e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 1.2874603271484375e-05s
INFO | --- Analysis for istat-immigrazione took 2.8926327228546143s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.1985340118408203s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.7053074836730957s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.023105382919311523s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.0994415283203125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 9.298324584960938e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.3343052864074707s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 0.19198250770568848s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.28772950172424316s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.152557373046875e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.239776611328125e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 2.7013492584228516s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.2438507080078125e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.26894116401672363s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.021126747131347656s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.0040740966796875e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 1.33514404296875e-05s
INFO | --- Analysis for iucr-acta-cryst-e took 3.0138068199157715s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 5.316734313964844e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.014323711395263672s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.26106977462768555s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.266334533691406e-05s
Believability | Calculation of trust value for IWMI Research Reports took 1.2636184692382812e-05s
INFO | --- Analysis for iwmi-research-reports took 2.9163942337036133s
Availability | SPARQL endpoint availability check for IWN took 4.220008850097656e-05s
Availability | VoID file availability check for IWN took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for IWN took 0.2717900276184082s
Reputation | Calculation of the PageRank for IWN took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for IWN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for IWN took 3.6716461181640625e-05s
Believability | Calculation of trust value for IWN took 8.821487426757812e-06s
INFO | --- Analysis for iwn took 5.863949298858643s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.172325134277344e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.2780942916870117s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 4.744529724121094e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 1.3113021850585938e-05s
INFO | --- Analysis for j-global-knowledge took 2.9386227130889893s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 8.7738037109375e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.24689817428588867s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 2.956390380859375e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 1.2159347534179688e-05s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.9470958709716797s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.600108861923218s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.009752750396728516s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2920095920562744s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.02097940444946289s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.556510925292969e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.3589859008789062e-05s
INFO | --- Analysis for jamendo-dbtune took 13.334487915039062s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 0.00011014938354492188s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2538149356842041s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.8160552978515625e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for japan-radioactivity-stat took 5.095987319946289s
Availability | SPARQL endpoint availability check for JEL Classification took 4.1961669921875e-05s
Availability | VoID file availability check for JEL Classification took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2699282169342041s
Reputation | Calculation of the PageRank for JEL Classification took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.2901763916015625e-05s
Believability | Calculation of trust value for JEL Classification took 1.3113021850585938e-05s
INFO | --- Analysis for jel-classification took 4.867733001708984s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.0592539310455322s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.28458690643310547s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.147125244140625e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.2874603271484375e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 8.102558135986328s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.3324656486511s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.26502203941345215s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.021481037139892578s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.0108642578125e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.1920928955078125e-05s
INFO | --- Analysis for jita took 540.2122492790222s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 8.130073547363281e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.6704483032226562s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.022440195083618164s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 2.8848648071289062e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 1.3113021850585938e-05s
INFO | --- Analysis for jmdict took 4.703730583190918s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.072723150253296s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.27886271476745605s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.440017700195312e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.2636184692382812e-05s
INFO | --- Analysis for john-goodwins-family-tree took 42.488508462905884s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 8.869171142578125e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.7006826400756836s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.981590270996094e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 6.4373016357421875e-06s
INFO | --- Analysis for jp-cos took 5.529285669326782s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.172325134277344e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.25264406204223633s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.695487976074219e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.1682510375976562e-05s
INFO | --- Analysis for jp-textbook took 4.308420419692993s
Availability | SPARQL endpoint availability check for JRC-Names took 8.153915405273438e-05s
Availability | VoID file availability check for JRC-Names took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.2704920768737793s
Reputation | Calculation of the PageRank for JRC-Names took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for JRC-Names took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.24249267578125e-05s
Believability | Calculation of trust value for JRC-Names took 9.775161743164062e-06s
INFO | --- Analysis for jrc-names-ec took 4.548537731170654s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.875941276550293s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.23593521118164062s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.413459777832031e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.2874603271484375e-05s
INFO | --- Analysis for jrc-names-mlode took 3.7586708068847656s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.172325134277344e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2783229351043701s
Reputation | Calculation of the PageRank for JudaicaLink took 0.024518728256225586s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.52587890625e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0015337467193603516s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00019931793212890625s
Believability | Calculation of trust value for JudaicaLink took 1.1205673217773438e-05s
INFO | --- Analysis for judaicalink took 22.465593099594116s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.315376281738281e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.25000786781311035s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 2.765655517578125e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 1.1920928955078125e-05s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.902238607406616s
Availability | SPARQL endpoint availability check for KAKEN took 4.100799560546875e-05s
Availability | VoID file availability check for KAKEN took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for KAKEN took 0.26058244705200195s
Reputation | Calculation of the PageRank for KAKEN took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for KAKEN took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for KAKEN took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for KAKEN took 2.7179718017578125e-05s
Believability | Calculation of trust value for KAKEN took 1.239776611328125e-05s
INFO | --- Analysis for kaken took 2.85359525680542s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.0585477352142334s
Availability | VoID file availability check for Kallikratis municipalities took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.25406956672668457s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.021965503692626953s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 8.654594421386719e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 9.298324584960938e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.5224976539611816s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.100799560546875e-05s
Availability | VoID file availability check for Openflights Routes took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.27588534355163574s
Reputation | Calculation of the PageRank for Openflights Routes took 0.021628379821777344s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0010738372802734375s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.814697265625e-05s
Believability | Calculation of trust value for Openflights Routes took 8.58306884765625e-06s
INFO | --- Analysis for kasabi-openflights-routes took 2.9075186252593994s
Availability | SPARQL endpoint availability check for EU Soccer League took 5.0067901611328125e-05s
Availability | VoID file availability check for EU Soccer League took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2644686698913574s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 2.9802322387695312e-05s
Believability | Calculation of trust value for EU Soccer League took 1.1205673217773438e-05s
INFO | --- Analysis for KG:Course_Submission took 4.183030366897583s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 6.079673767089844e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.257338285446167s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.1920928955078125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.2874603271484375e-05s
INFO | --- Analysis for KING took 2.564735174179077s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.100799560546875e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2962918281555176s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.151199340820312e-05s
Believability | Calculation of trust value for Klappstuhlclub took 9.059906005859375e-06s
INFO | --- Analysis for klappstuhlclub took 12.465220928192139s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.720179796218872s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.25102901458740234s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.02234482765197754s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.580352783203125e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.0967254638671875e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.192697525024414s
Availability | SPARQL endpoint availability check for Knowledge Forest took 8.273124694824219e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.27156805992126465s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02265310287475586s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.7418136596679688e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.0967254638671875e-05s
INFO | --- Analysis for knowledge-map took 2.8750686645507812s
Availability | SPARQL endpoint availability check for Knowledge Forest took 8.797645568847656e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2712841033935547s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.765655517578125e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.0728836059570312e-05s
INFO | --- Analysis for KnowledgeFusion took 2.3148796558380127s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 8.535385131835938e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.26841163635253906s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.246566772460938e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.1205673217773438e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.070698976516724s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 8.344650268554688e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.27541065216064453s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 2.6941299438476562e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 1.2874603271484375e-05s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.9621028900146484s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.4345855712890625e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.2523813247680664s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.7894973754882812e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.5497207641601562e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.4111952781677246s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.315376281738281e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.266737699508667s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.021097898483276367s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.0994415283203125e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 1.33514404296875e-05s
INFO | --- Analysis for ktr took 3.0949697494506836s
Availability | SPARQL endpoint availability check for Informatics Studies took 5.53131103515625e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2781684398651123s
Reputation | Calculation of the PageRank for Informatics Studies took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 6.246566772460938e-05s
Believability | Calculation of trust value for Informatics Studies took 1.4066696166992188e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.956374406814575s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.06898188591003418s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.24093317985534668s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.719329833984375e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 1.3828277587890625e-05s
INFO | --- Analysis for kupkb took 48.01127862930298s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 6.747245788574219e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.29230165481567383s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.504753112792969e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 1.2636184692382812e-05s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.9283156394958496s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 8.953842401504517s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.25498366355895996s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02055811882019043s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.510185241699219e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.239776611328125e-05s
INFO | --- Analysis for l3s-dblp took 43.27326679229736s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 22.57767677307129s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.2432384490966797s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 7.081031799316406e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for lak-dataset took 65.58254790306091s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.15584564208984375s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005490779876708984s
Extra | Recovery of all triples for  Language Name Authority List  took 219.10494351387024s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6150307655334473s
Amount of data | Number of triples check for  Language Name Authority List  took 106.15443515777588s
Interoperability | New terms check for  Language Name Authority List  took 72.79856419563293s
Versatility | Languages check for  Language Name Authority List  took 300.1410279273987s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 72.43716168403625s
Security | Check HTTPS for  Language Name Authority List  took 0.4108099937438965s
Interpretability | RDF structures check for  Language Name Authority List  took 0.45586585998535156s
Versatility | Serialization formats check for  Language Name Authority List  took 3.2206151485443115s
Availability | RDF dump link check for  Language Name Authority List  took 0.3748316764831543s
License | MR license check for  Language Name Authority List  took 0.3690304756164551s
License | HR license check for  Language Name Authority List  took 300.101420879364s
Amount of data | Number of property check for  Language Name Authority List  took 0.15285992622375488s
Understandability | Number of label check for  Language Name Authority List  took 1.8341343402862549s
Understandability | URI regex check for  Language Name Authority List  took 0.3979008197784424s
Understandability | Vocabs check for  Language Name Authority List  took 0.1160280704498291s
Verifiability | Authors check for  Language Name Authority List  took 0.35341978073120117s
Verifiability | Publishers check for  Language Name Authority List  took 0.1925044059753418s
Performance | Throughput check for  Language Name Authority List  took 10.639829874038696s
Amount of data | Check the number of entities for  Language Name Authority List  took 7.748603820800781e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.1948859691619873s
Interlinking | sameAs chians check for  Language Name Authority List  took 6.665398120880127s
Interlinking | skos check for  Language Name Authority List  took 0.3400249481201172s
Interlinking | skos check for  Language Name Authority List  took 0.3156447410583496s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.3850836753845215s
Currency | Creation date check for  Language Name Authority List  took 0.4357137680053711s
Currency | Modification date check for  Language Name Authority List  took 0.14058947563171387s
Rep.Conc. | URIs length for  Language Name Authority List  took 427.56848216056824s
Interoperability | New vocabularies check for  Language Name Authority List  took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.16569089889526367s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.28554749488830566s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.18487858772277832s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 40.4406533241272s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.0631487369537354s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.6286232471466064s
Consistency | Disjoint class check for  Language Name Authority List  took 0.16899657249450684s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.4308524131775s
Consistency | Misplaced classes for  Language Name Authority List  took 8.434032201766968s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 39.78290820121765s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.6615049839019775s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.5487325191498s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 2.9669108390808105s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.44303202629089355s
Security | Sign check for  Language Name Authority List  took 0.2554035186767578s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 19.389479875564575s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.6706817150115967s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021173954010009766s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 5.745887756347656e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 0.000141143798828125s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.6689300537109375e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.239776611328125e-05s
INFO | --- Analysis for language-authority-list took 15714.919822454453s
Availability | SPARQL endpoint availability check for Lark took 385.02169942855835s
Availability | VoID file availability check for Lark took 0.0008435249328613281s
Completeness | Calculation of interlinking completeness for Lark took 1.3347866535186768s
Reputation | Calculation of the PageRank for Lark took 0.022132158279418945s
Interlinking | Calculation of Degree of Connection for Lark took 6.461143493652344e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Lark took 8.034706115722656e-05s
Believability | Calculation of trust value for Lark took 1.2874603271484375e-05s
INFO | --- Analysis for LARK took 1682.1606857776642s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.672731876373291s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.2703359127044678s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for LASLA took 5.482766628265381s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.124641418457031e-05s
Availability | VoID file availability check for LATC Linksets took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.2501986026763916s
Reputation | Calculation of the PageRank for LATC Linksets took 0.020996809005737305s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.123283386230469e-05s
Believability | Calculation of trust value for LATC Linksets took 1.239776611328125e-05s
INFO | --- Analysis for latc-linksets took 3.6710431575775146s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.540635347366333s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.2550830841064453s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 4.988469839096069s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.5167346000671387s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.2730283737182617s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.023075103759765625s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for LatinAffectus took 4.357253789901733s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.5516245365142822s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.2568085193634033s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.021913766860961914s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.100799560546875e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for LatinWordnetLiLa took 5.131070137023926s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.00543212890625e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.2753753662109375s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.647804260253906e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 1.1444091796875e-05s
INFO | --- Analysis for lcc took 3.429652214050293s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 8.749961853027344e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.34833788871765137s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011777877807617188s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.239776611328125e-05s
INFO | --- Analysis for lcsh took 6.400810718536377s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 8.630752563476562e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2766730785369873s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.021129608154296875s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.0108642578125e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.0967254638671875e-05s
INFO | --- Analysis for lcsubjects took 2.6106083393096924s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.220008850097656e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.24762654304504395s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.022108793258666992s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 2.9087066650390625e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 1.33514404296875e-05s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.850263833999634s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.350810050964355s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.24821758270263672s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.021221160888671875s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.6253204345703125e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.239776611328125e-05s
INFO | --- Analysis for ldt@library took 34.43860340118408s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 8.511543273925781e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.25454258918762207s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 2.8848648071289062e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 1.1682510375976562e-05s
INFO | --- Analysis for learned-genre-ontology-eng took 2.9104104042053223s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.100799560546875e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.27574801445007324s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.022113323211669922s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.8848648071289062e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 1.2636184692382812e-05s
INFO | --- Analysis for learned-genre-ontology-intl took 2.903083562850952s
Availability | SPARQL endpoint availability check for U ime Legije took 5.340576171875e-05s
Availability | VoID file availability check for U ime Legije took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.27633213996887207s
Reputation | Calculation of the PageRank for U ime Legije took 0.020583152770996094s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 2.8848648071289062e-05s
Believability | Calculation of trust value for U ime Legije took 1.1682510375976562e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 2.898630142211914s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 5.8650970458984375e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.24538326263427734s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 2.956390380859375e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 1.2159347534179688e-05s
INFO | --- Analysis for legislation-openuplabs took 2.8857972621917725s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.5353810787200928s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.2590460777282715s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02077627182006836s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.128715515136719e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.1920928955078125e-05s
INFO | --- Analysis for LemmaBank took 4.685872554779053s
Availability | SPARQL endpoint availability check for lemonUby took 4.267692565917969e-05s
Availability | VoID file availability check for lemonUby took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for lemonUby took 0.24953484535217285s
Reputation | Calculation of the PageRank for lemonUby took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for lemonUby took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for lemonUby took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.031990051269531e-05s
Believability | Calculation of trust value for lemonUby took 1.3113021850585938e-05s
INFO | --- Analysis for lemonuby took 3.1561574935913086s
Availability | SPARQL endpoint availability check for LemonWiktionary took 9.369850158691406e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.2672295570373535s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.528594970703125e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.0967254638671875e-05s
INFO | --- Analysis for lemonwiktionary took 4.463462829589844s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.5118987560272217s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.25136399269104004s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.022484779357910156s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for LewisShort took 3.87135648727417s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.4686193466186523s
Availability | VoID file availability check for LEXIN-RDF took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.26633620262145996s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.021245718002319336s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.314018249511719e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.33514404296875e-05s
INFO | --- Analysis for lexin-rdf took 5.936803102493286s
Availability | SPARQL endpoint availability check for lexinfo took 8.392333984375e-05s
Availability | VoID file availability check for lexinfo took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for lexinfo took 0.26186418533325195s
Reputation | Calculation of the PageRank for lexinfo took 0.020975589752197266s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.7738037109375e-05s
Believability | Calculation of trust value for lexinfo took 1.2636184692382812e-05s
INFO | --- Analysis for lexinfo took 2.7305641174316406s
Availability | SPARQL endpoint availability check for Lexvo took 8.630752563476562e-05s
Availability | VoID file availability check for Lexvo took 0.0011849403381347656s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2651686668395996s
Reputation | Calculation of the PageRank for Lexvo took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.0001761913299560547s
Believability | Calculation of trust value for Lexvo took 1.0728836059570312e-05s
INFO | --- Analysis for lexvo took 2.8659727573394775s
Availability | SPARQL endpoint availability check for Lexvo.org took 8.702278137207031e-05s
Availability | VoID file availability check for Lexvo.org took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.2461378574371338s
Reputation | Calculation of the PageRank for Lexvo.org took 0.022349119186401367s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 6.985664367675781e-05s
Believability | Calculation of trust value for Lexvo.org took 1.0728836059570312e-05s
INFO | --- Analysis for lexvo-org took 2.4279329776763916s
Availability | SPARQL endpoint availability check for LIBRIS took 0.4149453639984131s
Availability | VoID file availability check for LIBRIS took 0.0005545616149902344s
Extra | Recovery of all triples for LIBRIS took 6.514486789703369s
Performance | Total latancy measurement for LIBRIS took 0.7191965579986572s
Amount of data | Number of triples check for LIBRIS took 19.07138705253601s
Interoperability | New terms check for LIBRIS took 15.606987714767456s
Versatility | Languages check for LIBRIS took 0.16324472427368164s
Interpretability | Number of blank nodes check for LIBRIS took 300.0902931690216s
Security | Check HTTPS for LIBRIS took 0.3523697853088379s
Interpretability | RDF structures check for LIBRIS took 0.25699853897094727s
Versatility | Serialization formats check for LIBRIS took 0.21856427192687988s
Availability | RDF dump link check for LIBRIS took 0.14029693603515625s
License | MR license check for LIBRIS took 0.2367715835571289s
License | HR license check for LIBRIS took 0.23990654945373535s
Amount of data | Number of property check for LIBRIS took 0.16142845153808594s
Understandability | Number of label check for LIBRIS took 0.4426915645599365s
Understandability | URI regex check for LIBRIS took 0.31321120262145996s
Understandability | Vocabs check for LIBRIS took 0.12937688827514648s
Verifiability | Authors check for LIBRIS took 0.16871166229248047s
Verifiability | Publishers check for LIBRIS took 0.16271066665649414s
Performance | Throughput check for LIBRIS took 10.868184804916382s
Amount of data | Check the number of entities for LIBRIS took 0.00011587142944335938s
Verifiability | Contribs. check for LIBRIS took 0.14798641204833984s
Interlinking | sameAs chians check for LIBRIS took 0.15772461891174316s
Interlinking | skos check for LIBRIS took 0.263960599899292s
Interlinking | skos check for LIBRIS took 0.12938785552978516s
Timeliness | dataset update frequency check for LIBRIS took 0.26412463188171387s
Currency | Creation date check for LIBRIS took 0.3056638240814209s
Currency | Modification date check for LIBRIS took 0.6119794845581055s
Rep.Conc. | URIs length for LIBRIS took 84.64201784133911s
Interoperability | New vocabularies check for LIBRIS took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.15691733360290527s
Accuracy | Check Functional Property for LIBRIS took 0.1546938419342041s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.16045022010803223s
Accuracy | Check Datatype consistency for LIBRIS took 0.26859474182128906s
Consistency | Disjoint class check for LIBRIS took 0.16233563423156738s
Consistency | Check Misplaced properties for LIBRIS took 61.21175765991211s
Consistency | Misplaced classes for LIBRIS took 1.059842824935913s
Consistency | Check Ontology hijacking for LIBRIS took 3.761798143386841s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.2812116146087646s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 62.271655559539795s
Conciseness | Check Extensional conciseness for LIBRIS took 0.27709507942199707s
Conciseness | Check Intensional conciseness for LIBRIS took 0.40126562118530273s
Security | Sign check for LIBRIS took 0.22121071815490723s
Availability | Check URIs Dereferenciability for LIBRIS took 15.55872631072998s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.2068471908569336s
Reputation | Calculation of the PageRank for LIBRIS took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 8.940696716308594e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.1920928955078125e-06s
Believability | Calculation of trust value for LIBRIS took 1.1205673217773438e-05s
INFO | --- Analysis for libris took 1069.7396380901337s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06675100326538086s
Availability | VoID file availability check for Public Library of Veroia took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.7032074928283691s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.343292236328125e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.33514404296875e-05s
INFO | --- Analysis for libver took 4.912505626678467s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.16374731063842773s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.25130248069763184s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02185201644897461s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 9.870529174804688e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 9.298324584960938e-06s
INFO | --- Analysis for lichfield-spending took 3.605668067932129s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.220008850097656e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.26111578941345215s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02272486686706543s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.170967102050781e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.239776611328125e-05s
INFO | --- Analysis for lime took 7.362826824188232s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.124641418457031e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.48069000244140625s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.264176607131958s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.022361278533935547s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010347366333007812s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.1444091796875e-05s
INFO | --- Analysis for lingvoj took 6.0939741134643555s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 7.43865966796875e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.26505494117736816s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020661354064941406s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.581710815429688e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.2159347534179688e-05s
INFO | --- Analysis for linked-crunchbase took 15.694154500961304s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.2676146030426025s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.717369556427002s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.818771362304688e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1444091796875e-05s
INFO | --- Analysis for linked-drugs took 19.851078987121582s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.685955286026001s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02023935317993164s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.00010061264038085938s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 8.344650268554688e-06s
INFO | --- Analysis for linked-edgar took 4.4965980052948s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 9.012222290039062e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.2733194828033447s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02024221420288086s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.1552734375e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.239776611328125e-05s
INFO | --- Analysis for linked-eurostat took 4.572793960571289s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.3392181396484375e-05s
Availability | VoID file availability check for linked hypernyms took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2651057243347168s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020750761032104492s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for linked hypernyms took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.128715515136719e-05s
Believability | Calculation of trust value for linked hypernyms took 1.239776611328125e-05s
INFO | --- Analysis for linked-hypernyms took 3.3703677654266357s
Availability | SPARQL endpoint availability check for Linked Life Data took 239.04100561141968s
Availability | VoID file availability check for Linked Life Data took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Linked Life Data took 1.0342166423797607s
Reputation | Calculation of the PageRank for Linked Life Data took 0.021407127380371094s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 0.00010943412780761719s
Believability | Calculation of trust value for Linked Life Data took 1.1444091796875e-05s
INFO | --- Analysis for linked-life-data took 724.5546238422394s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.24831795692443848s
Availability | VoID file availability check for Linked Logainm took 0.00048732757568359375s
Extra | Recovery of all triples for Linked Logainm took 1.5270507335662842s
Performance | Total latancy measurement for Linked Logainm took 0.7130126953125s
Amount of data | Number of triples check for Linked Logainm took 0.14691638946533203s
Interoperability | New terms check for Linked Logainm took 1.4220001697540283s
Versatility | Languages check for Linked Logainm took 1.4580936431884766s
Interpretability | Number of blank nodes check for Linked Logainm took 0.11827731132507324s
Security | Check HTTPS for Linked Logainm took 0.3076753616333008s
Interpretability | RDF structures check for Linked Logainm took 0.23436903953552246s
Versatility | Serialization formats check for Linked Logainm took 0.13095927238464355s
Availability | RDF dump link check for Linked Logainm took 0.12111496925354004s
License | MR license check for Linked Logainm took 0.13700151443481445s
License | HR license check for Linked Logainm took 0.12786245346069336s
Amount of data | Number of property check for Linked Logainm took 0.12352347373962402s
Understandability | Number of label check for Linked Logainm took 0.18525362014770508s
Understandability | URI regex check for Linked Logainm took 0.24631571769714355s
Understandability | Vocabs check for Linked Logainm took 0.11914730072021484s
Verifiability | Authors check for Linked Logainm took 0.12182092666625977s
Verifiability | Publishers check for Linked Logainm took 0.11914467811584473s
Performance | Throughput check for Linked Logainm took 10.54210877418518s
Amount of data | Check the number of entities for Linked Logainm took 8.392333984375e-05s
Verifiability | Contribs. check for Linked Logainm took 0.12349700927734375s
Interlinking | sameAs chians check for Linked Logainm took 0.1233663558959961s
Interlinking | skos check for Linked Logainm took 0.13389849662780762s
Interlinking | skos check for Linked Logainm took 0.11803984642028809s
Timeliness | dataset update frequency check for Linked Logainm took 0.12896084785461426s
Currency | Creation date check for Linked Logainm took 0.24222826957702637s
Currency | Modification date check for Linked Logainm took 0.24109435081481934s
Rep.Conc. | URIs length for Linked Logainm took 0.897705078125s
Interoperability | New vocabularies check for Linked Logainm took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.11741948127746582s
Accuracy | Check Functional Property for Linked Logainm took 0.20366764068603516s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.2021162509918213s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.5339436531066895s
Accuracy | Check White space in annotation for Linked Logainm took 0.02427840232849121s
Accuracy | Check Datatype consistency for Linked Logainm took 0.027188539505004883s
Consistency | Disjoint class check for Linked Logainm took 0.20352506637573242s
Consistency | Check Misplaced properties for Linked Logainm took 0.3406684398651123s
Consistency | Misplaced classes for Linked Logainm took 0.26069092750549316s
Consistency | Check Ontology hijacking for Linked Logainm took 1.8305249214172363s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.312969446182251s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.4970972537994385s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.031055927276611328s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.181685209274292s
Security | Sign check for Linked Logainm took 0.15271854400634766s
Availability | Check URIs Dereferenciability for Linked Logainm took 944.1206579208374s
Completeness | Calculation of interlinking completeness for Linked Logainm took 1.3436684608459473s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020922422409057617s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.392333984375e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Logainm took 1.33514404296875e-05s
INFO | --- Analysis for linked-logainm took 1006.2699193954468s
Availability | SPARQL endpoint availability check for Linked NUTS took 8.606910705566406e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.7225430011749268s
Reputation | Calculation of the PageRank for Linked NUTS took 0.021015167236328125s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.435943603515625e-05s
Believability | Calculation of trust value for Linked NUTS took 9.059906005859375e-06s
INFO | --- Analysis for linked-nuts took 3.9211559295654297s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.9591064453125e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.27260494232177734s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020949602127075195s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 3.075599670410156e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 1.3828277587890625e-05s
INFO | --- Analysis for linked-open-aalto-data-service took 3.6086947917938232s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 0.38173937797546387s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.2713053226470947s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.600120544433594e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 1.0251998901367188e-05s
INFO | --- Analysis for linked-open-camera took 3.4669809341430664s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 5.2872314453125s
Availability | VoID file availability check for Linked Open Commerce took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2881796360015869s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.2636184692382812e-05s
INFO | --- Analysis for linked-open-commerce took 16.18503165245056s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.22932767868042s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.29184746742248535s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.021429777145385742s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010228157043457031s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.239776611328125e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 4.3667893409729s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.00038552284240722656s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2768688201904297s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.021623611450195312s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.749961853027344e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.2159347534179688e-05s
INFO | --- Analysis for linked-open-numbers took 2.966510772705078s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 5.936622619628906e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2749190330505371s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.647804260253906e-05s
Believability | Calculation of trust value for Linked Open Piracy took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-piracy took 7.7491209506988525s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 8.273124694824219e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.2879924774169922s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.021967649459838867s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 1.1682510375976562e-05s
INFO | --- Analysis for linked-open-senate took 3.084261178970337s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 7.358640432357788s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0007188320159912109s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 81.9913592338562s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 4.524778366088867s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 2.0298912525177s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 3.2250242233276367s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 13.915080547332764s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 1.9298067092895508s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 1.408796787261963s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 1.365041732788086s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 2.6962766647338867s
License | MR license check for Linked Open Vocabularies (LOV) took 0.25174999237060547s
License | HR license check for Linked Open Vocabularies (LOV) took 44.38528895378113s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 1.1221733093261719s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 1.805410385131836s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 2.9221184253692627s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 2.0292484760284424s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 1.368276596069336s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 1.8478994369506836s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 14.795209407806396s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.032275915145874s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 1.1291160583496094s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 2.173413038253784s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 1.9124221801757812s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.9572455883026123s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 1.793656349182129s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 4.522412538528442s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 1.0296440124511719s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 25.489679098129272s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 17.234714031219482s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 0.25932836532592773s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.37062692642211914s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.20500802993774414s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 5.810100555419922s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6862857341766357s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.73956823348999s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.23461484909057617s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 6.311387300491333s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 0.3594985008239746s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 5.836517333984375s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.3857381343841553s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.8144257068634033s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 1.925572395324707s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.21016812324523926s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 6419.733504295349s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 1.154524803161621s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.021592378616333008s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 0.00011086463928222656s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 14.193799018859863s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.239776611328125e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 7554.508387088776s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.6587848663330078s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020992755889892578s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.528594970703125e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.4836273193359375e-06s
INFO | --- Analysis for linked-periodicals took 4.225481748580933s
Availability | SPARQL endpoint availability check for Linked Index took 4.3392181396484375e-05s
Availability | VoID file availability check for Linked Index took 0.014755010604858398s
Completeness | Calculation of interlinking completeness for Linked Index took 0.26180291175842285s
Reputation | Calculation of the PageRank for Linked Index took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Linked Index took 7.748603820800781e-05s
Believability | Calculation of trust value for Linked Index took 1.239776611328125e-05s
INFO | --- Analysis for linked-stockindex took 2.878373622894287s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 6.022203683853149s
Availability | VoID file availability check for Linked Structured Product Labels took 0.07308411598205566s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2624971866607666s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.02120804786682129s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.552436828613281e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.239776611328125e-05s
INFO | --- Analysis for linked-structured-product-labels took 19.5470552444458s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 16.067543506622314s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2627077102661133s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.3113021850585938e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 19.845646142959595s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.261611461639404s
Availability | VoID file availability check for Linked TCGA took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.26715707778930664s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02136707305908203s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.274482727050781e-05s
Believability | Calculation of trust value for Linked TCGA took 1.239776611328125e-05s
INFO | --- Analysis for linked-tcga took 63.10281419754028s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.09844684600830078s
Availability | VoID file availability check for Linked User Feedback took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.24857282638549805s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02258467674255371s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.838539123535156e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.0728836059570312e-05s
INFO | --- Analysis for linked-user-feedback took 2.9331045150756836s
Availability | SPARQL endpoint availability check for USPTO Patent data took 0.00013208389282226562s
Availability | VoID file availability check for USPTO Patent data took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2452685832977295s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 9.655952453613281e-05s
Believability | Calculation of trust value for USPTO Patent data took 1.1444091796875e-05s
INFO | --- Analysis for linked-uspto-patent-data took 53.36887836456299s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 8.249282836914062e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.24582147598266602s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 1.0967254638671875e-05s
INFO | --- Analysis for linked-web-apis took 2.8708434104919434s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 8.296966552734375e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.24852299690246582s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.02168726921081543s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.0279159545898438e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 1.1682510375976562e-05s
INFO | --- Analysis for linkedarc took 2.7853128910064697s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.0783531665802002s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2640998363494873s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.361701965332031e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.1205673217773438e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 2.7597062587738037s
Availability | SPARQL endpoint availability check for LinkedCT took 1.47575044631958s
Availability | VoID file availability check for LinkedCT took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.24847197532653809s
Reputation | Calculation of the PageRank for LinkedCT took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.608268737792969e-05s
Believability | Calculation of trust value for LinkedCT took 1.2874603271484375e-05s
INFO | --- Analysis for linkedct took 5.318734407424927s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.13466215133666992s
Availability | VoID file availability check for LinkedGeoData took 0.00045871734619140625s
Extra | Recovery of all triples for LinkedGeoData took 7.3900146484375s
Performance | Total latancy measurement for LinkedGeoData took 0.6405644416809082s
Amount of data | Number of triples check for LinkedGeoData took 46.858102798461914s
Interoperability | New terms check for LinkedGeoData took 91.49484419822693s
Versatility | Languages check for LinkedGeoData took 181.38444113731384s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.2877964973449707s
Security | Check HTTPS for LinkedGeoData took 0.32709765434265137s
Interpretability | RDF structures check for LinkedGeoData took 0.13238763809204102s
Versatility | Serialization formats check for LinkedGeoData took 0.14013218879699707s
Availability | RDF dump link check for LinkedGeoData took 0.13027071952819824s
License | MR license check for LinkedGeoData took 0.13120412826538086s
License | HR license check for LinkedGeoData took 113.17388224601746s
Amount of data | Number of property check for LinkedGeoData took 0.133378267288208s
Understandability | Number of label check for LinkedGeoData took 1.023806095123291s
Understandability | URI regex check for LinkedGeoData took 0.2568521499633789s
Understandability | Vocabs check for LinkedGeoData took 0.1414794921875s
Verifiability | Authors check for LinkedGeoData took 0.13191652297973633s
Verifiability | Publishers check for LinkedGeoData took 0.12436151504516602s
Performance | Throughput check for LinkedGeoData took 10.541370153427124s
Amount of data | Check the number of entities for LinkedGeoData took 0.06780147552490234s
Verifiability | Contribs. check for LinkedGeoData took 0.13972878456115723s
Interlinking | sameAs chians check for LinkedGeoData took 0.1733851432800293s
Interlinking | skos check for LinkedGeoData took 0.1318833827972412s
Interlinking | skos check for LinkedGeoData took 0.13159823417663574s
Timeliness | dataset update frequency check for LinkedGeoData took 0.1402444839477539s
Currency | Creation date check for LinkedGeoData took 0.25759243965148926s
Currency | Modification date check for LinkedGeoData took 0.25615954399108887s
Rep.Conc. | URIs length for LinkedGeoData took 271.1617102622986s
Interoperability | New vocabularies check for LinkedGeoData took 53.681729555130005s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.1334521770477295s
Accuracy | Check Functional Property for LinkedGeoData took 0.13997387886047363s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.13888812065124512s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.8797712326049805s
Accuracy | Check White space in annotation for LinkedGeoData took 0.1556694507598877s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13967108726501465s
Consistency | Disjoint class check for LinkedGeoData took 0.13455438613891602s
Consistency | Check Misplaced properties for LinkedGeoData took 180.72514033317566s
Consistency | Misplaced classes for LinkedGeoData took 0.6127443313598633s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.6768906116485596s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.3299098014831543s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.8766152858734s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.1475849151611328s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.35329270362854004s
Security | Sign check for LinkedGeoData took 0.12593770027160645s
Availability | Check URIs Dereferenciability for LinkedGeoData took 18.099438428878784s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.8911070823669434s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.02106928825378418s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.52587890625e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.0001239776611328125s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 43.238916873931885s
Believability | Calculation of trust value for LinkedGeoData took 1.9073486328125e-05s
INFO | --- Analysis for linkedgeodata took 2270.275226831436s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.220008850097656e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.26125144958496094s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.021788835525512695s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.7670135498046875e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 1.33514404296875e-05s
INFO | --- Analysis for linkedgeodata-aerodromes took 5.460299015045166s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.0578858852386475s
Availability | VoID file availability check for LinkedLCCN took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.25003528594970703s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010418891906738281s
Believability | Calculation of trust value for LinkedLCCN took 1.33514404296875e-05s
INFO | --- Analysis for linkedlccn took 23.38339877128601s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.291534423828125e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.709986686706543s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.02270817756652832s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.2901763916015625e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.2636184692382812e-05s
INFO | --- Analysis for linkedmarkmail took 3.3974814414978027s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.59570932388306s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.7186510562896729s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00012946128845214844s
Believability | Calculation of trust value for Linked Movie DataBase took 1.2636184692382812e-05s
INFO | --- Analysis for linkedmdb took 133.8613817691803s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.4703202247619629s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.7286210060119629s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.02108144760131836s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.581710815429688e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for linkedspending took 5.4521644115448s
Availability | SPARQL endpoint availability check for LinkedStats took 8.96453857421875e-05s
Availability | VoID file availability check for LinkedStats took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2508399486541748s
Reputation | Calculation of the PageRank for LinkedStats took 0.021368741989135742s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 2.8133392333984375e-05s
Believability | Calculation of trust value for LinkedStats took 1.239776611328125e-05s
INFO | --- Analysis for linkedstats took 2.855182647705078s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.9591064453125e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.2654232978820801s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 2.8133392333984375e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 7.009506225585938e-05s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.8927340507507324s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 8.654594421386719e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.27726101875305176s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 1.1920928955078125e-05s
INFO | --- Analysis for linking-open-drug-data took 2.8602752685546875s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.08060193061828613s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.2552919387817383s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00012135505676269531s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.1444091796875e-05s
INFO | --- Analysis for linklion took 2.4493844509124756s
Availability | SPARQL endpoint availability check for Lion's Den took 4.1484832763671875e-05s
Availability | VoID file availability check for Lion's Den took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.2583136558532715s
Reputation | Calculation of the PageRank for Lion's Den took 0.02031874656677246s
Interlinking | Calculation of Degree of Connection for Lion's Den took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lion's Den took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 2.5987625122070312e-05s
Believability | Calculation of trust value for Lion's Den took 7.152557373046875e-06s
INFO | --- Analysis for lionsden took 2.8182713985443115s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 30.199482679367065s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2481083869934082s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.269050598144531e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 35.55626916885376s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.076957702636719e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.44220948219299316s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 1.2874603271484375e-05s
INFO | --- Analysis for livtdm took 3.0728695392608643s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 0.00010991096496582031s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.29701662063598633s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.8133392333984375e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 1.3828277587890625e-05s
INFO | --- Analysis for livtdm2017 took 2.929471731185913s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.029273986816406e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.23933863639831543s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.021132946014404297s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 2.8133392333984375e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 1.3828277587890625e-05s
INFO | --- Analysis for lobi took 2.7837836742401123s
Availability | SPARQL endpoint availability check for lobid-organisations took 0.9524705410003662s
Availability | VoID file availability check for lobid-organisations took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.2756950855255127s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.417533874511719e-05s
Believability | Calculation of trust value for lobid-organisations took 1.3589859008789062e-05s
INFO | --- Analysis for lobid-organisations took 5.142054557800293s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.812868595123291s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.25377964973449707s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.846687316894531e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.3113021850585938e-05s
INFO | --- Analysis for lobid-resources took 7.295053720474243s
Availability | SPARQL endpoint availability check for Linked Open Colors took 6.842613220214844e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.26312756538391113s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.022075653076171875s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.3589859008789062e-05s
INFO | --- Analysis for loc took 7.797024488449097s
Availability | SPARQL endpoint availability check for Location Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Location Ontology took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.26360177993774414s
Reputation | Calculation of the PageRank for Location Ontology took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Location Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Location Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for Location_Ontology took 4.603637933731079s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.076957702636719e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.35660815238952637s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 2.6702880859375e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.2159347534179688e-05s
INFO | --- Analysis for locv took 43.05212378501892s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7288954257965088s
Availability | VoID file availability check for LOD-a-lot took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2535886764526367s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.023315906524658203s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.528594970703125e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.239776611328125e-05s
INFO | --- Analysis for lod-a-lot took 13.819602966308594s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.100799560546875e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.24875307083129883s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 1.0967254638671875e-05s
INFO | --- Analysis for lod-it_scuole-italiane took 2.8388912677764893s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.172325134277344e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.2611517906188965s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 2.8133392333984375e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.049041748046875e-05s
INFO | --- Analysis for lod-taiwan took 2.8210060596466064s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 5.054473876953125e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2511715888977051s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.177757263183594e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.1682510375976562e-05s
INFO | --- Analysis for lod2-project-wiki took 3.418008804321289s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.9836676120758057s
Availability | VoID file availability check for LODAC BDLS took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2593998908996582s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.02109527587890625s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 8.20159912109375e-05s
Believability | Calculation of trust value for LODAC BDLS took 1.1920928955078125e-05s
INFO | --- Analysis for lodac-bdls took 13.817538022994995s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.9114227294921875e-05s
Availability | VoID file availability check for LODRussia Math took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2425246238708496s
Reputation | Calculation of the PageRank for LODRussia Math took 0.02213573455810547s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.956390380859375e-05s
Believability | Calculation of trust value for LODRussia Math took 1.1205673217773438e-05s
INFO | --- Analysis for lodrussia-math took 2.7686779499053955s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.00543212890625e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00021719932556152344s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.25934624671936035s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 2.5987625122070312e-05s
Believability | Calculation of trust value for LODRussia Nano took 1.239776611328125e-05s
INFO | --- Analysis for lodrussia-nano took 2.8408007621765137s
Availability | SPARQL endpoint availability check for LODStats took 4.00543212890625e-05s
Availability | VoID file availability check for LODStats took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for LODStats took 0.25595617294311523s
Reputation | Calculation of the PageRank for LODStats took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for LODStats took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LODStats took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for LODStats took 2.8371810913085938e-05s
Believability | Calculation of trust value for LODStats took 7.867813110351562e-06s
INFO | --- Analysis for lodstats took 2.802032232284546s
Availability | SPARQL endpoint availability check for LODUM took 4.00543212890625e-05s
Availability | VoID file availability check for LODUM took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for LODUM took 0.2525482177734375s
Reputation | Calculation of the PageRank for LODUM took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for LODUM took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LODUM took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for LODUM took 2.8133392333984375e-05s
Believability | Calculation of trust value for LODUM took 7.3909759521484375e-06s
INFO | --- Analysis for lodum took 2.7903754711151123s
Availability | SPARQL endpoint availability check for lofd took 0.12963318824768066s
Availability | VoID file availability check for lofd took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for lofd took 0.27669215202331543s
Reputation | Calculation of the PageRank for lofd took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for lofd took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lofd took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for lofd took 2.9087066650390625e-05s
Believability | Calculation of trust value for lofd took 7.152557373046875e-06s
INFO | --- Analysis for lofd took 2.4297189712524414s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.88892006874084s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0010366439819335938s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2782258987426758s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.021678447723388672s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.698204040527344e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 1.0013580322265625e-05s
INFO | --- Analysis for loius took 586.0183000564575s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 9.584426879882812e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.7136712074279785s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.021037578582763672s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 2.8848648071289062e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 1.2159347534179688e-05s
INFO | --- Analysis for loius-linking-italian-university-statistics took 4.74755334854126s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 3.16559100151062s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.2516329288482666s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0009334087371826172s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.555152893066406e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 1.0013580322265625e-05s
INFO | --- Analysis for london-gazette took 7.327851295471191s
Availability | SPARQL endpoint availability check for Weather Stations took 8.630752563476562e-05s
Availability | VoID file availability check for Weather Stations took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.27539539337158203s
Reputation | Calculation of the PageRank for Weather Stations took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0009486675262451172s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 9.489059448242188e-05s
Believability | Calculation of trust value for Weather Stations took 1.239776611328125e-05s
INFO | --- Analysis for los_metar took 9.292205095291138s
Availability | SPARQL endpoint availability check for Lotico took 1.1678040027618408s
Availability | VoID file availability check for Lotico took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Lotico took 0.2624046802520752s
Reputation | Calculation of the PageRank for Lotico took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for Lotico took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Lotico took 7.700920104980469e-05s
Believability | Calculation of trust value for Lotico took 1.2874603271484375e-05s
INFO | --- Analysis for lotico took 6.942608118057251s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.3942391872406006s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0005986690521240234s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.0418434143066406s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.9585709571838379s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.23785114288330078s
Interoperability | New terms check for Lower Layer Super Output Areas took 2.2473526000976562s
Versatility | Languages check for Lower Layer Super Output Areas took 0.48723268508911133s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.188015937805176s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.10785460472106934s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.2841372489929199s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.20599055290222168s
Availability | RDF dump link check for Lower Layer Super Output Areas took 48.30837082862854s
License | MR license check for Lower Layer Super Output Areas took 0.24883031845092773s
License | HR license check for Lower Layer Super Output Areas took 30.23566961288452s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.1774141788482666s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.32743263244628906s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.41666078567504883s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.13438796997070312s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.15715527534484863s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.4021148681640625s
Performance | Throughput check for Lower Layer Super Output Areas took 11.406487226486206s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 6.842613220214844e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.19753003120422363s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.3114745616912842s
Interlinking | skos check for Lower Layer Super Output Areas took 0.30667614936828613s
Interlinking | skos check for Lower Layer Super Output Areas took 0.20228362083435059s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.12190794944763184s
Currency | Creation date check for Lower Layer Super Output Areas took 0.8643310070037842s
Currency | Modification date check for Lower Layer Super Output Areas took 0.21686410903930664s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.452594518661499s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.1563396453857422s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.21727204322814941s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.21283650398254395s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.3436698913574219s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.7908382415771484s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.097146987915039s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.633307695388794s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.0001392364501953125s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.3699381351470947s
Security | Sign check for Lower Layer Super Output Areas took 0.14062070846557617s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.7932033538818359s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.409385681152344e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 1.6689300537109375e-06s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.049041748046875e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 270.5247595310211s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4741535186767578s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007638931274414062s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 120.98242020606995s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.988762617111206s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.049230337142944s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.124807596206665s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.19958662986755s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.0093817710876465s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2734096050262451s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.721705436706543s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.24608373641967773s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6538360118865967s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2237374782562s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23401904106140137s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6643545627593994s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9297165870666504s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4142603874206543s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19684553146362305s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23143792152404785s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.302700996398926s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.200241088867188e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19779586791992188s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19611525535583496s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.47322750091552734s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4890773296356201s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.663994312286377s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.48541784286499023s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2498760223388672s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 147.66507482528687s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21022462844848633s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.37590575218200684s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3546631336212158s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 43.59824728965759s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.636139154434204s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6211330890655518s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19693493843078613s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.45098614692688s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.240626573562622s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 30.589496612548828s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3275387287139893s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 88.19831681251526s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6999940872192383s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5084710121154785s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.7230308055877686s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 17.419840812683105s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9345660209655762s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.021105527877807617s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for LPIS_(Poland) took 2302.1888194084167s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19270968437194824s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0005183219909667969s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 130.99105405807495s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9888641834259033s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.184373617172241s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.298094034194946s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2557752132416s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.999612808227539s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.29061269760131836s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.505405187606812s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3189074993133545s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.7089929580688477s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2226550579071s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2217714786529541s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.4620466232299805s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8467311859130859s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.47240352630615234s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18383383750915527s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.24725818634033203s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.197938442230225s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.271766662597656e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1986074447631836s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21411967277526855s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.46283578872680664s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4880857467651367s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.485726594924927s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4415144920349121s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.23598289489746094s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 162.62793636322021s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21110963821411133s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3839242458343506s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.37406492233276367s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 37.24664926528931s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.643303632736206s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6371521949768066s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20518040657043457s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 87.31081104278564s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.193848609924316s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 34.50699520111084s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3862254619598389s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 88.11105108261108s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7683534622192383s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5593068599700928s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.7675509452819824s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.21575140953064s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.6098155975341797s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.021027088165283203s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.3855438232421875e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3589859008789062e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2308.734619140625s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.57763671875e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.2568087577819824s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.022240400314331055s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 2.7418136596679688e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.430511474609375e-05s
INFO | --- Analysis for lremap-auth took 4.302502155303955s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 8.654594421386719e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.6778931617736816s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 2.765655517578125e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.3113021850585938e-05s
INFO | --- Analysis for lremap-conf took 3.41762638092041s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.220008850097656e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.6866116523742676s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020328521728515625s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.8133392333984375e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.1444091796875e-05s
INFO | --- Analysis for lremap-ri took 3.8815436363220215s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.410743713378906e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.25037360191345215s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 2.7418136596679688e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.0251998901367188e-05s
INFO | --- Analysis for lremap-sub took 2.6361241340637207s
Availability | SPARQL endpoint availability check for LSQ took 4.291534423828125e-05s
Availability | VoID file availability check for LSQ took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for LSQ took 0.25293779373168945s
Reputation | Calculation of the PageRank for LSQ took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for LSQ took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.7418136596679688e-05s
Believability | Calculation of trust value for LSQ took 1.2636184692382812e-05s
INFO | --- Analysis for lsq took 3.533787250518799s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6274828910827637s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.2612931728363037s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.022504568099975586s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for LucaniPharsalia took 4.67823600769043s
Availability | SPARQL endpoint availability check for Linked rules took 0.00010991096496582031s
Availability | VoID file availability check for Linked rules took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Linked rules took 0.25204920768737793s
Reputation | Calculation of the PageRank for Linked rules took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Linked rules took 2.6941299438476562e-05s
Believability | Calculation of trust value for Linked rules took 1.2636184692382812e-05s
INFO | --- Analysis for Luminaires_senlis took 2.311513662338257s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.887580871582031e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.25255608558654785s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 2.6941299438476562e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 1.1920928955078125e-05s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 3.234391927719116s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.184788465499878s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.26404833793640137s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.021093130111694336s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 2.765655517578125e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.2159347534179688e-05s
INFO | --- Analysis for makg took 63.39669871330261s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.029273986816406e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0003943443298339844s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.2545008659362793s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.0517578125e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 5.7220458984375e-06s
INFO | --- Analysis for manchester-university-reading-lists took 5.255889654159546s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.458427429199219e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2432396411895752s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.765655517578125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 6.198883056640625e-06s
INFO | --- Analysis for manish took 2.20060396194458s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 3.910064697265625e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.2651023864746094s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.6941299438476562e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 6.4373016357421875e-06s
INFO | --- Analysis for mapa-referencia-bogota took 3.688023090362549s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 7.009506225585938e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.000213623046875s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.24124884605407715s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 2.7179718017578125e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 6.198883056640625e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.7140052318573s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.076957702636719e-05s
Availability | VoID file availability check for MARC Codes List took 0.0003113746643066406s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.27823376655578613s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00011920928955078125s
Believability | Calculation of trust value for MARC Codes List took 5.4836273193359375e-06s
INFO | --- Analysis for marc-codes took 12.604264974594116s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0003635883331298828s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.687260627746582s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.023291587829589844s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.719329833984375e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for masc took 6.273749351501465s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 7.367134094238281e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2484140396118164s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.504753112792969e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.4781951904296875e-05s
INFO | --- Analysis for masc-bn-nif took 2.3014893531799316s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.621023416519165s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.26871156692504883s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.6464462280273438e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 1.1444091796875e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 4.094279050827026s
Availability | SPARQL endpoint availability check for medline took 4.172325134277344e-05s
Availability | VoID file availability check for medline took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for medline took 0.29564881324768066s
Reputation | Calculation of the PageRank for medline took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for medline took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for medline took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for medline took 3.314018249511719e-05s
Believability | Calculation of trust value for medline took 4.3392181396484375e-05s
INFO | --- Analysis for medline took 6.954509735107422s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.7521436214447021s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.25163984298706055s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02242279052734375s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.747245788574219e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.3828277587890625e-05s
INFO | --- Analysis for meducator took 13.186721324920654s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.1484832763671875e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2864649295806885s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.021443605422973633s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.9087066650390625e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 1.2159347534179688e-05s
INFO | --- Analysis for mesh-finnish took 2.9580836296081543s
Availability | SPARQL endpoint availability check for MeSH headings took 5.4836273193359375e-05s
Availability | VoID file availability check for MeSH headings took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.26558446884155273s
Reputation | Calculation of the PageRank for MeSH headings took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for MeSH headings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MeSH headings took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.86102294921875e-05s
Believability | Calculation of trust value for MeSH headings took 1.1920928955078125e-05s
INFO | --- Analysis for mesh_headings took 2.8508613109588623s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.00543212890625e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2598593235015869s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.02141404151916504s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.0279159545898438e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 1.2636184692382812e-05s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.7869744300842285s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.1484832763671875e-05s
Availability | VoID file availability check for MeSH pairs took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2532773017883301s
Reputation | Calculation of the PageRank for MeSH pairs took 0.02099299430847168s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.9087066650390625e-05s
Believability | Calculation of trust value for MeSH pairs took 7.62939453125e-06s
INFO | --- Analysis for mesh_pairs took 2.852368116378784s
Availability | SPARQL endpoint availability check for MeSH titles took 4.029273986816406e-05s
Availability | VoID file availability check for MeSH titles took 0.0029451847076416016s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.24664950370788574s
Reputation | Calculation of the PageRank for MeSH titles took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 2.9087066650390625e-05s
Believability | Calculation of trust value for MeSH titles took 1.3113021850585938e-05s
INFO | --- Analysis for mesh_titles took 2.859055519104004s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 9.679794311523438e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.26152849197387695s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.02328348159790039s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.0517578125e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 1.2636184692382812e-05s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.872934579849243s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.172325134277344e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.26333117485046387s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.0279159545898438e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.2636184692382812e-05s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.8411567211151123s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 9.202957153320312e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.27659010887145996s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.021587371826171875s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.985664367675781e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.2159347534179688e-05s
INFO | --- Analysis for metashare took 2.473820924758911s
Availability | SPARQL endpoint availability check for MExiCo took 9.298324584960938e-05s
Availability | VoID file availability check for MExiCo took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for MExiCo took 0.24222135543823242s
Reputation | Calculation of the PageRank for MExiCo took 0.022289276123046875s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.601478576660156e-05s
Believability | Calculation of trust value for MExiCo took 1.1444091796875e-05s
INFO | --- Analysis for mexico took 22.47506070137024s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.2973613739013672s
Availability | VoID file availability check for Coronavirus dataset took 0.0004942417144775391s
Extra | Recovery of all triples for Coronavirus dataset took 6.028852939605713s
Performance | Total latancy measurement for Coronavirus dataset took 2.4599480628967285s
Amount of data | Number of triples check for Coronavirus dataset took 1.1970741748809814s
Interoperability | New terms check for Coronavirus dataset took 2.5716323852539062s
Versatility | Languages check for Coronavirus dataset took 60.503172397613525s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.394376516342163s
Interpretability | RDF structures check for Coronavirus dataset took 0.5011589527130127s
Versatility | Serialization formats check for Coronavirus dataset took 0.5269284248352051s
Availability | RDF dump link check for Coronavirus dataset took 0.49358034133911133s
License | MR license check for Coronavirus dataset took 0.5328891277313232s
License | HR license check for Coronavirus dataset took 42.61059808731079s
Amount of data | Number of property check for Coronavirus dataset took 0.514446496963501s
Understandability | Number of label check for Coronavirus dataset took 1.352525234222412s
Understandability | URI regex check for Coronavirus dataset took 1.0017492771148682s
Understandability | Vocabs check for Coronavirus dataset took 0.49051856994628906s
Verifiability | Authors check for Coronavirus dataset took 0.5551321506500244s
Verifiability | Publishers check for Coronavirus dataset took 0.5052468776702881s
Performance | Throughput check for Coronavirus dataset took 14.722989559173584s
Amount of data | Check the number of entities for Coronavirus dataset took 7.343292236328125e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.496673583984375s
Interlinking | sameAs chians check for Coronavirus dataset took 0.4909505844116211s
Interlinking | skos check for Coronavirus dataset took 0.5187046527862549s
Interlinking | skos check for Coronavirus dataset took 0.5000741481781006s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.512049674987793s
Currency | Creation date check for Coronavirus dataset took 0.9990885257720947s
Currency | Modification date check for Coronavirus dataset took 0.9979047775268555s
Rep.Conc. | URIs length for Coronavirus dataset took 8.240181684494019s
Interoperability | New vocabularies check for Coronavirus dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5117232799530029s
Accuracy | Check Functional Property for Coronavirus dataset took 0.684722900390625s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.7212436199188232s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.118840217590332s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.02274298667907715s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.02758312225341797s
Consistency | Disjoint class check for Coronavirus dataset took 1.1170880794525146s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.502442836761475s
Consistency | Misplaced classes for Coronavirus dataset took 0.5980141162872314s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.3670666217803955s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.2630739212036133s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.771709203720093s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03583407402038574s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.49164891242980957s
Security | Sign check for Coronavirus dataset took 0.5272364616394043s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 2975.401669740677s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.8035895824432373s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021499156951904297s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 6.67572021484375e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.2159347534179688e-05s
INFO | --- Analysis for micro-coronavirus took 3214.4211797714233s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.6253204345703125e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00040411949157714844s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.8003983497619629s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02012038230895996s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0008924007415771484s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0001049041748046875s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 9.249399185180664s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 6.389617919921875e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0003485679626464844s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.25211191177368164s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011181831359863281s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for mismuseos-gnoss took 6.241730451583862s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.08533430099487305s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.6706619262695312s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.076957702636719e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.3909759521484375e-06s
INFO | --- Analysis for mlsa took 3.2122628688812256s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.220008850097656e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2710287570953369s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020661115646362305s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 2.7894973754882812e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 7.62939453125e-06s
INFO | --- Analysis for model took 35.2949333190918s
Availability | SPARQL endpoint availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 4.1484832763671875e-05s
Availability | VoID file availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.2676115036010742s
Reputation | Calculation of the PageRank for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 2.6702880859375e-05s
Believability | Calculation of trust value for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.3828277587890625e-05s
INFO | --- Analysis for model1 took 21.136319398880005s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.792213439941406e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.26135778427124023s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.6941299438476562e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 1.3589859008789062e-05s
INFO | --- Analysis for mond took 2.8718554973602295s
Availability | SPARQL endpoint availability check for MONDIS took 4.029273986816406e-05s
Availability | VoID file availability check for MONDIS took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for MONDIS took 0.2605557441711426s
Reputation | Calculation of the PageRank for MONDIS took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for MONDIS took 3.0040740966796875e-05s
Believability | Calculation of trust value for MONDIS took 8.58306884765625e-06s
INFO | --- Analysis for mondis took 2.8858795166015625s
Availability | SPARQL endpoint availability check for Monumentos took 4.1484832763671875e-05s
Availability | VoID file availability check for Monumentos took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Monumentos took 0.27647876739501953s
Reputation | Calculation of the PageRank for Monumentos took 0.020249605178833008s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0008182525634765625s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.0994415283203125e-05s
Believability | Calculation of trust value for Monumentos took 7.3909759521484375e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.880657911300659s
Availability | SPARQL endpoint availability check for MORElab took 0.9612271785736084s
Availability | VoID file availability check for MORElab took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for MORElab took 0.23802423477172852s
Reputation | Calculation of the PageRank for MORElab took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for MORElab took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for MORElab took 0.00010442733764648438s
Believability | Calculation of trust value for MORElab took 7.3909759521484375e-06s
INFO | --- Analysis for morelab took 5.140789270401001s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.8264122009277344s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.2600278854370117s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 9.250640869140625e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 7.3909759521484375e-06s
INFO | --- Analysis for msc took 16.436023473739624s
Availability | SPARQL endpoint availability check for Multext-East took 6.628036499023438e-05s
Availability | VoID file availability check for Multext-East took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Multext-East took 0.2717733383178711s
Reputation | Calculation of the PageRank for Multext-East took 0.020726919174194336s
Interlinking | Calculation of Degree of Connection for Multext-East took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Multext-East took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.147125244140625e-05s
Believability | Calculation of trust value for Multext-East took 7.62939453125e-06s
INFO | --- Analysis for multext-east took 2.3207337856292725s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.124641418457031e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.25978660583496094s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 2.6226043701171875e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 7.152557373046875e-06s
INFO | --- Analysis for multilingualeulaw took 2.838934898376465s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.220008850097656e-05s
Availability | VoID file availability check for Multimedia Lab took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.27924132347106934s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 4.696846008300781e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.0728836059570312e-05s
INFO | --- Analysis for multimedia-lab took 2.425098419189453s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.267692565917969e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.2885096073150635s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.021027565002441406s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 2.765655517578125e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 1.1920928955078125e-05s
INFO | --- Analysis for munich-offener-haushalt took 2.8621342182159424s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.5825321674346924s
Availability | VoID file availability check for Muninn World War I took 0.0007545948028564453s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2524569034576416s
Reputation | Calculation of the PageRank for Muninn World War I took 0.021124601364135742s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.225440979003906e-05s
Believability | Calculation of trust value for Muninn World War I took 1.3113021850585938e-05s
INFO | --- Analysis for muninn-world-war-i took 10.347796201705933s
Availability | SPARQL endpoint availability check for Musei Italiani took 6.508827209472656e-05s
Availability | VoID file availability check for Musei Italiani took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.2508676052093506s
Reputation | Calculation of the PageRank for Musei Italiani took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 2.8371810913085938e-05s
Believability | Calculation of trust value for Musei Italiani took 1.3113021850585938e-05s
INFO | --- Analysis for musei-italiani took 2.9269542694091797s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2600843906402588s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020899534225463867s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010943412780761719s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.1682510375976562e-05s
INFO | --- Analysis for museosespania-gnoss took 90.47152042388916s
Availability | SPARQL endpoint availability check for Italian Museums took 0.38339662551879883s
Availability | VoID file availability check for Italian Museums took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.6882555484771729s
Reputation | Calculation of the PageRank for Italian Museums took 0.020432710647583008s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 7.82012939453125e-05s
Believability | Calculation of trust value for Italian Museums took 1.2636184692382812e-05s
INFO | --- Analysis for museums-in-italy took 3.2245495319366455s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.1484832763671875e-05s
Availability | VoID file availability check for MusicBrainz took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.2533533573150635s
Reputation | Calculation of the PageRank for MusicBrainz took 0.023535490036010742s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0010991096496582031s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.743171691894531e-05s
Believability | Calculation of trust value for MusicBrainz took 1.2874603271484375e-05s
INFO | --- Analysis for musicbrainz_ took 2.893369436264038s
Availability | SPARQL endpoint availability check for MusicNet Codex took 5.3882598876953125e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.24968194961547852s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.02080368995666504s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.8371810913085938e-05s
Believability | Calculation of trust value for MusicNet Codex took 1.52587890625e-05s
INFO | --- Analysis for musicnet_codex took 3.2725346088409424s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7607066631317139s
Availability | VoID file availability check for Muziekweb took 0.0005490779876708984s
Extra | Recovery of all triples for Muziekweb took 1.6369338035583496s
Performance | Total latancy measurement for Muziekweb took 1.7429430484771729s
Amount of data | Number of triples check for Muziekweb took 0.3984649181365967s
Interoperability | New terms check for Muziekweb took 1.7004342079162598s
Versatility | Languages check for Muziekweb took 58.332605838775635s
Interpretability | Number of blank nodes check for Muziekweb took 0.3163292407989502s
Interpretability | RDF structures check for Muziekweb took 0.3376786708831787s
Versatility | Serialization formats check for Muziekweb took 0.31883835792541504s
Availability | RDF dump link check for Muziekweb took 0.30922818183898926s
License | MR license check for Muziekweb took 0.3530542850494385s
License | HR license check for Muziekweb took 13.018102169036865s
Amount of data | Number of property check for Muziekweb took 0.31342291831970215s
Understandability | Number of label check for Muziekweb took 1.0236167907714844s
Understandability | URI regex check for Muziekweb took 0.5852899551391602s
Understandability | Vocabs check for Muziekweb took 0.2988429069519043s
Verifiability | Authors check for Muziekweb took 0.3031883239746094s
Verifiability | Publishers check for Muziekweb took 0.32128190994262695s
Performance | Throughput check for Muziekweb took 12.260955810546875s
Amount of data | Check the number of entities for Muziekweb took 6.031990051269531e-05s
Verifiability | Contribs. check for Muziekweb took 0.3226804733276367s
Interlinking | sameAs chians check for Muziekweb took 0.3162665367126465s
Interlinking | skos check for Muziekweb took 0.3212409019470215s
Interlinking | skos check for Muziekweb took 0.33794713020324707s
Timeliness | dataset update frequency check for Muziekweb took 0.3322298526763916s
Currency | Creation date check for Muziekweb took 0.8966050148010254s
Currency | Modification date check for Muziekweb took 0.9382896423339844s
Rep.Conc. | URIs length for Muziekweb took 1.8346033096313477s
Interoperability | New vocabularies check for Muziekweb took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.34142398834228516s
Accuracy | Check Functional Property for Muziekweb took 0.6319282054901123s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.6489102840423584s
Accuracy | Check Empty annotation labels for Muziekweb took 3.226963996887207s
Accuracy | Check White space in annotation for Muziekweb took 0.02773427963256836s
Accuracy | Check Datatype consistency for Muziekweb took 0.027376890182495117s
Consistency | Disjoint class check for Muziekweb took 0.5536408424377441s
Consistency | Check Misplaced properties for Muziekweb took 1.255586862564087s
Consistency | Check Ontology hijacking for Muziekweb took 2.183936595916748s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.2623205184936523s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.6477580070495605s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03227567672729492s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3491246700286865s
Security | Sign check for Muziekweb took 0.31891417503356934s
Availability | Check URIs Dereferenciability for Muziekweb took 2095.850881099701s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.5110557079315186s
Reputation | Calculation of the PageRank for Muziekweb took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0006806850433349609s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.430511474609375e-06s
Believability | Calculation of trust value for Muziekweb took 1.2874603271484375e-05s
INFO | --- Analysis for muziekweb took 2243.8553154468536s
Availability | SPARQL endpoint availability check for myExperiment took 0.43178296089172363s
Availability | VoID file availability check for myExperiment took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for myExperiment took 0.6690607070922852s
Reputation | Calculation of the PageRank for myExperiment took 0.02007603645324707s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00011420249938964844s
Believability | Calculation of trust value for myExperiment took 6.67572021484375e-06s
INFO | --- Analysis for my-experiment took 5.576288461685181s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.06616353988647461s
Availability | VoID file availability check for My Family Lineage took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.6772222518920898s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020247697830200195s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.368492126464844e-05s
Believability | Calculation of trust value for My Family Lineage took 7.152557373046875e-06s
INFO | --- Analysis for my-family-lineage took 13.82790470123291s
Availability | SPARQL endpoint availability check for My ontology test took 1.3535552024841309s
Availability | VoID file availability check for My ontology test took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for My ontology test took 0.26487040519714355s
Reputation | Calculation of the PageRank for My ontology test took 0.02102947235107422s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for My ontology test took 2.6702880859375e-05s
Believability | Calculation of trust value for My ontology test took 1.1444091796875e-05s
INFO | --- Analysis for myontologytest took 3.867482900619507s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.076957702636719e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.000244140625s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.2583332061767578s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 9.751319885253906e-05s
Believability | Calculation of trust value for myopenlink dataspaces took 6.4373016357421875e-06s
INFO | --- Analysis for myopenlink-dataspaces took 3.5795559883117676s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 5.780807971954346s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.24643325805664062s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.4849853515625e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for n-lex-as-linked-data took 14.818174362182617s
Availability | SPARQL endpoint availability check for NAICS 2007 took 27.12283682823181s
Availability | VoID file availability check for NAICS 2007 took 0.0008370876312255859s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.2563514709472656s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.021098852157592773s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.887580871582031e-05s
Believability | Calculation of trust value for NAICS 2007 took 5.4836273193359375e-06s
INFO | --- Analysis for naics-2007 took 126.92619609832764s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.84711742401123s
Availability | VoID file availability check for NAICS 2012 took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.24590682983398438s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.021190166473388672s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.078315734863281e-05s
Believability | Calculation of trust value for NAICS 2012 took 5.245208740234375e-06s
INFO | --- Analysis for naics-2012 took 123.6623387336731s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.270125150680542s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.020188570022583008s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 6.222724914550781e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for nalt took 3.3894851207733154s
Availability | SPARQL endpoint availability check for Usernames  took 0.00010395050048828125s
Availability | VoID file availability check for Usernames  took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for Usernames  took 0.2526259422302246s
Reputation | Calculation of the PageRank for Usernames  took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Usernames  took 2.7418136596679688e-05s
Believability | Calculation of trust value for Usernames  took 1.1444091796875e-05s
INFO | --- Analysis for Names took 2.7037155628204346s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 0.830613374710083s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007855892181396484s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.0497939586639404s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 3.92085862159729s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.995161294937134s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 16.14898443222046s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.6842916011810303s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 14.049511909484863s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.8428492546081543s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.856109619140625s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.3996248245239258s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.6780712604522705s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.8701217174530029s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.39048171043396s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.9077498912811279s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.625777721405029s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 1.2744691371917725s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.4246494770050049s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.42963576316833496s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.4372570514678955s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 12.687650918960571s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 4.100799560546875e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.4335663318634033s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.9558744430541992s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.9158189296722412s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.1310858726501465s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3556675910949707s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1808652877807617s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 1.2492003440856934s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.8358936309814453s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.4315073490142822s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3714756965637207s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.36721301078796387s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.40268826484680176s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007326602935791016s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010833740234375s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.3838346004486084s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7699229717254639s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3807065486907959s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.7096972465515137s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.2550580501556396s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.7420082092285156s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0005826950073242188s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.411484956741333s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 5.757427453994751s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.26285457611083984s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.021519899368286133s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.556510925292969e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 9.059906005859375e-06s
INFO | --- Analysis for national-diet-library-authorities took 247.28996014595032s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.4413924217224121s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005822181701660156s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.0663020610809326s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 3.2825851440429688s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.628538846969604s
Interoperability | New terms check for National Diet Library of Japan subject headings took 15.184395551681519s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.40561842918395996s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.611683130264282s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.39626622200012207s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.38776493072509766s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.4262113571166992s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.3966495990753174s
License | MR license check for National Diet Library of Japan subject headings took 0.3783104419708252s
License | HR license check for National Diet Library of Japan subject headings took 91.84857225418091s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.3841407299041748s
Understandability | Number of label check for National Diet Library of Japan subject headings took 4.926279544830322s
Understandability | URI regex check for National Diet Library of Japan subject headings took 1.5351052284240723s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.4168219566345215s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.4425239562988281s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.37412238121032715s
Performance | Throughput check for National Diet Library of Japan subject headings took 13.563127279281616s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.940696716308594e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.8506603240966797s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.49625492095947266s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.354686975479126s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.0937509536743164s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.39624857902526855s
Currency | Creation date check for National Diet Library of Japan subject headings took 2.3709239959716797s
Currency | Modification date check for National Diet Library of Japan subject headings took 1.7380547523498535s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.7757108211517334s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.39270853996276855s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.8645462989807129s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.4305715560913086s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.5168547630310059s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007631778717041016s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0011055469512939453s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.3996758460998535s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 1.2394025325775146s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.44101881980895996s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.981454610824585s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.2686452865600586s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.6879708766937256s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006387233734130859s
Security | Sign check for National Diet Library of Japan subject headings took 0.8477318286895752s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 5.395690679550171s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.7349379062652588s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02184152603149414s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.6743621826171875e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 9.5367431640625e-07s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.3828277587890625e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 242.0557918548584s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.1738765239715576s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.6673996448516846s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02121567726135254s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.673004150390625e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.2159347534179688e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 6.493478059768677s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00012421607971191406s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.7112565040588379s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02293562889099121s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.723403930664062e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.239776611328125e-05s
INFO | --- Analysis for Naturopathy took 4.2212605476379395s
Availability | SPARQL endpoint availability check for Naturopathy took 6.246566772460938e-05s
Availability | VoID file availability check for Naturopathy took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.26788949966430664s
Reputation | Calculation of the PageRank for Naturopathy took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for Naturopathy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Naturopathy took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 2.765655517578125e-05s
Believability | Calculation of trust value for Naturopathy took 1.2874603271484375e-05s
INFO | --- Analysis for naturopathy2 took 2.823544502258301s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 8.273124694824219e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.27190661430358887s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 2.7418136596679688e-05s
Believability | Calculation of trust value for NCI Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for nci-thesaurus took 3.263118267059326s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.4198813438415527s
Availability | VoID file availability check for COVID-19 Data took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.2575094699859619s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 2.765655517578125e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.1682510375976562e-05s
INFO | --- Analysis for NCMI-COVID-19 took 7.18543267250061s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.3980627059936523s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.25443243980407715s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.021191835403442383s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0009472370147705078s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2636184692382812e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.2159347534179688e-05s
INFO | --- Analysis for NCMICOVID-19 took 6.2289228439331055s
Availability | SPARQL endpoint availability check for NDF-RT took 8.463859558105469e-05s
Availability | VoID file availability check for NDF-RT took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.23933935165405273s
Reputation | Calculation of the PageRank for NDF-RT took 0.02151656150817871s
Interlinking | Calculation of Degree of Connection for NDF-RT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 2.7418136596679688e-05s
Believability | Calculation of trust value for NDF-RT took 1.3589859008789062e-05s
INFO | --- Analysis for ndf-rt took 2.8473072052001953s
Availability | SPARQL endpoint availability check for Near took 4.3392181396484375e-05s
Availability | VoID file availability check for Near took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for Near took 0.2528834342956543s
Reputation | Calculation of the PageRank for Near took 0.022448062896728516s
Interlinking | Calculation of Degree of Connection for Near took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Near took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Near took 8.797645568847656e-05s
Believability | Calculation of trust value for Near took 1.2874603271484375e-05s
INFO | --- Analysis for near took 9.331428050994873s
Availability | SPARQL endpoint availability check for Neel took 8.559226989746094e-05s
Availability | VoID file availability check for Neel took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Neel took 0.27838802337646484s
Reputation | Calculation of the PageRank for Neel took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for Neel took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neel took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Neel took 3.0279159545898438e-05s
Believability | Calculation of trust value for Neel took 1.1682510375976562e-05s
INFO | --- Analysis for neel took 2.8806002140045166s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.029273986816406e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.29493284225463867s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 2.86102294921875e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 1.1682510375976562e-05s
INFO | --- Analysis for neurocommons_text_mining_pilot took 3.134735107421875s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.2438507080078125e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.280153751373291s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.8133392333984375e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.1682510375976562e-05s
INFO | --- Analysis for neurolex-wiki took 2.4059503078460693s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 5.3882598876953125e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.2518448829650879s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.02029132843017578s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.076957702636719e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.1444091796875e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.5667033195495605s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 9.703636169433594e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.24968934059143066s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.413459777832031e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.239776611328125e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.417843580245972s
Availability | SPARQL endpoint availability check for Newsweek took 4.076957702636719e-05s
Availability | VoID file availability check for Newsweek took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Newsweek took 0.26302266120910645s
Reputation | Calculation of the PageRank for Newsweek took 0.02243208885192871s
Interlinking | Calculation of Degree of Connection for Newsweek took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Newsweek took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Newsweek took 2.8848648071289062e-05s
Believability | Calculation of trust value for Newsweek took 1.2636184692382812e-05s
INFO | --- Analysis for newsweek took 2.863504648208618s
Availability | SPARQL endpoint availability check for neXtProt took 1.6027131080627441s
Availability | VoID file availability check for neXtProt took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for neXtProt took 0.281538724899292s
Reputation | Calculation of the PageRank for neXtProt took 0.02277350425720215s
Interlinking | Calculation of Degree of Connection for neXtProt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for neXtProt took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.337860107421875e-05s
Believability | Calculation of trust value for neXtProt took 1.2636184692382812e-05s
INFO | --- Analysis for nextprot took 4.678686857223511s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 8.368492126464844e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2462165355682373s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02324509620666504s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 9.918212890625e-05s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for nextweb-gnoss took 11.69800853729248s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.6253204345703125e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0011992454528808594s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.250704288482666s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 7.653236389160156e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 9.5367431640625e-06s
INFO | --- Analysis for nhs-jargon took 3.0182859897613525s
Availability | SPARQL endpoint availability check for NIT Patna took 6.198883056640625e-05s
Availability | VoID file availability check for NIT Patna took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.2511637210845947s
Reputation | Calculation of the PageRank for NIT Patna took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for NIT Patna took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NIT Patna took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.175041198730469e-05s
Believability | Calculation of trust value for NIT Patna took 7.867813110351562e-06s
INFO | --- Analysis for NITP took 3.02779483795166s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 3.981590270996094e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.25888538360595703s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020174503326416016s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.075599670410156e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 1.1444091796875e-05s
INFO | --- Analysis for nlm_2007_mesh took 2.7446372509002686s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 8.273124694824219e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.25139760971069336s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.152557373046875e-06s
INFO | --- Analysis for nlr-dataset-mod took 3.831843376159668s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.6936194896697998s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0011920928955078125s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2632322311401367s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.022429943084716797s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.314018249511719e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for NLW took 4.162630081176758s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.5982322692871094s
Availability | VoID file availability check for Nobel Prizes took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.2327744960784912s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 8.7738037109375e-05s
Believability | Calculation of trust value for Nobel Prizes took 8.106231689453125e-06s
INFO | --- Analysis for nobelprizes took 9.450582265853882s
Availability | SPARQL endpoint availability check for NoiPA took 0.32744812965393066s
Availability | VoID file availability check for NoiPA took 0.0005352497100830078s
Extra | Recovery of all triples for NoiPA took 1.4158198833465576s
Performance | Total latancy measurement for NoiPA took 0.5854358673095703s
Amount of data | Number of triples check for NoiPA took 1.4419193267822266s
Interoperability | New terms check for NoiPA took 2.861943006515503s
Versatility | Languages check for NoiPA took 60.17722821235657s
Interpretability | Number of blank nodes check for NoiPA took 0.17958736419677734s
Interpretability | RDF structures check for NoiPA took 0.3533761501312256s
Versatility | Serialization formats check for NoiPA took 0.14077019691467285s
Availability | RDF dump link check for NoiPA took 0.12072205543518066s
License | MR license check for NoiPA took 0.28223466873168945s
License | HR license check for NoiPA took 60.35414981842041s
Amount of data | Number of property check for NoiPA took 0.19269299507141113s
Understandability | Number of label check for NoiPA took 0.3640482425689697s
Understandability | URI regex check for NoiPA took 0.26541614532470703s
Understandability | Vocabs check for NoiPA took 0.13641953468322754s
Verifiability | Authors check for NoiPA took 0.1234121322631836s
Verifiability | Publishers check for NoiPA took 0.13254165649414062s
Performance | Throughput check for NoiPA took 10.51545786857605s
Amount of data | Check the number of entities for NoiPA took 7.2479248046875e-05s
Verifiability | Contribs. check for NoiPA took 0.10597443580627441s
Interlinking | sameAs chians check for NoiPA took 0.18088078498840332s
Interlinking | skos check for NoiPA took 0.4640018939971924s
Interlinking | skos check for NoiPA took 0.12932920455932617s
Timeliness | dataset update frequency check for NoiPA took 0.1223459243774414s
Currency | Creation date check for NoiPA took 0.25659728050231934s
Currency | Modification date check for NoiPA took 0.17319846153259277s
Rep.Conc. | URIs length for NoiPA took 19.472508430480957s
Interoperability | New vocabularies check for NoiPA took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.19345545768737793s
Accuracy | Check Functional Property for NoiPA took 0.11376357078552246s
Accuracy | Check Inverse Functional Property for NoiPA took 0.11475729942321777s
Accuracy | Check Empty annotation labels for NoiPA took 0.5491604804992676s
Accuracy | Check White space in annotation for NoiPA took 0.030270099639892578s
Accuracy | Check Datatype consistency for NoiPA took 0.028061866760253906s
Consistency | Disjoint class check for NoiPA took 0.11859512329101562s
Consistency | Check Misplaced properties for NoiPA took 17.42136549949646s
Consistency | Misplaced classes for NoiPA took 0.2770833969116211s
Consistency | Check Ontology hijacking for NoiPA took 1.6318435668945312s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.253807783126831s
Consistency | Check Invalid usage of undefined properties for NoiPA took 18.759434938430786s
Conciseness | Check Extensional conciseness for NoiPA took 0.03272294998168945s
Conciseness | Check Intensional conciseness for NoiPA took 0.2090902328491211s
Security | Sign check for NoiPA took 0.1313464641571045s
Availability | Check URIs Dereferenciability for NoiPA took 17.20217776298523s
Completeness | Calculation of interlinking completeness for NoiPA took 0.5506143569946289s
Reputation | Calculation of the PageRank for NoiPA took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for NoiPA took 2.9325485229492188e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.1920928955078125e-06s
Believability | Calculation of trust value for NoiPA took 1.1920928955078125e-05s
INFO | --- Analysis for NoiPA took 404.97489523887634s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.5420455932617188s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.68733811378479s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0009319782257080078s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 0.00010323524475097656s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.2159347534179688e-05s
INFO | --- Analysis for nom took 10.440168857574463s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 25.24720859527588s
Availability | VoID file availability check for Nomenclator Asturias took 0.0008933544158935547s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.27141571044921875s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.021274566650390625s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 7.963180541992188e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 1.0967254638671875e-05s
INFO | --- Analysis for nomenclator-asturias took 144.40611910820007s
Availability | SPARQL endpoint availability check for nomisma took 8.797645568847656e-05s
Availability | VoID file availability check for nomisma took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for nomisma took 0.2528696060180664s
Reputation | Calculation of the PageRank for nomisma took 0.021820545196533203s
Interlinking | Calculation of Degree of Connection for nomisma took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for nomisma took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for nomisma took 2.86102294921875e-05s
Believability | Calculation of trust value for nomisma took 1.3113021850585938e-05s
INFO | --- Analysis for nomisma took 3.3024826049804688s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.4288902282714844s
Availability | VoID file availability check for Nomisma.org  took 0.0006783008575439453s
Extra | Recovery of all triples for Nomisma.org  took 578.297461271286s
Performance | Total latancy measurement for Nomisma.org  took 2.025705575942993s
Amount of data | Number of triples check for Nomisma.org  took 49.89395093917847s
Interoperability | New terms check for Nomisma.org  took 9.529475212097168s
Versatility | Languages check for Nomisma.org  took 114.04513931274414s
Interpretability | Number of blank nodes check for Nomisma.org  took 37.27017855644226s
Security | Check HTTPS for Nomisma.org  took 1.2122101783752441s
Interpretability | RDF structures check for Nomisma.org  took 0.5335884094238281s
Versatility | Serialization formats check for Nomisma.org  took 0.3863821029663086s
Availability | RDF dump link check for Nomisma.org  took 890.6068346500397s
License | MR license check for Nomisma.org  took 0.43573474884033203s
License | HR license check for Nomisma.org  took 60.85908627510071s
Amount of data | Number of property check for Nomisma.org  took 0.3491671085357666s
Understandability | Number of label check for Nomisma.org  took 8.853768348693848s
Understandability | URI regex check for Nomisma.org  took 0.7504868507385254s
Understandability | Vocabs check for Nomisma.org  took 0.35913944244384766s
Verifiability | Authors check for Nomisma.org  took 0.35812807083129883s
Verifiability | Publishers check for Nomisma.org  took 0.4974684715270996s
Performance | Throughput check for Nomisma.org  took 11.569051504135132s
Amount of data | Check the number of entities for Nomisma.org  took 0.0008137226104736328s
Verifiability | Contribs. check for Nomisma.org  took 0.36779069900512695s
Interlinking | sameAs chians check for Nomisma.org  took 0.3755340576171875s
Interlinking | skos check for Nomisma.org  took 1.162261962890625s
Interlinking | skos check for Nomisma.org  took 0.5455584526062012s
Timeliness | dataset update frequency check for Nomisma.org  took 0.36479949951171875s
Currency | Creation date check for Nomisma.org  took 0.7376821041107178s
Currency | Modification date check for Nomisma.org  took 0.37011003494262695s
Rep.Conc. | URIs length for Nomisma.org  took 408.6086142063141s
Interoperability | New vocabularies check for Nomisma.org  took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.43611645698547363s
Accuracy | Check Functional Property for Nomisma.org  took 0.36216092109680176s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.37580227851867676s
Accuracy | Check Empty annotation labels for Nomisma.org  took 315.6519966125488s
Accuracy | Check White space in annotation for Nomisma.org  took 2.7089638710021973s
Consistency | Disjoint class check for Nomisma.org  took 0.39134716987609863s
Consistency | Check Misplaced properties for Nomisma.org  took 27.598440408706665s
Consistency | Check Ontology hijacking for Nomisma.org  took 356.12752318382263s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 28.871405601501465s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.000148773193359375s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.4056410789489746s
Security | Sign check for Nomisma.org  took 0.40421056747436523s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.7685267925262451s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.02123093605041504s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.430511474609375e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.2874603271484375e-05s
INFO | --- Analysis for nomisma_org took 6921.41052365303s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.4816899299621582s
Availability | VoID file availability check for Curriculum Vitae took 0.0002429485321044922s
Extra | Recovery of all triples for Curriculum Vitae took 1.4434177875518799s
Performance | Total latancy measurement for Curriculum Vitae took 1.3053572177886963s
Amount of data | Number of triples check for Curriculum Vitae took 0.2232363224029541s
Interoperability | New terms check for Curriculum Vitae took 1.4538853168487549s
Versatility | Languages check for Curriculum Vitae took 0.25513505935668945s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.2427811622619629s
Interpretability | RDF structures check for Curriculum Vitae took 0.13315486907958984s
Versatility | Serialization formats check for Curriculum Vitae took 0.24793696403503418s
Availability | RDF dump link check for Curriculum Vitae took 0.21349048614501953s
License | MR license check for Curriculum Vitae took 0.10576248168945312s
License | HR license check for Curriculum Vitae took 0.1212160587310791s
Amount of data | Number of property check for Curriculum Vitae took 0.30063867568969727s
Understandability | Number of label check for Curriculum Vitae took 0.13693547248840332s
Understandability | URI regex check for Curriculum Vitae took 0.4503669738769531s
Understandability | Vocabs check for Curriculum Vitae took 0.24118399620056152s
Verifiability | Authors check for Curriculum Vitae took 0.11028170585632324s
Verifiability | Publishers check for Curriculum Vitae took 0.27586841583251953s
Performance | Throughput check for Curriculum Vitae took 11.173060655593872s
Amount of data | Check the number of entities for Curriculum Vitae took 7.224082946777344e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.11848115921020508s
Interlinking | sameAs chians check for Curriculum Vitae took 0.1262972354888916s
Interlinking | skos check for Curriculum Vitae took 0.11804580688476562s
Interlinking | skos check for Curriculum Vitae took 0.2599165439605713s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.23934388160705566s
Currency | Creation date check for Curriculum Vitae took 0.2305006980895996s
Currency | Modification date check for Curriculum Vitae took 0.36237525939941406s
Rep.Conc. | URIs length for Curriculum Vitae took 0.6306979656219482s
Interoperability | New vocabularies check for Curriculum Vitae took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.2534768581390381s
Accuracy | Check Functional Property for Curriculum Vitae took 0.23220491409301758s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.12031388282775879s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.23856139183044434s
Accuracy | Check White space in annotation for Curriculum Vitae took 9.942054748535156e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0032622814178466797s
Consistency | Disjoint class check for Curriculum Vitae took 0.23839497566223145s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.47258973121643066s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.5383081436157227s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.3135645389556885s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.5536565780639648s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0014126300811767578s
Security | Sign check for Curriculum Vitae took 0.20673370361328125s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 20.525397777557373s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.6794183254241943s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.02161407470703125s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.147125244140625e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 4.76837158203125e-07s
Believability | Calculation of trust value for Curriculum Vitae took 6.67572021484375e-06s
INFO | --- Analysis for Nordine_Bittich took 61.2178909778595s
Availability | SPARQL endpoint availability check for NorPark took 0.07261085510253906s
Availability | VoID file availability check for NorPark took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for NorPark took 0.26836085319519043s
Reputation | Calculation of the PageRank for NorPark took 0.020479202270507812s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.3392181396484375e-05s
Believability | Calculation of trust value for NorPark took 7.152557373046875e-06s
INFO | --- Analysis for norpark took 3.009842872619629s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.021664857864379883s
Availability | VoID file availability check for Parking Dataset took 0.00021505355834960938s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.25870537757873535s
Reputation | Calculation of the PageRank for Parking Dataset took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.076957702636719e-05s
Believability | Calculation of trust value for Parking Dataset took 7.152557373046875e-06s
INFO | --- Analysis for norpark2 took 2.7742362022399902s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.6464829444885254s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0005366802215576172s
Extra | Recovery of all triples for Norway fishery stocks dataset took 108.97729682922363s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.9589488506317139s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.796171426773071s
Interoperability | New terms check for Norway fishery stocks dataset took 14.25507926940918s
Versatility | Languages check for Norway fishery stocks dataset took 300.20289063453674s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.1027801036834717s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.24027276039123535s
Versatility | Serialization formats check for Norway fishery stocks dataset took 8.572885036468506s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.35540223121643066s
License | MR license check for Norway fishery stocks dataset took 0.8360416889190674s
License | HR license check for Norway fishery stocks dataset took 300.18579292297363s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.20963215827941895s
Understandability | Number of label check for Norway fishery stocks dataset took 2.215911626815796s
Understandability | URI regex check for Norway fishery stocks dataset took 0.8047924041748047s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.3952951431274414s
Verifiability | Authors check for Norway fishery stocks dataset took 0.18293547630310059s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.26050424575805664s
Performance | Throughput check for Norway fishery stocks dataset took 11.342773914337158s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 6.937980651855469e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.1855921745300293s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.17766213417053223s
Interlinking | skos check for Norway fishery stocks dataset took 0.44317173957824707s
Interlinking | skos check for Norway fishery stocks dataset took 0.4347667694091797s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 4.065502405166626s
Currency | Creation date check for Norway fishery stocks dataset took 0.47406530380249023s
Currency | Modification date check for Norway fishery stocks dataset took 0.24887609481811523s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 155.9054114818573s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.1778857707977295s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.31084108352661133s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.3743758201599121s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 36.37432265281677s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.62790584564209s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.5469675064086914s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.17949509620666504s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 88.4943368434906s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.236662149429321s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 32.74646806716919s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.3314058780670166s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 88.6943986415863s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.704418897628784s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.6631593704223633s
Security | Sign check for Norway fishery stocks dataset took 0.5699005126953125s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 13.901540279388428s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.4563713073730469s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.027523279190063477s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 9.012222290039062e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 2.1457672119140625e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.3113021850585938e-05s
INFO | --- Analysis for Norway_Fishery_ took 2283.4090180397034s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.3737008571624756s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.6951231956481934s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.02085590362548828s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.078315734863281e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.3589859008789062e-05s
INFO | --- Analysis for norwegian-geo-divisions took 8.051195859909058s
Availability | SPARQL endpoint availability check for NorwegianSoE took 6.580352783203125e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.24216341972351074s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 2.9087066650390625e-05s
Believability | Calculation of trust value for NorwegianSoE took 1.2874603271484375e-05s
INFO | --- Analysis for norwegiansoe took 3.1234161853790283s
Availability | SPARQL endpoint availability check for NITP took 0.00010204315185546875s
Availability | VoID file availability check for NITP took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for NITP took 0.2532930374145508s
Reputation | Calculation of the PageRank for NITP took 0.021793127059936523s
Interlinking | Calculation of Degree of Connection for NITP took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NITP took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for NITP took 6.604194641113281e-05s
Believability | Calculation of trust value for NITP took 1.430511474609375e-05s
INFO | --- Analysis for notIdentifier took 3.204390525817871s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 8.606910705566406e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.25531911849975586s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.020234107971191406s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.147125244140625e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.33514404296875e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 3.1081063747406006s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 5.2928924560546875e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2788677215576172s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 3.504753112792969e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 1.1444091796875e-05s
INFO | --- Analysis for npg took 2.9514458179473877s
Availability | SPARQL endpoint availability check for NPM took 4.220008850097656e-05s
Availability | VoID file availability check for NPM took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for NPM took 0.2738521099090576s
Reputation | Calculation of the PageRank for NPM took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for NPM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NPM took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for NPM took 3.314018249511719e-05s
Believability | Calculation of trust value for NPM took 1.0251998901367188e-05s
INFO | --- Analysis for npm took 3.240859270095825s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.055616140365600586s
Availability | VoID file availability check for NTNU special collections took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.31402039527893066s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.4836273193359375e-05s
Believability | Calculation of trust value for NTNU special collections took 1.1205673217773438e-05s
INFO | --- Analysis for ntnusc took 5.688308954238892s
Availability | SPARQL endpoint availability check for links took 4.100799560546875e-05s
Availability | VoID file availability check for links took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for links took 0.2847716808319092s
Reputation | Calculation of the PageRank for links took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for links took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for links took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for links took 1.2159347534179688e-05s
Believability | Calculation of trust value for links took 1.1920928955078125e-05s
INFO | --- Analysis for nugmyanmar took 2.426591396331787s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.1484832763671875e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.25121450424194336s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.022953510284423828s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00010037422180175781s
Believability | Calculation of trust value for NUTS (GeoVocab) took 8.58306884765625e-06s
INFO | --- Analysis for nuts-geovocab took 2.600858211517334s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.39337921142578125s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.24726295471191406s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.4849853515625e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.1682510375976562e-05s
INFO | --- Analysis for nvd took 4.012596607208252s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.8448846340179443s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.2477867603302002s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.225440979003906e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.1205673217773438e-05s
INFO | --- Analysis for nvs took 9.366363286972046s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 8.7738037109375e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.25797462463378906s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.021337509155273438s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0002071857452392578s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.0967254638671875e-05s
INFO | --- Analysis for nytimes-linked-open-data took 2.4933998584747314s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 8.177757263183594e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.24346518516540527s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 2.765655517578125e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 1.3589859008789062e-05s
INFO | --- Analysis for o-anc took 2.80722975730896s
Availability | SPARQL endpoint availability check for OANetzwerk took 0.00010156631469726562s
Availability | VoID file availability check for OANetzwerk took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.2509124279022217s
Reputation | Calculation of the PageRank for OANetzwerk took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 2.8848648071289062e-05s
Believability | Calculation of trust value for OANetzwerk took 1.2159347534179688e-05s
INFO | --- Analysis for oanetzwerk took 2.793959617614746s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 8.58306884765625e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.24913287162780762s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.0994415283203125e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 1.1920928955078125e-05s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.8317878246307373s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.6659359931945801s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0005173683166503906s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.8103244304656982s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 2.3331806659698486s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 3.6479594707489014s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.983577251434326s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.43047475814819s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.5748119354248047s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.3668692111968994s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.48133301734924316s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5618805885314941s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.4620327949523926s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.47231459617614746s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.36638879776001s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.48296022415161133s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.7153525352478027s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.9704599380493164s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.6286356449127197s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.4812138080596924s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.48860764503479004s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 14.422631740570068s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 6.914138793945312e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.4788541793823242s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.4742164611816406s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.4736056327819824s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.44693803787231445s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.6342589855194092s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.9599800109863281s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.46709227561950684s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 18.793726205825806s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.49347472190856934s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.4664134979248047s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.4936056137084961s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.9581925868988037s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.023347854614257812s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.027753114700317383s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.5088484287261963s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 13.266904354095459s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.541273832321167s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.165444850921631s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.257997989654541s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.970819234848022s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.030527353286743164s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.5326809883117676s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.49175095558166504s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 14.564741611480713s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3316006660461426s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.021350383758544922s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.00067901611328125s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 9.918212890625e-05s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.1920928955078125e-05s
INFO | --- Analysis for ocd took 431.07035398483276s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 8.368492126464844e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2549571990966797s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.029273986816406e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.2874603271484375e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.236687660217285s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 2.963204860687256s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0007627010345458984s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2519216537475586s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.153915405273438e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.0251998901367188e-05s
INFO | --- Analysis for oceandrilling-codices took 8.962868452072144s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 2.686891794204712s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.27472758293151855s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02193307876586914s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.409385681152344e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 6.839293718338013s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 2.6695117950439453s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.26107358932495117s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02077937126159668s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.457069396972656e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-forams took 7.251215219497681s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 2.7079954147338867s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0007648468017578125s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.286590576171875s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 4.100799560546875e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-janus took 7.27539587020874s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 12.513509511947632s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.2632901668548584s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.528594970703125e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-janusamp took 17.055749893188477s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.6197824478149414s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007560253143310547s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2634851932525635s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.3589859008789062e-05s
INFO | --- Analysis for oceandrilling-ldeo took 7.164343595504761s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.2438507080078125e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.26119518280029297s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.745887756347656e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.2159347534179688e-05s
INFO | --- Analysis for oclc-fast took 7.859873533248901s
Availability | SPARQL endpoint availability check for Open Data Communities took 8.273124694824219e-05s
Availability | VoID file availability check for Open Data Communities took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.25087428092956543s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020864486694335938s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Data Communities took 1.239776611328125e-05s
INFO | --- Analysis for odc took 2.7551872730255127s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.00011086463928222656s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.2504274845123291s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.0517578125e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.775161743164062e-06s
INFO | --- Analysis for odc-imd-environment-score took 5.66706395149231s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 8.869171142578125e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.26991963386535645s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.7418136596679688e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 1.1920928955078125e-05s
INFO | --- Analysis for odc-imd-rank-2007 took 2.9783735275268555s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.18894696235656738s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005552768707275391s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.2995011806488037s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 1.4503169059753418s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.13979148864746094s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.5092003345489502s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.4488844871520996s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.26079249382019s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.16431856155395508s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.21506834030151367s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.15179753303527832s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 50.88494396209717s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.41533660888671875s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.226996898651123s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.22148919105529785s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.15073704719543457s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.3989138603210449s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.20389080047607422s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.1956043243408203s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.13492369651794434s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 11.50942063331604s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 8.130073547363281e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.21412897109985352s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.2018134593963623s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.14363813400268555s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.1889815330505371s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.14491868019104004s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.6695826053619385s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.20439696311950684s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.454361915588379s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.21266627311706543s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.12762212753295898s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.20342326164245605s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.2317216396331787s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.563021183013916s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 3.0206971168518066s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.5256478786468506s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.0001385211944580078s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.5781278610229492s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.2175912857055664s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.34402966499328613s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0008285045623779297s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.1920928955078125e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.245208740234375e-06s
INFO | --- Analysis for odc-lsoa took 271.5822443962097s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 0.00010919570922851562s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.24802422523498535s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 3.123283386230469e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 1.3113021850585938e-05s
INFO | --- Analysis for odc-population-2005 took 3.259204626083374s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 8.273124694824219e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.24766325950622559s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.02138805389404297s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 1.2636184692382812e-05s
INFO | --- Analysis for ods took 2.762981653213501s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.5805685520172119s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2882039546966553s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020440340042114258s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.322166442871094e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for oecd-linked-data took 3.0568642616271973s
Availability | SPARQL endpoint availability check for Offener Haushalt took 5.698204040527344e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.2628765106201172s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 2.6941299438476562e-05s
Believability | Calculation of trust value for Offener Haushalt took 1.239776611328125e-05s
INFO | --- Analysis for offener-haushalt took 2.89165997505188s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.358392000198364s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.24685382843017578s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.02086162567138672s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0010221004486083984s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 5.435943603515625e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 7.62939453125e-06s
INFO | --- Analysis for ogolod took 103.6190574169159s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.4345855712890625e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0007522106170654297s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.25632500648498535s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.022202491760253906s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.6716461181640625e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.239776611328125e-05s
INFO | --- Analysis for olac took 22.712365865707397s
Availability | SPARQL endpoint availability check for OLiA took 5.4836273193359375e-05s
Availability | VoID file availability check for OLiA took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for OLiA took 0.2488574981689453s
Reputation | Calculation of the PageRank for OLiA took 0.020770549774169922s
Interlinking | Calculation of Degree of Connection for OLiA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012040138244628906s
Believability | Calculation of trust value for OLiA took 1.1205673217773438e-05s
INFO | --- Analysis for olia took 12.367756366729736s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.00543212890625e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.24880290031433105s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02138066291809082s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.00543212890625e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.0967254638671875e-05s
INFO | --- Analysis for olia-discourse took 7.182448148727417s
Availability | SPARQL endpoint availability check for Open Land Use took 0.19578981399536133s
Availability | VoID file availability check for Open Land Use took 0.0002105236053466797s
Extra | Recovery of all triples for Open Land Use took 124.19685435295105s
Performance | Total latancy measurement for Open Land Use took 0.9944677352905273s
Amount of data | Number of triples check for Open Land Use took 9.274221897125244s
Interoperability | New terms check for Open Land Use took 14.140428304672241s
Versatility | Languages check for Open Land Use took 300.2116496562958s
Interpretability | Number of blank nodes check for Open Land Use took 2.269951105117798s
Interpretability | RDF structures check for Open Land Use took 0.27062296867370605s
Versatility | Serialization formats check for Open Land Use took 8.112999677658081s
Availability | RDF dump link check for Open Land Use took 0.2904491424560547s
License | MR license check for Open Land Use took 0.626899242401123s
License | HR license check for Open Land Use took 300.19244623184204s
Amount of data | Number of property check for Open Land Use took 0.21999740600585938s
Understandability | Number of label check for Open Land Use took 3.1724853515625s
Understandability | URI regex check for Open Land Use took 0.9847795963287354s
Understandability | Vocabs check for Open Land Use took 0.5868487358093262s
Verifiability | Authors check for Open Land Use took 0.21282458305358887s
Verifiability | Publishers check for Open Land Use took 0.2510073184967041s
Performance | Throughput check for Open Land Use took 11.25624966621399s
Amount of data | Check the number of entities for Open Land Use took 6.937980651855469e-05s
Verifiability | Contribs. check for Open Land Use took 0.19900274276733398s
Interlinking | sameAs chians check for Open Land Use took 0.19936800003051758s
Interlinking | skos check for Open Land Use took 0.4584312438964844s
Interlinking | skos check for Open Land Use took 0.4116966724395752s
Timeliness | dataset update frequency check for Open Land Use took 5.496204614639282s
Currency | Creation date check for Open Land Use took 0.4740264415740967s
Currency | Modification date check for Open Land Use took 0.2537102699279785s
Rep.Conc. | URIs length for Open Land Use took 152.79202342033386s
Interoperability | New vocabularies check for Open Land Use took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.19983553886413574s
Accuracy | Check Functional Property for Open Land Use took 0.34945249557495117s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.40211963653564453s
Accuracy | Check Empty annotation labels for Open Land Use took 40.718360900878906s
Accuracy | Check White space in annotation for Open Land Use took 2.6588823795318604s
Accuracy | Check Datatype consistency for Open Land Use took 2.5942366123199463s
Consistency | Disjoint class check for Open Land Use took 0.18265652656555176s
Consistency | Check Misplaced properties for Open Land Use took 88.72606682777405s
Consistency | Misplaced classes for Open Land Use took 8.18508768081665s
Consistency | Check Ontology hijacking for Open Land Use took 35.28828024864197s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.3814640045166016s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 89.55218839645386s
Conciseness | Check Extensional conciseness for Open Land Use took 2.6980438232421875s
Conciseness | Check Intensional conciseness for Open Land Use took 0.5088050365447998s
Security | Sign check for Open Land Use took 1.0154578685760498s
Availability | Check URIs Dereferenciability for Open Land Use took 13.326276063919067s
Completeness | Calculation of interlinking completeness for Open Land Use took 1.2160069942474365s
Reputation | Calculation of the PageRank for Open Land Use took 0.021094560623168945s
Interlinking | Calculation of Degree of Connection for Open Land Use took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Land Use took 1.3589859008789062e-05s
INFO | --- Analysis for OLU took 2300.2971560955048s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.076957702636719e-05s
Availability | VoID file availability check for OmegaWiki took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.2621133327484131s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0006818771362304688s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 2.8848648071289062e-05s
Believability | Calculation of trust value for OmegaWiki took 1.2159347534179688e-05s
INFO | --- Analysis for omegawiki took 4.61505126953125s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.8240365982055664s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.2510521411895752s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020202159881591797s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-als took 3.678154230117798s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.32176876068115234s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.25149106979370117s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.02023935317993164s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.457069396972656e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-arb took 3.0550782680511475s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.26069092750549316s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.25762486457824707s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-bul took 3.0787134170532227s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.28242039680480957s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.26173925399780273s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020334482192993164s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.457069396972656e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-cow took 3.0595719814300537s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.27319860458374023s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2526731491088867s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02019333839416504s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-cwn took 2.973433256149292s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.27485179901123047s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.24457979202270508s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.4809112548828125e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-dan took 3.015071153640747s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.2469158172607422s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.23553109169006348s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-ell took 2.9006214141845703s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.3033275604248047s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2631955146789551s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.021886587142944336s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-eng took 3.007267713546753s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.298145055770874s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.27381467819213867s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-fas took 3.0452475547790527s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2507047653198242s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2579920291900635s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.020235061645507812s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
INFO | --- Analysis for omwn-fin took 2.929213523864746s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.22933721542358398s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.24268507957458496s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-fra took 2.908950090408325s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2537667751312256s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.23929548263549805s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.4332275390625e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-heb took 3.0208959579467773s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2749192714691162s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2393205165863037s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.02020573616027832s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-hrv took 2.982586622238159s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.27199220657348633s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.25617146492004395s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.409385681152344e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-isl took 2.9809234142303467s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.24313807487487793s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2408912181854248s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-ita took 2.881474018096924s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.25708961486816406s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.23658347129821777s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-iwn took 2.9640674591064453s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2562587261199951s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2383718490600586s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-jpn took 2.9687588214874268s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.24869656562805176s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.25088953971862793s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.314018249511719e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-mcr took 2.8802826404571533s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.24393677711486816s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.256671667098999s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-msa took 2.926086902618408s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.2852463722229004s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.27761244773864746s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.02021193504333496s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-nld took 3.0913257598876953s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.30065488815307617s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2526390552520752s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.022637128829956055s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-nor took 3.0884759426116943s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2542765140533447s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.23741984367370605s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.021989107131958008s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-pol took 2.987121820449829s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.23381471633911133s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2567605972290039s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-por took 2.924236297607422s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2608764171600342s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.24515390396118164s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-ron took 3.013094663619995s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2612440586090088s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2345597743988037s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02034759521484375s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-slk took 2.909680128097534s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.23415899276733398s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.24911165237426758s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.021776199340820312s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 4.38690185546875e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-slv took 2.9293053150177s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2598755359649658s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2586934566497803s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.02119135856628418s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0009026527404785156s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 4.363059997558594e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-swe took 2.982447862625122s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.28647732734680176s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2560298442840576s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.02106332778930664s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-tha took 3.0346763134002686s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.918195009231567s
Availability | VoID file availability check for OntoBeef Domain took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2342529296875s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 5.054473876953125e-05s
Believability | Calculation of trust value for OntoBeef Domain took 6.67572021484375e-06s
INFO | --- Analysis for ontobeef-domain took 35.19256591796875s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.1961669921875e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.278012752532959s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 8.988380432128906e-05s
Believability | Calculation of trust value for Ontos News Portal took 1.33514404296875e-05s
INFO | --- Analysis for ontos-news-portal took 19.02485466003418s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.9114227294921875e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.23989295959472656s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.0994415283203125e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.152557373046875e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.428849935531616s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.363059997558594e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.26663804054260254s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.62396240234375e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 5.7220458984375e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 10.20899248123169s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 6.198883056640625e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.24062180519104004s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 1.33514404296875e-05s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.7684412002563477s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 8.654594421386719e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0007965564727783203s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.24701189994812012s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.673004150390625e-05s
Believability | Calculation of trust value for Open Data Euskadi took 5.4836273193359375e-06s
INFO | --- Analysis for open-data-euskadi took 7.837505102157593s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.172325134277344e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.2663118839263916s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.022571563720703125s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010037422180175781s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 1.1682510375976562e-05s
INFO | --- Analysis for open-data-risp took 22.895722150802612s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.3212001323699951s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006897449493408203s
Extra | Recovery of all triples for Open Data Thesaurus took 1.2893266677856445s
Performance | Total latancy measurement for Open Data Thesaurus took 0.6381893157958984s
Amount of data | Number of triples check for Open Data Thesaurus took 0.1290299892425537s
Interoperability | New terms check for Open Data Thesaurus took 1.414599895477295s
Versatility | Languages check for Open Data Thesaurus took 0.1306910514831543s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.12963342666625977s
Security | Check HTTPS for Open Data Thesaurus took 0.45870423316955566s
Interpretability | RDF structures check for Open Data Thesaurus took 0.12475061416625977s
Versatility | Serialization formats check for Open Data Thesaurus took 0.13323307037353516s
Availability | RDF dump link check for Open Data Thesaurus took 1.5478529930114746s
License | MR license check for Open Data Thesaurus took 0.13039565086364746s
License | HR license check for Open Data Thesaurus took 0.12600040435791016s
Amount of data | Number of property check for Open Data Thesaurus took 0.1312403678894043s
Understandability | Number of label check for Open Data Thesaurus took 0.11790013313293457s
Understandability | URI regex check for Open Data Thesaurus took 0.25578784942626953s
Understandability | Vocabs check for Open Data Thesaurus took 0.11762118339538574s
Verifiability | Authors check for Open Data Thesaurus took 0.12688159942626953s
Verifiability | Publishers check for Open Data Thesaurus took 0.14324617385864258s
Performance | Throughput check for Open Data Thesaurus took 10.353460311889648s
Amount of data | Check the number of entities for Open Data Thesaurus took 5.745887756347656e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.13199949264526367s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.11535096168518066s
Interlinking | skos check for Open Data Thesaurus took 0.13181328773498535s
Interlinking | skos check for Open Data Thesaurus took 0.1359570026397705s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.1294260025024414s
Currency | Creation date check for Open Data Thesaurus took 0.2543933391571045s
Currency | Modification date check for Open Data Thesaurus took 0.26629018783569336s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.5476946830749512s
Interoperability | New vocabularies check for Open Data Thesaurus took 0.7128429412841797s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11589646339416504s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.12937211990356445s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.1312730312347412s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1985492706298828s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011150836944580078s
Consistency | Disjoint class check for Open Data Thesaurus took 0.12995052337646484s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.27412962913513184s
Consistency | Misplaced classes for Open Data Thesaurus took 0.16897082328796387s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.4994819164276123s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.431349515914917s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00014328956604003906s
Security | Sign check for Open Data Thesaurus took 0.12084531784057617s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.26442551612854004s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.02011847496032715s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0006759166717529297s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.749961853027344e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.4747915267944336s
Believability | Calculation of trust value for Open Data Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for open-data-thesaurus took 75.56839299201965s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 8.344650268554688e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2751739025115967s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 2.956390380859375e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 1.1682510375976562e-05s
INFO | --- Analysis for open-data-tor-vergata took 3.005967855453491s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.3255295753479004s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 7.390975952148438e-05s
Believability | Calculation of trust value for Open Election Data Project took 7.62939453125e-06s
INFO | --- Analysis for open-election-data-project took 42.419400215148926s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.9459915161132812s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.271087646484375s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.106231689453125e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 8.821487426757812e-06s
INFO | --- Analysis for open-energy-info-wiki took 11.060858011245728s
Availability | SPARQL endpoint availability check for Open Library took 8.487701416015625e-05s
Availability | VoID file availability check for Open Library took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Open Library took 0.28668856620788574s
Reputation | Calculation of the PageRank for Open Library took 0.02109384536743164s
Interlinking | Calculation of Degree of Connection for Open Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.724761962890625e-05s
Believability | Calculation of trust value for Open Library took 9.775161743164062e-06s
INFO | --- Analysis for open-library took 9.854382514953613s
Availability | SPARQL endpoint availability check for Open Directory took 4.029273986816406e-05s
Availability | VoID file availability check for Open Directory took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Open Directory took 0.2508671283721924s
Reputation | Calculation of the PageRank for Open Directory took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Open Directory took 2.956390380859375e-05s
Believability | Calculation of trust value for Open Directory took 1.049041748046875e-05s
INFO | --- Analysis for open_directory took 2.8434040546417236s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.3517758846282959s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0004487037658691406s
Extra | Recovery of all triples for Open Land Use @PSNC took 117.06109809875488s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9521398544311523s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.19979739189148s
Interoperability | New terms check for Open Land Use @PSNC took 14.103934526443481s
Versatility | Languages check for Open Land Use @PSNC took 300.1777431964874s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.097433567047119s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.20763349533081055s
Versatility | Serialization formats check for Open Land Use @PSNC took 8.206443071365356s
Availability | RDF dump link check for Open Land Use @PSNC took 0.2914559841156006s
License | MR license check for Open Land Use @PSNC took 0.596712589263916s
License | HR license check for Open Land Use @PSNC took 300.19178652763367s
Amount of data | Number of property check for Open Land Use @PSNC took 0.20343828201293945s
Understandability | Number of label check for Open Land Use @PSNC took 2.2754557132720947s
Understandability | URI regex check for Open Land Use @PSNC took 1.00028657913208s
Understandability | Vocabs check for Open Land Use @PSNC took 0.4944908618927002s
Verifiability | Authors check for Open Land Use @PSNC took 0.2160203456878662s
Verifiability | Publishers check for Open Land Use @PSNC took 0.24140644073486328s
Performance | Throughput check for Open Land Use @PSNC took 11.207395553588867s
Amount of data | Check the number of entities for Open Land Use @PSNC took 7.43865966796875e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.20049738883972168s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.19237565994262695s
Interlinking | skos check for Open Land Use @PSNC took 0.4040834903717041s
Interlinking | skos check for Open Land Use @PSNC took 0.42542505264282227s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 5.851881742477417s
Currency | Creation date check for Open Land Use @PSNC took 0.4931652545928955s
Currency | Modification date check for Open Land Use @PSNC took 0.24485230445861816s
Rep.Conc. | URIs length for Open Land Use @PSNC took 148.08719682693481s
Interoperability | New vocabularies check for Open Land Use @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.18532252311706543s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.3468129634857178s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.3472788333892822s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 37.1610746383667s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.6477959156036377s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.6051883697509766s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.17716288566589355s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 88.34163737297058s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.236329555511475s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 34.20259952545166s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.392725944519043s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 88.16184091567993s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.68833327293396s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.5207915306091309s
Security | Sign check for Open Land Use @PSNC took 1.0559453964233398s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 14.234753131866455s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 1.3974714279174805s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for Open_Land_Use took 2282.603340148926s
Availability | SPARQL endpoint availability check for flyatlas took 1.3179776668548584s
Availability | VoID file availability check for flyatlas took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for flyatlas took 0.25208115577697754s
Reputation | Calculation of the PageRank for flyatlas took 0.020929813385009766s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.743171691894531e-05s
Believability | Calculation of trust value for flyatlas took 1.3113021850585938e-05s
INFO | --- Analysis for openbiomed-flyatlas took 7.013688802719116s
Availability | SPARQL endpoint availability check for OpenCalais took 4.267692565917969e-05s
Availability | VoID file availability check for OpenCalais took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.28780603408813477s
Reputation | Calculation of the PageRank for OpenCalais took 0.022842884063720703s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010943412780761719s
Believability | Calculation of trust value for OpenCalais took 1.0728836059570312e-05s
INFO | --- Analysis for opencalais took 6.443485736846924s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 8.606910705566406e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.6747403144836426s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.2479248046875e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 9.059906005859375e-06s
INFO | --- Analysis for opencorporates took 3.0454869270324707s
Availability | SPARQL endpoint availability check for OpenCyc took 4.38690185546875e-05s
Availability | VoID file availability check for OpenCyc took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.25156331062316895s
Reputation | Calculation of the PageRank for OpenCyc took 0.021076202392578125s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010275840759277344s
Believability | Calculation of trust value for OpenCyc took 1.0251998901367188e-05s
INFO | --- Analysis for opencyc took 2.8971755504608154s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.24571681022644043s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.337860107421875e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.3167741298675537s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.2599635124206543s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.187422752380371s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 6.389617919921875e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0013229846954345703s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.26610732078552246s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02302098274230957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.031274318695068s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2725341320037842s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.315084218978882s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2534167766571045s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.2626383304595947s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 8.821487426757812e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.25632309913635254s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 8.092561721801758s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 8.702278137207031e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0008423328399658203s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.24973440170288086s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.022179365158081055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.5762786865234375e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 3.898076295852661s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 5.435943603515625e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.23553729057312012s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020915508270263672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.3183891773223877s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 8.463859558105469e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.2567155361175537s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 5.478930473327637s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2592933177947998s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 3.024329423904419s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 7.62939453125e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2664661407470703s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.39959716796875s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.27649402618408203s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.6213009357452393s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 9.918212890625e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.2433938980102539s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.0321054458618164s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 5.245208740234375e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.25856781005859375s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020425081253051758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.345087766647339s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.26494503021240234s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 4.121595621109009s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 5.078315734863281e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2345445156097412s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.982948303222656e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 3.1163578033447266s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.2375659942626953s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02147197723388672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.0148308277130127s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.24538731575012207s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.1160683631896973s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 5.364418029785156e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2763059139251709s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.3423187732696533s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.24201297760009766s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020740032196044922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.6450881958007812e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.1415185928344727s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.2859158515930176s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.0224761962890625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.3153374195098877s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 8.749961853027344e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.24672555923461914s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.4809112548828125e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 4.309284210205078s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.2743077278137207s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 3.799577474594116s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 8.511543273925781e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.24740219116210938s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.02230525016784668s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.993688583374023s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.26078009605407715s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.022834300994873047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.5475046634674072s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.6253204345703125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2600240707397461s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02149796485900879s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.969970703125s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.916854858398438e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2595508098602295s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.7085883617401123s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0003261566162109375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.2429060935974121s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020245075225830078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 3.874948740005493s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.27776598930358887s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 3.9961416721343994s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 6.651878356933594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.27654075622558594s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.5406124591827393s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 5.53131103515625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.287689208984375s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020112276077270508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.525245428085327s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2476818561553955s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.641183614730835s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2741281986236572s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.02070474624633789s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.022393226623535s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.630752563476562e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.2514340877532959s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.310436964035034s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 8.845329284667969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.27724432945251465s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.26485538482666s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 8.726119995117188e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.27829790115356445s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.3642098903656006s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 7.2479248046875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2492222785949707s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.539897918701172s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.24828243255615234s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.022803068161010742s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 3.991737127304077s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.24627995491027832s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 3.522435188293457s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.296966552734375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.22872304916381836s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020440340042114258s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 3.3132290840148926s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.2382948398590088s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.4809112548828125e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.9485363960266113s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2727174758911133s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0225985050201416s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.805219888687134s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2607414722442627s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 4.0572450160980225s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 5.989194393157959s
Availability | VoID file availability check for Open Data of Ecuador took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2617340087890625s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 9.131431579589844e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.0967254638671875e-05s
INFO | --- Analysis for opendataec took 11.526607751846313s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.00010013580322265625s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.24176454544067383s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.1920928955078125e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 5.40057110786438s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.100799560546875e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.25218915939331055s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.1920928955078125e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.545243263244629s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.220008850097656e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.24877452850341797s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.33514404296875e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.5290253162384033s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 8.678436279296875e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2776932716369629s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.1205673217773438e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.6183390617370605s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.24657964706420898s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02087235450744629s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.0967254638671875e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.53961181640625s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 9.989738464355469e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.3306746482849121s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.02103424072265625s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.0967254638671875e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.759263515472412s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 8.535385131835938e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.04852485656738281s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.26587629318237305s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02099919319152832s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.3828277587890625e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.6488027572631836s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2724902629852295s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.5679831504821777s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 0.00010919570922851562s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.26354432106018066s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.1920928955078125e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.3985402584075928s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.477010250091553s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2536897659301758s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.3589859008789062e-05s
INFO | --- Analysis for openlink-lod-cache took 62.893768310546875s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 8.630752563476562e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.2668745517730713s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.036064147949219e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.3113021850585938e-05s
INFO | --- Analysis for openlinksw-dataspaces took 2.799861431121826s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 8.893013000488281e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.40512681007385254s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.021961212158203125s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0009357929229736328s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 0.000102996826171875s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 9.059906005859375e-06s
INFO | --- Analysis for openlylocal took 24.147458791732788s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.6599516868591309s
Availability | VoID file availability check for OpenMobileNetwork took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2635843753814697s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02147674560546875s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.176399230957031e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.239776611328125e-05s
INFO | --- Analysis for openmobilenetwork took 5.132264852523804s
Availability | SPARQL endpoint availability check for OpenTox took 3.981590270996094e-05s
Availability | VoID file availability check for OpenTox took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for OpenTox took 0.24849987030029297s
Reputation | Calculation of the PageRank for OpenTox took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.075599670410156e-05s
Believability | Calculation of trust value for OpenTox took 1.4066696166992188e-05s
INFO | --- Analysis for opentox took 2.7940337657928467s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 0.00010132789611816406s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.24087142944335938s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.0040740966796875e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 1.33514404296875e-05s
INFO | --- Analysis for openuplabs took 2.8457446098327637s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.076957702636719e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.26497530937194824s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 2.9802322387695312e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 1.3589859008789062e-05s
INFO | --- Analysis for opus took 2.8662118911743164s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 4.1961669921875e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.26299166679382324s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0009348392486572266s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 4.267692565917969e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 1.3589859008789062e-05s
INFO | --- Analysis for orcid took 2.849622964859009s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.282639741897583s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.26270294189453125s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0009992122650146484s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.0001361370086669922s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.3113021850585938e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 6.3117663860321045s
Availability | SPARQL endpoint availability check for oreilly took 4.57763671875e-05s
Availability | VoID file availability check for oreilly took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for oreilly took 0.25965261459350586s
Reputation | Calculation of the PageRank for oreilly took 0.02288818359375s
Interlinking | Calculation of Degree of Connection for oreilly took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.14984130859375e-05s
Believability | Calculation of trust value for oreilly took 1.2636184692382812e-05s
INFO | --- Analysis for oreilly took 4.39721155166626s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.3697288036346436s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.27437901496887207s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.02229762077331543s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.33514404296875e-05s
INFO | --- Analysis for Organchem-Data took 7.195918798446655s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.18596100807189941s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.25208210945129395s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.022228240966796875s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.009506225585938e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for organic-edunet took 9.155700445175171s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.47673606872558594s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005440711975097656s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 6.1093151569366455s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7288575172424316s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.15432143211364746s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.6923282146453857s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 6.638173341751099s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.14481735229492188s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.4706759452819824s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.1759505271911621s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.16188311576843262s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.1560041904449463s
License | HR license check for Open Research Knowledge Graph (ORKG) took 4.223955392837524s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.16956591606140137s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.19539308547973633s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.2718076705932617s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.15110111236572266s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.1694045066833496s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.15253424644470215s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.594080448150635s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.2479248046875e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.13249492645263672s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.16096735000610352s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.183058500289917s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.17490363121032715s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.14659619331359863s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.30386829376220703s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.2832317352294922s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 3.9648396968841553s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.1473073959350586s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.1177825927734375s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.1658797264099121s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.314863443374634s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.26746439933776855s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.27141380310058594s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.3103961944580078s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.3265745639801025s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.8564596176147461s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.2897024154663086s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.3486573696136475s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.103135824203491s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.28089356422424316s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.1329786777496338s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.14823389053344727s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 1883.6875960826874s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 1.0118491649627686s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.021651744842529297s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.4543533325195312e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.33514404296875e-05s
INFO | --- Analysis for orkg took 2133.7073500156403s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.2226338386535645s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.2791292667388916s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.20159912109375e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.1682510375976562e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 30.442172288894653s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.5392284393310547s
Availability | VoID file availability check for OSM Semantic Network took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.24859142303466797s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.790855407714844e-05s
Believability | Calculation of trust value for OSM Semantic Network took 7.867813110351562e-06s
INFO | --- Analysis for osm-semantic-network took 8.452077627182007s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.3244762420654297s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0002601146697998047s
Extra | Recovery of all triples for Open Transport Map @PSNC took 113.64054322242737s
Performance | Total latancy measurement for Open Transport Map @PSNC took 1.2540862560272217s
Amount of data | Number of triples check for Open Transport Map @PSNC took 9.182914972305298s
Interoperability | New terms check for Open Transport Map @PSNC took 14.110735893249512s
Versatility | Languages check for Open Transport Map @PSNC took 300.23534893989563s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 1.939636468887329s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.3022756576538086s
Versatility | Serialization formats check for Open Transport Map @PSNC took 8.370894193649292s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.3288595676422119s
License | MR license check for Open Transport Map @PSNC took 0.8039088249206543s
License | HR license check for Open Transport Map @PSNC took 300.2461166381836s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.20003843307495117s
Understandability | Number of label check for Open Transport Map @PSNC took 2.425848960876465s
Understandability | URI regex check for Open Transport Map @PSNC took 1.0474941730499268s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.4779224395751953s
Verifiability | Authors check for Open Transport Map @PSNC took 0.20013904571533203s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.24709367752075195s
Performance | Throughput check for Open Transport Map @PSNC took 11.571236371994019s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 3.457069396972656e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.19549083709716797s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.1926887035369873s
Interlinking | skos check for Open Transport Map @PSNC took 0.40377306938171387s
Interlinking | skos check for Open Transport Map @PSNC took 0.4873471260070801s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 5.521522521972656s
Currency | Creation date check for Open Transport Map @PSNC took 0.4588282108306885s
Currency | Modification date check for Open Transport Map @PSNC took 0.24190902709960938s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 159.08728957176208s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.1974959373474121s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.39671850204467773s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.37987780570983887s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 41.78077530860901s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.656911849975586s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.595550537109375s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.197767972946167s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 87.23912453651428s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.315454244613647s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 29.797221422195435s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.4013457298278809s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 87.97301316261292s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.7217888832092285s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.9003338813781738s
Security | Sign check for Open Transport Map @PSNC took 0.8651077747344971s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 14.364437341690063s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 1.0394103527069092s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.02124619483947754s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for OTM took 2300.028695344925s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.4345855712890625e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.6667041778564453s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.266334533691406e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 1.3828277587890625e-05s
INFO | --- Analysis for ounl-dspace-in-rdf took 4.173827409744263s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.029273986816406e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.2513720989227295s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020374298095703125s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.2159347534179688e-05s
INFO | --- Analysis for ox-ac-uk-catalogue took 3.270167827606201s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.029273986816406e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.25103092193603516s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.1444091796875e-05s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 2.7674167156219482s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.00543212890625e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.27919936180114746s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.02174854278564453s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 1.1205673217773438e-05s
INFO | --- Analysis for ox-ac-uk-openmeters took 2.872610092163086s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 8.344650268554688e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.27608704566955566s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020854473114013672s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.956390380859375e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 1.1444091796875e-05s
INFO | --- Analysis for ox-ac-uk-timeseries took 2.8753907680511475s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.0531158447265625e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.277585506439209s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 1.0728836059570312e-05s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.904317617416382s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 9.989738464355469e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.24934816360473633s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 1.0967254638671875e-05s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.813758134841919s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 7.176399230957031e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.26447606086730957s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.8133392333984375e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 1.1444091796875e-05s
INFO | --- Analysis for oxpoints took 2.8842294216156006s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 0.5232224464416504s
Availability | VoID file availability check for Pali English Lexicon took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.25155162811279297s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.981590270996094e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.3589859008789062e-05s
INFO | --- Analysis for pali-english-lexicon took 5.159693241119385s
Availability | SPARQL endpoint availability check for PanLex took 1.8830761909484863s
Availability | VoID file availability check for PanLex took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for PanLex took 0.241743803024292s
Reputation | Calculation of the PageRank for PanLex took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.128715515136719e-05s
Believability | Calculation of trust value for PanLex took 1.1920928955078125e-05s
INFO | --- Analysis for panlex took 4.255275726318359s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.696846008300781e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.28896260261535645s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020268917083740234s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.4809112548828125e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.1444091796875e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.37060284614563s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.05311870574951172s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.27430272102355957s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020204544067382812s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.506111145019531e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 9.059906005859375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.4841697216033936s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 6.747245788574219e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.26046133041381836s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020212173461914062s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.62396240234375e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.2874603271484375e-05s
INFO | --- Analysis for pdev-lemon took 4.19749116897583s
Availability | SPARQL endpoint availability check for pdevlemon took 9.298324584960938e-05s
Availability | VoID file availability check for pdevlemon took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.24379420280456543s
Reputation | Calculation of the PageRank for pdevlemon took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for pdevlemon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.123283386230469e-05s
Believability | Calculation of trust value for pdevlemon took 1.1682510375976562e-05s
INFO | --- Analysis for pdevlemon took 3.1412386894226074s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.887580871582031e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008382797241210938s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2476036548614502s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.677078247070312e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.33514404296875e-05s
INFO | --- Analysis for periodo took 19.279766082763672s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.1961669921875e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.26462793350219727s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00038623809814453125s
Believability | Calculation of trust value for Personal_Homepages took 8.344650268554688e-06s
INFO | --- Analysis for personal-homepages took 2.2896804809570312s
Availability | SPARQL endpoint availability check for Ontology of University People took 5.1021575927734375e-05s
Availability | VoID file availability check for Ontology of University People took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.2466294765472412s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.0279159545898438e-05s
Believability | Calculation of trust value for Ontology of University People took 8.821487426757812e-06s
INFO | --- Analysis for PersonOnto took 2.295027017593384s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 5.783721685409546s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2625999450683594s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02144002914428711s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1682510375976562e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2874603271484375e-05s
INFO | --- Analysis for PFKHS took 10.800079822540283s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.2615928649902344s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.30097246170043945s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1682510375976562e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.239776611328125e-05s
INFO | --- Analysis for PFRPPH took 7.639146089553833s
Availability | SPARQL endpoint availability check for PGxLOD took 30.18483567237854s
Availability | VoID file availability check for PGxLOD took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.27434539794921875s
Reputation | Calculation of the PageRank for PGxLOD took 0.02189779281616211s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 4.172325134277344e-05s
Believability | Calculation of trust value for PGxLOD took 1.33514404296875e-05s
INFO | --- Analysis for PGxLOD took 72.69779849052429s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.9233629703521729s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.00038433074951171875s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.25577735900878906s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02087545394897461s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0009722709655761719s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 4.100799560546875e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 7.3909759521484375e-06s
INFO | --- Analysis for phoible took 4.350061655044556s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 5.1975250244140625e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.3425629138946533s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.02081131935119629s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 4.601478576660156e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 7.3909759521484375e-06s
INFO | --- Analysis for PISM took 195.2081582546234s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.291534423828125e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.28589677810668945s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.416175842285156e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.1682510375976562e-05s
INFO | --- Analysis for planetdata-project-wiki took 2.3119795322418213s
Availability | SPARQL endpoint availability check for digitized plant specimen took 0.9894230365753174s
Availability | VoID file availability check for digitized plant specimen took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.2538776397705078s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.104873657226562e-05s
Believability | Calculation of trust value for digitized plant specimen took 6.67572021484375e-06s
INFO | --- Analysis for plant-specimen took 3.326707363128662s
Availability | SPARQL endpoint availability check for Pleiades took 4.458427429199219e-05s
Availability | VoID file availability check for Pleiades took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Pleiades took 0.25322699546813965s
Reputation | Calculation of the PageRank for Pleiades took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for Pleiades took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pleiades took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Pleiades took 7.653236389160156e-05s
Believability | Calculation of trust value for Pleiades took 1.1205673217773438e-05s
INFO | --- Analysis for pleiades took 13.522496223449707s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.1484832763671875e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.00037479400634765625s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.2549293041229248s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 2.9087066650390625e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.62939453125e-06s
INFO | --- Analysis for podorozhnyk took 3.231616973876953s
Availability | SPARQL endpoint availability check for Poképédia took 8.511543273925781e-05s
Availability | VoID file availability check for Poképédia took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for Poképédia took 0.26644444465637207s
Reputation | Calculation of the PageRank for Poképédia took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.295608520507812e-05s
Believability | Calculation of trust value for Poképédia took 1.1444091796875e-05s
INFO | --- Analysis for pokepedia-fr took 2.560751438140869s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 6.67572021484375e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.2517423629760742s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.748603820800781e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.3113021850585938e-05s
INFO | --- Analysis for polymath-virtual-library took 5.58119010925293s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.31206250190734863s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006570816040039062s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.943307161331177s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.5555195808410645s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.44916725158691406s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5923147201538086s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2643449306488037s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.36282920837402344s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11261558532714844s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11117959022521973s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.10042381286621094s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.10045504570007324s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6529617309570312s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1100924015045166s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.14353346824645996s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2240288257598877s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.10868096351623535s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.10991168022155762s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11597776412963867s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.797651767730713s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.008148193359375e-05s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.10741281509399414s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.10779285430908203s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11535334587097168s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.10753273963928223s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1080935001373291s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2071542739868164s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.21584272384643555s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.409735918045044s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1093289852142334s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.09949874877929688s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11385250091552734s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.0315947532653809s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19324970245361328s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.7798824310302734s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.10805225372314453s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.8367013931274414s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.4375457763671875s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2963764667510986s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.1178624629974365s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.442347764968872s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.09831714630126953s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4808.306045055389s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.214827299118042s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.02145862579345703s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.890296936035156e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5974044799804688e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3113021850585938e-05s
INFO | --- Analysis for portuguese_prisons_releases took 4880.492425203323s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 8.559226989746094e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.2774503231048584s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.027654409408569336s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.838539123535156e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 1.2874603271484375e-05s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 4.610541105270386s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 0.00017499923706054688s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.6914117336273193s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.021558284759521484s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 3.0517578125e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 1.3828277587890625e-05s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 3.3256492614746094s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 8.034706115722656e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.2760491371154785s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.021741628646850586s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 3.0279159545898438e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 1.3589859008789062e-05s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.8917076587677s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 8.416175842285156e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2532620429992676s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 2.9325485229492188e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 1.33514404296875e-05s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.8582911491394043s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 3.910064697265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2524073123931885s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.02196502685546875s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 1.239776611328125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.827686071395874s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 6.198883056640625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.24176359176635742s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.02054119110107422s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 1.1444091796875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.8670709133148193s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.2589564323425293s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 2.6702880859375e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.870206594467163s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.25072789192199707s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.021152257919311523s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 1.33514404296875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.845566749572754s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.100799560546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.29058337211608887s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 1.3589859008789062e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.7994046211242676s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 8.20159912109375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2517867088317871s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.021773576736450195s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.2901763916015625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 1.33514404296875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.8089983463287354s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 5.245208740234375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2516648769378662s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 2.86102294921875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 1.3589859008789062e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.859210729598999s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.0531158447265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.23778223991394043s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 1.33514404296875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.8519022464752197s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 8.440017700195312e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2733802795410156s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 1.2636184692382812e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.9001612663269043s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 8.535385131835938e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2527601718902588s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.24249267578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 1.2636184692382812e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.839498281478882s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 0.000102996826171875s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.23880386352539062s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020209550857543945s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 2.8133392333984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 1.3113021850585938e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.7546167373657227s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2728276252746582s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.02133035659790039s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 1.1682510375976562e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.8645191192626953s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.26274871826171875s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 1.3113021850585938e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.878544569015503s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2664620876312256s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.02267622947692871s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.8133392333984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 1.239776611328125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.8453006744384766s
Availability | SPARQL endpoint availability check for prefix.cc took 8.654594421386719e-05s
Availability | VoID file availability check for prefix.cc took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2484898567199707s
Reputation | Calculation of the PageRank for prefix.cc took 0.022043228149414062s
Interlinking | Calculation of Degree of Connection for prefix.cc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.600120544433594e-05s
Believability | Calculation of trust value for prefix.cc took 1.1682510375976562e-05s
INFO | --- Analysis for prefix-cc took 3.4063801765441895s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.6501893997192383s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0007414817810058594s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.25879716873168945s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.553794860839844e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 7.477313756942749s
Availability | SPARQL endpoint availability check for PreLex took 5.378073692321777s
Availability | VoID file availability check for PreLex took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for PreLex took 0.25381016731262207s
Reputation | Calculation of the PageRank for PreLex took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for PreLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for PreLex took 6.699562072753906e-05s
Believability | Calculation of trust value for PreLex took 1.1444091796875e-05s
INFO | --- Analysis for prelex took 15.860674619674683s
Availability | SPARQL endpoint availability check for Prelinger Archives took 1.446178913116455s
Availability | VoID file availability check for Prelinger Archives took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.265228271484375s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.647804260253906e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.1682510375976562e-05s
INFO | --- Analysis for prelinger_archives took 8.480996131896973s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 9.995749711990356s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.2621195316314697s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 5.078315734863281e-05s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 1.239776611328125e-05s
INFO | --- Analysis for premon took 14.248918056488037s
Availability | SPARQL endpoint availability check for Previsible took 0.00010418891906738281s
Availability | VoID file availability check for Previsible took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Previsible took 0.2740817070007324s
Reputation | Calculation of the PageRank for Previsible took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for Previsible took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.1682510375976562e-05s
Believability | Calculation of trust value for Previsible took 1.3113021850585938e-05s
INFO | --- Analysis for Previsible took 2.5900373458862305s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 8.726119995117188e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.25186991691589355s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.02073836326599121s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.3882598876953125e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 7.152557373046875e-06s
INFO | --- Analysis for princeton-library-findingaids took 3.6079914569854736s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.6835720539093018s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.27007532119750977s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for PrinParLat took 4.38338565826416s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.44490981101989746s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.2583882808685303s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.021097183227539062s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.915496826171875e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.3589859008789062e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 3.2006213665008545s
Availability | SPARQL endpoint availability check for Prior Panel took 4.220008850097656e-05s
Availability | VoID file availability check for Prior Panel took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.2587852478027344s
Reputation | Calculation of the PageRank for Prior Panel took 0.02093982696533203s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.24249267578125e-05s
Believability | Calculation of trust value for Prior Panel took 1.239776611328125e-05s
INFO | --- Analysis for Prior_Panel took 2.376070499420166s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.100799560546875e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.25687146186828613s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.021126985549926758s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 2.956390380859375e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 1.2874603271484375e-05s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.9266085624694824s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 8.392333984375e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0003364086151123047s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.24378633499145508s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 2.956390380859375e-05s
Believability | Calculation of trust value for Procomún SPARQL took 1.239776611328125e-05s
INFO | --- Analysis for procomun-sparql took 2.818128824234009s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.100799560546875e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.24989748001098633s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.0994415283203125e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 1.239776611328125e-05s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.846651077270508s
Availability | SPARQL endpoint availability check for ProductDB took 0.6846194267272949s
Availability | VoID file availability check for ProductDB took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for ProductDB took 0.23961281776428223s
Reputation | Calculation of the PageRank for ProductDB took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.009506225585938e-05s
Believability | Calculation of trust value for ProductDB took 1.239776611328125e-05s
INFO | --- Analysis for productdb took 3.5648021697998047s
Availability | SPARQL endpoint availability check for Product Types Ontology took 8.153915405273438e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2589914798736572s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.486343383789062e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for productontology took 3.2135496139526367s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 8.630752563476562e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.2792503833770752s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.0001010894775390625s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.4066696166992188e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 9.45984697341919s
Availability | SPARQL endpoint availability check for provenanceweb took 0.0572812557220459s
Availability | VoID file availability check for provenanceweb took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.2532694339752197s
Reputation | Calculation of the PageRank for provenanceweb took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.867813110351562e-05s
Believability | Calculation of trust value for provenanceweb took 1.4066696166992188e-05s
INFO | --- Analysis for provenanceweb took 60.47811436653137s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.3392181396484375e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2509453296661377s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.022380590438842773s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010013580322265625s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.2636184692382812e-05s
INFO | --- Analysis for proyectoapadrina took 10.917270421981812s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.41874599456787s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008645057678222656s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.3346214294433594s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.0517578125e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 9.059906005859375e-06s
INFO | --- Analysis for pscs-catalogue took 124.67805910110474s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 8.440017700195312e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.25754666328430176s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.05718994140625e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 7.3909759521484375e-06s
INFO | --- Analysis for psh-subject-headings took 3.1186981201171875s
Availability | SPARQL endpoint availability check for Depression took 0.4900670051574707s
Availability | VoID file availability check for Depression took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Depression took 0.25850939750671387s
Reputation | Calculation of the PageRank for Depression took 0.02047562599182129s
Interlinking | Calculation of Degree of Connection for Depression took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Depression took 2.7179718017578125e-05s
Believability | Calculation of trust value for Depression took 1.2159347534179688e-05s
INFO | --- Analysis for Psychology took 2.897648572921753s
Availability | SPARQL endpoint availability check for PubChem RDF took 8.559226989746094e-05s
Availability | VoID file availability check for PubChem RDF took 0.057544708251953125s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.2611119747161865s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.9114227294921875e-05s
Believability | Calculation of trust value for PubChem RDF took 1.1682510375976562e-05s
INFO | --- Analysis for PubChem_RDF took 5.835843086242676s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.076957702636719e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.24530291557312012s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 2.7894973754882812e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 1.33514404296875e-05s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.8835904598236084s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.6338901519775391s
Availability | VoID file availability check for Public Spending in Greece took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.2713785171508789s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 7.534027099609375e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.0728836059570312e-05s
INFO | --- Analysis for public-spending-in-greece took 8.642359972000122s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 8.225440979003906e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.2784144878387451s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.022316694259643555s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.7179718017578125e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 1.0728836059570312e-05s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.864885091781616s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.35428452491760254s
Availability | VoID file availability check for Publications Office Authority tables took 0.0005981922149658203s
Extra | Recovery of all triples for Publications Office Authority tables took 172.2092616558075s
Performance | Total latancy measurement for Publications Office Authority tables took 0.5927493572235107s
Amount of data | Number of triples check for Publications Office Authority tables took 69.61611676216125s
Interoperability | New terms check for Publications Office Authority tables took 75.32172703742981s
Versatility | Languages check for Publications Office Authority tables took 300.1436038017273s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 21.76445508003235s
Security | Check HTTPS for Publications Office Authority tables took 0.3217792510986328s
Interpretability | RDF structures check for Publications Office Authority tables took 0.5489485263824463s
Versatility | Serialization formats check for Publications Office Authority tables took 3.2654454708099365s
Availability | RDF dump link check for Publications Office Authority tables took 0.246690034866333s
License | MR license check for Publications Office Authority tables took 0.3419055938720703s
License | HR license check for Publications Office Authority tables took 300.10176396369934s
Amount of data | Number of property check for Publications Office Authority tables took 0.1661059856414795s
Understandability | Number of label check for Publications Office Authority tables took 1.9437177181243896s
Understandability | URI regex check for Publications Office Authority tables took 0.3204185962677002s
Understandability | Vocabs check for Publications Office Authority tables took 0.11523914337158203s
Verifiability | Authors check for Publications Office Authority tables took 0.2474517822265625s
Verifiability | Publishers check for Publications Office Authority tables took 0.17607641220092773s
Performance | Throughput check for Publications Office Authority tables took 10.507922649383545s
Amount of data | Check the number of entities for Publications Office Authority tables took 0.00010848045349121094s
Verifiability | Contribs. check for Publications Office Authority tables took 0.10963964462280273s
Interlinking | sameAs chians check for Publications Office Authority tables took 7.636873722076416s
Interlinking | skos check for Publications Office Authority tables took 0.30049967765808105s
Interlinking | skos check for Publications Office Authority tables took 0.16492414474487305s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.3436098098754883s
Currency | Creation date check for Publications Office Authority tables took 0.4247405529022217s
Currency | Modification date check for Publications Office Authority tables took 0.1393892765045166s
Rep.Conc. | URIs length for Publications Office Authority tables took 423.06585478782654s
Interoperability | New vocabularies check for Publications Office Authority tables took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.16468262672424316s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.22812461853027344s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.2108767032623291s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 41.13204908370972s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.0612406730651855s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.587263345718384s
Consistency | Disjoint class check for Publications Office Authority tables took 0.12412595748901367s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.5140655040741s
Consistency | Misplaced classes for Publications Office Authority tables took 8.280191421508789s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 41.55805325508118s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.6482110023498535s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.49686336517334s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.051349401473999s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.46407198905944824s
Security | Sign check for Publications Office Authority tables took 0.11018919944763184s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 16.22161555290222s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.374849796295166s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.021454572677612305s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.6689300537109375e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 9.298324584960938e-06s
INFO | --- Analysis for publications_office_authority_tables took 15338.802298307419s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.57763671875e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.6870765686035156s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.4332275390625e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 1.1920928955078125e-05s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 4.704627275466919s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.100799560546875e-05s
Availability | VoID file availability check for QBOAirbase took 0.0007500648498535156s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.2803621292114258s
Reputation | Calculation of the PageRank for QBOAirbase took 0.02070307731628418s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.677078247070312e-05s
Believability | Calculation of trust value for QBOAirbase took 1.2159347534179688e-05s
INFO | --- Analysis for qboairbase took 137.71047163009644s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 8.058547973632812e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.3222317695617676s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 2.86102294921875e-05s
Believability | Calculation of trust value for qualitywebdata.org took 1.33514404296875e-05s
INFO | --- Analysis for qualitywebdata-org took 2.9594688415527344s
Availability | SPARQL endpoint availability check for Qualité de l'air took 0.00010919570922851562s
Availability | VoID file availability check for Qualité de l'air took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.25493907928466797s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.218650817871094e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.2159347534179688e-05s
INFO | --- Analysis for Qualité_de_l'air took 2.839111089706421s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 7.748603820800781e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.2556617259979248s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 2.9802322387695312e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.239776611328125e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 52.184231996536255s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.6822593212127686s
Availability | VoID file availability check for Querolus in LiLa took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.28272581100463867s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for Querolus in LiLa took 9.775161743164062e-06s
INFO | --- Analysis for Querolus took 4.163832664489746s
Availability | SPARQL endpoint availability check for Quotations Book took 5.364418029785156e-05s
Availability | VoID file availability check for Quotations Book took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.2584545612335205s
Reputation | Calculation of the PageRank for Quotations Book took 0.022829771041870117s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.266334533691406e-05s
Believability | Calculation of trust value for Quotations Book took 6.67572021484375e-06s
INFO | --- Analysis for quotations_book took 2.907748222351074s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 8.296966552734375e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.29540085792541504s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02066349983215332s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for r4r took 2.8798253536224365s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.4460282325744629s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0006992816925048828s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 29.222601890563965s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7252881526947021s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.4047749042510986s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.8056774139404297s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.817806720733643s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.522298812866211s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13282203674316406s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1435534954071045s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1415417194366455s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14302682876586914s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19682621955871582s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14212870597839355s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13402724266052246s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.28438329696655273s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14679908752441406s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14282655715942383s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13141798973083496s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.782733917236328s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.605552673339844e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19249773025512695s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13231492042541504s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15322494506835938s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13073325157165527s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14249110221862793s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2882864475250244s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.29486727714538574s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 20.559813022613525s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12758874893188477s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15056157112121582s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14111089706420898s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14466190338134766s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.62396240234375e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.141101360321045s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15413451194763184s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.63134503364563s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.121932744979858s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.4013798236846924s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.73247218132019s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.789809465408325s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15083932876586914s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.62334132194519s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.28415703773498535s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.430511474609375e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1444091796875e-05s
INFO | --- Analysis for racai-legalnero took 309.9876022338867s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.0531158447265625e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.272289514541626s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.147125244140625e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 5.9604644775390625e-06s
INFO | --- Analysis for racai-llod-corola-we took 2.7117435932159424s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.15446758270263672s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0002841949462890625s
Extra | Recovery of all triples for PARSEME-Ro corpus took 35.596341371536255s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.7342298030853271s
Amount of data | Number of triples check for PARSEME-Ro corpus took 7.070767402648926s
Interoperability | New terms check for PARSEME-Ro corpus took 2.2798027992248535s
Versatility | Languages check for PARSEME-Ro corpus took 18.740299463272095s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.349600553512573s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.15197134017944336s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.1696157455444336s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.14085125923156738s
License | MR license check for PARSEME-Ro corpus took 0.14070439338684082s
License | HR license check for PARSEME-Ro corpus took 10.167754888534546s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.14127802848815918s
Understandability | Number of label check for PARSEME-Ro corpus took 0.18784093856811523s
Understandability | URI regex check for PARSEME-Ro corpus took 0.27289462089538574s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.1307837963104248s
Verifiability | Authors check for PARSEME-Ro corpus took 0.13156819343566895s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.13064837455749512s
Performance | Throughput check for PARSEME-Ro corpus took 10.632534980773926s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 6.794929504394531e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.15578913688659668s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.13006162643432617s
Interlinking | skos check for PARSEME-Ro corpus took 0.16215276718139648s
Interlinking | skos check for PARSEME-Ro corpus took 0.1416325569152832s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.13163375854492188s
Currency | Creation date check for PARSEME-Ro corpus took 0.273364782333374s
Currency | Modification date check for PARSEME-Ro corpus took 0.2933058738708496s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 79.64465975761414s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.14311552047729492s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.15827417373657227s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.14232206344604492s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 2.100700616836548s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23288249969482422s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 4.0579211711883545s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.13233017921447754s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.0128014087677s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 30.362478971481323s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.599318265914917s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 13.606781721115112s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.800680637359619s
Security | Sign check for PARSEME-Ro corpus took 0.14217376708984375s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.27077579498291s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.47194933891296387s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020882368087768555s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0006706714630126953s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 1.9073486328125e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.3589859008789062e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 286.8789610862732s
Availability | SPARQL endpoint availability check for RoLEX took 0.13550782203674316s
Availability | VoID file availability check for RoLEX took 0.0006349086761474609s
Extra | Recovery of all triples for RoLEX took 42.64070916175842s
Performance | Total latancy measurement for RoLEX took 0.7191338539123535s
Amount of data | Number of triples check for RoLEX took 1.7485809326171875s
Interoperability | New terms check for RoLEX took 1.7011702060699463s
Versatility | Languages check for RoLEX took 4.181029558181763s
Interpretability | Number of blank nodes check for RoLEX took 1.0628621578216553s
Interpretability | RDF structures check for RoLEX took 0.14694571495056152s
Versatility | Serialization formats check for RoLEX took 0.14328980445861816s
Availability | RDF dump link check for RoLEX took 0.13080549240112305s
License | MR license check for RoLEX took 0.1530170440673828s
License | HR license check for RoLEX took 0.1416332721710205s
Amount of data | Number of property check for RoLEX took 0.14101147651672363s
Understandability | Number of label check for RoLEX took 0.14326977729797363s
Understandability | URI regex check for RoLEX took 0.3076765537261963s
Understandability | Vocabs check for RoLEX took 0.15346121788024902s
Verifiability | Authors check for RoLEX took 0.14161205291748047s
Verifiability | Publishers check for RoLEX took 0.15688848495483398s
Performance | Throughput check for RoLEX took 10.581250190734863s
Amount of data | Check the number of entities for RoLEX took 0.00010633468627929688s
Verifiability | Contribs. check for RoLEX took 0.14179277420043945s
Interlinking | sameAs chians check for RoLEX took 0.16276073455810547s
Interlinking | skos check for RoLEX took 0.14160537719726562s
Interlinking | skos check for RoLEX took 0.13034319877624512s
Timeliness | dataset update frequency check for RoLEX took 0.14206790924072266s
Currency | Creation date check for RoLEX took 0.2866959571838379s
Currency | Modification date check for RoLEX took 0.28313374519348145s
Rep.Conc. | URIs length for RoLEX took 53.883360624313354s
Interoperability | New vocabularies check for RoLEX took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.12891173362731934s
Accuracy | Check Functional Property for RoLEX took 0.13797688484191895s
Accuracy | Check Inverse Functional Property for RoLEX took 0.1459217071533203s
Accuracy | Check Datatype consistency for RoLEX took 4.029192686080933s
Consistency | Disjoint class check for RoLEX took 0.13556766510009766s
Consistency | Check Misplaced properties for RoLEX took 2.740264415740967s
Consistency | Check Ontology hijacking for RoLEX took 8.683901309967041s
Consistency | Check Invalid usage of undefined classes for RoLEX took 1.9241676330566406s
Consistency | Check Invalid usage of undefined properties for RoLEX took 3.9245645999908447s
Conciseness | Check Extensional conciseness for RoLEX took 3.0527591705322266s
Security | Sign check for RoLEX took 0.14197587966918945s
Availability | Check URIs Dereferenciability for RoLEX took 7.35296368598938s
Completeness | Calculation of interlinking completeness for RoLEX took 0.3636147975921631s
Reputation | Calculation of the PageRank for RoLEX took 0.020815134048461914s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.4809112548828125e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 2.1457672119140625e-06s
Believability | Calculation of trust value for RoLEX took 1.2636184692382812e-05s
INFO | --- Analysis for racai-llod-rolex took 181.29337668418884s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 6.914138793945312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0003769397735595703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.25312280654907227s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.021485328674316406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.314018249511719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 4.859685182571411s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.1961669921875e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.24896669387817383s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.765655517578125e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.5717124938964844s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.029273986816406e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.25804781913757324s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.021364450454711914s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 2.765655517578125e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.3113021850585938e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.9979004859924316s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 8.654594421386719e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.27491188049316406s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.6464462280273438e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.1444091796875e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.6827290058135986s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.1560056209564209s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006463527679443359s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.58461594581604s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.7538607120513916s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.32255101203918457s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.4331789016723633s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.6285703182220459s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.2646064758300781s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.142897367477417s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.13118195533752441s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.14235711097717285s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.13039875030517578s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.15959572792053223s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.12891244888305664s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.14698243141174316s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.30004048347473145s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.1415259838104248s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.15455245971679688s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.1415996551513672s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 10.583587408065796s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 7.271766662597656e-05s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.15219974517822266s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.1329793930053711s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.13066744804382324s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.15220332145690918s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.130479097366333s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.2935755252838135s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.2944619655609131s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.8309614658355713s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 5.4836273193359375e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.1535816192626953s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.14016151428222656s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.1295175552368164s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.3603856563568115s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009630203247070312s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.2215676307678223s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.12798547744750977s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.5183103084564209s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.305447578430176s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.2561426162719727s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.6342284679412842s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.818666934967041s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.1509695053100586s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 3649.166438102722s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 1.5576388835906982s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.021924734115600586s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 8.726119995117188e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 2.1457672119140625e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.2159347534179688e-05s
INFO | --- Analysis for racai-llod-rtasc took 3792.852983236313s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.14063358306884766s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0005328655242919922s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 34.00712013244629s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.7526583671569824s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0758419036865234s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.4847791194915771s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.4358205795288086s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8475496768951416s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.13040447235107422s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.13690686225891113s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.14007925987243652s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.14095211029052734s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.510187387466431s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.15200233459472656s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.15937256813049316s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.29228711128234863s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.1309206485748291s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.1446089744567871s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.13061022758483887s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.898439884185791s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 6.842613220214844e-05s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.14281678199768066s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.1434929370880127s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.14201641082763672s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.14398980140686035s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.13162016868591309s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.3155653476715088s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.3809518814086914s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.254523992538452s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.128509521484375s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.12732768058776855s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.12809205055236816s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.7029018402099609s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.01953887939453125s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.063839435577393s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.1645050048828125s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.733625888824463s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.520259380340576s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.332920789718628s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.7832391262054443s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 2.9101991653442383s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.1510164737701416s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1636.1332972049713s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 1.349733591079712s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.022259950637817383s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.9073486328125e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.3828277587890625e-05s
INFO | --- Analysis for racai-llod-simonero took 1743.04598402977s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.2968456745147705s
Availability | VoID file availability check for Rådata nå! took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2517361640930176s
Reputation | Calculation of the PageRank for Rådata nå! took 0.027420759201049805s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0010633468627929688s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 0.00010228157043457031s
Believability | Calculation of trust value for Rådata nå! took 9.775161743164062e-06s
INFO | --- Analysis for radatana took 6.361237525939941s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 5.030632019042969e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.31558942794799805s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.838539123535156e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.2874603271484375e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 16.677637815475464s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.172325134277344e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.24731063842773438s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.0214235782623291s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.170967102050781e-05s
Believability | Calculation of trust value for Raphael Research Resource took 1.049041748046875e-05s
INFO | --- Analysis for raphaelresearchresource took 3.412902355194092s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 13.926028966903687s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.3860175609588623s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.4809112548828125e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.2636184692382812e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 29.55369520187378s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.67604780197144s
Availability | VoID file availability check for Polish LGU financial statements took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.30565905570983887s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021233320236206055s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.910064697265625e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 7.152557373046875e-06s
INFO | --- Analysis for Rb_PL_LGU took 667.5880017280579s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.25872278213500977s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.02112436294555664s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 3.0517578125e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 1.3828277587890625e-05s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 4.805011510848999s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 6.389617919921875e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.2644534111022949s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 2.7418136596679688e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 3.7405571937561035s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 8.273124694824219e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.28870153427124023s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.02268838882446289s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0009479522705078125s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.2901763916015625e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 3.7549705505371094s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.2663447856903076s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 2.7179718017578125e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 3.2809090614318848s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.9591064453125e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.2883036136627197s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.0040740966796875e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 1.2636184692382812e-05s
INFO | --- Analysis for rcahmw-periods-list took 2.8438944816589355s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 5.173683166503906e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.001039266586303711s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.25522899627685547s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020165681838989258s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.320808410644531e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.239776611328125e-05s
INFO | --- Analysis for rdf-book-mashup took 3.3560690879821777s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.076957702636719e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.24753165245056152s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020303964614868164s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 9.417533874511719e-05s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 7.867813110351562e-06s
INFO | --- Analysis for rdfize-lastfm took 2.4532759189605713s
Availability | SPARQL endpoint availability check for RDFLicense took 260.42445945739746s
Availability | VoID file availability check for RDFLicense took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.7386560440063477s
Reputation | Calculation of the PageRank for RDFLicense took 0.021170616149902344s
Interlinking | Calculation of Degree of Connection for RDFLicense took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0010581016540527344s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 4.5299530029296875e-05s
Believability | Calculation of trust value for RDFLicense took 1.1920928955078125e-05s
INFO | --- Analysis for rdflicense took 535.8651449680328s
Availability | SPARQL endpoint availability check for RDFohloh took 5.650520324707031e-05s
Availability | VoID file availability check for RDFohloh took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.2470989227294922s
Reputation | Calculation of the PageRank for RDFohloh took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 8.869171142578125e-05s
Believability | Calculation of trust value for RDFohloh took 1.2159347534179688e-05s
INFO | --- Analysis for rdfohloh took 9.575440168380737s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.5893974304199219s
Availability | VoID file availability check for Reactome RDF took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.2694697380065918s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020287513732910156s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for Reactome RDF took 1.0013580322265625e-05s
INFO | --- Analysis for reactome-rdf took 3.625619411468506s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.12402510643005371s
Availability | VoID file availability check for Rechtspraak.nl took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.2696671485900879s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.022666454315185547s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.107589721679688e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 8.106231689453125e-06s
INFO | --- Analysis for rechtspraak took 3.5024242401123047s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 8.630752563476562e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2766239643096924s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02192544937133789s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.940696716308594e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.1205673217773438e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 2.78690505027771s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.0776832103729248s
Availability | VoID file availability check for reference.data.gov.uk took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.28154754638671875s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020743370056152344s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00014925003051757812s
Believability | Calculation of trust value for reference.data.gov.uk took 1.0013580322265625e-05s
INFO | --- Analysis for reference-data-gov-uk took 2.645956039428711s
Availability | SPARQL endpoint availability check for Regiony took 4.00543212890625e-05s
Availability | VoID file availability check for Regiony took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Regiony took 0.2661550045013428s
Reputation | Calculation of the PageRank for Regiony took 0.021373271942138672s
Interlinking | Calculation of Degree of Connection for Regiony took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.24249267578125e-05s
Believability | Calculation of trust value for Regiony took 1.049041748046875e-05s
INFO | --- Analysis for regiony took 2.846261739730835s
Availability | SPARQL endpoint availability check for RELD took 0.5559461116790771s
Availability | VoID file availability check for RELD took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for RELD took 0.251554012298584s
Reputation | Calculation of the PageRank for RELD took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for RELD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RELD took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for RELD took 3.123283386230469e-05s
Believability | Calculation of trust value for RELD took 1.049041748046875e-05s
INFO | --- Analysis for RELD took 3.6762778759002686s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.2283310890197754s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.26395511627197266s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.021271705627441406s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 3.62396240234375e-05s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.239776611328125e-05s
INFO | --- Analysis for reload took 11.216766595840454s
Availability | SPARQL endpoint availability check for Land use merced dataset took 9.5367431640625e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.2362959384918213s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.239776611328125e-05s
INFO | --- Analysis for remote_Sensing took 3.032630205154419s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 0.9976797103881836s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.23796987533569336s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.363059997558594e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 1.0013580322265625e-05s
INFO | --- Analysis for renewable_energy_generators took 9.4302499294281s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.07321977615356445s
Availability | VoID file availability check for research.data.gov.uk took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.2794930934906006s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.02259206771850586s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 8.869171142578125e-05s
Believability | Calculation of trust value for research.data.gov.uk took 8.58306884765625e-06s
INFO | --- Analysis for research-data-gov-uk took 2.5714480876922607s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 7.939338684082031e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.27701687812805176s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020815372467041016s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.0517578125e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 1.1205673217773438e-05s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 2.88331937789917s
Availability | SPARQL endpoint availability check for Restaurantes took 8.082389831542969e-05s
Availability | VoID file availability check for Restaurantes took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.26205992698669434s
Reputation | Calculation of the PageRank for Restaurantes took 0.02114248275756836s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 2.9325485229492188e-05s
Believability | Calculation of trust value for Restaurantes took 1.0967254638671875e-05s
INFO | --- Analysis for restaurantes-zaragoza took 2.9009082317352295s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 8.296966552734375e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.26387691497802734s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.022561073303222656s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.461143493652344e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.239776611328125e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.016432285308838s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.06788992881774902s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.26940441131591797s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.022170066833496094s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 2.9087066650390625e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.2874603271484375e-05s
INFO | --- Analysis for revistas_turismo took 2.430022954940796s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2944934368133545s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.25058460235595703s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011014938354492188s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.239776611328125e-05s
INFO | --- Analysis for revyu took 2.6008718013763428s
Availability | SPARQL endpoint availability check for sdafsadf took 0.3346273899078369s
Availability | VoID file availability check for sdafsadf took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.26491618156433105s
Reputation | Calculation of the PageRank for sdafsadf took 0.020125389099121094s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 2.6941299438476562e-05s
Believability | Calculation of trust value for sdafsadf took 1.1920928955078125e-05s
INFO | --- Analysis for rgsdfg took 3.133993148803711s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.1484832763671875e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.27037620544433594s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.02109217643737793s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 5.173683166503906e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.3113021850585938e-05s
INFO | --- Analysis for riese took 22.64707350730896s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 8.630752563476562e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.26645565032958984s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 2.765655517578125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 1.3113021850585938e-05s
INFO | --- Analysis for rijksmuseum took 2.8643457889556885s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.24352169036865234s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0005207061767578125s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 22.565462589263916s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.48652029037475586s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 54.61261439323425s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 2.191049337387085s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 161.49608731269836s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 49.87811493873596s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.2325434684753418s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.1351475715637207s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.11211466789245605s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.09426236152648926s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.12319016456604004s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.0751566886902s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.11522579193115234s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 9.271942853927612s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.2156391143798828s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.10588860511779785s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.09273314476013184s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.11722660064697266s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.661659955978394s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 7.271766662597656e-05s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.12843751907348633s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.123579502105713s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.1650376319885254s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.10519075393676758s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.10710287094116211s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.19979619979858398s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.25195956230163574s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 80.81865382194519s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.10978364944458008s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.1012122631072998s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.09390664100646973s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 11.658214569091797s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.389021158218384s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.7880687713623047s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.10832834243774414s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 48.54209589958191s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 5.281641006469727s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.3920979499816895s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 48.81441283226013s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.7307209968566895s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.11954808235168457s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 1.0671944618225098s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.9284927845001221s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.021546602249145508s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 1.9073486328125e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 1.2636184692382812e-05s
INFO | --- Analysis for rism took 1259.150622367859s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.09480404853820801s
Availability | VoID file availability check for RISM Authority data took 0.00027561187744140625s
Extra | Recovery of all triples for RISM Authority data took 24.130077362060547s
Performance | Total latancy measurement for RISM Authority data took 0.4550786018371582s
Amount of data | Number of triples check for RISM Authority data took 60.58426880836487s
Interoperability | New terms check for RISM Authority data took 1.6422367095947266s
Versatility | Languages check for RISM Authority data took 168.0063509941101s
Interpretability | Number of blank nodes check for RISM Authority data took 50.54948329925537s
Security | Check HTTPS for RISM Authority data took 0.14742684364318848s
Interpretability | RDF structures check for RISM Authority data took 0.09673142433166504s
Versatility | Serialization formats check for RISM Authority data took 0.08519506454467773s
Availability | RDF dump link check for RISM Authority data took 0.09849095344543457s
License | MR license check for RISM Authority data took 0.12266278266906738s
License | HR license check for RISM Authority data took 300.1038770675659s
Amount of data | Number of property check for RISM Authority data took 0.09763574600219727s
Understandability | Number of label check for RISM Authority data took 9.459110975265503s
Understandability | URI regex check for RISM Authority data took 0.18712186813354492s
Understandability | Vocabs check for RISM Authority data took 0.09277510643005371s
Verifiability | Authors check for RISM Authority data took 0.09210753440856934s
Verifiability | Publishers check for RISM Authority data took 0.09932804107666016s
Performance | Throughput check for RISM Authority data took 10.370211124420166s
Amount of data | Check the number of entities for RISM Authority data took 0.0001049041748046875s
Verifiability | Contribs. check for RISM Authority data took 0.0832223892211914s
Interlinking | sameAs chians check for RISM Authority data took 1.349073886871338s
Interlinking | skos check for RISM Authority data took 0.08850717544555664s
Interlinking | skos check for RISM Authority data took 0.09943819046020508s
Timeliness | dataset update frequency check for RISM Authority data took 0.10389900207519531s
Currency | Creation date check for RISM Authority data took 0.18521499633789062s
Currency | Modification date check for RISM Authority data took 0.19234180450439453s
Rep.Conc. | URIs length for RISM Authority data took 80.56386494636536s
Interoperability | New vocabularies check for RISM Authority data took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.10858845710754395s
Accuracy | Check Functional Property for RISM Authority data took 0.0915529727935791s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.09636497497558594s
Accuracy | Check Empty annotation labels for RISM Authority data took 14.854379415512085s
Accuracy | Check White space in annotation for RISM Authority data took 2.3933515548706055s
Accuracy | Check Datatype consistency for RISM Authority data took 3.8708903789520264s
Consistency | Disjoint class check for RISM Authority data took 0.09067416191101074s
Consistency | Check Misplaced properties for RISM Authority data took 47.40940761566162s
Consistency | Check Ontology hijacking for RISM Authority data took 4.149059534072876s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.3616161346435547s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 49.872236490249634s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.8083248138427734s
Security | Sign check for RISM Authority data took 0.10452103614807129s
Availability | Check URIs Dereferenciability for RISM Authority data took 1.0217030048370361s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.9337673187255859s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020931720733642578s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 5.7220458984375e-06s
Believability | Calculation of trust value for RISM Authority data took 1.2636184692382812e-05s
INFO | --- Analysis for rism-authorities took 1078.6865479946136s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.172325134277344e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.26548171043395996s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0517578125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.239776611328125e-05s
INFO | --- Analysis for rk took 3.707446813583374s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.041034698486328125s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.6827967166900635s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002243518829345703s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-acm took 3.8686177730560303s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.04420351982116699s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.2508413791656494s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.020859241485595703s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001373291015625s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.8227436542510986s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.04388785362243652s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2511012554168701s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.021820545196533203s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00022411346435546875s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.494551658630371s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.06553030014038086s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.257596492767334s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0001685619354248047s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-cordis took 2.947803020477295s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.05092000961303711s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.23686003684997559s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00016641616821289062s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-courseware took 2.451099157333374s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.06609773635864258s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2781546115875244s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.021930456161499023s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.647804260253906e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-crime took 3.3198328018188477s
Availability | SPARQL endpoint availability check for crm took 4.0531158447265625e-05s
Availability | VoID file availability check for crm took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for crm took 0.2571721076965332s
Reputation | Calculation of the PageRank for crm took 0.020960092544555664s
Interlinking | Calculation of Degree of Connection for crm took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for crm took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for crm took 3.123283386230469e-05s
Believability | Calculation of trust value for crm took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-crm took 2.788508653640747s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0488584041595459s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.27337050437927246s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0001690387725830078s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 2.476099729537964s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.06022524833679199s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.253833532333374s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.1975250244140625e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.5112056732177734s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.042830705642700195s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0009400844573974609s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.26027488708496094s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.022484779357910156s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002334117889404297s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.5128509998321533s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04787755012512207s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.23569989204406738s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.021075963973999023s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.001016855239868164s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 8.96453857421875e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 2.4699769020080566s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.05505728721618652s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0010514259338378906s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.26790499687194824s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.655952453613281e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-deploy took 2.505537271499634s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.051644086837768555s
Availability | VoID file availability check for digitaleconomy took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.2440638542175293s
Reputation | Calculation of the PageRank for digitaleconomy took 0.022301197052001953s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.956390380859375e-05s
Believability | Calculation of trust value for digitaleconomy took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.4961600303649902s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.05460762977600098s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2840890884399414s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.0001480579376220703s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.5438830852508545s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.05016446113586426s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2762026786804199s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.458427429199219e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-ecs took 2.679562568664551s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.076957702636719e-05s
Availability | VoID file availability check for enaktingpsi took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.2746458053588867s
Reputation | Calculation of the PageRank for enaktingpsi took 0.02127861976623535s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 3.075599670410156e-05s
Believability | Calculation of trust value for enaktingpsi took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.9800734519958496s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0511927604675293s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.258594274520874s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0001842975616455078s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.5880115032196045s
Availability | SPARQL endpoint availability check for epsrc took 0.048178911209106445s
Availability | VoID file availability check for epsrc took 0.0004127025604248047s
Completeness | Calculation of interlinking completeness for epsrc took 0.27011799812316895s
Reputation | Calculation of the PageRank for epsrc took 0.020821094512939453s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.936622619628906e-05s
Believability | Calculation of trust value for epsrc took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.478720188140869s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.05507159233093262s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.2687387466430664s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.02031683921813965s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.891654968261719e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-era took 2.5050208568573s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.0539700984954834s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.25616884231567383s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.000102996826171875s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 2.6357791423797607s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 8.58306884765625e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.2726755142211914s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.0225675106048584s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 2.8133392333984375e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-foreign took 2.925478219985962s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.04393625259399414s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.26778197288513184s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.022901058197021484s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.916854858398438e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-ft took 2.494582176208496s
Availability | SPARQL endpoint availability check for fun took 0.048601627349853516s
Availability | VoID file availability check for fun took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for fun took 0.28426051139831543s
Reputation | Calculation of the PageRank for fun took 0.020977497100830078s
Interlinking | Calculation of Degree of Connection for fun took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for fun took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for fun took 7.081031799316406e-05s
Believability | Calculation of trust value for fun took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-fun took 2.4105710983276367s
Availability | SPARQL endpoint availability check for gdlc took 0.04578232765197754s
Availability | VoID file availability check for gdlc took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for gdlc took 0.24876618385314941s
Reputation | Calculation of the PageRank for gdlc took 0.021046161651611328s
Interlinking | Calculation of Degree of Connection for gdlc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.628036499023438e-05s
Believability | Calculation of trust value for gdlc took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.4374136924743652s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.0700225830078125s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.29950428009033203s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020678997039794922s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00015163421630859375s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.587059736251831s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.050888776779174805s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00041794776916503906s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2694368362426758s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001342296600341797s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-ieee took 2.511798143386841s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0349888801574707s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.27736449241638184s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02069544792175293s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00016641616821289062s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-irit took 2.4758245944976807s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.036054372787475586s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0003197193145751953s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.26215100288391113s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.152557373046875e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-italy took 2.377178192138672s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.044188499450683594s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.2579798698425293s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.022228240966796875s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 8.20159912109375e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.4683358669281006s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.06035661697387695s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0004131793975830078s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.27045130729675293s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 2.5008139610290527s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.03776049613952637s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2519071102142334s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.02217864990234375s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016355514526367188s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-kisti took 2.44950270652771s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.04637551307678223s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.26476526260375977s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00015163421630859375s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-laas took 2.535024881362915s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.037354469299316406s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.23515844345092773s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02044844627380371s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.413459777832031e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.4526028633117676s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.04856276512145996s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.2568068504333496s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020175695419311523s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015997886657714844s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-newcastle took 2.4452927112579346s
Availability | SPARQL endpoint availability check for notube took 0.050321340560913086s
Availability | VoID file availability check for notube took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for notube took 0.24719977378845215s
Reputation | Calculation of the PageRank for notube took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for notube took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for notube took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for notube took 4.267692565917969e-05s
Believability | Calculation of trust value for notube took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.467648506164551s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.05411982536315918s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004057884216308594s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.26459598541259766s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020755290985107422s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00012993812561035156s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 2.86102294921875e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.4799914360046387s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.07437705993652344s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2516324520111084s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015592575073242188s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.399869441986084s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.00020885467529296875s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.2368021011352539s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.803180456161499s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.04692649841308594s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.23592376708984375s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.022606372833251953s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.200241088867188e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-os took 2.362305164337158s
Availability | SPARQL endpoint availability check for photos took 0.05530691146850586s
Availability | VoID file availability check for photos took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for photos took 0.2644820213317871s
Reputation | Calculation of the PageRank for photos took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for photos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for photos took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for photos took 6.842613220214844e-05s
Believability | Calculation of trust value for photos took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-photos took 2.5501458644866943s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.04276704788208008s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.2651219367980957s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011229515075683594s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-pisa took 2.486374855041504s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.04115700721740723s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2677173614501953s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.02140641212463379s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00021266937255859375s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.4284071922302246s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.04693198204040527s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.2643153667449951s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020601987838745117s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0001423358917236328s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-resex took 2.4283435344696045s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.04403090476989746s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.276094913482666s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.250640869140625e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.5255980491638184s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.04643559455871582s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2727396488189697s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.021137714385986328s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0001239776611328125s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-roma took 2.4412131309509277s
Availability | SPARQL endpoint availability check for roni took 0.05182838439941406s
Availability | VoID file availability check for roni took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for roni took 0.2506117820739746s
Reputation | Calculation of the PageRank for roni took 0.02109217643737793s
Interlinking | Calculation of Degree of Connection for roni took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for roni took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for roni took 3.075599670410156e-05s
Believability | Calculation of trust value for roni took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-roni took 2.4132797718048096s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.03826165199279785s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.25618863105773926s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020987987518310547s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002224445343017578s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.489933729171753s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.03568696975708008s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.2583892345428467s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010919570922851562s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.40401029586792s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.0518031120300293s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.2363910675048828s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.021768808364868164s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.608268737792969e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 2.481074810028076s
Availability | SPARQL endpoint availability check for webconf took 0.03735828399658203s
Availability | VoID file availability check for webconf took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for webconf took 0.256605863571167s
Reputation | Calculation of the PageRank for webconf took 0.021053552627563477s
Interlinking | Calculation of Degree of Connection for webconf took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for webconf took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010204315185546875s
Believability | Calculation of trust value for webconf took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-webconf took 12.688540935516357s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.06818866729736328s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004067420959472656s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.2486894130706787s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.021784067153930664s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 6.699562072753906e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-webscience took 2.4715476036071777s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.049835920333862305s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.25806498527526855s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002124309539794922s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.447523832321167s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.03568696975708008s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.28858113288879395s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02028679847717285s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.131431579589844e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 2.5212926864624023s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 8.559226989746094e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.25426793098449707s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.022006511688232422s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for RKB Explorer Data took 1.0728836059570312e-05s
INFO | --- Analysis for rkb_explorer_data took 2.9429008960723877s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.5509967803955078s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.2773122787475586s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.021317720413208008s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 7.319450378417969e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.0967254638671875e-05s
INFO | --- Analysis for roceeh-road took 3.8634777069091797s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.458427429199219e-05s
Availability | VoID file availability check for The Rosetta Project took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.2832634449005127s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.020923137664794922s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.695487976074219e-05s
Believability | Calculation of trust value for The Rosetta Project took 1.3113021850585938e-05s
INFO | --- Analysis for rosetta-project took 3.1362950801849365s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 8.368492126464844e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.255155086517334s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.0040740966796875e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.2874603271484375e-05s
INFO | --- Analysis for ROSHANI took 4.055298328399658s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.172325134277344e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.24196338653564453s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02193760871887207s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.8623809814453125e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.049041748046875e-05s
INFO | --- Analysis for ROSHANI_SAHU took 2.39510440826416s
Availability | SPARQL endpoint availability check for x took 4.458427429199219e-05s
Availability | VoID file availability check for x took 0.005123615264892578s
Completeness | Calculation of interlinking completeness for x took 0.26873111724853516s
Reputation | Calculation of the PageRank for x took 0.020876169204711914s
Interlinking | Calculation of Degree of Connection for x took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for x took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for x took 3.790855407714844e-05s
Believability | Calculation of trust value for x took 1.1205673217773438e-05s
INFO | --- Analysis for Rozprawa,_artykuł took 2.329798936843872s
Availability | SPARQL endpoint availability check for Rpm Find took 8.344650268554688e-05s
Availability | VoID file availability check for Rpm Find took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.24006366729736328s
Reputation | Calculation of the PageRank for Rpm Find took 0.022200584411621094s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0008203983306884766s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.4809112548828125e-05s
Believability | Calculation of trust value for Rpm Find took 1.1920928955078125e-05s
INFO | --- Analysis for rpm_find took 2.940800905227661s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.4345855712890625e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.265094518661499s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.020554780960083008s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.67572021484375e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.1205673217773438e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.8870675563812256s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 8.511543273925781e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.009539127349853516s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2383716106414795s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020772695541381836s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.176399230957031e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 1.0728836059570312e-05s
INFO | --- Analysis for rubentaelman took 2.963064670562744s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.315376281738281e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.27612924575805664s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02290177345275879s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 9.274482727050781e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.1205673217773438e-05s
INFO | --- Analysis for rubenverborgh took 3.0068583488464355s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.116450548172s
Availability | VoID file availability check for Russian Universities Specialities took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.7639262676239014s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.02108311653137207s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.2438507080078125e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.1682510375976562e-05s
INFO | --- Analysis for russian-universities-specialities took 677.3330492973328s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.2438507080078125e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.6851403713226318s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.02287769317626953s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 2.956390380859375e-05s
Believability | Calculation of trust value for RuThes Cloud took 1.33514404296875e-05s
INFO | --- Analysis for ruthes took 3.800612688064575s
Availability | SPARQL endpoint availability check for RxNorm took 4.1961669921875e-05s
Availability | VoID file availability check for RxNorm took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for RxNorm took 0.2735629081726074s
Reputation | Calculation of the PageRank for RxNorm took 0.022232532501220703s
Interlinking | Calculation of Degree of Connection for RxNorm took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RxNorm took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.6716461181640625e-05s
Believability | Calculation of trust value for RxNorm took 1.1920928955078125e-05s
INFO | --- Analysis for rxnorm took 2.9482712745666504s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.1421191692352295s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.24181222915649414s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.0279159545898438e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.2874603271484375e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 9.983703851699829s
Availability | SPARQL endpoint availability check for SALDO took 6.723403930664062e-05s
Availability | VoID file availability check for SALDO took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for SALDO took 0.252760648727417s
Reputation | Calculation of the PageRank for SALDO took 0.020984888076782227s
Interlinking | Calculation of Degree of Connection for SALDO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.695487976074219e-05s
Believability | Calculation of trust value for SALDO took 1.1920928955078125e-05s
INFO | --- Analysis for saldo took 2.959792375564575s
Availability | SPARQL endpoint availability check for SALDO-RDF took 0.9225771427154541s
Availability | VoID file availability check for SALDO-RDF took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.263408899307251s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.504753112792969e-05s
Believability | Calculation of trust value for SALDO-RDF took 1.2159347534179688e-05s
INFO | --- Analysis for saldo-rdf took 5.813780784606934s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6270792484283447s
Availability | VoID file availability check for SALDOM-RDF took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.25461673736572266s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.24249267578125e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.1205673217773438e-05s
INFO | --- Analysis for saldom-rdf took 4.76606822013855s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.4345855712890625e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2619669437408447s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.021658658981323242s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010561943054199219s
Believability | Calculation of trust value for Salzburgerland DE took 1.2636184692382812e-05s
INFO | --- Analysis for salzburgerland-com-de took 2.9764277935028076s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.9114227294921875e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.26125240325927734s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.0001010894775390625s
Believability | Calculation of trust value for Salzburgerland EN took 1.239776611328125e-05s
INFO | --- Analysis for salzburgerland-com-en took 2.851651906967163s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.506111145019531e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.25961875915527344s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010085105895996094s
Believability | Calculation of trust value for Salzburgerland IT took 1.1920928955078125e-05s
INFO | --- Analysis for salzburgerland-com-it took 2.830132007598877s
Availability | SPARQL endpoint availability check for sameAs.org took 4.124641418457031e-05s
Availability | VoID file availability check for sameAs.org took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.2504615783691406s
Reputation | Calculation of the PageRank for sameAs.org took 0.021716833114624023s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 2.86102294921875e-05s
Believability | Calculation of trust value for sameAs.org took 1.2636184692382812e-05s
INFO | --- Analysis for sameas-org took 2.918731927871704s
Availability | SPARQL endpoint availability check for sandrart.net took 0.00011157989501953125s
Availability | VoID file availability check for sandrart.net took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.2788076400756836s
Reputation | Calculation of the PageRank for sandrart.net took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.246566772460938e-05s
Believability | Calculation of trust value for sandrart.net took 1.1444091796875e-05s
INFO | --- Analysis for sandrart-net took 3.67073655128479s
Availability | SPARQL endpoint availability check for Taxons  took 0.1783597469329834s
Availability | VoID file availability check for Taxons  took 0.0004737377166748047s
Extra | Recovery of all triples for Taxons  took 18.488799571990967s
Performance | Total latancy measurement for Taxons  took 0.43114519119262695s
Amount of data | Number of triples check for Taxons  took 2.1871137619018555s
Interoperability | New terms check for Taxons  took 1.879709005355835s
Versatility | Languages check for Taxons  took 38.25869536399841s
Interpretability | Number of blank nodes check for Taxons  took 0.6240532398223877s
Security | Check HTTPS for Taxons  took 0.19585466384887695s
Interpretability | RDF structures check for Taxons  took 0.7212483882904053s
Versatility | Serialization formats check for Taxons  took 0.4757423400878906s
Availability | RDF dump link check for Taxons  took 0.24955463409423828s
License | MR license check for Taxons  took 1.3136041164398193s
License | HR license check for Taxons  took 1.8585219383239746s
Amount of data | Number of property check for Taxons  took 0.09158086776733398s
Understandability | Number of label check for Taxons  took 2.318253993988037s
Understandability | URI regex check for Taxons  took 0.6384527683258057s
Understandability | Vocabs check for Taxons  took 0.2205190658569336s
Verifiability | Authors check for Taxons  took 0.09026932716369629s
Verifiability | Publishers check for Taxons  took 0.0888826847076416s
Performance | Throughput check for Taxons  took 10.43583083152771s
Amount of data | Check the number of entities for Taxons  took 8.296966552734375e-05s
Verifiability | Contribs. check for Taxons  took 0.0913398265838623s
Interlinking | sameAs chians check for Taxons  took 0.1221773624420166s
Interlinking | skos check for Taxons  took 0.12347126007080078s
Interlinking | skos check for Taxons  took 0.0864553451538086s
Timeliness | dataset update frequency check for Taxons  took 0.38336706161499023s
Currency | Creation date check for Taxons  took 0.17135882377624512s
Currency | Modification date check for Taxons  took 0.22260499000549316s
Rep.Conc. | URIs length for Taxons  took 7.9346747398376465s
Interoperability | New vocabularies check for Taxons  took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.10064005851745605s
Accuracy | Check Functional Property for Taxons  took 0.308696985244751s
Accuracy | Check Inverse Functional Property for Taxons  took 0.2947216033935547s
Accuracy | Check Empty annotation labels for Taxons  took 3.3841373920440674s
Accuracy | Check White space in annotation for Taxons  took 0.3000187873840332s
Accuracy | Check Datatype consistency for Taxons  took 0.2637317180633545s
Consistency | Disjoint class check for Taxons  took 0.11765432357788086s
Consistency | Check Misplaced properties for Taxons  took 3.7155966758728027s
Consistency | Misplaced classes for Taxons  took 0.9234147071838379s
Consistency | Check Ontology hijacking for Taxons  took 3.6293866634368896s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.3645861148834229s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.0299389362335205s
Conciseness | Check Extensional conciseness for Taxons  took 0.2806363105773926s
Conciseness | Check Intensional conciseness for Taxons  took 0.18216633796691895s
Security | Sign check for Taxons  took 0.7611148357391357s
Availability | Check URIs Dereferenciability for Taxons  took 1925.6201074123383s
Completeness | Calculation of interlinking completeness for Taxons  took 0.31973886489868164s
Reputation | Calculation of the PageRank for Taxons  took 0.021754026412963867s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Taxons  took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 5.0067901611328125e-06s
Believability | Calculation of trust value for Taxons  took 1.1920928955078125e-05s
INFO | --- Analysis for sandre took 2105.976994037628s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.0163300037384033s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.2781689167022705s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.552436828613281e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.0728836059570312e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 4.93317723274231s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 265.0653028488159s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0008351802825927734s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.29056382179260254s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.0531158447265625e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.049041748046875e-05s
INFO | --- Analysis for santillana_guide_dataset took 671.9426794052124s
Availability | SPARQL endpoint availability check for SATAR test  took 8.511543273925781e-05s
Availability | VoID file availability check for SATAR test  took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.2517235279083252s
Reputation | Calculation of the PageRank for SATAR test  took 0.02185821533203125s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.9802322387695312e-05s
Believability | Calculation of trust value for SATAR test  took 1.1682510375976562e-05s
INFO | --- Analysis for SATAR_test took 6.379256010055542s
Availability | SPARQL endpoint availability check for SCBG Data took 21.510550498962402s
Availability | VoID file availability check for SCBG Data took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.6951854228973389s
Reputation | Calculation of the PageRank for SCBG Data took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 7.700920104980469e-05s
Believability | Calculation of trust value for SCBG Data took 1.2159347534179688e-05s
INFO | --- Analysis for SCBG-Data took 55.427820444107056s
Availability | SPARQL endpoint availability check for schema.org took 4.100799560546875e-05s
Availability | VoID file availability check for schema.org took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for schema.org took 0.2786870002746582s
Reputation | Calculation of the PageRank for schema.org took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for schema.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for schema.org took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.218650817871094e-05s
Believability | Calculation of trust value for schema.org took 1.239776611328125e-05s
INFO | --- Analysis for schema-org took 2.8973939418792725s
Availability | SPARQL endpoint availability check for Schemantra took 8.7738037109375e-05s
Availability | VoID file availability check for Schemantra took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Schemantra took 0.28609132766723633s
Reputation | Calculation of the PageRank for Schemantra took 0.02120351791381836s
Interlinking | Calculation of Degree of Connection for Schemantra took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Schemantra took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Schemantra took 2.7894973754882812e-05s
Believability | Calculation of trust value for Schemantra took 1.239776611328125e-05s
INFO | --- Analysis for Schemantra took 2.7806572914123535s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 0.14310050010681152s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.2742476463317871s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0009586811065673828s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.695487976074219e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.1682510375976562e-05s
INFO | --- Analysis for schemapedia took 2.641983985900879s
Availability | SPARQL endpoint availability check for scholarlydata took 4.124641418457031e-05s
Availability | VoID file availability check for scholarlydata took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.24608111381530762s
Reputation | Calculation of the PageRank for scholarlydata took 0.02890777587890625s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0014846324920654297s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 4.506111145019531e-05s
Believability | Calculation of trust value for scholarlydata took 9.775161743164062e-06s
INFO | --- Analysis for scholarlydata took 2.875647783279419s
Availability | SPARQL endpoint availability check for Scholarometer took 5.7220458984375e-05s
Availability | VoID file availability check for Scholarometer took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.28168249130249023s
Reputation | Calculation of the PageRank for Scholarometer took 0.020531892776489258s
Interlinking | Calculation of Degree of Connection for Scholarometer took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.249282836914062e-05s
Believability | Calculation of trust value for Scholarometer took 1.33514404296875e-05s
INFO | --- Analysis for scholarometer took 7.870555400848389s
Availability | SPARQL endpoint availability check for Science Commons took 4.0531158447265625e-05s
Availability | VoID file availability check for Science Commons took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Science Commons took 0.28821802139282227s
Reputation | Calculation of the PageRank for Science Commons took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for Science Commons took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Science Commons took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Science Commons took 2.765655517578125e-05s
Believability | Calculation of trust value for Science Commons took 1.2874603271484375e-05s
INFO | --- Analysis for science_commons took 2.8926520347595215s
Availability | SPARQL endpoint availability check for ScienceWise took 0.00014400482177734375s
Availability | VoID file availability check for ScienceWise took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.25072312355041504s
Reputation | Calculation of the PageRank for ScienceWise took 0.02039027214050293s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 2.7179718017578125e-05s
Believability | Calculation of trust value for ScienceWise took 1.1920928955078125e-05s
INFO | --- Analysis for sciencewise took 2.939716339111328s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.291534423828125e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.2457418441772461s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 4.553794860839844e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 9.059906005859375e-06s
INFO | --- Analysis for scoreboard took 4.530435800552368s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.1961669921875e-05s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007710456848144531s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.26325058937072754s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.528594970703125e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.3113021850585938e-05s
INFO | --- Analysis for SDDEC took 26.83355975151062s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.1484832763671875e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0009427070617675781s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.28502583503723145s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.02291107177734375s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.0517578125e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 8.106231689453125e-06s
INFO | --- Analysis for SDG took 3.6177895069122314s
Availability | SPARQL endpoint availability check for sears.com took 4.100799560546875e-05s
Availability | VoID file availability check for sears.com took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for sears.com took 0.2552821636199951s
Reputation | Calculation of the PageRank for sears.com took 0.02103877067565918s
Interlinking | Calculation of Degree of Connection for sears.com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.222724914550781e-05s
Believability | Calculation of trust value for sears.com took 1.2159347534179688e-05s
INFO | --- Analysis for sears took 5.056018114089966s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.06378436088562012s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.24320626258850098s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.021324634552001953s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.440017700195312e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.775161743164062e-06s
INFO | --- Analysis for sec-rdfabout took 2.6372647285461426s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.994205236434937s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007793903350830078s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.26696252822875977s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.678436279296875e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.3828277587890625e-05s
INFO | --- Analysis for secold took 168.0518355369568s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 5.4836273193359375e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.3482320308685303s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.86102294921875e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 1.3828277587890625e-05s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 2.9989871978759766s
Availability | SPARQL endpoint availability check for semanlink took 4.4345855712890625e-05s
Availability | VoID file availability check for semanlink took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for semanlink took 0.281574010848999s
Reputation | Calculation of the PageRank for semanlink took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00013875961303710938s
Believability | Calculation of trust value for semanlink took 1.33514404296875e-05s
INFO | --- Analysis for semanlink took 3.5120420455932617s
Availability | SPARQL endpoint availability check for Semantic Library took 8.797645568847656e-05s
Availability | VoID file availability check for Semantic Library took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.2847120761871338s
Reputation | Calculation of the PageRank for Semantic Library took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for Semantic Library took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 2.86102294921875e-05s
Believability | Calculation of trust value for Semantic Library took 1.2636184692382812e-05s
INFO | --- Analysis for semantic-library took 2.98224139213562s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 3.981590270996094e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.27683472633361816s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.6716461181640625e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 1.7404556274414062e-05s
INFO | --- Analysis for semantic-profiling-network took 2.911823272705078s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.09234619140625s
Availability | VoID file availability check for Semantic Universe Data took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.2629997730255127s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.86102294921875e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.239776611328125e-05s
INFO | --- Analysis for semantic-universe took 2.4329326152801514s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.18765377998352s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.27214670181274414s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011301040649414062s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.2636184692382812e-05s
INFO | --- Analysis for semantic-web-dog-food took 82.71158981323242s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 5.078315734863281e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.25138282775878906s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.220008850097656e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 5.7220458984375e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.021117925643921s
Availability | SPARQL endpoint availability check for semantic-web-journal took 6.628036499023438e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2734553813934326s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.020684003829956055s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.075599670410156e-05s
Believability | Calculation of trust value for semantic-web-journal took 1.3589859008789062e-05s
INFO | --- Analysis for semantic-web-journal took 2.9348487854003906s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 6.4849853515625e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.2533538341522217s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0009491443634033203s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 9.560585021972656e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 1.0013580322265625e-05s
INFO | --- Analysis for semantic-xbrl took 3.352139711380005s
Availability | SPARQL endpoint availability check for Semantic Bible took 8.606910705566406e-05s
Availability | VoID file availability check for Semantic Bible took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.26315808296203613s
Reputation | Calculation of the PageRank for Semantic Bible took 0.02176809310913086s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 4.839897155761719e-05s
Believability | Calculation of trust value for Semantic Bible took 1.2874603271484375e-05s
INFO | --- Analysis for semantic_bible took 2.827902317047119s
Availability | SPARQL endpoint availability check for SemanticQuran took 6.962105989456177s
Availability | VoID file availability check for SemanticQuran took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.25475358963012695s
Reputation | Calculation of the PageRank for SemanticQuran took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 6.67572021484375e-05s
Believability | Calculation of trust value for SemanticQuran took 1.049041748046875e-05s
INFO | --- Analysis for semanticquran took 16.063642978668213s
Availability | SPARQL endpoint availability check for SemanticTweet took 6.151199340820312e-05s
Availability | VoID file availability check for SemanticTweet took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.27962660789489746s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02084946632385254s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.340576171875e-05s
Believability | Calculation of trust value for SemanticTweet took 1.1920928955078125e-05s
INFO | --- Analysis for semantictweet took 2.6570985317230225s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.1484832763671875e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.2769010066986084s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.082389831542969e-05s
Believability | Calculation of trust value for semanticweb.org took 1.0251998901367188e-05s
INFO | --- Analysis for semanticweb-org took 22.660196781158447s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.08737015724182129s
Availability | VoID file availability check for Semantic CrunchBase took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.29704809188842773s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.270408630371094e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.049041748046875e-05s
INFO | --- Analysis for semsol-crunchbase took 2.4960172176361084s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.172325134277344e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.27002620697021484s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.021712303161621094s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 2.8848648071289062e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 5.9604644775390625e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.855600595474243s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2651493549346924s
Availability | VoID file availability check for SentimentWortschatz took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.26508474349975586s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020730972290039062s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 3.981590270996094e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.2636184692382812e-05s
INFO | --- Analysis for sentiws took 3.405338764190674s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.02760601043701s
Availability | VoID file availability check for seoul-bike-data took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.2706482410430908s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.020750761032104492s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.600120544433594e-05s
Believability | Calculation of trust value for seoul-bike-data took 7.152557373046875e-06s
INFO | --- Analysis for seoul-bike-data took 72.63222551345825s
Availability | SPARQL endpoint availability check for Serendipity took 8.167959451675415s
Availability | VoID file availability check for Serendipity took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Serendipity took 0.27249860763549805s
Reputation | Calculation of the PageRank for Serendipity took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Serendipity took 6.771087646484375e-05s
Believability | Calculation of trust value for Serendipity took 7.3909759521484375e-06s
INFO | --- Analysis for serendipity took 17.103749752044678s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 8.535385131835938e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.2524726390838623s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.24249267578125e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.1920928955078125e-05s
INFO | --- Analysis for Sherry_Wine took 2.401870012283325s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.3392181396484375e-05s
Availability | VoID file availability check for Sherry Wine took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.2400209903717041s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.9087066650390625e-05s
Believability | Calculation of trust value for Sherry Wine took 8.821487426757812e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.362760066986084s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.1799769401550293s
Availability | VoID file availability check for Shoah victims? names took 0.8348479270935059s
Extra | Recovery of all triples for Shoah victims? names took 0.8654143810272217s
Performance | Total latancy measurement for Shoah victims? names took 0.44167327880859375s
Amount of data | Number of triples check for Shoah victims? names took 1.3346564769744873s
Interoperability | New terms check for Shoah victims? names took 1.646150827407837s
Versatility | Languages check for Shoah victims? names took 15.885622501373291s
Interpretability | Number of blank nodes check for Shoah victims? names took 1.603996753692627s
Security | Check HTTPS for Shoah victims? names took 0.23441815376281738s
Interpretability | RDF structures check for Shoah victims? names took 0.21690106391906738s
Versatility | Serialization formats check for Shoah victims? names took 0.2707862854003906s
Availability | RDF dump link check for Shoah victims? names took 0.17765474319458008s
License | MR license check for Shoah victims? names took 0.3743429183959961s
License | HR license check for Shoah victims? names took 7.199328660964966s
Amount of data | Number of property check for Shoah victims? names took 0.11618638038635254s
Understandability | Number of label check for Shoah victims? names took 0.891019344329834s
Understandability | URI regex check for Shoah victims? names took 0.4292774200439453s
Understandability | Vocabs check for Shoah victims? names took 0.09947085380554199s
Verifiability | Authors check for Shoah victims? names took 0.16088056564331055s
Verifiability | Publishers check for Shoah victims? names took 0.15959858894348145s
Performance | Throughput check for Shoah victims? names took 10.256785869598389s
Amount of data | Check the number of entities for Shoah victims? names took 0.00011086463928222656s
Verifiability | Contribs. check for Shoah victims? names took 0.10064530372619629s
Interlinking | sameAs chians check for Shoah victims? names took 0.10020089149475098s
Interlinking | skos check for Shoah victims? names took 0.21254634857177734s
Interlinking | skos check for Shoah victims? names took 0.07591676712036133s
Timeliness | dataset update frequency check for Shoah victims? names took 0.21686267852783203s
Currency | Creation date check for Shoah victims? names took 0.15458917617797852s
Currency | Modification date check for Shoah victims? names took 0.16948270797729492s
Rep.Conc. | URIs length for Shoah victims? names took 2.2412073612213135s
Interoperability | New vocabularies check for Shoah victims? names took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.0813283920288086s
Accuracy | Check Functional Property for Shoah victims? names took 0.07419896125793457s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.0625452995300293s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.2745640277862549s
Accuracy | Check White space in annotation for Shoah victims? names took 0.02798914909362793s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.0287325382232666s
Consistency | Disjoint class check for Shoah victims? names took 0.16257095336914062s
Consistency | Check Misplaced properties for Shoah victims? names took 1.8240511417388916s
Consistency | Misplaced classes for Shoah victims? names took 0.1587672233581543s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.5799260139465332s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.2606887817382812s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.1560935974121094s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.0325169563293457s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.12404608726501465s
Security | Sign check for Shoah victims? names took 0.5020720958709717s
Availability | Check URIs Dereferenciability for Shoah victims? names took 849.5912506580353s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.4918336868286133s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.022750377655029297s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 6.008148193359375e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 5.2928924560546875e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.9073486328125e-06s
Believability | Calculation of trust value for Shoah victims? names took 1.1444091796875e-05s
INFO | --- Analysis for shoah-victims-names took 959.1358413696289s
Availability | SPARQL endpoint availability check for Person took 5.221366882324219e-05s
Availability | VoID file availability check for Person took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Person took 0.2476034164428711s
Reputation | Calculation of the PageRank for Person took 0.02087879180908203s
Interlinking | Calculation of Degree of Connection for Person took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Person took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Person took 3.600120544433594e-05s
Believability | Calculation of trust value for Person took 1.2874603271484375e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.783174991607666s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.029273986816406e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.26731204986572266s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.0222320556640625s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.1920928955078125e-05s
INFO | --- Analysis for Shutterstock took 2.288144826889038s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 8.058547973632812e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.25275468826293945s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.022252321243286133s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 2.9087066650390625e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 1.1205673217773438e-05s
INFO | --- Analysis for simile_data_collection took 3.347663640975952s
Availability | SPARQL endpoint availability check for SIMPLE took 4.6253204345703125e-05s
Availability | VoID file availability check for SIMPLE took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.2645599842071533s
Reputation | Calculation of the PageRank for SIMPLE took 0.0210573673248291s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.8160552978515625e-05s
Believability | Calculation of trust value for SIMPLE took 1.0967254638671875e-05s
INFO | --- Analysis for simple took 7.762940168380737s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.949360370635986s
Availability | VoID file availability check for SITC-V4 took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.25471019744873047s
Reputation | Calculation of the PageRank for SITC-V4 took 0.022717714309692383s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.218650817871094e-05s
Believability | Calculation of trust value for SITC-V4 took 8.58306884765625e-06s
INFO | --- Analysis for sitc-v4 took 124.77361392974854s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 8.7738037109375e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.2761702537536621s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.022204160690307617s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.029273986816406e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.2874603271484375e-05s
INFO | --- Analysis for sli_galnet_rdf took 13.349981307983398s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.076957702636719e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.2431507110595703s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 2.765655517578125e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.2636184692382812e-05s
INFO | --- Analysis for slideshare2rdf took 2.8122220039367676s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 3.9577484130859375e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.2557816505432129s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.123283386230469e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 1.239776611328125e-05s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.858393907546997s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.37120771408081055s
Availability | VoID file availability check for Linked Stage Graph took 0.0005061626434326172s
Extra | Recovery of all triples for Linked Stage Graph took 1.7583017349243164s
Performance | Total latancy measurement for Linked Stage Graph took 1.0203464031219482s
Amount of data | Number of triples check for Linked Stage Graph took 0.21750783920288086s
Interoperability | New terms check for Linked Stage Graph took 1.6133651733398438s
Versatility | Languages check for Linked Stage Graph took 0.6576590538024902s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.2677898406982422s
Security | Check HTTPS for Linked Stage Graph took 0.1355576515197754s
Interpretability | RDF structures check for Linked Stage Graph took 0.27590155601501465s
Versatility | Serialization formats check for Linked Stage Graph took 0.26270008087158203s
Availability | RDF dump link check for Linked Stage Graph took 0.19853830337524414s
License | MR license check for Linked Stage Graph took 0.24542570114135742s
License | HR license check for Linked Stage Graph took 1.7613646984100342s
Amount of data | Number of property check for Linked Stage Graph took 0.2083723545074463s
Understandability | Number of label check for Linked Stage Graph took 0.2605459690093994s
Understandability | URI regex check for Linked Stage Graph took 0.5373539924621582s
Understandability | Vocabs check for Linked Stage Graph took 0.21523451805114746s
Verifiability | Authors check for Linked Stage Graph took 0.22180747985839844s
Verifiability | Publishers check for Linked Stage Graph took 0.19585299491882324s
Performance | Throughput check for Linked Stage Graph took 10.412678956985474s
Amount of data | Check the number of entities for Linked Stage Graph took 3.266334533691406e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.2181243896484375s
Interlinking | sameAs chians check for Linked Stage Graph took 0.287900447845459s
Interlinking | skos check for Linked Stage Graph took 0.22381210327148438s
Interlinking | skos check for Linked Stage Graph took 0.20606327056884766s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.2617621421813965s
Currency | Creation date check for Linked Stage Graph took 0.4015810489654541s
Currency | Modification date check for Linked Stage Graph took 0.41478419303894043s
Rep.Conc. | URIs length for Linked Stage Graph took 1.5586292743682861s
Interoperability | New vocabularies check for Linked Stage Graph took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.20045995712280273s
Accuracy | Check Functional Property for Linked Stage Graph took 0.20458459854125977s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.21308040618896484s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.851902961730957s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.02347731590270996s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.02703571319580078s
Consistency | Disjoint class check for Linked Stage Graph took 0.19000887870788574s
Consistency | Check Misplaced properties for Linked Stage Graph took 0.9386584758758545s
Consistency | Misplaced classes for Linked Stage Graph took 0.5312099456787109s
Consistency | Check Ontology hijacking for Linked Stage Graph took 1.9862422943115234s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.2649791240692139s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.7511482238769531s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.025728940963745117s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.5219395160675049s
Security | Sign check for Linked Stage Graph took 0.3157477378845215s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 1217.8746502399445s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.9779374599456787s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.02184152603149414s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 5.817413330078125e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.3113021850585938e-05s
INFO | --- Analysis for slod took 1288.1183686256409s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.1961669921875e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.6765894889831543s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.023167848587036133s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.0994415283203125e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.2636184692382812e-05s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 4.112717390060425s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.5909411907196045s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0005028247833251953s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 113.66043162345886s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9367034435272217s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.651150941848755s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.271082162857056s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.21829748153687s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.120023250579834s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.24193191528320312s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 10.475111961364746s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.2866783142089844s
License | MR license check for Smart Points Of Interest @PSNC took 0.7433230876922607s
License | HR license check for Smart Points Of Interest @PSNC took 300.1817138195038s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.19693732261657715s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.337522029876709s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.9701180458068848s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.4340977668762207s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.19633841514587402s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.22476673126220703s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.361170530319214s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 7.224082946777344e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.18370676040649414s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.18650388717651367s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.5277783870697021s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4378800392150879s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 5.208151578903198s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.4871554374694824s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.25490665435791016s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 157.68554663658142s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.18517184257507324s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.3637254238128662s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.3605799674987793s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 44.8670494556427s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.6372101306915283s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.5960092544555664s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.1820676326751709s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 87.37372398376465s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.345872640609741s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 36.87948250770569s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.33585786819458s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 88.18208956718445s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.708676815032959s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5494036674499512s
Security | Sign check for Smart Points Of Interest @PSNC took 1.2480676174163818s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 14.278280973434448s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.3379018306732178s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00012087821960449219s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 9.298324584960938e-06s
INFO | --- Analysis for Smart_POI_dataset took 2304.915025472641s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.528949022293091s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0009205341339111328s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.2640721797943115s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 4.172325134277344e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 6.9141387939453125e-06s
INFO | --- Analysis for smartlink took 13.110682010650635s
Availability | SPARQL endpoint availability check for SNIK took 9.589821815490723s
Availability | VoID file availability check for SNIK took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for SNIK took 0.24499845504760742s
Reputation | Calculation of the PageRank for SNIK took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for SNIK took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.009506225585938e-05s
Believability | Calculation of trust value for SNIK took 7.867813110351562e-06s
INFO | --- Analysis for snik took 61.012144327163696s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.076957702636719e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.2662982940673828s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.170967102050781e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 8.106231689453125e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 3.0704798698425293s
Availability | SPARQL endpoint availability check for SocialLink took 79.29638409614563s
Availability | VoID file availability check for SocialLink took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for SocialLink took 0.28114986419677734s
Reputation | Calculation of the PageRank for SocialLink took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.772445678710938e-05s
Believability | Calculation of trust value for SocialLink took 1.2636184692382812e-05s
INFO | --- Analysis for SocialLink took 167.81267857551575s
Availability | SPARQL endpoint availability check for SocialLink took 7.05718994140625e-05s
Availability | VoID file availability check for SocialLink took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for SocialLink took 0.6768770217895508s
Reputation | Calculation of the PageRank for SocialLink took 0.02240586280822754s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0010695457458496094s
Interlinking | Calculation of Clustering coefficient for SocialLink took 3.528594970703125e-05s
Believability | Calculation of trust value for SocialLink took 1.2636184692382812e-05s
INFO | --- Analysis for sociallink took 3.6795554161071777s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 8.678436279296875e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.2642550468444824s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.02097463607788086s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 2.9325485229492188e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.2636184692382812e-05s
INFO | --- Analysis for SocialRoles took 20.31420874595642s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.14524149894714355s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0006632804870605469s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 15.033536672592163s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.47018933296203613s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.15667414665222168s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.4699068069458008s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.40854692459106445s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.17594122886657715s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.3150451183319092s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.09496569633483887s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.09546971321105957s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7184796333312988s
License | MR license check for Social Semantic Web Thesaurus took 0.09861874580383301s
License | HR license check for Social Semantic Web Thesaurus took 0.09409594535827637s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.08823418617248535s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.08578610420227051s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.17798876762390137s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.09359025955200195s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.08789992332458496s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.09476757049560547s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.601134538650513s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 7.200241088867188e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.08965110778808594s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.08955097198486328s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.09687614440917969s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.08101439476013184s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.1045527458190918s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.2036147117614746s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.17275762557983398s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.4011688232421875s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 0.6649541854858398s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.08748745918273926s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.09750795364379883s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.10256218910217285s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4167606830596924s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012380599975585938s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.09499788284301758s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.2882678508758545s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.09444904327392578s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.031193971633911s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.472036600112915s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.0001461505889892578s
Security | Sign check for Social Semantic Web Thesaurus took 0.08728432655334473s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 90.9730544090271s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.3056960105895996s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020171642303466797s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 8.654594421386719e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.6266176700592041s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.33514404296875e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 274.9087743759155s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1822948455810547s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0002319812774658203s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 130.0145127773285s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9867105484008789s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.610976457595825s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.083058595657349s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.22472524642944s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.189427137374878s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3027682304382324s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.906835317611694s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.26384425163269043s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.6906113624572754s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.21718549728394s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21391701698303223s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.8140504360198975s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.8324475288391113s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.46563076972961426s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.22392511367797852s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.22997570037841797s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.401973009109497s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.62396240234375e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19737553596496582s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21834182739257812s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5264289379119873s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4463460445404053s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.837029218673706s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.46013450622558594s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2507445812225342s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 157.22257804870605s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18760132789611816s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.40900087356567383s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4065742492675781s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 42.79265570640564s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6587893962860107s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.5860860347747803s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18216753005981445s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 87.67666578292847s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.42273998260498s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 34.53597331047058s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.3288297653198242s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 89.41857743263245s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6994190216064453s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.7658226490020752s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0407342910766602s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 16.271997451782227s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3417494297027588s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for Soil_maps took 2312.6346259117126s
Availability | SPARQL endpoint availability check for terrorrist ontology took 6.723403930664062e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.2604198455810547s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.02130746841430664s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.0967254638671875e-05s
INFO | --- Analysis for somya_omer took 2.3118479251861572s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.100799560546875e-05s
Availability | VoID file availability check for Sonclubcx took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.26648783683776855s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.049041748046875e-05s
Believability | Calculation of trust value for Sonclubcx took 1.049041748046875e-05s
INFO | --- Analysis for sonclubcx took 4.243002414703369s
Availability | SPARQL endpoint availability check for SORS took 8.344650268554688e-05s
Availability | VoID file availability check for SORS took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for SORS took 0.2534666061401367s
Reputation | Calculation of the PageRank for SORS took 0.02086782455444336s
Interlinking | Calculation of Degree of Connection for SORS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SORS took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for SORS took 4.6253204345703125e-05s
Believability | Calculation of trust value for SORS took 4.291534423828125e-06s
INFO | --- Analysis for sors took 12.526350498199463s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.3392181396484375e-05s
Availability | VoID file availability check for Soudy České republiky took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.2679715156555176s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 2.7894973754882812e-05s
Believability | Calculation of trust value for Soudy České republiky took 1.3113021850585938e-05s
INFO | --- Analysis for soudy--esk--republiky took 2.7865827083587646s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.887580871582031e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.2638680934906006s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.02115654945373535s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 8.7738037109375e-05s
Believability | Calculation of trust value for southampton-ac-uk took 1.1682510375976562e-05s
INFO | --- Analysis for southampton-ac-uk took 3.6632885932922363s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.038531541824341s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.2771749496459961s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 1.2159347534179688e-05s
INFO | --- Analysis for southampton-ac-uk-apps took 10.11919116973877s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 8.487701416015625e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.44654083251953125s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.26245880126953125s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020221948623657227s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.250640869140625e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.1920928955078125e-05s
INFO | --- Analysis for southampton-ecs-eprints took 4.721158504486084s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.503293514251709s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.00052642822265625s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 156.72948217391968s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.157226800918579s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.2542269229888916s
Interoperability | New terms check for Spanish Linguistic Datasets took 2.877328634262085s
Versatility | Languages check for Spanish Linguistic Datasets took 44.4470911026001s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.163994550704956s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.13242053985595703s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.2810695171356201s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.27001452445983887s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.25751566886901855s
License | MR license check for Spanish Linguistic Datasets took 0.26575422286987305s
License | HR license check for Spanish Linguistic Datasets took 0.3412032127380371s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.25798535346984863s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.33825206756591797s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5465655326843262s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.31679439544677734s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.2817385196685791s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.256319522857666s
Performance | Throughput check for Spanish Linguistic Datasets took 12.110747337341309s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 7.414817810058594e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.2643616199493408s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.26813483238220215s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2614748477935791s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2407245635986328s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.26917314529418945s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5366334915161133s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5368726253509521s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 57.257147789001465s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2765204906463623s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.27458691596984863s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.2761399745941162s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9274437427520752s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.01032400131225586s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.632983684539795s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.2628211975097656s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.703520059585571s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.415358304977417s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 43.90577435493469s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.4942636489868164s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.672236442565918s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.872074604034424s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.2933650016784668s
Security | Sign check for Spanish Linguistic Datasets took 0.26625514030456543s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 17.22887086868286s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.3375670909881592s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.24249267578125e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.384185791015625e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 7.152557373046875e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 413.8197977542877s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.050693511962890625s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2474384307861328s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.839897155761719e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 1.0967254638671875e-05s
INFO | --- Analysis for sparql-endpoint-status took 2.3828816413879395s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 0.00010848045349121094s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.2501413822174072s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.021968841552734375s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 2.8371810913085938e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 1.2159347534179688e-05s
INFO | --- Analysis for spc-publikovan--s-kl took 2.8474531173706055s
Availability | SPARQL endpoint availability check for SPQR took 4.029273986816406e-05s
Availability | VoID file availability check for SPQR took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for SPQR took 0.2462763786315918s
Reputation | Calculation of the PageRank for SPQR took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for SPQR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.8371810913085938e-05s
Believability | Calculation of trust value for SPQR took 1.2159347534179688e-05s
INFO | --- Analysis for spqr took 2.8157567977905273s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.1961669921875e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.25629258155822754s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.249282836914062e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.2636184692382812e-05s
INFO | --- Analysis for springernaturescigraph took 2.868990898132324s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 8.463859558105469e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.30582284927368164s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.02079606056213379s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.33514404296875e-05s
INFO | --- Analysis for srcmf took 8.446607828140259s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.2972238063812256s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0006353855133056641s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.250474452972412s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 0.7749207019805908s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.16417598724365234s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.3921735286712646s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.1594080924987793s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.15610003471374512s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.10539674758911133s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.14981698989868164s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.15420222282409668s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.15158319473266602s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.14704275131225586s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.1681225299835205s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.15027332305908203s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.16273880004882812s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.2975294589996338s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.1734616756439209s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.178558349609375s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.1574084758758545s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 10.720179557800293s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 6.723403930664062e-05s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.15367603302001953s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.15363168716430664s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.14514946937561035s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.14335274696350098s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.16264104843139648s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.32732629776000977s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.2929961681365967s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.5024991035461426s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.1369485855102539s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.17011332511901855s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.16052770614624023s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.15467214584350586s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.0003044605255126953s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.037114858627319336s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.14483642578125s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.329998254776001s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.20235180854797363s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.4989440441131592s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.3163371086120605s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.460921287536621s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.019269943237304688s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.16833186149597168s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.15888524055480957s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 461.6559405326843s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.4064915180206299s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.021444082260131836s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 5.91278076171875e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 1.430511474609375e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 7.3909759521484375e-06s
INFO | --- Analysis for ssf took 504.41774678230286s
Availability | SPARQL endpoint availability check for SSF took 4.172325134277344e-05s
Availability | VoID file availability check for SSF took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for SSF took 0.2518138885498047s
Reputation | Calculation of the PageRank for SSF took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for SSF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SSF took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for SSF took 2.86102294921875e-05s
Believability | Calculation of trust value for SSF took 1.2636184692382812e-05s
INFO | --- Analysis for ssf-lexicon took 3.409125566482544s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.1484832763671875e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.6834709644317627s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 4.172325134277344e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 1.1920928955078125e-05s
INFO | --- Analysis for st-andrews-resource-lists took 3.5994129180908203s
Availability | SPARQL endpoint availability check for STAC took 6.103515625e-05s
Availability | VoID file availability check for STAC took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for STAC took 0.24384403228759766s
Reputation | Calculation of the PageRank for STAC took 0.020583152770996094s
Interlinking | Calculation of Degree of Connection for STAC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for STAC took 2.8371810913085938e-05s
Believability | Calculation of trust value for STAC took 1.1682510375976562e-05s
INFO | --- Analysis for stac took 2.8692593574523926s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.076957702636719e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.23584532737731934s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.147125244140625e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 7.3909759521484375e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.8574845790863037s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.291534423828125e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.27988433837890625s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020801305770874023s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.2901763916015625e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0251998901367188e-05s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 3.8612072467803955s
Availability | SPARQL endpoint availability check for Stammbuch took 4.38690185546875e-05s
Availability | VoID file availability check for Stammbuch took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.24224615097045898s
Reputation | Calculation of the PageRank for Stammbuch took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for Stammbuch took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.123283386230469e-05s
Believability | Calculation of trust value for Stammbuch took 1.239776611328125e-05s
INFO | --- Analysis for Stammbuch took 2.3352131843566895s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.2087883949279785s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.25565409660339355s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010395050048828125s
Believability | Calculation of trust value for statistics.data.gov.uk took 9.775161743164062e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.458349227905273s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 3.981590270996094e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.26217031478881836s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.956390380859375e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 7.3909759521484375e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.83687162399292s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.280289888381958s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010800361633300781s
Believability | Calculation of trust value for statusnet-1w6-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-1w6-org took 3.6895575523376465s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 7.486343383789062e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2574951648712158s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-20100-org took 2.517045021057129s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2748281955718994s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 3.126335859298706s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.2784299850463867s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.02071547508239746s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.249282836914062e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.350548267364502s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 8.7738037109375e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.2636692523956299s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.131431579589844e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.5561506748199463s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 5.1021575927734375e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.2791013717651367s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02069544792175293s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0008969306945800781s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00012183189392089844s
Believability | Calculation of trust value for statusnet-bka-li took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-bka-li took 12.51837706565857s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.24898314476013184s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.021086931228637695s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.9577484130859375e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.242042064666748s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0003147125244140625s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.24173974990844727s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.696846008300781e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ced117-net took 3.6557912826538086s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0003657341003417969s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.28388285636901855s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 4.744529724121094e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.4359309673309326s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.00034046173095703125s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.2554740905761719s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00010919570922851562s
Believability | Calculation of trust value for statusnet-chromic-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.4743895530700684s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2575876712799072s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.677078247070312e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.697596311569214s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 7.176399230957031e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0002124309539794922s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2697567939758301s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020696640014648438s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.3256871700286865s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0003867149353027344s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2706162929534912s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02033543586730957s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.389617919921875e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.0513713359832764s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.24512147903442383s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010180473327636719s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.404590368270874s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 5.8650970458984375e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.24539494514465332s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.3433518409729004s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 8.869171142578125e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2510347366333008s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.1021575927734375e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-doomicile-de took 3.1989800930023193s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 8.678436279296875e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.24365711212158203s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-dtdns-net took 22.32922649383545s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 8.7738037109375e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.26447367668151855s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.02089071273803711s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.361701965332031e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 2.3856639862060547s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 8.678436279296875e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.27214741706848145s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-exdc-net took 2.6031830310821533s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.25965213775634766s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.489059448242188e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-fcac-com took 22.30588173866272s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2831766605377197s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.021344900131225586s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 3.1343939304351807s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 0.00011444091796875s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.2540774345397949s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.0001862049102783203s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-fragdev-com took 3.2727620601654053s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.26038217544555664s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020787954330444336s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.486343383789062e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-freelish-us took 2.5059566497802734s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 8.702278137207031e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.24837970733642578s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.021228790283203125s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 2.4389846324920654s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.2532541751861572s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.022902727127075195s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.723403930664062e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-glou-org took 2.463573932647705s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 8.249282836914062e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2546553611755371s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020757436752319336s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.0001251697540283203s
Believability | Calculation of trust value for statusnet-gomertronic-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-gomertronic-com took 2.346693515777588s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 8.296966552734375e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2626769542694092s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010466575622558594s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 2.906287670135498s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.29306745529174805s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.673004150390625e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-hii-co-il took 4.058102369308472s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 8.869171142578125e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2511019706726074s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.02283501625061035s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 8.916854858398438e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 2.769341230392456s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 9.846687316894531e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.24066162109375s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020513296127319336s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.389617919921875e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 2.5110371112823486s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.29090452194213867s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.814697265625e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-integralblue-com took 2.7053134441375732s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.26422834396362305s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020971298217773438s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.3480224609375s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 5.316734313964844e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2773244380950928s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011396408081054688s
Believability | Calculation of trust value for statusnet-jonkman-ca took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-jonkman-ca took 3.353227138519287s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2605767250061035s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.226799011230469e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.4182562828063965s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 8.7738037109375e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2602570056915283s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.601478576660156e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 2.3703930377960205s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0010919570922851562s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.23520469665527344s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.0210416316986084s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.696846008300781e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 3.2043960094451904s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.28905200958251953s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.3821725845336914s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0009827613830566406s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2600593566894531s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020293712615966797s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.291534423828125e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.4714784622192383s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.26309680938720703s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 5.817413330078125e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 2.539670705795288s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.26186370849609375s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.34600830078125e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.6032745838165283s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.2643771171569824s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.022017240524291992s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011348724365234375s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.3789803981781006s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.2664034366607666s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-ludost-net took 3.6150760650634766s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 0.00010824203491210938s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2728290557861328s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02234339714050293s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.751319885253906e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.337247133255005s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2731914520263672s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 7.128715515136719e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.424671173095703s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2742767333984375s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.0001475811004638672s
Believability | Calculation of trust value for statusnet-macno-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-macno-org took 2.4228055477142334s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.24657464027404785s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.4450550079345703s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2711920738220215s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020747661590576172s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 7.891654968261719e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-maymay-net took 41.92235565185547s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 6.604194641113281e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0002052783966064453s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2493271827697754s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00015664100646972656s
Believability | Calculation of trust value for statusnet-morphtown-de took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.4279043674468994s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.2645406723022461s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.021088600158691406s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.894371032714844e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 2.493086814880371s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.792213439941406e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.2587761878967285s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.6743621826171875e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.3450448513031006s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.28830766677856445s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.02233576774597168s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.626678466796875e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.4687416553497314s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 9.608268737792969e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.26390910148620605s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.021300554275512695s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010919570922851562s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.413914680480957s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0007536411285400391s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.27086687088012695s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.678001642227173s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 8.678436279296875e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.2545166015625s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.4065918922424316s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.24941325187683105s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.463859558105469e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.4131081104278564s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2603189945220947s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.863739013671875e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-panda-id-au took 4.157074213027954s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.25275588035583496s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.021778106689453125s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.560585021972656e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-piana-eu took 2.389519453048706s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.2543361186981201s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.022563695907592773s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.3384101390838623s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.27773022651672363s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.021986007690429688s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002315044403076172s
Believability | Calculation of trust value for statusnet-postblue-info took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-postblue-info took 2.618881940841675s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2573366165161133s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.437301635742188e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-progval-net took 2.4355759620666504s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.2623863220214844s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020725011825561523s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011324882507324219s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-qdnx-org took 2.8329954147338867s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2465980052947998s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-qth-fr took 3.2530016899108887s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.27292847633361816s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.02075791358947754s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00023555755615234375s
Believability | Calculation of trust value for statusnet-quitter-se took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-quitter-se took 2.5136985778808594s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 0.0001087188720703125s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.2677896022796631s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010037422180175781s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.6783738136291504s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.24655437469482422s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.02158331871032715s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-recit-org took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-recit-org took 2.381363868713379s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.25129055976867676s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00014638900756835938s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-russwurm-org took 3.1823086738586426s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 0.0001010894775390625s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.2546961307525635s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 7.987022399902344e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-samnoble-org took 5.060701370239258s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 8.988380432128906e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.25034451484680176s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.082389831542969e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-schiessle-org took 2.421435594558716s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.25385117530822754s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.822845458984375e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 2.4015045166015625s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.23930740356445312s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.02111077308654785s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 5.936622619628906e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 2.4516756534576416s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 0.00010323524475097656s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.2602400779724121s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.02120685577392578s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.414817810058594e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 3.200620412826538s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.25594186782836914s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.02029705047607422s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021147727966308594s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 2.9014062881469727s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2793576717376709s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02088332176208496s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0008792877197265625s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00012731552124023438s
Believability | Calculation of trust value for statusnet-somsants-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.4138355255126953s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2372875213623047s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.0001430511474609375s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-soucy-cc took 2.3858349323272705s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2605016231536865s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.022140979766845703s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.4849853515625e-05s
Believability | Calculation of trust value for statusnet-spip-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-spip-org took 3.3498058319091797s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2611842155456543s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.023049116134643555s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-spraci-org took 2.3778703212738037s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.25863003730773926s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00010800361633300781s
Believability | Calculation of trust value for statusnet-ssweeny-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.340350151062012s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.23394060134887695s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00021958351135253906s
Believability | Calculation of trust value for statusnet-status-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-status-net took 3.4284703731536865s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.24790143966674805s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.02195429801940918s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0011146068572998047s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 6.699562072753906e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.362837791442871s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.2674133777618408s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020817041397094727s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 8.726119995117188e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.4526727199554443s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.24584054946899414s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02110147476196289s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012683868408203125s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 2.585709810256958s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.25942349433898926s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.271766662597656e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-thornton2-com took 5.127788543701172s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 5.125999450683594e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.2512245178222656s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.6747684478759766s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2652721405029297s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.5705130100250244s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 5.4836273193359375e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2623765468597412s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.02205681800842285s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.681304931640625s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.24685239791870117s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.647804260253906e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.741222620010376s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.3392181396484375e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.32631969451904297s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for steak took 2.823176622390747s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 7.43865966796875e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0003838539123535156s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.24746155738830566s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.054473876953125e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.2874603271484375e-05s
INFO | --- Analysis for stitch-rameau took 4.083513975143433s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.7887957096099854s
Availability | VoID file availability check for Stone Tech Square took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.24967169761657715s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.1920928955078125e-05s
Believability | Calculation of trust value for Stone Tech Square took 6.67572021484375e-06s
INFO | --- Analysis for stone-tech-square-data took 4.253702878952026s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 8.893013000488281e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.25902366638183594s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.021218299865722656s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.0517578125e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 1.2159347534179688e-05s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.8767387866973877s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.3947412967681885s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0007078647613525391s
Extra | Recovery of all triples for STW Thesaurus for Economics took 19.281933307647705s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.1675491333007812s
Amount of data | Number of triples check for STW Thesaurus for Economics took 1.1641309261322021s
Interoperability | New terms check for STW Thesaurus for Economics took 1.5704889297485352s
Versatility | Languages check for STW Thesaurus for Economics took 3.0421156883239746s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.7827751636505127s
Security | Check HTTPS for STW Thesaurus for Economics took 0.16073226928710938s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2051084041595459s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.2255232334136963s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.301938533782959s
License | MR license check for STW Thesaurus for Economics took 0.2198164463043213s
License | HR license check for STW Thesaurus for Economics took 5.25008749961853s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.2589294910430908s
Understandability | Number of label check for STW Thesaurus for Economics took 1.5285520553588867s
Understandability | URI regex check for STW Thesaurus for Economics took 0.5016019344329834s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.21579265594482422s
Verifiability | Authors check for STW Thesaurus for Economics took 0.24087047576904297s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.23610520362854004s
Performance | Throughput check for STW Thesaurus for Economics took 11.43106985092163s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7231807708740234s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.22428655624389648s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.20432567596435547s
Interlinking | skos check for STW Thesaurus for Economics took 0.42529773712158203s
Interlinking | skos check for STW Thesaurus for Economics took 0.48029088973999023s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.20709013938903809s
Currency | Creation date check for STW Thesaurus for Economics took 0.49228549003601074s
Currency | Modification date check for STW Thesaurus for Economics took 0.4577159881591797s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 10.494046688079834s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 2.7999985218048096s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.24029278755187988s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2341926097869873s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.22634506225585938s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 6.570204496383667s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0355792045593262s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.2912960052490234s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.22905874252319336s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 2.321491241455078s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.7217035293579102s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.2742831707000732s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 3.1127095222473145s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6075630187988281s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2032151222229004s
Security | Sign check for STW Thesaurus for Economics took 0.20481228828430176s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2729.766584634781s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.5502595901489258s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.6999130249023438s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00012421607971191406s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 3.2024872303009033s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.0967254638671875e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 2843.9415135383606s
Availability | SPARQL endpoint availability check for SudershanTech took 4.9114227294921875e-05s
Availability | VoID file availability check for SudershanTech took 0.0002067089080810547s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.2883622646331787s
Reputation | Calculation of the PageRank for SudershanTech took 0.0208895206451416s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.409385681152344e-05s
Believability | Calculation of trust value for SudershanTech took 1.1444091796875e-05s
INFO | --- Analysis for SudershanTech took 3.664397716522217s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.5462632179260254s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0008058547973632812s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.24559378623962402s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.02073955535888672s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 5.435943603515625e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 8.106231689453125e-06s
INFO | --- Analysis for sudocfr took 33.9843647480011s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0323963165283203s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006732940673828125s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 21.02891993522644s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.692394971847534s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.3445188999176025s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.8898983001708984s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 2.3401310443878174s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.2570431232452393s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5349071025848389s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5250406265258789s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.530886173248291s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5384912490844727s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 7.039053201675415s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5553877353668213s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.7046763896942139s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.1273236274719238s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5366652011871338s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5692117214202881s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5404918193817139s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.420114040374756s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 7.128715515136719e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5470647811889648s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5480172634124756s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6186046600341797s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5930697917938232s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.544884204864502s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0675549507141113s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.06980562210083s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 35.06084418296814s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5299692153930664s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5266542434692383s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5239639282226562s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 2.8676061630249023s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.377399206161499s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5703792572021484s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 30.83324384689331s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.364256620407104s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.4413514137268s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 25.482621669769287s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9241220951080322s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.5201656818389893s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5334103107452393s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4390.0138194561005s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.738631010055542s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.022621870040893555s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 7.867813110351562e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.0967254638671875e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 7939.940038919449s
Availability | SPARQL endpoint availability check for Surge Radio took 9.5367431640625e-05s
Availability | VoID file availability check for Surge Radio took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.7058799266815186s
Reputation | Calculation of the PageRank for Surge Radio took 0.02093958854675293s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.559226989746094e-05s
Believability | Calculation of trust value for Surge Radio took 1.3113021850585938e-05s
INFO | --- Analysis for surge-radio took 5.2971014976501465s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 9.179115295410156e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.27099132537841797s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020956039428710938s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.147125244140625e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.2636184692382812e-05s
INFO | --- Analysis for SWAT took 30.759018898010254s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.1961669921875e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.40973615646362305s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.24583935737609863s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.985664367675781e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.2874603271484375e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 5.930601119995117s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.094794511795044s
Availability | VoID file availability check for SweFN-RDF took 0.0008180141448974609s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.2837703227996826s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020795345306396484s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.600120544433594e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.2636184692382812e-05s
INFO | --- Analysis for swefn-rdf took 6.113588094711304s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.2438507080078125e-05s
Availability | VoID file availability check for SwetoDblp took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2419142723083496s
Reputation | Calculation of the PageRank for SwetoDblp took 0.023873090744018555s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.790855407714844e-05s
Believability | Calculation of trust value for SwetoDblp took 1.2159347534179688e-05s
INFO | --- Analysis for sweto-dblp took 22.68510866165161s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.5651509761810303s
Availability | VoID file availability check for Swift Vocabulary took 0.0006682872772216797s
Extra | Recovery of all triples for Swift Vocabulary took 2.4941723346710205s
Performance | Total latancy measurement for Swift Vocabulary took 1.08894944190979s
Amount of data | Number of triples check for Swift Vocabulary took 0.20427703857421875s
Interoperability | New terms check for Swift Vocabulary took 1.521773338317871s
Versatility | Languages check for Swift Vocabulary took 0.240523099899292s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.24161505699157715s
Interpretability | RDF structures check for Swift Vocabulary took 0.21704602241516113s
Versatility | Serialization formats check for Swift Vocabulary took 0.20579743385314941s
Availability | RDF dump link check for Swift Vocabulary took 0.20921874046325684s
License | MR license check for Swift Vocabulary took 0.18875885009765625s
License | HR license check for Swift Vocabulary took 0.19240689277648926s
Amount of data | Number of property check for Swift Vocabulary took 0.2227919101715088s
Understandability | Number of label check for Swift Vocabulary took 0.2131667137145996s
Understandability | URI regex check for Swift Vocabulary took 0.4519357681274414s
Understandability | Vocabs check for Swift Vocabulary took 0.20846199989318848s
Verifiability | Authors check for Swift Vocabulary took 0.20875167846679688s
Verifiability | Publishers check for Swift Vocabulary took 0.22597265243530273s
Performance | Throughput check for Swift Vocabulary took 11.359305620193481s
Amount of data | Check the number of entities for Swift Vocabulary took 8.654594421386719e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.2445845603942871s
Interlinking | sameAs chians check for Swift Vocabulary took 0.22812318801879883s
Interlinking | skos check for Swift Vocabulary took 0.24169182777404785s
Interlinking | skos check for Swift Vocabulary took 0.20847010612487793s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.22716760635375977s
Currency | Creation date check for Swift Vocabulary took 0.45462799072265625s
Currency | Modification date check for Swift Vocabulary took 0.4592103958129883s
Rep.Conc. | URIs length for Swift Vocabulary took 0.825650691986084s
Interoperability | New vocabularies check for Swift Vocabulary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.20222783088684082s
Accuracy | Check Functional Property for Swift Vocabulary took 0.2069683074951172s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.24092912673950195s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.35297131538391113s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.0019989013671875s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03590965270996094s
Consistency | Disjoint class check for Swift Vocabulary took 0.2255091667175293s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.47442102432250977s
Consistency | Misplaced classes for Swift Vocabulary took 0.2811901569366455s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.645751714706421s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.3167037963867188s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.5044426918029785s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.026540756225585938s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.18684887886047363s
Security | Sign check for Swift Vocabulary took 0.18314743041992188s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 1124.7699699401855s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.47893524169921875s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.022478580474853516s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 2.384185791015625e-06s
Believability | Calculation of trust value for Swift Vocabulary took 1.0251998901367188e-05s
INFO | --- Analysis for Swift took 1176.3020870685577s
Availability | SPARQL endpoint availability check for SymbolicData took 3.981590270996094e-05s
Availability | VoID file availability check for SymbolicData took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.27303409576416016s
Reputation | Calculation of the PageRank for SymbolicData took 0.020349979400634766s
Interlinking | Calculation of Degree of Connection for SymbolicData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SymbolicData took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.170967102050781e-05s
Believability | Calculation of trust value for SymbolicData took 1.1205673217773438e-05s
INFO | --- Analysis for symbolicdata took 2.8095762729644775s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 8.630752563476562e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.2507450580596924s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 2.7894973754882812e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.2636184692382812e-05s
INFO | --- Analysis for symptoms-in-chinese took 52.643012285232544s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.46460962295532227s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0006279945373535156s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.535463809967041s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.8956599235534668s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 8.728884220123291s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 18.93506360054016s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.1789109706878662s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 4.015547752380371s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.12216043472290039s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.35505032539367676s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.19806838035583496s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.18255949020385742s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.27306556701660156s
License | HR license check for National Digital Data Archive of Hungary (partial) took 53.19833159446716s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.6055111885070801s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 37.89062452316284s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3726847171783447s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.23047280311584473s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.1954798698425293s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.17212677001953125s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 14.02379298210144s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 6.866455078125e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 2.024038314819336s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 2.234161853790283s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 2.033818483352661s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.9359543323516846s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.8891911506652832s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.572897434234619s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 3.344454288482666s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 65.12273931503296s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.16801023483276367s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.19124984741210938s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.19678092002868652s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.25147342681884766s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0011959075927734375s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0014371871948242188s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.18489313125610352s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.83501744270325s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2788574695587158s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.5546777248382568s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.279362678527832s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 46.91579270362854s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002053976058959961s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.3797011375427246s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.1718752384185791s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 17.046169757843018s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.7534804344177246s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 9.655952453613281e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.2636184692382812e-05s
INFO | --- Analysis for sztaki-lod took 545.2611491680145s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.267692565917969e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.26279520988464355s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020519733428955078s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.269050598144531e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.430511474609375e-05s
INFO | --- Analysis for t4gm-info took 3.258807420730591s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.1484832763671875e-05s
Availability | VoID file availability check for tags2con delicious took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.690929651260376s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 3.9577484130859375e-05s
Believability | Calculation of trust value for tags2con delicious took 1.1444091796875e-05s
INFO | --- Analysis for tags2con-delicious took 45.90695238113403s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 264.1587300300598s
Availability | VoID file availability check for Taiwan geographic names took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.31286168098449707s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.02194833755493164s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0010862350463867188s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 8.440017700195312e-05s
Believability | Calculation of trust value for Taiwan geographic names took 6.699562072753906e-05s
INFO | --- Analysis for taiwan-geographic-names took 670.1461160182953s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.2516756057739258s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 8.916854858398438e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 7.152557373046875e-06s
INFO | --- Analysis for talis-openlibrary took 3.6884512901306152s
Availability | SPARQL endpoint availability check for TalkBank took 4.982948303222656e-05s
Availability | VoID file availability check for TalkBank took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for TalkBank took 0.2628624439239502s
Reputation | Calculation of the PageRank for TalkBank took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.9087066650390625e-05s
Believability | Calculation of trust value for TalkBank took 1.2636184692382812e-05s
INFO | --- Analysis for talkbank took 2.8314008712768555s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 1.3058197498321533s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.26204824447631836s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00011968612670898438s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.2159347534179688e-05s
INFO | --- Analysis for taxonconcept took 13.636838912963867s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 0.00010156631469726562s
Availability | VoID file availability check for taxonconcept-assets took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.24412989616394043s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 7.963180541992188e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.239776611328125e-05s
INFO | --- Analysis for taxonconcept-assets took 2.7656774520874023s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 8.416175842285156e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2464902400970459s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02345871925354004s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0009632110595703125s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 6.389617919921875e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 7.867813110351562e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.624504566192627s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 22.052632093429565s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.2652854919433594s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 5.1021575927734375e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 1.33514404296875e-05s
INFO | --- Analysis for taxref-ld took 76.96412324905396s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.96895027160645s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.2587735652923584s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.100799560546875e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.239776611328125e-05s
INFO | --- Analysis for tcga took 541.522302865982s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3927764892578125s
Availability | VoID file availability check for TCGA Roadmap took 0.00032258033752441406s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.7084066867828369s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02162027359008789s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.033348083496094e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.2636184692382812e-05s
INFO | --- Analysis for tcga-roadmap took 8.278854608535767s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.1587400436401367s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.33206677436828613s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.021578550338745117s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00012040138244628906s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for tcmgenedit_dataset took 138.4076657295227s
Availability | SPARQL endpoint availability check for TDS took 4.4345855712890625e-05s
Availability | VoID file availability check for TDS took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for TDS took 0.6876330375671387s
Reputation | Calculation of the PageRank for TDS took 0.02037835121154785s
Interlinking | Calculation of Degree of Connection for TDS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TDS took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for TDS took 3.647804260253906e-05s
Believability | Calculation of trust value for TDS took 1.239776611328125e-05s
INFO | --- Analysis for tds took 6.4672160148620605s
Availability | SPARQL endpoint availability check for TED Talks took 6.937980651855469e-05s
Availability | VoID file availability check for TED Talks took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for TED Talks took 0.24888920783996582s
Reputation | Calculation of the PageRank for TED Talks took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for TED Talks took 2.8371810913085938e-05s
Believability | Calculation of trust value for TED Talks took 7.152557373046875e-06s
INFO | --- Analysis for ted-talks took 4.087486505508423s
Availability | SPARQL endpoint availability check for TEKORD took 4.673004150390625e-05s
Availability | VoID file availability check for TEKORD took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2528414726257324s
Reputation | Calculation of the PageRank for TEKORD took 0.02255725860595703s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.506111145019531e-05s
Believability | Calculation of trust value for TEKORD took 1.2159347534179688e-05s
INFO | --- Analysis for tekord took 5.082992792129517s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 1.5686085224151611s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.2522122859954834s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.0232846736907959s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00012540817260742188s
Believability | Calculation of trust value for Telegraphis Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for telegraphis took 7.52582311630249s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.935264587402344e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.25992250442504883s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 6.771087646484375e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.3113021850585938e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.930135011672974s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.029273986816406e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.25136613845825195s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.020852327346801758s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.314018249511719e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.8492841720581055s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 8.177757263183594e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.25215792655944824s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.022020816802978516s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 2.7894973754882812e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for terminesp took 2.824862480163574s
Availability | SPARQL endpoint availability check for Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Ontology took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Ontology took 0.26668262481689453s
Reputation | Calculation of the PageRank for Ontology took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.218650817871094e-05s
Believability | Calculation of trust value for Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Terrorist_attack took 2.902904748916626s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.315376281738281e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2732086181640625s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.075599670410156e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.3113021850585938e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 2.2729709148406982s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.172325134277344e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.23498773574829102s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 3.504753112792969e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 1.33514404296875e-05s
INFO | --- Analysis for tesauro-materias-bupm took 2.7765767574310303s
Availability | SPARQL endpoint availability check for Teseo took 4.76837158203125e-05s
Availability | VoID file availability check for Teseo took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Teseo took 0.2575533390045166s
Reputation | Calculation of the PageRank for Teseo took 0.020816802978515625s
Interlinking | Calculation of Degree of Connection for Teseo took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Teseo took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.147125244140625e-05s
Believability | Calculation of trust value for Teseo took 8.58306884765625e-06s
INFO | --- Analysis for teseo took 2.804924249649048s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.00013184547424316406s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.2954437732696533s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.02223038673400879s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.0517578125e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 7.3909759521484375e-06s
INFO | --- Analysis for Tesla_Deaths took 4.020630359649658s
Availability | SPARQL endpoint availability check for test took 4.291534423828125e-05s
Availability | VoID file availability check for test took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for test took 0.25104761123657227s
Reputation | Calculation of the PageRank for test took 0.021571874618530273s
Interlinking | Calculation of Degree of Connection for test took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for test took 0.0008385181427001953s
Interlinking | Calculation of Clustering coefficient for test took 3.4332275390625e-05s
Believability | Calculation of trust value for test took 1.3113021850585938e-05s
INFO | --- Analysis for test took 2.3879661560058594s
Availability | SPARQL endpoint availability check for Test took 0.00010514259338378906s
Availability | VoID file availability check for Test took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Test took 0.25049686431884766s
Reputation | Calculation of the PageRank for Test took 0.021175384521484375s
Interlinking | Calculation of Degree of Connection for Test took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Test took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Test took 3.075599670410156e-05s
Believability | Calculation of trust value for Test took 1.3589859008789062e-05s
INFO | --- Analysis for Test took 2.3215138912200928s
Availability | SPARQL endpoint availability check for test-svu took 20.185189962387085s
Availability | VoID file availability check for test-svu took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for test-svu took 0.2595841884613037s
Reputation | Calculation of the PageRank for test-svu took 0.021024227142333984s
Interlinking | Calculation of Degree of Connection for test-svu took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for test-svu took 2.8133392333984375e-05s
Believability | Calculation of trust value for test-svu took 9.298324584960938e-06s
INFO | --- Analysis for test-svu took 52.64214253425598s
Availability | SPARQL endpoint availability check for Test took 8.58306884765625e-05s
Availability | VoID file availability check for Test took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Test took 0.23639988899230957s
Reputation | Calculation of the PageRank for Test took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Test took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Test took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Test took 2.9802322387695312e-05s
Believability | Calculation of trust value for Test took 1.2159347534179688e-05s
INFO | --- Analysis for Test_ took 2.2839112281799316s
Availability | SPARQL endpoint availability check for xxxxx took 261.2430884838104s
Availability | VoID file availability check for xxxxx took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for xxxxx took 0.6923513412475586s
Reputation | Calculation of the PageRank for xxxxx took 0.02099609375s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for xxxxx took 0.00010657310485839844s
Believability | Calculation of trust value for xxxxx took 1.239776611328125e-05s
INFO | --- Analysis for testee took 798.3361976146698s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.410743713378906e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.6792690753936768s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.0220339298248291s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 2.765655517578125e-05s
Believability | Calculation of trust value for Texai Lexicon took 1.3113021850585938e-05s
INFO | --- Analysis for texai_lexicon took 6.027884244918823s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.3392181396484375e-05s
Availability | VoID file availability check for tharawat magazine took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.25727367401123047s
Reputation | Calculation of the PageRank for tharawat magazine took 0.020338773727416992s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00011754035949707031s
Believability | Calculation of trust value for tharawat magazine took 1.2159347534179688e-05s
INFO | --- Analysis for tharawat-magazine-com took 3.3835113048553467s
Availability | SPARQL endpoint availability check for The CIARD RING took 0.00012230873107910156s
Availability | VoID file availability check for The CIARD RING took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.25911664962768555s
Reputation | Calculation of the PageRank for The CIARD RING took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.123283386230469e-05s
Believability | Calculation of trust value for The CIARD RING took 1.3589859008789062e-05s
INFO | --- Analysis for the-ciard-ring took 3.352813482284546s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.4230427742004395s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.25293922424316406s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.0220949649810791s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 2.8133392333984375e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.2636184692382812e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 8.518327713012695s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 1.525237798690796s
Availability | VoID file availability check for The European Library Open Dataset took 0.0006749629974365234s
Extra | Recovery of all triples for The European Library Open Dataset took 1.0569570064544678s
Performance | Total latancy measurement for The European Library Open Dataset took 1.3916141986846924s
Amount of data | Number of triples check for The European Library Open Dataset took 30.215624570846558s
Versatility | Languages check for The European Library Open Dataset took 0.36184191703796387s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.28472900390625s
Interpretability | RDF structures check for The European Library Open Dataset took 0.22820496559143066s
Versatility | Serialization formats check for The European Library Open Dataset took 0.23931145668029785s
Availability | RDF dump link check for The European Library Open Dataset took 0.2149367332458496s
License | MR license check for The European Library Open Dataset took 0.24410700798034668s
License | HR license check for The European Library Open Dataset took 0.2541971206665039s
Amount of data | Number of property check for The European Library Open Dataset took 0.2509121894836426s
Understandability | Number of label check for The European Library Open Dataset took 1.0477368831634521s
Understandability | URI regex check for The European Library Open Dataset took 0.4968540668487549s
Understandability | Vocabs check for The European Library Open Dataset took 0.25619959831237793s
Verifiability | Authors check for The European Library Open Dataset took 0.22663617134094238s
Verifiability | Publishers check for The European Library Open Dataset took 0.26479220390319824s
Performance | Throughput check for The European Library Open Dataset took 11.679527044296265s
Amount of data | Check the number of entities for The European Library Open Dataset took 6.818771362304688e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.22644448280334473s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.30587124824523926s
Interlinking | skos check for The European Library Open Dataset took 0.28264403343200684s
Interlinking | skos check for The European Library Open Dataset took 0.29479074478149414s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.22947001457214355s
Currency | Creation date check for The European Library Open Dataset took 0.5249416828155518s
Currency | Modification date check for The European Library Open Dataset took 0.5247528553009033s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.496236085891724s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.24349665641784668s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 0.47230052947998047s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.028126239776611328s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.028316736221313477s
Consistency | Disjoint class check for The European Library Open Dataset took 0.2165217399597168s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.451448917388916s
Consistency | Misplaced classes for The European Library Open Dataset took 0.32417798042297363s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.8233070373535156s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.3118457794189453s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.489177942276s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03240013122558594s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.2947845458984375s
Security | Sign check for The European Library Open Dataset took 0.228607177734375s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 17.555617094039917s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.5046303272247314s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for the-european-library-open-dataset took 408.64794635772705s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 0.7642354965209961s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.264636754989624s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.02091073989868164s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 9.965896606445312e-05s
Believability | Calculation of trust value for The Eurostat Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for the-eurostat-linked-data took 7.243516206741333s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 8.296966552734375e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.25612926483154297s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.0517578125e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.1920928955078125e-05s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 2.7376773357391357s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.2438507080078125e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0012540817260742188s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.29169702529907227s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.43865966796875e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.1444091796875e-05s
INFO | --- Analysis for the-living-lod-cloud took 56.914530754089355s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 3.981590270996094e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.2519395351409912s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 2.9087066650390625e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 1.239776611328125e-05s
INFO | --- Analysis for the-midi-linked-data-cloud took 2.839689254760742s
Availability | SPARQL endpoint availability check for The View From took 0.09104514122009277s
Availability | VoID file availability check for The View From took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for The View From took 0.2570195198059082s
Reputation | Calculation of the PageRank for The View From took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for The View From took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for The View From took 7.843971252441406e-05s
Believability | Calculation of trust value for The View From took 1.049041748046875e-05s
INFO | --- Analysis for the-view-from took 3.317556142807007s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 1.7063426971435547s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2359483242034912s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.02073955535888672s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.218650817871094e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 9.5367431640625e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 5.717141151428223s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 1.1143312454223633s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2772331237792969s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.022290945053100586s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.5762786865234375e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.049041748046875e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 7.496715307235718s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.291534423828125e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.2594125270843506s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010204315185546875s
Believability | Calculation of trust value for The Content Wrangler took 1.1444091796875e-05s
INFO | --- Analysis for thecontentwrangler-com took 2.8437583446502686s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.839897155761719e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.26149415969848633s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.023170948028564453s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.0040740966796875e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 1.1682510375976562e-05s
INFO | --- Analysis for thesaurus-bncf took 2.888155698776245s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 6.914138793945312e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2436842918395996s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020977020263671875s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.0517578125e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 9.775161743164062e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.4745161533355713s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.5283486843109131s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.2591536045074463s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.021455049514770508s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 8.058547973632812e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.2874603271484375e-05s
INFO | --- Analysis for thesaurus-w took 3.7073566913604736s
Availability | SPARQL endpoint availability check for theses.fr took 8.845329284667969e-05s
Availability | VoID file availability check for theses.fr took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for theses.fr took 0.2396857738494873s
Reputation | Calculation of the PageRank for theses.fr took 0.022025585174560547s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.863739013671875e-05s
Believability | Calculation of trust value for theses.fr took 1.0251998901367188e-05s
INFO | --- Analysis for thesesfr took 4.086805105209351s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.2438507080078125e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.2524137496948242s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0214536190032959s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.504753112792969e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 6.4373016357421875e-06s
INFO | --- Analysis for Thinkphile took 2.267549991607666s
Availability | SPARQL endpoint availability check for ThIST took 264.7518525123596s
Availability | VoID file availability check for ThIST took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for ThIST took 0.29204249382019043s
Reputation | Calculation of the PageRank for ThIST took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for ThIST took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.630752563476562e-05s
Believability | Calculation of trust value for ThIST took 1.2874603271484375e-05s
INFO | --- Analysis for thist took 562.3283133506775s
Availability | SPARQL endpoint availability check for TIP took 40.03784799575806s
Availability | VoID file availability check for TIP took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for TIP took 0.24742531776428223s
Reputation | Calculation of the PageRank for TIP took 0.02080678939819336s
Interlinking | Calculation of Degree of Connection for TIP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TIP took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010585784912109375s
Believability | Calculation of trust value for TIP took 7.867813110351562e-06s
INFO | --- Analysis for tip took 103.40904879570007s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.267692565917969e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.2755093574523926s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.02275395393371582s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.361701965332031e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.1682510375976562e-05s
INFO | --- Analysis for TOPMODEL took 26.217338800430298s
Availability | SPARQL endpoint availability check for Tourpedia took 8.511543273925781e-05s
Availability | VoID file availability check for Tourpedia took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.256683349609375s
Reputation | Calculation of the PageRank for Tourpedia took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 2.7418136596679688e-05s
Believability | Calculation of trust value for Tourpedia took 1.430511474609375e-05s
INFO | --- Analysis for tourpedia took 3.7576024532318115s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 4.447268724441528s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.25052714347839355s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.147125244140625e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.1444091796875e-05s
INFO | --- Analysis for TP-data took 8.20304536819458s
Availability | SPARQL endpoint availability check for Trackloaded Artist Profiles took 3.173025608062744s
Availability | VoID file availability check for Trackloaded Artist Profiles took 0.0006644725799560547s
Extra | Recovery of all triples for Trackloaded Artist Profiles took 2.853890895843506s
Performance | Total latancy measurement for Trackloaded Artist Profiles took 6.28439474105835s
Amount of data | Number of triples check for Trackloaded Artist Profiles took 3.6422669887542725s
Interoperability | New terms check for Trackloaded Artist Profiles took 4.616663932800293s
Versatility | Languages check for Trackloaded Artist Profiles took 2.435749053955078s
Interpretability | Number of blank nodes check for Trackloaded Artist Profiles took 2.0771381855010986s
Interpretability | RDF structures check for Trackloaded Artist Profiles took 2.3110482692718506s
Versatility | Serialization formats check for Trackloaded Artist Profiles took 1.3875916004180908s
Availability | RDF dump link check for Trackloaded Artist Profiles took 2.040114402770996s
License | MR license check for Trackloaded Artist Profiles took 1.5870509147644043s
License | HR license check for Trackloaded Artist Profiles took 2.4836270809173584s
Amount of data | Number of property check for Trackloaded Artist Profiles took 2.6336722373962402s
Understandability | Number of label check for Trackloaded Artist Profiles took 1.906198263168335s
Understandability | URI regex check for Trackloaded Artist Profiles took 3.2660984992980957s
Understandability | Vocabs check for Trackloaded Artist Profiles took 1.3765320777893066s
Verifiability | Authors check for Trackloaded Artist Profiles took 3.3962180614471436s
Verifiability | Publishers check for Trackloaded Artist Profiles took 1.6970939636230469s
Performance | Throughput check for Trackloaded Artist Profiles took 14.092285394668579s
Amount of data | Check the number of entities for Trackloaded Artist Profiles took 4.1484832763671875e-05s
Verifiability | Contribs. check for Trackloaded Artist Profiles took 0.8174126148223877s
Interlinking | sameAs chians check for Trackloaded Artist Profiles took 1.1185708045959473s
Interlinking | skos check for Trackloaded Artist Profiles took 0.4879739284515381s
Interlinking | skos check for Trackloaded Artist Profiles took 0.407620906829834s
Timeliness | dataset update frequency check for Trackloaded Artist Profiles took 0.42380380630493164s
Currency | Creation date check for Trackloaded Artist Profiles took 0.9765620231628418s
Currency | Modification date check for Trackloaded Artist Profiles took 0.7841849327087402s
Rep.Conc. | URIs length for Trackloaded Artist Profiles took 1.5992136001586914s
Interoperability | New vocabularies check for Trackloaded Artist Profiles took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Artist Profiles took 0.6044299602508545s
Consistency | Disjoint class check for Trackloaded Artist Profiles took 1.0872864723205566s
Consistency | Check Ontology hijacking for Trackloaded Artist Profiles took 0.4124436378479004s
Consistency | Check Invalid usage of undefined properties for Trackloaded Artist Profiles took 1.6757028102874756s
Conciseness | Check Extensional conciseness for Trackloaded Artist Profiles took 0.0001373291015625s
Security | Sign check for Trackloaded Artist Profiles took 0.38528919219970703s
Completeness | Calculation of interlinking completeness for Trackloaded Artist Profiles took 0.2359910011291504s
Reputation | Calculation of the PageRank for Trackloaded Artist Profiles took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Trackloaded Artist Profiles took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Trackloaded Artist Profiles took 0.0006799697875976562s
Interlinking | Calculation of Clustering coefficient for Trackloaded Artist Profiles took 1.6450881958007812e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Artist Profiles took 1.430511474609375e-06s
Believability | Calculation of trust value for Trackloaded Artist Profiles took 6.9141387939453125e-06s
INFO | --- Analysis for trackloaded took 100.00828647613525s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.4170389175415039s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.6845417022705078s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.019966602325439453s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.029273986816406e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for traditional-korean-medicine took 3.7655606269836426s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.2549147605895996s
Availability | VoID file availability check for Traffic Scotland took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.24218344688415527s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.1948089599609375e-05s
Believability | Calculation of trust value for Traffic Scotland took 9.5367431640625e-06s
INFO | --- Analysis for traffic-scotland took 3.09942889213562s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.5731854438781738s
Availability | VoID file availability check for Transparency International Linked Data took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.2777290344238281s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02042412757873535s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010085105895996094s
Believability | Calculation of trust value for Transparency International Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for transparency-linked-data took 3.459882974624634s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.6849327087402344s
Availability | VoID file availability check for transport.data.gov.uk took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2459430694580078s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 8.559226989746094e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 8.344650268554688e-06s
INFO | --- Analysis for transport-data-gov-uk took 3.858180046081543s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 3.9577484130859375e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.25136280059814453s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.02116084098815918s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 1.2636184692382812e-05s
INFO | --- Analysis for transport-openuplabs took 2.8852381706237793s
Availability | SPARQL endpoint availability check for Trelios took 4.220008850097656e-05s
Availability | VoID file availability check for Trelios took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Trelios took 0.27805376052856445s
Reputation | Calculation of the PageRank for Trelios took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Trelios took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.0967254638671875e-05s
Believability | Calculation of trust value for Trelios took 7.3909759521484375e-06s
INFO | --- Analysis for Trelios took 2.3870558738708496s
Availability | SPARQL endpoint availability check for Twarql took 10.573992013931274s
Availability | VoID file availability check for Twarql took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Twarql took 0.24715781211853027s
Reputation | Calculation of the PageRank for Twarql took 0.02149510383605957s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.580352783203125e-05s
Believability | Calculation of trust value for Twarql took 1.4066696166992188e-05s
INFO | --- Analysis for twarql took 12.976405382156372s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.1961669921875e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.2653627395629883s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.02090764045715332s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.9577484130859375e-05s
Believability | Calculation of trust value for TWC Data-gov took 1.0251998901367188e-05s
INFO | --- Analysis for twc-data-gov took 12.733168125152588s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 5.9604644775390625e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.0004000663757324219s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.24645781517028809s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 3.2901763916015625e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 1.239776611328125e-05s
INFO | --- Analysis for twc-demos took 2.854982614517212s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.15124225616455078s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.2793402671813965s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.0994415283203125e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 1.0013580322265625e-05s
INFO | --- Analysis for twc-healthdata took 29.19393754005432s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.2381744384765625s
Availability | VoID file availability check for Instance Hub (all) took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.3738529682159424s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.104873657226562e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.1682510375976562e-05s
INFO | --- Analysis for twc-hub took 85.64375853538513s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.14238595962524414s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.3226349353790283s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.021616697311401367s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00011229515075683594s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.2159347534179688e-05s
INFO | --- Analysis for twc-ieeevis took 118.27710175514221s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 8.535385131835938e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.26418375968933105s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.020583152770996094s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.1552734375e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 5.245208740234375e-06s
INFO | --- Analysis for twc-logd took 2.447354555130005s
Availability | SPARQL endpoint availability check for twc-opendap took 0.13082122802734375s
Availability | VoID file availability check for twc-opendap took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.25277256965637207s
Reputation | Calculation of the PageRank for twc-opendap took 0.022914409637451172s
Interlinking | Calculation of Degree of Connection for twc-opendap took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 6.437301635742188e-05s
Believability | Calculation of trust value for twc-opendap took 1.2874603271484375e-05s
INFO | --- Analysis for twc-opendap took 62.073615312576294s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 4.029273986816406e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.2899913787841797s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.02242588996887207s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 2.86102294921875e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.1920928955078125e-05s
INFO | --- Analysis for tweetskb took 2.8965837955474854s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 8.225440979003906e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.2488565444946289s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.020574092864990234s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 2.7179718017578125e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 1.2159347534179688e-05s
INFO | --- Analysis for twitter-lids took 2.8538384437561035s
Availability | SPARQL endpoint availability check for typepad took 0.00010180473327636719s
Availability | VoID file availability check for typepad took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for typepad took 0.2548513412475586s
Reputation | Calculation of the PageRank for typepad took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for typepad took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for typepad took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for typepad took 4.887580871582031e-05s
Believability | Calculation of trust value for typepad took 7.867813110351562e-06s
INFO | --- Analysis for typepad took 3.469287872314453s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.9847397804260254s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.2420186996459961s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.022060394287109375s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 3.814697265625e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.1205673217773438e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 4.582449674606323s
Availability | SPARQL endpoint availability check for Uberblic.org took 3.841609239578247s
Availability | VoID file availability check for Uberblic.org took 0.0014019012451171875s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.271451473236084s
Reputation | Calculation of the PageRank for Uberblic.org took 0.02112865447998047s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010180473327636719s
Believability | Calculation of trust value for Uberblic.org took 1.0967254638671875e-05s
INFO | --- Analysis for uberblic took 8.760344743728638s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6304287910461426s
Availability | VoID file availability check for UDante in LiLa took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.295604944229126s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.02146315574645996s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for UDante in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for UDante took 4.135655403137207s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 0.9530360698699951s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.26421189308166504s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.021953344345092773s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for ufo took 4.522263288497925s
Availability | SPARQL endpoint availability check for Uganda Disasters took 6.628036499023438e-05s
Availability | VoID file availability check for Uganda Disasters took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.2445991039276123s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.38690185546875e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.1682510375976562e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.3150458335876465s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0615391731262207s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0010485649108886719s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.26878952980041504s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.02026057243347168s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 9.632110595703125e-05s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.3113021850585938e-05s
INFO | --- Analysis for uis-linked-data took 2.4166479110717773s
Availability | SPARQL endpoint availability check for UK Legislation took 6.866455078125e-05s
Availability | VoID file availability check for UK Legislation took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.26769042015075684s
Reputation | Calculation of the PageRank for UK Legislation took 0.020263195037841797s
Interlinking | Calculation of Degree of Connection for UK Legislation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.654594421386719e-05s
Believability | Calculation of trust value for UK Legislation took 9.775161743164062e-06s
INFO | --- Analysis for uk-legislation-api took 3.5206353664398193s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.172325134277344e-05s
Availability | VoID file availability check for UK Postcodes took 0.0006964206695556641s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.2593874931335449s
Reputation | Calculation of the PageRank for UK Postcodes took 0.021030902862548828s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.9604644775390625e-05s
Believability | Calculation of trust value for UK Postcodes took 1.1682510375976562e-05s
INFO | --- Analysis for uk-postcodes took 22.33285689353943s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 7.152557373046875e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.26238179206848145s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.022038936614990234s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00014281272888183594s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.2636184692382812e-05s
INFO | --- Analysis for umbel took 6.71259331703186s
Availability | SPARQL endpoint availability check for UMTHES took 8.702278137207031e-05s
Availability | VoID file availability check for UMTHES took 0.0011212825775146484s
Completeness | Calculation of interlinking completeness for UMTHES took 0.26411867141723633s
Reputation | Calculation of the PageRank for UMTHES took 0.022548913955688477s
Interlinking | Calculation of Degree of Connection for UMTHES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for UMTHES took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.076957702636719e-05s
Believability | Calculation of trust value for UMTHES took 9.5367431640625e-06s
INFO | --- Analysis for umthes took 3.593869686126709s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 0.9530806541442871s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.24691462516784668s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 2.8848648071289062e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 9.059906005859375e-06s
INFO | --- Analysis for un-hazardous-numbers took 6.512548446655273s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.25191450119018555s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for unesco-thesaurus took 2.8469152450561523s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2733776569366455s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020638227462768555s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 2.765655517578125e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for unescothes took 2.9524147510528564s
Availability | SPARQL endpoint availability check for UniProt took 2.2406606674194336s
Availability | VoID file availability check for UniProt took 0.0006151199340820312s
Extra | Recovery of all triples for UniProt took 15.669735193252563s
Performance | Total latancy measurement for UniProt took 4.386847019195557s
Amount of data | Number of triples check for UniProt took 0.42284584045410156s
Interoperability | New terms check for UniProt took 1.6628589630126953s
Versatility | Languages check for UniProt took 1.296215534210205s
Interpretability | Number of blank nodes check for UniProt took 1.5530002117156982s
Interpretability | RDF structures check for UniProt took 1.6262683868408203s
Versatility | Serialization formats check for UniProt took 1.911559820175171s
Availability | RDF dump link check for UniProt took 0.23778414726257324s
License | MR license check for UniProt took 1.2098097801208496s
License | HR license check for UniProt took 300.162136554718s
Amount of data | Number of property check for UniProt took 0.09395933151245117s
Understandability | Number of label check for UniProt took 40.772483348846436s
Understandability | URI regex check for UniProt took 0.5791542530059814s
Understandability | Vocabs check for UniProt took 0.6690113544464111s
Verifiability | Authors check for UniProt took 1.2896432876586914s
Verifiability | Publishers check for UniProt took 1.0524115562438965s
Performance | Throughput check for UniProt took 22.021673679351807s
Amount of data | Check the number of entities for UniProt took 6.961822509765625e-05s
Verifiability | Contribs. check for UniProt took 0.727210521697998s
Interlinking | sameAs chians check for UniProt took 0.3512580394744873s
Interlinking | skos check for UniProt took 0.7749695777893066s
Interlinking | skos check for UniProt took 0.821042537689209s
Timeliness | dataset update frequency check for UniProt took 1.3462095260620117s
Currency | Creation date check for UniProt took 1.6074209213256836s
Currency | Modification date check for UniProt took 1.4193179607391357s
Rep.Conc. | URIs length for UniProt took 105.42646670341492s
Interoperability | New vocabularies check for UniProt took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.22762727737426758s
Accuracy | Check Functional Property for UniProt took 0.3562657833099365s
Accuracy | Check Inverse Functional Property for UniProt took 0.2731764316558838s
Accuracy | Check Empty annotation labels for UniProt took 10.754054546356201s
Accuracy | Check White space in annotation for UniProt took 2.639662027359009s
Accuracy | Check Datatype consistency for UniProt took 7.191020488739014s
Consistency | Disjoint class check for UniProt took 0.3469870090484619s
Consistency | Check Misplaced properties for UniProt took 5.3385608196258545s
Consistency | Check Ontology hijacking for UniProt took 7.231569051742554s
Consistency | Check Invalid usage of undefined classes for UniProt took 18870.432344198227s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.9035887718200684s
Conciseness | Check Extensional conciseness for UniProt took 2.6221189498901367s
Conciseness | Check Intensional conciseness for UniProt took 0.6280684471130371s
Security | Sign check for UniProt took 0.845181941986084s
Availability | Check URIs Dereferenciability for UniProt took 4.179598808288574s
Completeness | Calculation of interlinking completeness for UniProt took 1.8002374172210693s
Reputation | Calculation of the PageRank for UniProt took 0.021746397018432617s
Interlinking | Calculation of Degree of Connection for UniProt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for UniProt took 5.030632019042969e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.9073486328125e-06s
Believability | Calculation of trust value for UniProt took 7.867813110351562e-06s
INFO | --- Analysis for UniProt took 19846.550595760345s
Availability | SPARQL endpoint availability check for UniProt took 2.062314033508301s
Availability | VoID file availability check for UniProt took 0.0005998611450195312s
Extra | Recovery of all triples for UniProt took 18.36771821975708s
Performance | Total latancy measurement for UniProt took 5.330885171890259s
Amount of data | Number of triples check for UniProt took 0.5730438232421875s
Versatility | Languages check for UniProt took 1.51609468460083s
Interpretability | Number of blank nodes check for UniProt took 1.9309144020080566s
Security | Check HTTPS for UniProt took 0.1952667236328125s
Interpretability | RDF structures check for UniProt took 0.16015052795410156s
Versatility | Serialization formats check for UniProt took 0.14896607398986816s
Availability | RDF dump link check for UniProt took 0.16139435768127441s
License | MR license check for UniProt took 0.15337657928466797s
License | HR license check for UniProt took 0.16636371612548828s
Amount of data | Number of property check for UniProt took 0.14632511138916016s
Understandability | Number of label check for UniProt took 0.1465160846710205s
Understandability | URI regex check for UniProt took 0.31058621406555176s
Understandability | Vocabs check for UniProt took 0.160888671875s
Verifiability | Authors check for UniProt took 0.1476287841796875s
Verifiability | Publishers check for UniProt took 0.14890146255493164s
Performance | Throughput check for UniProt took 26.032466888427734s
Amount of data | Check the number of entities for UniProt took 0.00016736984252929688s
Verifiability | Contribs. check for UniProt took 0.20956969261169434s
Interlinking | sameAs chians check for UniProt took 0.1406252384185791s
Interlinking | skos check for UniProt took 0.16467547416687012s
Interlinking | skos check for UniProt took 0.1455521583557129s
Timeliness | dataset update frequency check for UniProt took 0.1540820598602295s
Currency | Creation date check for UniProt took 0.30297327041625977s
Currency | Modification date check for UniProt took 0.30156421661376953s
Rep.Conc. | URIs length for UniProt took 109.24990057945251s
Interoperability | New vocabularies check for UniProt took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.14394402503967285s
Accuracy | Check Datatype consistency for UniProt took 7.187614917755127s
Consistency | Disjoint class check for UniProt took 0.1210787296295166s
Consistency | Check Ontology hijacking for UniProt took 0.16682052612304688s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.8824410438537598s
Conciseness | Check Extensional conciseness for UniProt took 2.6520040035247803s
Security | Sign check for UniProt took 0.13304996490478516s
Availability | Check URIs Dereferenciability for UniProt took 3.5885043144226074s
Completeness | Calculation of interlinking completeness for UniProt took 0.8758087158203125s
Reputation | Calculation of the PageRank for UniProt took 0.021149635314941406s
Interlinking | Calculation of Degree of Connection for UniProt took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006794929504394531s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.1920928955078125e-06s
Believability | Calculation of trust value for UniProt took 1.3828277587890625e-05s
INFO | --- Analysis for uniprot took 721.372766494751s
Availability | SPARQL endpoint availability check for UniProt citations took 8.511543273925781e-05s
Availability | VoID file availability check for UniProt citations took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.26874279975891113s
Reputation | Calculation of the PageRank for UniProt citations took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 3.24249267578125e-05s
Believability | Calculation of trust value for UniProt citations took 1.1444091796875e-05s
INFO | --- Analysis for uniprot-citations took 3.6558926105499268s
Availability | SPARQL endpoint availability check for UniProt databases took 3.9577484130859375e-05s
Availability | VoID file availability check for UniProt databases took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.24563002586364746s
Reputation | Calculation of the PageRank for UniProt databases took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 2.86102294921875e-05s
Believability | Calculation of trust value for UniProt databases took 1.33514404296875e-05s
INFO | --- Analysis for uniprot-databases took 3.672177791595459s
Availability | SPARQL endpoint availability check for uniprot-metadata took 4.506111145019531e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.30331945419311523s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.022140979766845703s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.222724914550781e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.33514404296875e-05s
INFO | --- Analysis for uniprot-metadata took 3.810333490371704s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 4.124641418457031e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.23356342315673828s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 2.9325485229492188e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 1.33514404296875e-05s
INFO | --- Analysis for uniprot-taxonomy took 2.8764941692352295s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.124641418457031e-05s
Availability | VoID file availability check for UniProt UniParc took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.26249122619628906s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 2.9087066650390625e-05s
Believability | Calculation of trust value for UniProt UniParc took 1.3589859008789062e-05s
INFO | --- Analysis for uniprot-uniparc took 2.866089105606079s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 6.723403930664062e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.264512300491333s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.02265620231628418s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 3.075599670410156e-05s
Believability | Calculation of trust value for UniProt UniPathway took 1.0728836059570312e-05s
INFO | --- Analysis for uniprot-unipathway took 2.9241385459899902s
Availability | SPARQL endpoint availability check for UniProtKB took 1.9950411319732666s
Availability | VoID file availability check for UniProtKB took 0.0005216598510742188s
Extra | Recovery of all triples for UniProtKB took 13.770121335983276s
Performance | Total latancy measurement for UniProtKB took 4.409904956817627s
Amount of data | Number of triples check for UniProtKB took 0.42147040367126465s
Interoperability | New terms check for UniProtKB took 1.6832804679870605s
Versatility | Languages check for UniProtKB took 1.435943841934204s
Interpretability | Number of blank nodes check for UniProtKB took 1.8390653133392334s
Interpretability | RDF structures check for UniProtKB took 1.8341846466064453s
Versatility | Serialization formats check for UniProtKB took 1.702672004699707s
Availability | RDF dump link check for UniProtKB took 0.2220749855041504s
License | MR license check for UniProtKB took 1.4965670108795166s
License | HR license check for UniProtKB took 300.0669538974762s
Amount of data | Number of property check for UniProtKB took 0.14506936073303223s
Understandability | Number of label check for UniProtKB took 43.969136476516724s
Understandability | URI regex check for UniProtKB took 0.5918662548065186s
Understandability | Vocabs check for UniProtKB took 0.6925342082977295s
Verifiability | Authors check for UniProtKB took 1.2917449474334717s
Verifiability | Publishers check for UniProtKB took 1.1230361461639404s
Performance | Throughput check for UniProtKB took 22.77656102180481s
Amount of data | Check the number of entities for UniProtKB took 6.771087646484375e-05s
Verifiability | Contribs. check for UniProtKB took 0.7036187648773193s
Interlinking | sameAs chians check for UniProtKB took 0.3790285587310791s
Interlinking | skos check for UniProtKB took 0.8448667526245117s
Interlinking | skos check for UniProtKB took 0.08769607543945312s
Timeliness | dataset update frequency check for UniProtKB took 1.3243529796600342s
Currency | Creation date check for UniProtKB took 1.4025368690490723s
Currency | Modification date check for UniProtKB took 1.6322448253631592s
Rep.Conc. | URIs length for UniProtKB took 100.64270162582397s
Interoperability | New vocabularies check for UniProtKB took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.21555066108703613s
Accuracy | Check Functional Property for UniProtKB took 0.28299498558044434s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.3164350986480713s
Accuracy | Check Empty annotation labels for UniProtKB took 20.87219786643982s
Accuracy | Check White space in annotation for UniProtKB took 2.636584520339966s
Accuracy | Check Datatype consistency for UniProtKB took 7.261779308319092s
Consistency | Disjoint class check for UniProtKB took 0.32009077072143555s
Consistency | Check Misplaced properties for UniProtKB took 4.656343936920166s
Consistency | Check Ontology hijacking for UniProtKB took 6.3636863231658936s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 18852.857983112335s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 1.8319852352142334s
Conciseness | Check Extensional conciseness for UniProtKB took 2.6254944801330566s
Conciseness | Check Intensional conciseness for UniProtKB took 0.5718693733215332s
Security | Sign check for UniProtKB took 0.6684145927429199s
Availability | Check URIs Dereferenciability for UniProtKB took 4.293824195861816s
Completeness | Calculation of interlinking completeness for UniProtKB took 1.2343239784240723s
Reputation | Calculation of the PageRank for UniProtKB took 0.021140098571777344s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProtKB took 1.1205673217773438e-05s
INFO | --- Analysis for uniprotkb took 19904.0435256958s
Availability | SPARQL endpoint availability check for UniProt UniRef took 8.177757263183594e-05s
Availability | VoID file availability check for UniProt UniRef took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.6913983821868896s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.02233433723449707s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 2.8371810913085938e-05s
Believability | Calculation of trust value for UniProt UniRef took 1.239776611328125e-05s
INFO | --- Analysis for uniref took 5.968092203140259s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 3.9577484130859375e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.26230788230895996s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 2.7418136596679688e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.239776611328125e-05s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 3.3211557865142822s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 4.029273986816406e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.26631927490234375s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 2.6464462280273438e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 1.239776611328125e-05s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 4.150506496429443s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 0.00010156631469726562s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.28203654289245605s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.560055255889893s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.00010514259338378906s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.2768261432647705s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 3.975710868835449s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 8.416175842285156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.2566096782684326s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.022480010986328125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 3.552436828613281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.2543203830719s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.3048276901245117s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.02105426788330078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.441458463668823s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 8.320808410644531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0007600784301757812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.2799224853515625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.021117210388183594s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.302936792373657s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 8.249282836914062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.2649867534637451s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 15.052912950515747s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 7.843971252441406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.00038623809814453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 5.29276180267334s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.021463632583618164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 9.286861896514893s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 8.749961853027344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.30107903480529785s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.021131277084350586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.249699831008911s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 5.2928924560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.3361091613769531s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.241090536117554s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.001165151596069336s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.2630574703216553s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.020962238311767578s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.24966812133789s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.27655625343322754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020926952362060547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 12.99283766746521s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.24509382247924805s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.12317419052124s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 9.584426879882812e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.26059675216674805s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.021062374114990234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.06230092048645s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 8.7738037109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0007734298706054688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.385115385055542s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.021756410598754883s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.381737470626831s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.24614262580871582s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.021173477172851562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.220968246459961s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 5.316734313964844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.24907946586608887s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.02118396759033203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 18.04931330680847s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 5.1021575927734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.000766754150390625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.2637028694152832s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.02131795883178711s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.839897155761719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.031501293182373s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.7516043186187744s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.021915674209594727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 3.552436828613281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.455667734146118s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.5020990371704102s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 14.057029008865356s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.26638031005859375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.021158456802368164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 4.548672914505005s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2631239891052246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.02123260498046875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.085551977157593s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0007789134979248047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.25792956352233887s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.02111673355102539s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.068715333938599s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.26729655265808105s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.021308422088623047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.22849726676941s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 6.818771362304688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.2535276412963867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.8286147117614746s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.27362489700317383s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02315354347229004s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 3.909088611602783s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.24921083450317383s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 3.85876202583313s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.2545464038848877s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020971298217773438s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 4.26050329208374s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.29559779167175293s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.217881441116333s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 7.343292236328125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.2453293800354004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.021294355392456055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0010080337524414062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.122390747070312s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.2542393207550049s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.021754980087280273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 3.855811834335327s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 7.390975952148438e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.23994731903076172s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.081205368041992s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.26207709312438965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 3.8122920989990234s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.25881004333496094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020977497100830078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.240411758422852s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 8.559226989746094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.3002445697784424s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.24445915222168s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 8.630752563476562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.25273847579956055s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 3.5758607387542725s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.744529724121094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.2791616916656494s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020855188369750977s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.288472890853882s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 8.416175842285156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.2819352149963379s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.021955013275146484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 3.959876775741577s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.3432481288909912s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02146768569946289s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 12.991321563720703s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.24045443534851074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.072735071182251s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.27347540855407715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.021787643432617188s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.28033185005188s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.25532102584838867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020586252212524414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 12.970065593719482s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.24649405479431152s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.117425680160522s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.2752063274383545s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 3.748563051223755s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.705925464630127s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.557723760604858s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 8.559226989746094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.3264482021331787s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 12.790413856506348s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0007548332214355469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.26874566078186035s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 12.92083477973938s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.2547459602355957s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.264495134353638s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.26468610763549805s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0009832382202148438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.240983247756958s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.2785987854003906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.020961761474609375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.00106048583984375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.294870615005493s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.00034236907958984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.2660186290740967s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 3.821058511734009s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.2661924362182617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 5.555152893066406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.17918610572815s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.23918652534484863s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.020947933197021484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 1.5020370483398438e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.122220277786255s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.3295130729675293s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.293227434158325s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.26761555671691895s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020610570907592773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.046000719070435s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.24194765090942383s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.12573504447937s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 9.5367431640625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.24179863929748535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 12.895883321762085s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.24925637245178223s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 3.9837515354156494s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.2531754970550537s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.021342039108276367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 3.534301996231079s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 8.654594421386719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.24210095405578613s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.452075719833374s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.2639501094818115s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.106600046157837s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 5.698204040527344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.2723424434661865s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020984649658203125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.199387073516846s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0008518695831298828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.26085448265075684s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.02072429656982422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.2407386302948s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 8.58306884765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.2545480728149414s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.325469970703125s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.35779714584350586s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.021586179733276367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.27349066734314s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.3392181396484375e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.25342726707458496s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.02112102508544922s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.604194641113281e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.1920928955078125e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.4497363567352295s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 4.100799560546875e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.24613642692565918s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.020757675170898438s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 3.123283386230469e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 1.1444091796875e-05s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 2.8323843479156494s
Availability | SPARQL endpoint availability check for University of Bristol took 8.034706115722656e-05s
Availability | VoID file availability check for University of Bristol took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.2913365364074707s
Reputation | Calculation of the PageRank for University of Bristol took 0.022551298141479492s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 2.9325485229492188e-05s
Believability | Calculation of trust value for University of Bristol took 1.1920928955078125e-05s
INFO | --- Analysis for university-of-bristol took 2.9859635829925537s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.3392181396484375e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.26427197456359863s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020848751068115234s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.1021575927734375e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.2159347534179688e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 2.8869192600250244s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.887580871582031e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.2767322063446045s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.021821022033691406s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.6716461181640625e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.1444091796875e-05s
INFO | --- Analysis for university-sussex-reading-lists took 2.7368788719177246s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 5.766263961791992s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.27219414710998535s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.82012939453125e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.239776611328125e-05s
INFO | --- Analysis for unodc took 15.58171534538269s
Availability | SPARQL endpoint availability check for Super Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Super Ontology took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.26817798614501953s
Reputation | Calculation of the PageRank for Super Ontology took 0.020757436752319336s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 8.106231689453125e-05s
Believability | Calculation of trust value for Super Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for upper-ontology took 3.445641040802002s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 1.3565459251403809s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.2599010467529297s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.022287607192993164s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.504753112792969e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.1444091796875e-05s
INFO | --- Analysis for Upper_Ontology took 4.859880447387695s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 9.72747802734375e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.26850199699401855s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 2.9802322387695312e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.3589859008789062e-05s
INFO | --- Analysis for Urban_Atlas_ took 2.3988611698150635s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 10.769439458847046s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.2787973880767822s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.022452354431152344s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0009846687316894531s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 3.528594970703125e-05s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for Urban_Atlas_Dataset took 13.893128395080566s
Availability | SPARQL endpoint availability check for URIBurner took 1.8023602962493896s
Availability | VoID file availability check for URIBurner took 0.0007176399230957031s
Extra | Recovery of all triples for URIBurner took 120.58001470565796s
Performance | Total latancy measurement for URIBurner took 2.892176389694214s
Amount of data | Number of triples check for URIBurner took 4.089522838592529s
Interoperability | New terms check for URIBurner took 37.770142555236816s
Versatility | Languages check for URIBurner took 123.24080538749695s
Interpretability | Number of blank nodes check for URIBurner took 1.8926143646240234s
Security | Check HTTPS for URIBurner took 0.9323899745941162s
Interpretability | RDF structures check for URIBurner took 0.7208223342895508s
Versatility | Serialization formats check for URIBurner took 6.19825291633606s
Availability | RDF dump link check for URIBurner took 47.767478942871094s
License | MR license check for URIBurner took 0.7815427780151367s
License | HR license check for URIBurner took 122.69026851654053s
Amount of data | Number of property check for URIBurner took 0.8040118217468262s
Understandability | Number of label check for URIBurner took 3.157388210296631s
Understandability | URI regex check for URIBurner took 1.2717275619506836s
Understandability | Vocabs check for URIBurner took 0.6002302169799805s
Verifiability | Authors check for URIBurner took 1.7437705993652344s
Verifiability | Publishers check for URIBurner took 0.5797579288482666s
Performance | Throughput check for URIBurner took 10.947645664215088s
Amount of data | Check the number of entities for URIBurner took 9.393692016601562e-05s
Verifiability | Contribs. check for URIBurner took 0.5804660320281982s
Interlinking | sameAs chians check for URIBurner took 0.8782269954681396s
Interlinking | skos check for URIBurner took 0.5726630687713623s
Interlinking | skos check for URIBurner took 0.5346450805664062s
Timeliness | dataset update frequency check for URIBurner took 1.035343885421753s
Currency | Creation date check for URIBurner took 3.204084634780884s
Currency | Modification date check for URIBurner took 0.6158113479614258s
Rep.Conc. | URIs length for URIBurner took 113.99132251739502s
Interoperability | New vocabularies check for URIBurner took 38.21759104728699s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.6111500263214111s
Accuracy | Check Functional Property for URIBurner took 0.5791411399841309s
Accuracy | Check Inverse Functional Property for URIBurner took 0.5892565250396729s
Accuracy | Check Empty annotation labels for URIBurner took 56.24107003211975s
Accuracy | Check White space in annotation for URIBurner took 0.18262791633605957s
Consistency | Disjoint class check for URIBurner took 0.5680639743804932s
Consistency | Check Misplaced properties for URIBurner took 301.53232884407043s
Consistency | Misplaced classes for URIBurner took 57.434520959854126s
Consistency | Check Ontology hijacking for URIBurner took 58.7044472694397s
Consistency | Check Invalid usage of undefined properties for URIBurner took 59.612719774246216s
Conciseness | Check Extensional conciseness for URIBurner took 0.0001232624053955078s
Conciseness | Check Intensional conciseness for URIBurner took 112.8251039981842s
Security | Sign check for URIBurner took 0.8545753955841064s
Completeness | Calculation of interlinking completeness for URIBurner took 1.9364814758300781s
Reputation | Calculation of the PageRank for URIBurner took 0.020934104919433594s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for URIBurner took 9.72747802734375e-05s
Interoperability | Check the re-using of existing vocabs for URIBurner took 31.94566512107849s
Believability | Calculation of trust value for URIBurner took 7.867813110351562e-06s
INFO | --- Analysis for uriburner took 11908.622511863708s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 5.316734313964844e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.28832101821899414s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02121877670288086s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.9325485229492188e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1444091796875e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 3.6666128635406494s
Availability | SPARQL endpoint availability check for Legija Stranaca took 9.679794311523438e-05s
Availability | VoID file availability check for Legija Stranaca took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.23217391967773438s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.022268056869506836s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 2.8371810913085938e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.2874603271484375e-05s
INFO | --- Analysis for Uros_Legija_Susa took 3.2152814865112305s
Availability | SPARQL endpoint availability check for Legija took 8.487701416015625e-05s
Availability | VoID file availability check for Legija took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Legija took 0.7037651538848877s
Reputation | Calculation of the PageRank for Legija took 0.021500825881958008s
Interlinking | Calculation of Degree of Connection for Legija took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Legija took 2.956390380859375e-05s
Believability | Calculation of trust value for Legija took 1.2636184692382812e-05s
INFO | --- Analysis for Uros_Susa took 3.2385191917419434s
Availability | SPARQL endpoint availability check for US Political Violence took 4.100799560546875e-05s
Availability | VoID file availability check for US Political Violence took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.6906182765960693s
Reputation | Calculation of the PageRank for US Political Violence took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for US Political Violence took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 2.6464462280273438e-05s
Believability | Calculation of trust value for US Political Violence took 1.2159347534179688e-05s
INFO | --- Analysis for us-political-violence took 3.3683922290802s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.4280524253845215s
Availability | VoID file availability check for USAGE review corpus took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.27055883407592773s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.022478580474853516s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.24249267578125e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.3828277587890625e-05s
INFO | --- Analysis for usage-review-corpus took 3.557629108428955s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 5.96738076210022s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.29324984550476074s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.021146774291992188s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.557868957519531e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for utpl-lod took 11.91396188735962s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 8.487701416015625e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.2796938419342041s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.021918773651123047s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 3.0040740966796875e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 9.775161743164062e-06s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 2.9386913776397705s
Availability | SPARQL endpoint availability check for terrorist attack took 4.172325134277344e-05s
Availability | VoID file availability check for terrorist attack took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.2566967010498047s
Reputation | Calculation of the PageRank for terrorist attack took 0.022756338119506836s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0010347366333007812s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.5762786865234375e-05s
Believability | Calculation of trust value for terrorist attack took 1.3113021850585938e-05s
INFO | --- Analysis for varsha took 3.9673118591308594s
Availability | SPARQL endpoint availability check for VA took 8.559226989746094e-05s
Availability | VoID file availability check for VA took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for VA took 0.23775649070739746s
Reputation | Calculation of the PageRank for VA took 0.020784378051757812s
Interlinking | Calculation of Degree of Connection for VA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VA took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for VA took 3.0040740966796875e-05s
Believability | Calculation of trust value for VA took 1.1205673217773438e-05s
INFO | --- Analysis for Vehicule_Autonome took 3.7396152019500732s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.6512835025787354s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.24065876007080078s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 4.257054567337036s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.563456058502197s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.24946880340576172s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.344650268554688e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.0967254638671875e-05s
INFO | --- Analysis for verrijktkoninkrijk took 15.061660051345825s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 4.220008850097656e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.2809321880340576s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.020893573760986328s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00017523765563964844s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.4066696166992188e-05s
INFO | --- Analysis for viaf took 19.65535807609558s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 7.557868957519531e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.2530515193939209s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.020714998245239258s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 2.956390380859375e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 1.239776611328125e-05s
INFO | --- Analysis for vias-publicas-zaragoza took 2.7999300956726074s
Availability | SPARQL endpoint availability check for Vihar Exports took 6.127357482910156e-05s
Availability | VoID file availability check for Vihar Exports took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.2692251205444336s
Reputation | Calculation of the PageRank for Vihar Exports took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 2.8133392333984375e-05s
Believability | Calculation of trust value for Vihar Exports took 1.1444091796875e-05s
INFO | --- Analysis for Vihar_Exports took 2.32407808303833s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 8.058547973632812e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.2597651481628418s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.02248859405517578s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0011200904846191406s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 3.647804260253906e-05s
Believability | Calculation of trust value for vimeo.videoobject took 1.1682510375976562e-05s
INFO | --- Analysis for vimeo_videoobject took 2.839104652404785s
Availability | SPARQL endpoint availability check for VIVO took 8.463859558105469e-05s
Availability | VoID file availability check for VIVO took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for VIVO took 0.27800536155700684s
Reputation | Calculation of the PageRank for VIVO took 0.02270674705505371s
Interlinking | Calculation of Degree of Connection for VIVO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.437301635742188e-05s
Believability | Calculation of trust value for VIVO took 1.0967254638671875e-05s
INFO | --- Analysis for vivo took 4.750542640686035s
Availability | SPARQL endpoint availability check for VIVO Cornell took 8.249282836914062e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.27913546562194824s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.021504640579223633s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 7.796287536621094e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.049041748046875e-05s
INFO | --- Analysis for vivo-cornell-university took 5.807804346084595s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 8.916854858398438e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.2588226795196533s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 2.7418136596679688e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 1.2159347534179688e-05s
INFO | --- Analysis for vivo-cu-boulder took 2.787468910217285s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.267692565917969e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.25188446044921875s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.021693944931030273s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 7.843971252441406e-05s
Believability | Calculation of trust value for VIVO Indiana took 5.7220458984375e-06s
INFO | --- Analysis for vivo-indiana-university took 2.9173624515533447s
Availability | SPARQL endpoint availability check for VIVO Ponce took 4.076957702636719e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.25843214988708496s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.314018249511719e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.0967254638671875e-05s
INFO | --- Analysis for vivo-ponce took 2.7155473232269287s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 0.0001010894775390625s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.25324296951293945s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.6716461181640625e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.0728836059570312e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 2.840951442718506s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 8.440017700195312e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.301807165145874s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.022651195526123047s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.72747802734375e-05s
Believability | Calculation of trust value for VIVO University of Florida took 1.0013580322265625e-05s
INFO | --- Analysis for vivo-university-of-florida took 2.662925958633423s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 6.914138793945312e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.2530856132507324s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.02099776268005371s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.62396240234375e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 1.0251998901367188e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.9042155742645264s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 8.630752563476562e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.25063467025756836s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.62396240234375e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.0251998901367188e-05s
INFO | --- Analysis for vivo-wustl took 2.711381196975708s
Availability | SPARQL endpoint availability check for vivo2doi took 8.344650268554688e-05s
Availability | VoID file availability check for vivo2doi took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.30600690841674805s
Reputation | Calculation of the PageRank for vivo2doi took 0.023094892501831055s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.7206878662109375e-05s
Believability | Calculation of trust value for vivo2doi took 1.0728836059570312e-05s
INFO | --- Analysis for vivo2doi took 33.5432071685791s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 0.00010704994201660156s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.27673792839050293s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020721435546875s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.508827209472656e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.0251998901367188e-05s
INFO | --- Analysis for vu-wordnet took 14.538843154907227s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.8830552101135254s
Availability | VoID file availability check for vulnerapedia took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.2638590335845947s
Reputation | Calculation of the PageRank for vulnerapedia took 0.021578073501586914s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 7.104873657226562e-05s
Believability | Calculation of trust value for vulnerapedia took 1.0013580322265625e-05s
INFO | --- Analysis for vulnerapedia took 3.7443747520446777s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 5.3882598876953125e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.24831748008728027s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.021092653274536133s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2636184692382812e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2874603271484375e-05s
INFO | --- Analysis for VVASIAK took 2.343627691268921s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 8.726119995117188e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.29697275161743164s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.314018249511719e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.2874603271484375e-05s
INFO | --- Analysis for Vyvasta took 2.411670207977295s
Availability | SPARQL endpoint availability check for W3C took 4.57763671875e-05s
Availability | VoID file availability check for W3C took 0.0007624626159667969s
Completeness | Calculation of interlinking completeness for W3C took 0.263777494430542s
Reputation | Calculation of the PageRank for W3C took 0.02159738540649414s
Interlinking | Calculation of Degree of Connection for W3C took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for W3C took 0.0009868144989013672s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00016188621520996094s
Believability | Calculation of trust value for W3C took 1.239776611328125e-05s
INFO | --- Analysis for w3c took 3.0824735164642334s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.38690185546875e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.24971532821655273s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.022480249404907227s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 3.910064697265625e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 1.2636184692382812e-05s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 3.0047731399536133s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.553794860839844e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0007593631744384766s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.26293277740478516s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00014328956604003906s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.2874603271484375e-05s
INFO | --- Analysis for w3c-wordnet took 3.563901662826538s
Availability | SPARQL endpoint availability check for WarSampo took 0.3830435276031494s
Availability | VoID file availability check for WarSampo took 0.0006783008575439453s
Extra | Recovery of all triples for WarSampo took 28.354332208633423s
Performance | Total latancy measurement for WarSampo took 0.9684963226318359s
Amount of data | Number of triples check for WarSampo took 22.573630571365356s
Interoperability | New terms check for WarSampo took 4.818320035934448s
Versatility | Languages check for WarSampo took 54.00315880775452s
Interpretability | Number of blank nodes check for WarSampo took 20.45028066635132s
Security | Check HTTPS for WarSampo took 0.4715394973754883s
Interpretability | RDF structures check for WarSampo took 0.2063908576965332s
Versatility | Serialization formats check for WarSampo took 0.1888258457183838s
Availability | RDF dump link check for WarSampo took 0.8553245067596436s
License | MR license check for WarSampo took 0.19056940078735352s
License | HR license check for WarSampo took 43.52903485298157s
Amount of data | Number of property check for WarSampo took 0.19514703750610352s
Understandability | Number of label check for WarSampo took 12.790042877197266s
Understandability | URI regex check for WarSampo took 0.4012417793273926s
Understandability | Vocabs check for WarSampo took 0.18320512771606445s
Verifiability | Authors check for WarSampo took 0.22104954719543457s
Verifiability | Publishers check for WarSampo took 0.2095942497253418s
Performance | Throughput check for WarSampo took 11.165995121002197s
Amount of data | Check the number of entities for WarSampo took 15.695619106292725s
Verifiability | Contribs. check for WarSampo took 0.19537639617919922s
Interlinking | sameAs chians check for WarSampo took 0.19093823432922363s
Interlinking | skos check for WarSampo took 0.2215714454650879s
Interlinking | skos check for WarSampo took 0.18538403511047363s
Timeliness | dataset update frequency check for WarSampo took 0.21423888206481934s
Currency | Creation date check for WarSampo took 0.3952333927154541s
Currency | Modification date check for WarSampo took 0.42722129821777344s
Rep.Conc. | URIs length for WarSampo took 49.14955115318298s
Interoperability | New vocabularies check for WarSampo took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.1931471824645996s
Accuracy | Check Functional Property for WarSampo took 0.18281340599060059s
Accuracy | Check Inverse Functional Property for WarSampo took 0.17088532447814941s
Accuracy | Check Empty annotation labels for WarSampo took 11.632593393325806s
Accuracy | Check White space in annotation for WarSampo took 2.186872720718384s
Accuracy | Check Datatype consistency for WarSampo took 5.31488037109375s
Consistency | Disjoint class check for WarSampo took 0.2294480800628662s
Consistency | Check Misplaced properties for WarSampo took 20.25046396255493s
Consistency | Check Ontology hijacking for WarSampo took 19.01041865348816s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.3412384986877441s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.5998518466949463s
Conciseness | Check Extensional conciseness for WarSampo took 2.7769885063171387s
Conciseness | Check Intensional conciseness for WarSampo took 0.2717604637145996s
Security | Sign check for WarSampo took 0.18030738830566406s
Availability | Check URIs Dereferenciability for WarSampo took 3.109654188156128s
Completeness | Calculation of interlinking completeness for WarSampo took 1.4472472667694092s
Reputation | Calculation of the PageRank for WarSampo took 0.02092766761779785s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.797645568847656e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.6689300537109375e-06s
Believability | Calculation of trust value for WarSampo took 1.1444091796875e-05s
INFO | --- Analysis for warsampo took 978.3558378219604s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.47603416442871s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.2547264099121094s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.020474910736083984s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.557868957519531e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for wasabi took 56.31390929222107s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.49964261054992676s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0005056858062744141s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 134.06863260269165s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.9764440059661865s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 300.2354311943054s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 14.231492519378662s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.2144739627838s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 2.17916202545166s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.3487257957458496s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 7.776960849761963s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.3682570457458496s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.7494184970855713s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.2508316040039s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.19798707962036133s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 2.703347682952881s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 1.0537409782409668s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.49374818801879883s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.22481656074523926s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.2322371006011963s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.500823020935059s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 7.939338684082031e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.22432589530944824s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.20022797584533691s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.5145494937896729s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.4010896682739258s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 6.927026271820068s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.46486639976501465s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.2701089382171631s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 155.307541847229s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.19934320449829102s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 45.01423645019531s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.649146795272827s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.594312906265259s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.21275615692138672s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 85.62205576896667s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.265510320663452s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 36.41428995132446s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.3882830142974854s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 86.20049142837524s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.7150654792785645s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.569486141204834s
Security | Sign check for FAO water areas classification as linked data @PSNC took 1.2275562286376953s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 14.058297634124756s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.357804536819458s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.026242494583129883s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 3.933906555175781e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.3828277587890625e-05s
INFO | --- Analysis for Water_Areas_Classification took 3173.351087808609s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.18156647682189941s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00024962425231933594s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 128.14859795570374s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 0.9799275398254395s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 9.267042636871338s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 14.56212306022644s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.2323637008667s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 1.8718364238739014s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.22642064094543457s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 14.419479131698608s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.2311115264892578s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.32265663146972656s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.237872838974s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.3333108425140381s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 2.851330280303955s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 1.115997552871704s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.5690069198608398s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.20795989036560059s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.24751734733581543s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 10.996166706085205s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 0.0001087188720703125s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.20001602172851562s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.2010951042175293s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.42772650718688965s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4213430881500244s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 5.481683015823364s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.5037257671356201s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.25039148330688477s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 164.54399991035461s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.2015979290008545s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.19304728507995605s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.5148706436157227s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 40.15509271621704s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.640439748764038s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.6123392581939697s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.18010735511779785s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 87.41784381866455s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.30105185508728s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 43.7468421459198s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.3653888702392578s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 87.60644459724426s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.73679780960083s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.5924947261810303s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 1.0614726543426514s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 14.034278869628906s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.3443317413330078s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.021611928939819336s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for Water_Buffer took 2326.8779962062836s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.18363022804260254s
Availability | VoID file availability check for WebIsALOD took 0.0005896091461181641s
Extra | Recovery of all triples for WebIsALOD took 1.3067348003387451s
Performance | Total latancy measurement for WebIsALOD took 0.4206376075744629s
Amount of data | Number of triples check for WebIsALOD took 31.28899383544922s
Interoperability | New terms check for WebIsALOD took 42.62762403488159s
Versatility | Languages check for WebIsALOD took 62.03383159637451s
Interpretability | Number of blank nodes check for WebIsALOD took 0.07852387428283691s
Interpretability | RDF structures check for WebIsALOD took 0.11568140983581543s
Versatility | Serialization formats check for WebIsALOD took 0.10985279083251953s
Availability | RDF dump link check for WebIsALOD took 1.4177031517028809s
License | MR license check for WebIsALOD took 1.6177680492401123s
License | HR license check for WebIsALOD took 20.409070253372192s
Amount of data | Number of property check for WebIsALOD took 0.09667134284973145s
Understandability | Number of label check for WebIsALOD took 0.4655265808105469s
Understandability | URI regex check for WebIsALOD took 0.1718587875366211s
Understandability | Vocabs check for WebIsALOD took 0.08676576614379883s
Verifiability | Authors check for WebIsALOD took 0.10996699333190918s
Verifiability | Publishers check for WebIsALOD took 0.09192848205566406s
Performance | Throughput check for WebIsALOD took 10.46250319480896s
Amount of data | Check the number of entities for WebIsALOD took 7.319450378417969e-05s
Verifiability | Contribs. check for WebIsALOD took 0.09791088104248047s
Interlinking | sameAs chians check for WebIsALOD took 0.1240086555480957s
Interlinking | skos check for WebIsALOD took 0.12514758110046387s
Interlinking | skos check for WebIsALOD took 0.08257031440734863s
Timeliness | dataset update frequency check for WebIsALOD took 0.09341955184936523s
Currency | Creation date check for WebIsALOD took 0.1627821922302246s
Currency | Modification date check for WebIsALOD took 0.18294835090637207s
Rep.Conc. | URIs length for WebIsALOD took 79.48109269142151s
Interoperability | New vocabularies check for WebIsALOD took 3.294543981552124s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.07872819900512695s
Accuracy | Check Functional Property for WebIsALOD took 0.12722182273864746s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.12049031257629395s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.4656376838684082s
Accuracy | Check White space in annotation for WebIsALOD took 0.0295712947845459s
Accuracy | Check Datatype consistency for WebIsALOD took 0.02873969078063965s
Consistency | Disjoint class check for WebIsALOD took 0.13698816299438477s
Consistency | Check Misplaced properties for WebIsALOD took 61.344361305236816s
Consistency | Misplaced classes for WebIsALOD took 0.22162365913391113s
Consistency | Check Ontology hijacking for WebIsALOD took 1.8435733318328857s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.4485774040222168s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 63.455891847610474s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.031414031982421875s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.1216881275177002s
Security | Sign check for WebIsALOD took 0.09601974487304688s
Availability | Check URIs Dereferenciability for WebIsALOD took 15.759058475494385s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.7216784954071045s
Reputation | Calculation of the PageRank for WebIsALOD took 0.02097296714782715s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 7.390975952148438e-05s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 2.3877882957458496s
Believability | Calculation of trust value for WebIsALOD took 1.33514404296875e-05s
INFO | --- Analysis for webisalod took 585.3194370269775s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.315376281738281e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.27098846435546875s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.552436828613281e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.5020370483398438e-05s
INFO | --- Analysis for webnmasunotraveler took 6.460448503494263s
Availability | SPARQL endpoint availability check for Whisky Circle took 4.172325134277344e-05s
Availability | VoID file availability check for Whisky Circle took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.2624390125274658s
Reputation | Calculation of the PageRank for Whisky Circle took 0.021074533462524414s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010848045349121094s
Believability | Calculation of trust value for Whisky Circle took 1.2159347534179688e-05s
INFO | --- Analysis for whisky-circle-info took 5.430574893951416s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 20.835143089294434s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.00086212158203125s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.2883429527282715s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.743171691894531e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.239776611328125e-05s
INFO | --- Analysis for WHOnto took 41.23551964759827s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.29121971130371094s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.023199796676635742s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for whonto took 11.553793668746948s
Availability | SPARQL endpoint availability check for Wikidata took 0.5035316944122314s
Availability | VoID file availability check for Wikidata took 0.0006084442138671875s
Extra | Recovery of all triples for Wikidata took 24.43346381187439s
Performance | Total latancy measurement for Wikidata took 1.480623722076416s
Amount of data | Number of triples check for Wikidata took 65.21316862106323s
Interoperability | New terms check for Wikidata took 1.9503200054168701s
Versatility | Languages check for Wikidata took 60.24940299987793s
Interpretability | Number of blank nodes check for Wikidata took 65.20113372802734s
Interpretability | RDF structures check for Wikidata took 0.35416102409362793s
Versatility | Serialization formats check for Wikidata took 0.38082265853881836s
Availability | RDF dump link check for Wikidata took 0.21277308464050293s
License | MR license check for Wikidata took 0.2665212154388428s
License | HR license check for Wikidata took 65.21497797966003s
Amount of data | Number of property check for Wikidata took 0.3369605541229248s
Understandability | Number of label check for Wikidata took 65.37496852874756s
Understandability | URI regex check for Wikidata took 0.44145774841308594s
Understandability | Vocabs check for Wikidata took 0.2059650421142578s
Verifiability | Authors check for Wikidata took 0.4083380699157715s
Verifiability | Publishers check for Wikidata took 0.21631526947021484s
Performance | Throughput check for Wikidata took 11.267866611480713s
Amount of data | Check the number of entities for Wikidata took 0.00019121170043945312s
Verifiability | Contribs. check for Wikidata took 0.20482444763183594s
Interlinking | sameAs chians check for Wikidata took 15.077561378479004s
Interlinking | skos check for Wikidata took 0.21895194053649902s
Interlinking | skos check for Wikidata took 0.22898507118225098s
Timeliness | dataset update frequency check for Wikidata took 0.5229356288909912s
Currency | Creation date check for Wikidata took 0.45505356788635254s
Currency | Modification date check for Wikidata took 0.4589362144470215s
Rep.Conc. | URIs length for Wikidata took 36.63576912879944s
Interoperability | New vocabularies check for Wikidata took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.32652974128723145s
Accuracy | Check Empty annotation labels for Wikidata took 12.639700412750244s
Accuracy | Check White space in annotation for Wikidata took 2.647707223892212s
Accuracy | Check Datatype consistency for Wikidata took 4.627649784088135s
Consistency | Disjoint class check for Wikidata took 0.22692561149597168s
Consistency | Check Misplaced properties for Wikidata took 15.737695217132568s
Consistency | Misplaced classes for Wikidata took 8.938631057739258s
Consistency | Check Ontology hijacking for Wikidata took 24.038410902023315s
Consistency | Check Invalid usage of undefined classes for Wikidata took 1.410982608795166s
Consistency | Check Invalid usage of undefined properties for Wikidata took 5.542733192443848s
Conciseness | Check Extensional conciseness for Wikidata took 2.7778477668762207s
Conciseness | Check Intensional conciseness for Wikidata took 1.6976690292358398s
Security | Sign check for Wikidata took 0.3913874626159668s
Availability | Check URIs Dereferenciability for Wikidata took 9.690938711166382s
Completeness | Calculation of interlinking completeness for Wikidata took 0.3894336223602295s
Reputation | Calculation of the PageRank for Wikidata took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0002830028533935547s
Interoperability | Check the re-using of existing vocabs for Wikidata took 1.6689300537109375e-06s
Believability | Calculation of trust value for Wikidata took 5.245208740234375e-06s
INFO | --- Analysis for wikidata took 938.4885156154633s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 5.1975250244140625e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.2502932548522949s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.022294282913208008s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 6.890296936035156e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.2636184692382812e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 2.388573169708252s
Availability | SPARQL endpoint availability check for WikiPathways took 3.9577484130859375e-05s
Availability | VoID file availability check for WikiPathways took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2843754291534424s
Reputation | Calculation of the PageRank for WikiPathways took 0.021813631057739258s
Interlinking | Calculation of Degree of Connection for WikiPathways took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WikiPathways took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.765655517578125e-05s
Believability | Calculation of trust value for WikiPathways took 1.2159347534179688e-05s
INFO | --- Analysis for wikipathways took 2.887906312942505s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 4.00543212890625e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.6870803833007812s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.021542787551879883s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 2.7894973754882812e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 1.2159347534179688e-05s
INFO | --- Analysis for wikiword_thesaurus took 3.354947566986084s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2875192165374756s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.00032448768615722656s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.2617480754852295s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.021978378295898438s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.130073547363281e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.0013580322265625e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.396134853363037s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.2535841464996338s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.020628690719604492s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 8.106231689453125e-06s
INFO | --- Analysis for wings-workflow-provenance-dataset took 2.8132927417755127s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.7774138450622559s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.26642870903015137s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.0994415283203125e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.3828277587890625e-05s
INFO | --- Analysis for wl-kg took 4.4415459632873535s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 4.5299530029296875e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0013501644134521484s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.2746083736419678s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 6.532669067382812e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.2159347534179688e-05s
INFO | --- Analysis for wn-wiki-instances took 3.0736637115478516s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.14278435707092285s
Availability | VoID file availability check for World Loanword Database took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.2544221878051758s
Reputation | Calculation of the PageRank for World Loanword Database took 0.021781206130981445s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 6.794929504394531e-05s
Believability | Calculation of trust value for World Loanword Database took 7.152557373046875e-06s
INFO | --- Analysis for wold took 2.6436550617218018s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 4.315376281738281e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.26377010345458984s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.021456480026245117s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 2.8133392333984375e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.239776611328125e-05s
INFO | --- Analysis for woodtrick took 2.891223907470703s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.6091923713684082s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.26280832290649414s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 3.314018249511719e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for WordFormationLatin took 4.321855783462524s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 4.1484832763671875e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.2680044174194336s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.021111011505126953s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.000102996826171875s
Believability | Calculation of trust value for WordLift Blog EN took 1.2159347534179688e-05s
INFO | --- Analysis for wordlift-io-blog-en took 2.845665454864502s
Availability | SPARQL endpoint availability check for WordLift IT took 4.220008850097656e-05s
Availability | VoID file availability check for WordLift IT took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.2590982913970947s
Reputation | Calculation of the PageRank for WordLift IT took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for WordLift IT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WordLift IT took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.0001010894775390625s
Believability | Calculation of trust value for WordLift IT took 1.3113021850585938e-05s
INFO | --- Analysis for wordlift-io-blog-it took 2.856365919113159s
Availability | SPARQL endpoint availability check for Wordnet took 4.00543212890625e-05s
Availability | VoID file availability check for Wordnet took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Wordnet took 0.2843971252441406s
Reputation | Calculation of the PageRank for Wordnet took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wordnet took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Wordnet took 4.553794860839844e-05s
Believability | Calculation of trust value for Wordnet took 8.821487426757812e-06s
INFO | --- Analysis for wordnet took 2.8366637229919434s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.291534423828125e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.27596449851989746s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.226799011230469e-05s
Believability | Calculation of trust value for WordNet-RDF took 7.62939453125e-06s
INFO | --- Analysis for wordnet-rdf took 2.3137948513031006s
Availability | SPARQL endpoint availability check for wordpress took 4.935264587402344e-05s
Availability | VoID file availability check for wordpress took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for wordpress took 0.2691984176635742s
Reputation | Calculation of the PageRank for wordpress took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for wordpress took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for wordpress took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.463859558105469e-05s
Believability | Calculation of trust value for wordpress took 1.239776611328125e-05s
INFO | --- Analysis for wordpress took 2.8982961177825928s
Availability | SPARQL endpoint availability check for wordpress.post took 4.1961669921875e-05s
Availability | VoID file availability check for wordpress.post took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.2516012191772461s
Reputation | Calculation of the PageRank for wordpress.post took 0.022561311721801758s
Interlinking | Calculation of Degree of Connection for wordpress.post took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for wordpress.post took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 2.9325485229492188e-05s
Believability | Calculation of trust value for wordpress.post took 1.239776611328125e-05s
INFO | --- Analysis for wordpress_post took 2.7726552486419678s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.11230349540710449s
Availability | VoID file availability check for World Bank Linked Data took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.2376415729522705s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.022056102752685547s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012683868408203125s
Believability | Calculation of trust value for World Bank Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for world-bank-linked-data took 2.5535178184509277s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.9264845848083496s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.001178741455078125s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.2671651840209961s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.296966552734375e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.3113021850585938e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 5.097109079360962s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 8.320808410644531e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.26001667976379395s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.021272659301757812s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0011262893676757812s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 0.0001068115234375s
Believability | Calculation of trust value for World Wide Web Foundation took 9.059906005859375e-06s
INFO | --- Analysis for world-wide-web-foundation took 5.558557033538818s
Availability | SPARQL endpoint availability check for WikiPathways took 4.1484832763671875e-05s
Availability | VoID file availability check for WikiPathways took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2498321533203125s
Reputation | Calculation of the PageRank for WikiPathways took 0.021034955978393555s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.0994415283203125e-05s
Believability | Calculation of trust value for WikiPathways took 1.2159347534179688e-05s
INFO | --- Analysis for wp took 2.8597586154937744s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 8.7738037109375e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.2538583278656006s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.021921873092651367s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 3.0994415283203125e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 1.2159347534179688e-05s
INFO | --- Analysis for wunderground_weatherreport took 2.8901150226593018s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.21254277229309082s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005016326904296875s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 4.978683948516846s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.9439976215362549s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.24263381958007812s
Interoperability | New terms check for World War 1 as Linked Open Data took 2.0657355785369873s
Versatility | Languages check for World War 1 as Linked Open Data took 0.60561203956604s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.23935675621032715s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.5286726951599121s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.3661932945251465s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.24443721771240234s
Availability | RDF dump link check for World War 1 as Linked Open Data took 8.914876699447632s
License | MR license check for World War 1 as Linked Open Data took 0.21932077407836914s
License | HR license check for World War 1 as Linked Open Data took 1.6391489505767822s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.2083907127380371s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.3760852813720703s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.44699597358703613s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.296689510345459s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.2365713119506836s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.19781899452209473s
Performance | Throughput check for World War 1 as Linked Open Data took 10.910346269607544s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.06842875480651855s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.22428059577941895s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.24695563316345215s
Interlinking | skos check for World War 1 as Linked Open Data took 0.19324588775634766s
Interlinking | skos check for World War 1 as Linked Open Data took 0.19470810890197754s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.23444318771362305s
Currency | Creation date check for World War 1 as Linked Open Data took 0.40309810638427734s
Currency | Modification date check for World War 1 as Linked Open Data took 0.18436932563781738s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 4.15967583656311s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 6.122029781341553s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.2442636489868164s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.21554064750671387s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.22176551818847656s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 2.1322386264801025s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.04992961883544922s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.3122267723083496s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.20751309394836426s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.7074120044708252s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.5475053787231445s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.275634765625s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.55491304397583s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.18522310256958008s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.7920312881469727s
Security | Sign check for World War 1 as Linked Open Data took 0.2122185230255127s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1650.8131685256958s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 1.1539766788482666s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 6.628036499023438e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 0.00010061264038085938s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 14.651484727859497s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.3113021850585938e-05s
INFO | --- Analysis for ww1lod took 1757.7205216884613s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 4.696846008300781e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.25168418884277344s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.021353483200073242s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 3.170967102050781e-05s
Believability | Calculation of trust value for XlendiAmphorae took 1.3113021850585938e-05s
INFO | --- Analysis for xlendiamphorae took 2.8791580200195312s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.2826395034790039s
Availability | VoID file availability check for xLiD-Lexica took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.2911953926086426s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020661354064941406s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 6.937980651855469e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.3828277587890625e-05s
INFO | --- Analysis for xlid-lexica took 5.10558819770813s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.2438507080078125e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.26346778869628906s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.020653724670410156s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.695487976074219e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.2874603271484375e-05s
INFO | --- Analysis for xwn took 3.4480488300323486s
Availability | SPARQL endpoint availability check for xxx took 8.606910705566406e-05s
Availability | VoID file availability check for xxx took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for xxx took 0.27681946754455566s
Reputation | Calculation of the PageRank for xxx took 0.020653724670410156s
Interlinking | Calculation of Degree of Connection for xxx took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for xxx took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for xxx took 5.841255187988281e-05s
Believability | Calculation of trust value for xxx took 1.2159347534179688e-05s
INFO | --- Analysis for xx took 2.7671854496002197s
Availability | SPARQL endpoint availability check for YAGO took 8.463859558105469e-05s
Availability | VoID file availability check for YAGO took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for YAGO took 0.28740811347961426s
Reputation | Calculation of the PageRank for YAGO took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for YAGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00013327598571777344s
Believability | Calculation of trust value for YAGO took 1.4543533325195312e-05s
INFO | --- Analysis for yago took 4.446592330932617s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 1.0656237602233887s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.28104257583618164s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.023079872131347656s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 8.273124694824219e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.2159347534179688e-05s
INFO | --- Analysis for yahoo_geoplanet took 9.312382698059082s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.1406238079071045s
Availability | VoID file availability check for Yale Senselab took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.24170374870300293s
Reputation | Calculation of the PageRank for Yale Senselab took 0.02092599868774414s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 2.6702880859375e-05s
Believability | Calculation of trust value for Yale Senselab took 1.1205673217773438e-05s
INFO | --- Analysis for yale_senselab took 11.654752254486084s
Availability | SPARQL endpoint availability check for test-dapp-2 took 4.3392181396484375e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.2739899158477783s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.022241592407226562s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.0517578125e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.3113021850585938e-05s
INFO | --- Analysis for yordhis took 2.342895269393921s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.8709959983825684s
Availability | VoID file availability check for Yovisto - academic video search took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.25630736351013184s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.0207366943359375s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.604194641113281e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 1.0013580322265625e-05s
INFO | --- Analysis for yovisto took 25.938183546066284s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 8.654594421386719e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.0015375614166259766s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.2518324851989746s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.266334533691406e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 1.33514404296875e-05s
INFO | --- Analysis for ysa took 3.426563024520874s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 8.392333984375e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.2779862880706787s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 4.9114227294921875e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 1.239776611328125e-05s
INFO | --- Analysis for yso took 4.130227327346802s
Availability | SPARQL endpoint availability check for yso-fi-allars took 9.822845458984375e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.2887153625488281s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.021927356719970703s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.62396240234375e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.1444091796875e-05s
INFO | --- Analysis for yso-fi-allars took 3.106053113937378s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 8.487701416015625e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.25830817222595215s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.020999908447265625s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.170967102050781e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.2159347534179688e-05s
INFO | --- Analysis for yso-fi-ysa took 2.9320850372314453s
Availability | SPARQL endpoint availability check for YSO places took 0.63466477394104s
Availability | VoID file availability check for YSO places took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for YSO places took 0.24421453475952148s
Reputation | Calculation of the PageRank for YSO places took 0.021136999130249023s
Interlinking | Calculation of Degree of Connection for YSO places took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.075599670410156e-05s
Believability | Calculation of trust value for YSO places took 1.2159347534179688e-05s
INFO | --- Analysis for yso-paikat took 3.641099452972412s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.291534423828125e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0011782646179199219s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.2542097568511963s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.337860107421875e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 1.1444091796875e-05s
INFO | --- Analysis for zaragoza-datosabiertos took 6.4635443687438965s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 5.6743621826171875e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.2657468318939209s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.020716428756713867s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.337860107421875e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.1444091796875e-05s
INFO | --- Analysis for zaragoza_turruta took 2.642934560775757s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.1961669921875e-05s
Availability | VoID file availability check for ZBW Labs took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.23878026008605957s
Reputation | Calculation of the PageRank for ZBW Labs took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 7.271766662597656e-05s
Believability | Calculation of trust value for ZBW Labs took 1.3589859008789062e-05s
INFO | --- Analysis for zbw-labs took 3.3278987407684326s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.19115161895751953s
Availability | VoID file availability check for 20th Century Press Archives took 0.0006136894226074219s
Extra | Recovery of all triples for 20th Century Press Archives took 21.959025859832764s
Performance | Total latancy measurement for 20th Century Press Archives took 0.8184859752655029s
Amount of data | Number of triples check for 20th Century Press Archives took 1.5357794761657715s
Interoperability | New terms check for 20th Century Press Archives took 2.0693979263305664s
Versatility | Languages check for 20th Century Press Archives took 4.559948921203613s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 1.3394949436187744s
Interpretability | RDF structures check for 20th Century Press Archives took 0.1784508228302002s
Versatility | Serialization formats check for 20th Century Press Archives took 0.1685488224029541s
Availability | RDF dump link check for 20th Century Press Archives took 0.1532280445098877s
License | MR license check for 20th Century Press Archives took 0.14535069465637207s
License | HR license check for 20th Century Press Archives took 7.436805963516235s
Amount of data | Number of property check for 20th Century Press Archives took 0.15509319305419922s
Understandability | Number of label check for 20th Century Press Archives took 0.7990343570709229s
Understandability | URI regex check for 20th Century Press Archives took 0.2932584285736084s
Understandability | Vocabs check for 20th Century Press Archives took 0.14574456214904785s
Verifiability | Authors check for 20th Century Press Archives took 0.18573689460754395s
Verifiability | Publishers check for 20th Century Press Archives took 0.14170455932617188s
Performance | Throughput check for 20th Century Press Archives took 10.604490995407104s
Amount of data | Check the number of entities for 20th Century Press Archives took 0.00011730194091796875s
Verifiability | Contribs. check for 20th Century Press Archives took 0.13098478317260742s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.1302194595336914s
Interlinking | skos check for 20th Century Press Archives took 0.2594473361968994s
Interlinking | skos check for 20th Century Press Archives took 0.18050527572631836s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.16280436515808105s
Currency | Creation date check for 20th Century Press Archives took 0.28916406631469727s
Currency | Modification date check for 20th Century Press Archives took 0.3247501850128174s
Rep.Conc. | URIs length for 20th Century Press Archives took 41.20633840560913s
Interoperability | New vocabularies check for 20th Century Press Archives took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.14474081993103027s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.16233134269714355s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.14789390563964844s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 6.717200994491577s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8821847438812256s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.025400876998901s
Consistency | Disjoint class check for 20th Century Press Archives took 1.3427510261535645s
Consistency | Check Misplaced properties for 20th Century Press Archives took 3.1264169216156006s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.7380504608154297s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 6.861969232559204s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 4.372963190078735s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7247626781463623s
Security | Sign check for 20th Century Press Archives took 0.18736982345581055s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1023.619166135788s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.8151519298553467s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.020926475524902344s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.0001652240753173828s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.1920928955078125e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.33514404296875e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1177.6276366710663s
Availability | SPARQL endpoint availability check for zhishi.lemon took 8.654594421386719e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.27568936347961426s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.4345855712890625e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.2159347534179688e-05s
INFO | --- Analysis for zhishi-lemon took 25.3643000125885s
Availability | SPARQL endpoint availability check for Zhishi.me took 2.750370502471924s
Availability | VoID file availability check for Zhishi.me took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.2785346508026123s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020534515380859375s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 6.937980651855469e-05s
Believability | Calculation of trust value for Zhishi.me took 1.2874603271484375e-05s
INFO | --- Analysis for zhishi-me took 8.977213621139526s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 0.00011658668518066406s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.27795958518981934s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 5.745887756347656e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.1920928955078125e-05s
INFO | --- Analysis for zitgist-musicbrainz took 3.420395851135254s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 9.846687316894531e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.24164366722106934s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 2.9325485229492188e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.2159347534179688e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.619708299636841s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.3659529685974121s
Availability | VoID file availability check for performing-arts.ch took 0.0005166530609130859s
Extra | Recovery of all triples for performing-arts.ch took 14.930670261383057s
Performance | Total latancy measurement for performing-arts.ch took 0.8015873432159424s
Amount of data | Number of triples check for performing-arts.ch took 43.33003902435303s
Interoperability | New terms check for performing-arts.ch took 1.5429878234863281s
Versatility | Languages check for performing-arts.ch took 60.13948893547058s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.12109112739563s
Interpretability | RDF structures check for performing-arts.ch took 0.1849818229675293s
Versatility | Serialization formats check for performing-arts.ch took 0.16182708740234375s
Availability | RDF dump link check for performing-arts.ch took 0.1411733627319336s
License | MR license check for performing-arts.ch took 0.1650245189666748s
License | HR license check for performing-arts.ch took 60.133219480514526s
Amount of data | Number of property check for performing-arts.ch took 14.162315845489502s
Understandability | Number of label check for performing-arts.ch took 10.186520099639893s
Understandability | URI regex check for performing-arts.ch took 0.3054807186126709s
Understandability | Vocabs check for performing-arts.ch took 0.14759135246276855s
Verifiability | Authors check for performing-arts.ch took 0.15165257453918457s
Verifiability | Publishers check for performing-arts.ch took 0.14560818672180176s
Performance | Throughput check for performing-arts.ch took 11.619244575500488s
Amount of data | Check the number of entities for performing-arts.ch took 7.867813110351562e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.1617274284362793s
Interlinking | sameAs chians check for performing-arts.ch took 0.5295228958129883s
Interlinking | skos check for performing-arts.ch took 0.174485445022583s
Interlinking | skos check for performing-arts.ch took 0.19093847274780273s
Timeliness | dataset update frequency check for performing-arts.ch took 0.16451811790466309s
Currency | Creation date check for performing-arts.ch took 0.32849550247192383s
Currency | Modification date check for performing-arts.ch took 0.32458019256591797s
Rep.Conc. | URIs length for performing-arts.ch took 20.403067111968994s
Interoperability | New vocabularies check for performing-arts.ch took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.15645766258239746s
Accuracy | Check Functional Property for performing-arts.ch took 0.15597915649414062s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.17079854011535645s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.787652254104614s
Accuracy | Check White space in annotation for performing-arts.ch took 2.513491153717041s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.759031057357788s
Consistency | Disjoint class check for performing-arts.ch took 0.3354837894439697s
Consistency | Check Misplaced properties for performing-arts.ch took 1.049809217453003s
Consistency | Misplaced classes for performing-arts.ch took 8.378419876098633s
Consistency | Check Ontology hijacking for performing-arts.ch took 41.430426359176636s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 16843.393179655075s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.9435796737670898s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.878350019454956s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.2792959213256836s
Security | Sign check for performing-arts.ch took 0.16033554077148438s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.3188281059265137s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 1.622877836227417s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.021162986755371094s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.5974044799804688e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 1.6689300537109375e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.33514404296875e-05s
INFO | --- Analysis for performing-arts.ch took 17625.8484852314s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.840507745742798s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.00037670135498046875s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.2484753131866455s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.02113962173461914s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.2874603271484375e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for The-AA-Thesaurus took 9.753491878509521s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.5506012439727783s
Availability | VoID file availability check for MiMoTextBase took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.6794109344482422s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.2159347534179688e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.2874603271484375e-05s
INFO | --- Analysis for MiMoTextBase took 8.28705096244812s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.49016499519348145s
Availability | VoID file availability check for National Library of Sweden took 0.0006239414215087891s
Extra | Recovery of all triples for National Library of Sweden took 5.9546544551849365s
Performance | Total latancy measurement for National Library of Sweden took 1.0486021041870117s
Amount of data | Number of triples check for National Library of Sweden took 20.006157875061035s
Interoperability | New terms check for National Library of Sweden took 15.776624917984009s
Versatility | Languages check for National Library of Sweden took 0.21266984939575195s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.1977889537811s
Interpretability | RDF structures check for National Library of Sweden took 0.366560697555542s
Versatility | Serialization formats check for National Library of Sweden took 0.24709796905517578s
Availability | RDF dump link check for National Library of Sweden took 0.22444891929626465s
License | MR license check for National Library of Sweden took 0.24393153190612793s
License | HR license check for National Library of Sweden took 0.32188940048217773s
Amount of data | Number of property check for National Library of Sweden took 0.22978568077087402s
Understandability | Number of label check for National Library of Sweden took 0.4536757469177246s
Understandability | URI regex check for National Library of Sweden took 0.5783390998840332s
Understandability | Vocabs check for National Library of Sweden took 0.24917888641357422s
Verifiability | Authors check for National Library of Sweden took 0.39342212677001953s
Verifiability | Publishers check for National Library of Sweden took 0.23244976997375488s
Performance | Throughput check for National Library of Sweden took 10.841166973114014s
Amount of data | Check the number of entities for National Library of Sweden took 7.128715515136719e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.2565150260925293s
Interlinking | sameAs chians check for National Library of Sweden took 0.2944338321685791s
Interlinking | skos check for National Library of Sweden took 0.3770945072174072s
Interlinking | skos check for National Library of Sweden took 0.21276354789733887s
Timeliness | dataset update frequency check for National Library of Sweden took 0.25071167945861816s
Currency | Creation date check for National Library of Sweden took 0.5260879993438721s
Currency | Modification date check for National Library of Sweden took 0.46414923667907715s
Rep.Conc. | URIs length for National Library of Sweden took 82.13169550895691s
Interoperability | New vocabularies check for National Library of Sweden took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.21208882331848145s
Accuracy | Check Functional Property for National Library of Sweden took 0.2651078701019287s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.2340409755706787s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2690284252166748s
Consistency | Disjoint class check for National Library of Sweden took 0.26966214179992676s
Consistency | Check Misplaced properties for National Library of Sweden took 61.95885133743286s
Consistency | Misplaced classes for National Library of Sweden took 1.1290960311889648s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.5380136966705322s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.387542486190796s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 62.815539598464966s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.27950096130371094s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.3436293601989746s
Security | Sign check for National Library of Sweden took 0.4088742733001709s
Availability | Check URIs Dereferenciability for National Library of Sweden took 15.743117094039917s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.8049612045288086s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 8.153915405273438e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 2.1696090698242188e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.430511474609375e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.1682510375976562e-05s
INFO | --- Analysis for NLS took 1377.8524293899536s
Availability | SPARQL endpoint availability check for Japan Search took 1.3119258880615234s
Availability | VoID file availability check for Japan Search took 0.0002353191375732422s
Extra | Recovery of all triples for Japan Search took 3.26737642288208s
Performance | Total latancy measurement for Japan Search took 2.5055153369903564s
Amount of data | Number of triples check for Japan Search took 5.328645706176758s
Interoperability | New terms check for Japan Search took 4.1909003257751465s
Versatility | Languages check for Japan Search took 0.7340357303619385s
Interpretability | Number of blank nodes check for Japan Search took 12.295656442642212s
Interpretability | RDF structures check for Japan Search took 0.4274570941925049s
Versatility | Serialization formats check for Japan Search took 0.3747410774230957s
Availability | RDF dump link check for Japan Search took 0.3497192859649658s
License | MR license check for Japan Search took 0.9352719783782959s
License | HR license check for Japan Search took 10.295403242111206s
Amount of data | Number of property check for Japan Search took 0.7368409633636475s
Understandability | Number of label check for Japan Search took 2.958035945892334s
Understandability | URI regex check for Japan Search took 0.549161434173584s
Understandability | Vocabs check for Japan Search took 0.26428771018981934s
Verifiability | Authors check for Japan Search took 0.33635497093200684s
Verifiability | Publishers check for Japan Search took 0.3047494888305664s
Performance | Throughput check for Japan Search took 11.207811832427979s
Amount of data | Check the number of entities for Japan Search took 7.271766662597656e-05s
Verifiability | Contribs. check for Japan Search took 0.2621762752532959s
Interlinking | sameAs chians check for Japan Search took 0.2868189811706543s
Interlinking | skos check for Japan Search took 0.2826197147369385s
Interlinking | skos check for Japan Search took 0.2642056941986084s
Timeliness | dataset update frequency check for Japan Search took 0.3377809524536133s
Currency | Creation date check for Japan Search took 0.5756914615631104s
Currency | Modification date check for Japan Search took 0.5961935520172119s
Rep.Conc. | URIs length for Japan Search took 13.717610120773315s
Interoperability | New vocabularies check for Japan Search took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.7344880104064941s
Accuracy | Check Empty annotation labels for Japan Search took 1.741957426071167s
Accuracy | Check White space in annotation for Japan Search took 0.02975606918334961s
Accuracy | Check Datatype consistency for Japan Search took 0.028261899948120117s
Consistency | Disjoint class check for Japan Search took 0.25930023193359375s
Consistency | Check Misplaced properties for Japan Search took 10.57835841178894s
Consistency | Misplaced classes for Japan Search took 0.3554856777191162s
Consistency | Check Ontology hijacking for Japan Search took 3.548211097717285s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3674674034118652s
Consistency | Check Invalid usage of undefined properties for Japan Search took 12.364398002624512s
Conciseness | Check Extensional conciseness for Japan Search took 0.03549361228942871s
Conciseness | Check Intensional conciseness for Japan Search took 0.9532196521759033s
Security | Sign check for Japan Search took 0.2893340587615967s
Availability | Check URIs Dereferenciability for Japan Search took 15.285614967346191s
Completeness | Calculation of interlinking completeness for Japan Search took 0.39946794509887695s
Reputation | Calculation of the PageRank for Japan Search took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.0728836059570312e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.1920928955078125e-06s
Believability | Calculation of trust value for Japan Search took 7.867813110351562e-06s
INFO | --- Analysis for Japan-Search took 400.0700886249542s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.1284830570220947s
Availability | VoID file availability check for Rijksmuseum Collection took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.2534661293029785s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.022131681442260742s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.0728836059570312e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.2159347534179688e-05s
INFO | --- Analysis for Rijksmuseum took 6.397123575210571s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.9255754947662354s
Availability | VoID file availability check for Finnish Public Libraries took 0.0005881786346435547s
Extra | Recovery of all triples for Finnish Public Libraries took 14.01694917678833s
Performance | Total latancy measurement for Finnish Public Libraries took 1.4611408710479736s
Amount of data | Number of triples check for Finnish Public Libraries took 49.422953844070435s
Interoperability | New terms check for Finnish Public Libraries took 13.813062191009521s
Versatility | Languages check for Finnish Public Libraries took 60.318251609802246s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 51.07945156097412s
Interpretability | RDF structures check for Finnish Public Libraries took 0.2721102237701416s
Versatility | Serialization formats check for Finnish Public Libraries took 0.2525367736816406s
Availability | RDF dump link check for Finnish Public Libraries took 0.46736669540405273s
License | MR license check for Finnish Public Libraries took 0.2512190341949463s
License | HR license check for Finnish Public Libraries took 33.8688588142395s
Amount of data | Number of property check for Finnish Public Libraries took 0.13144159317016602s
Understandability | Number of label check for Finnish Public Libraries took 11.27076506614685s
Understandability | URI regex check for Finnish Public Libraries took 0.5634486675262451s
Understandability | Vocabs check for Finnish Public Libraries took 0.2176799774169922s
Verifiability | Authors check for Finnish Public Libraries took 0.24901747703552246s
Verifiability | Publishers check for Finnish Public Libraries took 0.2630879878997803s
Performance | Throughput check for Finnish Public Libraries took 11.591856718063354s
Amount of data | Check the number of entities for Finnish Public Libraries took 7.367134094238281e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.24257731437683105s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.31286168098449707s
Interlinking | skos check for Finnish Public Libraries took 0.24239587783813477s
Interlinking | skos check for Finnish Public Libraries took 0.23793363571166992s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.23632502555847168s
Currency | Creation date check for Finnish Public Libraries took 0.4520714282989502s
Currency | Modification date check for Finnish Public Libraries took 0.25764966011047363s
Rep.Conc. | URIs length for Finnish Public Libraries took 72.8621437549591s
Interoperability | New vocabularies check for Finnish Public Libraries took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.7859480381011963s
Accuracy | Check Functional Property for Finnish Public Libraries took 0.22385025024414062s
Accuracy | Check Inverse Functional Property for Finnish Public Libraries took 0.1305992603302002s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 7.606671571731567s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.1705334186553955s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.274233818054199s
Consistency | Disjoint class check for Finnish Public Libraries took 0.2653675079345703s
Consistency | Check Misplaced properties for Finnish Public Libraries took 53.14227795600891s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 13.271873235702515s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.6041855812072754s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 56.69804048538208s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.7249650955200195s
Security | Sign check for Finnish Public Libraries took 0.4259164333343506s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.5114362239837646s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.3892979621887207s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.021336793899536133s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 1.9073486328125e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 1.3113021850585938e-05s
INFO | --- Analysis for FI-Library took 654.857568025589s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 3.848329544067383s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.27762699127197266s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.020833253860473633s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.2874603271484375e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.1920928955078125e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 10.074596881866455s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.3448936939239502s
Availability | VoID file availability check for National Library Netherlands took 0.0006034374237060547s
Extra | Recovery of all triples for National Library Netherlands took 0.6506268978118896s
Performance | Total latancy measurement for National Library Netherlands took 0.7596747875213623s
Amount of data | Number of triples check for National Library Netherlands took 0.14814019203186035s
Interoperability | New terms check for National Library Netherlands took 1.4509897232055664s
Versatility | Languages check for National Library Netherlands took 58.14557099342346s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.15269064903259277s
Interpretability | RDF structures check for National Library Netherlands took 0.164902925491333s
Versatility | Serialization formats check for National Library Netherlands took 0.14177799224853516s
Availability | RDF dump link check for National Library Netherlands took 0.14627766609191895s
License | MR license check for National Library Netherlands took 0.1573469638824463s
License | HR license check for National Library Netherlands took 0.20582962036132812s
Amount of data | Number of property check for National Library Netherlands took 0.16504168510437012s
Understandability | Number of label check for National Library Netherlands took 0.16741013526916504s
Understandability | URI regex check for National Library Netherlands took 0.3198075294494629s
Understandability | Vocabs check for National Library Netherlands took 0.15255236625671387s
Verifiability | Authors check for National Library Netherlands took 0.14217519760131836s
Verifiability | Publishers check for National Library Netherlands took 0.15618324279785156s
Performance | Throughput check for National Library Netherlands took 10.61563754081726s
Amount of data | Check the number of entities for National Library Netherlands took 7.677078247070312e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.15891146659851074s
Interlinking | sameAs chians check for National Library Netherlands took 0.14917516708374023s
Interlinking | skos check for National Library Netherlands took 0.1655588150024414s
Interlinking | skos check for National Library Netherlands took 0.1624736785888672s
Timeliness | dataset update frequency check for National Library Netherlands took 0.15253496170043945s
Currency | Creation date check for National Library Netherlands took 0.32018256187438965s
Currency | Modification date check for National Library Netherlands took 0.32598304748535156s
Rep.Conc. | URIs length for National Library Netherlands took 0.6839907169342041s
Interoperability | New vocabularies check for National Library Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.15574121475219727s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.3912160396575928s
Accuracy | Check White space in annotation for National Library Netherlands took 0.02704024314880371s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.02803325653076172s
Consistency | Disjoint class check for National Library Netherlands took 0.15866446495056152s
Consistency | Check Misplaced properties for National Library Netherlands took 0.31522631645202637s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.7818381786346436s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.3401498794555664s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.4781250953674316s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.032598018646240234s
Security | Sign check for National Library Netherlands took 0.14394474029541016s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1672.1826558113098s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 1.6786813735961914s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.021096467971801758s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.002716064453125e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.0728836059570312e-05s
INFO | --- Analysis for National-Library-Netherlands took 1782.5058600902557s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.435471773147583s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.6803405284881592s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.3589859008789062e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.2636184692382812e-05s
INFO | --- Analysis for Antique-Renaissance took 6.750100612640381s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 6.219461441040039s
Availability | VoID file availability check for ARTSDATA.CA took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.6720092296600342s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 3.0994415283203125e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.001718282699584961s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.9550323486328125e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.2159347534179688e-05s
INFO | --- Analysis for ARTSDATA-CA took 12.279810667037964s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.1647188663482666s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.25653553009033203s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.0212099552154541s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.0251998901367188e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 1.239776611328125e-05s
INFO | --- Analysis for ArCo took 3.320361614227295s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.2360992431640625s
Availability | VoID file availability check for ConfermentSampo took 0.0005080699920654297s
Extra | Recovery of all triples for ConfermentSampo took 26.834871768951416s
Performance | Total latancy measurement for ConfermentSampo took 0.9125237464904785s
Amount of data | Number of triples check for ConfermentSampo took 18.022311449050903s
Interoperability | New terms check for ConfermentSampo took 3.169670820236206s
Versatility | Languages check for ConfermentSampo took 0.1850721836090088s
Interpretability | Number of blank nodes check for ConfermentSampo took 22.027467966079712s
Security | Check HTTPS for ConfermentSampo took 0.4447965621948242s
Interpretability | RDF structures check for ConfermentSampo took 0.18863487243652344s
Versatility | Serialization formats check for ConfermentSampo took 0.19578051567077637s
Availability | RDF dump link check for ConfermentSampo took 3.332456588745117s
License | MR license check for ConfermentSampo took 0.17837214469909668s
License | HR license check for ConfermentSampo took 0.3554494380950928s
Amount of data | Number of property check for ConfermentSampo took 0.17889189720153809s
Understandability | Number of label check for ConfermentSampo took 16.878389835357666s
Understandability | URI regex check for ConfermentSampo took 0.36026692390441895s
Understandability | Vocabs check for ConfermentSampo took 0.20379185676574707s
Verifiability | Authors check for ConfermentSampo took 0.2052004337310791s
Verifiability | Publishers check for ConfermentSampo took 0.20936179161071777s
Performance | Throughput check for ConfermentSampo took 10.561287879943848s
Amount of data | Check the number of entities for ConfermentSampo took 4.028557538986206s
Verifiability | Contribs. check for ConfermentSampo took 0.17699337005615234s
Interlinking | sameAs chians check for ConfermentSampo took 0.9364278316497803s
Interlinking | skos check for ConfermentSampo took 0.19423627853393555s
Interlinking | skos check for ConfermentSampo took 0.1878645420074463s
Timeliness | dataset update frequency check for ConfermentSampo took 0.1920304298400879s
Currency | Creation date check for ConfermentSampo took 0.4001166820526123s
Currency | Modification date check for ConfermentSampo took 0.4075448513031006s
Rep.Conc. | URIs length for ConfermentSampo took 49.70421099662781s
Interoperability | New vocabularies check for ConfermentSampo took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.20035576820373535s
Accuracy | Check Functional Property for ConfermentSampo took 0.19805908203125s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.18189501762390137s
Accuracy | Check Empty annotation labels for ConfermentSampo took 22.485569715499878s
Accuracy | Check White space in annotation for ConfermentSampo took 3.0083467960357666s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.2096107006073s
Consistency | Disjoint class check for ConfermentSampo took 0.1675245761871338s
Consistency | Check Misplaced properties for ConfermentSampo took 9.711007595062256s
Consistency | Check Ontology hijacking for ConfermentSampo took 22.058411359786987s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.5273354053497314s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.6738817691802979s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.815856456756592s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.18163776397705078s
Security | Sign check for ConfermentSampo took 0.174544095993042s
Availability | Check URIs Dereferenciability for ConfermentSampo took 2.588336229324341s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.3696777820587158s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 2.86102294921875e-06s
Believability | Calculation of trust value for ConfermentSampo took 8.106231689453125e-06s
INFO | --- Analysis for ConfermentSampo took 434.8304238319397s
Availability | SPARQL endpoint availability check for Museum Finland took 0.3203904628753662s
Availability | VoID file availability check for Museum Finland took 0.0005140304565429688s
Extra | Recovery of all triples for Museum Finland took 16.424737215042114s
Performance | Total latancy measurement for Museum Finland took 0.8731088638305664s
Amount of data | Number of triples check for Museum Finland took 0.3425867557525635s
Interoperability | New terms check for Museum Finland took 1.7448303699493408s
Versatility | Languages check for Museum Finland took 0.6892585754394531s
Interpretability | Number of blank nodes check for Museum Finland took 0.3144557476043701s
Security | Check HTTPS for Museum Finland took 0.26316404342651367s
Interpretability | RDF structures check for Museum Finland took 0.3553786277770996s
Versatility | Serialization formats check for Museum Finland took 0.20218586921691895s
Availability | RDF dump link check for Museum Finland took 0.17564868927001953s
License | MR license check for Museum Finland took 0.3319096565246582s
License | HR license check for Museum Finland took 0.42028260231018066s
Amount of data | Number of property check for Museum Finland took 0.18030881881713867s
Understandability | Number of label check for Museum Finland took 0.2816464900970459s
Understandability | URI regex check for Museum Finland took 0.3708076477050781s
Understandability | Vocabs check for Museum Finland took 0.17897582054138184s
Verifiability | Authors check for Museum Finland took 0.19539904594421387s
Verifiability | Publishers check for Museum Finland took 0.17513298988342285s
Performance | Throughput check for Museum Finland took 10.453526020050049s
Amount of data | Check the number of entities for Museum Finland took 4.863739013671875e-05s
Verifiability | Contribs. check for Museum Finland took 0.1852424144744873s
Interlinking | sameAs chians check for Museum Finland took 0.1711111068725586s
Interlinking | skos check for Museum Finland took 0.19011211395263672s
Interlinking | skos check for Museum Finland took 0.17916083335876465s
Timeliness | dataset update frequency check for Museum Finland took 0.17413759231567383s
Currency | Creation date check for Museum Finland took 0.3617093563079834s
Currency | Modification date check for Museum Finland took 0.5694968700408936s
Rep.Conc. | URIs length for Museum Finland took 3.564779043197632s
Interoperability | New vocabularies check for Museum Finland took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.16304755210876465s
Accuracy | Check Functional Property for Museum Finland took 0.16345667839050293s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.17428016662597656s
Accuracy | Check Empty annotation labels for Museum Finland took 1.0563738346099854s
Accuracy | Check White space in annotation for Museum Finland took 0.06111788749694824s
Accuracy | Check Datatype consistency for Museum Finland took 0.9568462371826172s
Consistency | Disjoint class check for Museum Finland took 0.2146167755126953s
Consistency | Check Misplaced properties for Museum Finland took 0.7632400989532471s
Consistency | Check Ontology hijacking for Museum Finland took 2.4264395236968994s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.5391597747802734s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.7152481079101562s
Conciseness | Check Extensional conciseness for Museum Finland took 0.655134916305542s
Conciseness | Check Intensional conciseness for Museum Finland took 0.27010607719421387s
Security | Sign check for Museum Finland took 0.17588305473327637s
Availability | Check URIs Dereferenciability for Museum Finland took 2986.918437242508s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.8169705867767334s
Reputation | Calculation of the PageRank for Museum Finland took 0.021378040313720703s
Interlinking | Calculation of Degree of Connection for Museum Finland took 6.747245788574219e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.7404556274414062e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 1.9073486328125e-06s
Believability | Calculation of trust value for Museum Finland took 1.3113021850585938e-05s
INFO | --- Analysis for FI-Museum took 3053.942220926285s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.18236017227172852s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0006344318389892578s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 17.436365842819214s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.8353431224822998s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 34.24704670906067s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.80129075050354s
Versatility | Languages check for Mapping Manuscript Migrations took 76.1907730102539s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 28.874539852142334s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.4613642692565918s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.192979097366333s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.19310450553894043s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.18885207176208496s
License | MR license check for Mapping Manuscript Migrations took 0.16872668266296387s
License | HR license check for Mapping Manuscript Migrations took 1.7791528701782227s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.17293524742126465s
Understandability | Number of label check for Mapping Manuscript Migrations took 8.89443325996399s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.34207630157470703s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.17735910415649414s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.16947650909423828s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.16384363174438477s
Performance | Throughput check for Mapping Manuscript Migrations took 10.276027202606201s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0353198051452637s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.17420744895935059s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.512683629989624s
Interlinking | skos check for Mapping Manuscript Migrations took 0.17256402969360352s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16346144676208496s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.17522931098937988s
Currency | Creation date check for Mapping Manuscript Migrations took 0.3249845504760742s
Currency | Modification date check for Mapping Manuscript Migrations took 0.20671844482421875s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 48.16917061805725s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.1735095977783203s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.1735827922821045s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.18195104598999023s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 12.661595821380615s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.4599738121032715s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.727522373199463s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.20019006729125977s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 22.74288058280945s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.19870138168335s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.5592236518859863s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.6017091274261475s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.8288376331329346s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.17618703842163086s
Security | Sign check for Mapping Manuscript Migrations took 0.1648693084716797s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1564.8595526218414s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.9769103527069092s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.021013736724853516s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 2.3126602172851562e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 2.1457672119140625e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 8.630752563476562e-05s
INFO | --- Analysis for MMM took 1976.320696592331s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.21838927268981934s
Availability | VoID file availability check for Semantic Kalevala took 0.0002951622009277344s
Extra | Recovery of all triples for Semantic Kalevala took 10.933992147445679s
Performance | Total latancy measurement for Semantic Kalevala took 0.8589296340942383s
Amount of data | Number of triples check for Semantic Kalevala took 0.411144495010376s
Interoperability | New terms check for Semantic Kalevala took 2.2614705562591553s
Versatility | Languages check for Semantic Kalevala took 0.9690287113189697s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.4798297882080078s
Security | Check HTTPS for Semantic Kalevala took 0.4353470802307129s
Interpretability | RDF structures check for Semantic Kalevala took 0.24177026748657227s
Versatility | Serialization formats check for Semantic Kalevala took 0.17882585525512695s
Availability | RDF dump link check for Semantic Kalevala took 0.17261266708374023s
License | MR license check for Semantic Kalevala took 0.2102067470550537s
License | HR license check for Semantic Kalevala took 1.0247247219085693s
Amount of data | Number of property check for Semantic Kalevala took 0.1693437099456787s
Understandability | Number of label check for Semantic Kalevala took 0.580157995223999s
Understandability | URI regex check for Semantic Kalevala took 0.3398263454437256s
Understandability | Vocabs check for Semantic Kalevala took 0.189408540725708s
Verifiability | Authors check for Semantic Kalevala took 0.16457128524780273s
Verifiability | Publishers check for Semantic Kalevala took 0.18091368675231934s
Performance | Throughput check for Semantic Kalevala took 10.781196594238281s
Amount of data | Check the number of entities for Semantic Kalevala took 8.463859558105469e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.16992735862731934s
Interlinking | sameAs chians check for Semantic Kalevala took 0.17166924476623535s
Interlinking | skos check for Semantic Kalevala took 0.2742593288421631s
Interlinking | skos check for Semantic Kalevala took 0.16582727432250977s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.18816041946411133s
Currency | Creation date check for Semantic Kalevala took 0.3564760684967041s
Currency | Modification date check for Semantic Kalevala took 0.3368654251098633s
Rep.Conc. | URIs length for Semantic Kalevala took 4.811211109161377s
Interoperability | New vocabularies check for Semantic Kalevala took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.17114782333374023s
Accuracy | Check Functional Property for Semantic Kalevala took 0.16436433792114258s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.17818212509155273s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.8058288097381592s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.294766902923584s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.3788368701934814s
Consistency | Disjoint class check for Semantic Kalevala took 0.17583584785461426s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.8018336296081543s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.3968591690063477s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.4127662181854248s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.603456974029541s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8757379055023193s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.24297809600830078s
Security | Sign check for Semantic Kalevala took 0.1737375259399414s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2886.160090446472s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 1.5869810581207275s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.811981201171875e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.9073486328125e-06s
Believability | Calculation of trust value for Semantic Kalevala took 7.152557373046875e-06s
INFO | --- Analysis for Semantic-Kalevala took 2957.632949590683s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.937065839767456s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0005445480346679688s
Extra | Recovery of all triples for Smithsonian American Art Museum took 274.45305132865906s
Performance | Total latancy measurement for Smithsonian American Art Museum took 2.950941324234009s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5845530033111572s
Interoperability | New terms check for Smithsonian American Art Museum took 2.8975391387939453s
Versatility | Languages check for Smithsonian American Art Museum took 29.895660400390625s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5815649032592773s
Security | Check HTTPS for Smithsonian American Art Museum took 0.3817405700683594s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.6597499847412109s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6334397792816162s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.5978398323059082s
License | MR license check for Smithsonian American Art Museum took 0.5817101001739502s
License | HR license check for Smithsonian American Art Museum took 18.068598985671997s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.584850549697876s
Understandability | Number of label check for Smithsonian American Art Museum took 0.6392645835876465s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1850063800811768s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.5864129066467285s
Verifiability | Authors check for Smithsonian American Art Museum took 0.5708205699920654s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5748813152313232s
Performance | Throughput check for Smithsonian American Art Museum took 11.561548233032227s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 6.842613220214844e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.6007335186004639s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5921571254730225s
Interlinking | skos check for Smithsonian American Art Museum took 0.5731368064880371s
Interlinking | skos check for Smithsonian American Art Museum took 0.5741143226623535s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.6131055355072021s
Currency | Creation date check for Smithsonian American Art Museum took 1.199765682220459s
Currency | Modification date check for Smithsonian American Art Museum took 1.1986141204833984s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 104.35295701026917s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.580153226852417s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 23.375567197799683s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.49861764907836914s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.251697540283203s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5705568790435791s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 5.5936620235443115s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 100.69874906539917s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.6144440174102783s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 5.347259044647217s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.848858594894409s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6428737640380859s
Security | Sign check for Smithsonian American Art Museum took 0.5931069850921631s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.148245811462402s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.8853068351745605s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.02124190330505371s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 1.9073486328125e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 7.3909759521484375e-06s
INFO | --- Analysis for Smithsonian took 709.6146795749664s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.18169450759887695s
Availability | VoID file availability check for Zeri Photo Archive took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.2656679153442383s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.020226001739501953s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.2159347534179688e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.2636184692382812e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 7.268759727478027s
Availability | SPARQL endpoint availability check for Archives Hub took 21.506244897842407s
Availability | VoID file availability check for Archives Hub took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.26595520973205566s
Reputation | Calculation of the PageRank for Archives Hub took 0.020215511322021484s
Interlinking | Calculation of Degree of Connection for Archives Hub took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.4781951904296875e-05s
Believability | Calculation of trust value for Archives Hub took 1.2874603271484375e-05s
INFO | --- Analysis for Archives-Hub took 54.9629807472229s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.4209563732147217s
Availability | VoID file availability check for Yale centre of British Art took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.2395334243774414s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.0728836059570312e-05s
Believability | Calculation of trust value for Yale centre of British Art took 7.3909759521484375e-06s
INFO | --- Analysis for Yale took 4.669445037841797s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.5390028953552s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.6668789386749268s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.02136969566345215s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.7642974853515625e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.33514404296875e-05s
INFO | --- Analysis for ADL took 539.5352056026459s
Availability | SPARQL endpoint availability check for MusicKG took 0.7483739852905273s
Availability | VoID file availability check for MusicKG took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for MusicKG took 0.2640340328216553s
Reputation | Calculation of the PageRank for MusicKG took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.1920928955078125e-05s
Believability | Calculation of trust value for MusicKG took 1.239776611328125e-05s
INFO | --- Analysis for MusicKG took 5.701271295547485s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.8184006214141846s
Availability | VoID file availability check for CIDOC-CRM took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.26422810554504395s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.020904064178466797s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.2636184692382812e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.3828277587890625e-05s
INFO | --- Analysis for CIDOC-CRM took 4.460229158401489s
Availability | SPARQL endpoint availability check for Mondis took 0.3828883171081543s
Availability | VoID file availability check for Mondis took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Mondis took 0.31003856658935547s
Reputation | Calculation of the PageRank for Mondis took 0.021096467971801758s
Interlinking | Calculation of Degree of Connection for Mondis took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.239776611328125e-05s
Believability | Calculation of trust value for Mondis took 1.1920928955078125e-05s
INFO | --- Analysis for Mondis took 3.680434226989746s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.090102195739746s
Availability | VoID file availability check for DigitalNZ took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.2719895839691162s
Reputation | Calculation of the PageRank for DigitalNZ took 0.021336793899536133s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.049041748046875e-05s
Believability | Calculation of trust value for DigitalNZ took 1.2159347534179688e-05s
INFO | --- Analysis for DigitalNZ took 7.13587212562561s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.16802978515625s
Availability | VoID file availability check for Fondazione Zeri took 0.00030517578125s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.23764681816101074s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.026352643966674805s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0008313655853271484s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.239776611328125e-05s
Believability | Calculation of trust value for Fondazione Zeri took 7.3909759521484375e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.102796792984009s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.2406628131866455s
Availability | VoID file availability check for Digital Public Library of America took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.24820590019226074s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.021188020706176758s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.1920928955078125e-05s
Believability | Calculation of trust value for Digital Public Library of America took 7.3909759521484375e-06s
INFO | --- Analysis for Library-of-America took 3.6648495197296143s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.6496288776397705s
Availability | VoID file availability check for Auckland Museum took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.27777981758117676s
Reputation | Calculation of the PageRank for Auckland Museum took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.1682510375976562e-05s
Believability | Calculation of trust value for Auckland Museum took 1.1920928955078125e-05s
INFO | --- Analysis for Auckland-Museum took 6.178933382034302s
Availability | SPARQL endpoint availability check for National Library of Spain took 5.511149168014526s
Availability | VoID file availability check for National Library of Spain took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.2576420307159424s
Reputation | Calculation of the PageRank for National Library of Spain took 0.02637648582458496s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.1444091796875e-05s
Believability | Calculation of trust value for National Library of Spain took 1.239776611328125e-05s
INFO | --- Analysis for BNE took 8.337818622589111s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.4407927989959717s
Availability | VoID file availability check for National Library of Korea took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.26090526580810547s
Reputation | Calculation of the PageRank for National Library of Korea took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.1205673217773438e-05s
Believability | Calculation of trust value for National Library of Korea took 1.239776611328125e-05s
INFO | --- Analysis for Korea-Library took 5.2962446212768555s
Availability | SPARQL endpoint availability check for The State Russian Museum took 2.6572115421295166s
Availability | VoID file availability check for The State Russian Museum took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.2626197338104248s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.021453857421875s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.1444091796875e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.1444091796875e-05s
INFO | --- Analysis for Russian-Museum took 5.46333122253418s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.7251262664794922s
Availability | VoID file availability check for National Library of Scotland took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.2651541233062744s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.022209644317626953s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0010879039764404297s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.430511474609375e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.3113021850585938e-05s
INFO | --- Analysis for National-Library-of-Scotland took 6.868543386459351s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.32868385314941406s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.2677347660064697s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.021851778030395508s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0012154579162597656s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.7642974853515625e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.2159347534179688e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.317446231842041s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.20342326164245605s
Availability | VoID file availability check for OntoComedySources took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.2530982494354248s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02141427993774414s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.1920928955078125e-05s
Believability | Calculation of trust value for OntoComedySources took 1.3113021850585938e-05s
INFO | --- Analysis for OntoComedySources took 3.731923818588257s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.19472885131835938s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.24522805213928223s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.239776611328125e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.0013580322265625e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 4.152703046798706s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.14197516441345215s
Availability | VoID file availability check for SaintGall Ontology took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.2638065814971924s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.0967254638671875e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for SaintGall-Ontology took 3.011800765991211s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.7404141426086426s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.24990415573120117s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020435810089111328s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.1682510375976562e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 3.7719383239746094s
Availability | SPARQL endpoint availability check for ICON took 0.3549647331237793s
Availability | VoID file availability check for ICON took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for ICON took 0.2727229595184326s
Reputation | Calculation of the PageRank for ICON took 0.021065950393676758s
Interlinking | Calculation of Degree of Connection for ICON took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ICON took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for ICON took 1.0728836059570312e-05s
Believability | Calculation of trust value for ICON took 1.0251998901367188e-05s
INFO | --- Analysis for ICON took 4.1297996044158936s
Availability | SPARQL endpoint availability check for Polifonia took 0.2556014060974121s
Availability | VoID file availability check for Polifonia took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Polifonia took 0.2566707134246826s
Reputation | Calculation of the PageRank for Polifonia took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.1444091796875e-05s
Believability | Calculation of trust value for Polifonia took 1.1205673217773438e-05s
INFO | --- Analysis for Polifonia took 4.006455183029175s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.27598094940185547s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.2588353157043457s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.1205673217773438e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 1.1205673217773438e-05s
INFO | --- Analysis for Atlas-of-Paths took 3.897904396057129s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.21791434288024902s
Availability | VoID file availability check for Music Note Ontology took 0.0006964206695556641s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.2748603820800781s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.239776611328125e-05s
Believability | Calculation of trust value for Music Note Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for Music-Note-Ontology took 7.912996053695679s
Availability | SPARQL endpoint availability check for HaMSE took 0.1924285888671875s
Availability | VoID file availability check for HaMSE took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for HaMSE took 0.23744773864746094s
Reputation | Calculation of the PageRank for HaMSE took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.0967254638671875e-05s
Believability | Calculation of trust value for HaMSE took 1.1444091796875e-05s
INFO | --- Analysis for HaMSE took 4.9716246128082275s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.0796651840209961s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.25248026847839355s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.1205673217773438e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for FOod took 4.740761756896973s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.7030613422393799s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.2510712146759033s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.1682510375976562e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.3113021850585938e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 4.969414472579956s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.4983179569244385s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.2613368034362793s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.022896528244018555s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.2159347534179688e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 1.239776611328125e-05s
INFO | --- Analysis for ARIADNE took 5.564414739608765s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.303267240524292s
Availability | VoID file availability check for Odeuropa Ontology took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.2467038631439209s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.2159347534179688e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for Odeuropa took 3.0583229064941406s

--- Total time for analysis:347647.25140857697s ---
--- Total time for analysis:96.56868094682693 hours ---