Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.172325134277344e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.16080093383789062s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.5122933387756348s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00041103363037109375s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 9.775161743164062e-06s
INFO | --- Analysis for 0080-3626 took 2.532214403152466s
Availability | SPARQL endpoint availability check for 土地利用图 took 8.96453857421875e-05s
Availability | VoID file availability check for 土地利用图 took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.15455102920532227s
Reputation | Calculation of the PageRank for 土地利用图 took 0.02015376091003418s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.147125244140625e-05s
Believability | Calculation of trust value for 土地利用图 took 1.6450881958007812e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 1.7665882110595703s
Availability | SPARQL endpoint availability check for 113322 took 9.250640869140625e-05s
Availability | VoID file availability check for 113322 took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for 113322 took 0.1528491973876953s
Reputation | Calculation of the PageRank for 113322 took 0.0229189395904541s
Interlinking | Calculation of Degree of Connection for 113322 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for 113322 took 4.601478576660156e-05s
Believability | Calculation of trust value for 113322 took 1.3828277587890625e-05s
INFO | --- Analysis for 11 took 1.8330700397491455s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.673004150390625e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0003676414489746094s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.15494966506958008s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020642995834350586s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.981590270996094e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.1920928955078125e-05s
INFO | --- Analysis for 12323 took 1.7243690490722656s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 4.887580871582031e-05s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0003292560577392578s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.15174317359924316s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.02523636817932129s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0015819072723388672s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.0001442432403564453s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.0728836059570312e-05s
INFO | --- Analysis for 2000-us-census-rdf took 1.7162461280822754s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 6.008148193359375e-05s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.16565275192260742s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020984411239624023s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 5.1975250244140625e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 1.2874603271484375e-05s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 1.837707281112671s
Availability | SPARQL endpoint availability check for Open Data Web took 8.940696716308594e-05s
Availability | VoID file availability check for Open Data Web took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.1547091007232666s
Reputation | Calculation of the PageRank for Open Data Web took 0.021775484085083008s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 4.935264587402344e-05s
Believability | Calculation of trust value for Open Data Web took 1.5497207641601562e-05s
INFO | --- Analysis for _data.odw.tw took 1.7664804458618164s
Availability | SPARQL endpoint availability check for 土地利用 took 9.179115295410156e-05s
Availability | VoID file availability check for 土地利用 took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.15948963165283203s
Reputation | Calculation of the PageRank for 土地利用 took 0.021030187606811523s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 4.410743713378906e-05s
Believability | Calculation of trust value for 土地利用 took 1.7404556274414062e-05s
INFO | --- Analysis for _data1.odw.tw took 1.752793550491333s
Availability | SPARQL endpoint availability check for 土地利用模型 took 9.1552734375e-05s
Availability | VoID file availability check for 土地利用模型 took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.15271568298339844s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.022064685821533203s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 4.76837158203125e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.1920928955078125e-05s
INFO | --- Analysis for _data2.odw.tw took 1.74814772605896s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.726119995117188e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.1608748435974121s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021856307983398438s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 4.4345855712890625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.5974044799804688e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 1.787095546722412s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 9.512901306152344e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.18642044067382812s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.021214962005615234s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 4.4345855712890625e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.5497207641601562e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 1.7905514240264893s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 9.179115295410156e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.15945196151733398s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.021033525466918945s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 4.458427429199219e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 9.775161743164062e-06s
INFO | --- Analysis for A1 took 1.7762491703033447s
Availability | SPARQL endpoint availability check for SummerOlympics took 9.441375732421875e-05s
Availability | VoID file availability check for SummerOlympics took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.16077470779418945s
Reputation | Calculation of the PageRank for SummerOlympics took 0.022385358810424805s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 8.535385131835938e-05s
Believability | Calculation of trust value for SummerOlympics took 1.4066696166992188e-05s
INFO | --- Analysis for abc took 1.777069091796875s
Availability | SPARQL endpoint availability check for Test_m took 9.012222290039062e-05s
Availability | VoID file availability check for Test_m took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Test_m took 0.15440821647644043s
Reputation | Calculation of the PageRank for Test_m took 0.02193474769592285s
Interlinking | Calculation of Degree of Connection for Test_m took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Test_m took 5.2928924560546875e-05s
Believability | Calculation of trust value for Test_m took 1.52587890625e-05s
INFO | --- Analysis for ABC took 1.771101951599121s
Availability | SPARQL endpoint availability check for my intro took 8.630752563476562e-05s
Availability | VoID file availability check for my intro took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for my intro took 0.16134047508239746s
Reputation | Calculation of the PageRank for my intro took 0.021470308303833008s
Interlinking | Calculation of Degree of Connection for my intro took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for my intro took 4.8160552978515625e-05s
Believability | Calculation of trust value for my intro took 1.3828277587890625e-05s
INFO | --- Analysis for abhay_intro took 1.7928862571716309s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 4.553794860839844e-05s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.14662957191467285s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.021072864532470703s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00011801719665527344s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.621246337890625e-05s
INFO | --- Analysis for abs-linked-data took 1.71622896194458s
Availability | SPARQL endpoint availability check for AcadOnto took 4.76837158203125e-05s
Availability | VoID file availability check for AcadOnto took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.15404963493347168s
Reputation | Calculation of the PageRank for AcadOnto took 0.0220794677734375s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 4.57763671875e-05s
Believability | Calculation of trust value for AcadOnto took 1.049041748046875e-05s
INFO | --- Analysis for acadonto took 1.7462046146392822s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.9114227294921875e-05s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.14952325820922852s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.021259784698486328s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.982948303222656e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.049041748046875e-05s
INFO | --- Analysis for acorn-sat took 1.7222316265106201s
Availability | SPARQL endpoint availability check for Addgene took 0.00010442733764648438s
Availability | VoID file availability check for Addgene took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Addgene took 0.1538865566253662s
Reputation | Calculation of the PageRank for Addgene took 0.02132129669189453s
Interlinking | Calculation of Degree of Connection for Addgene took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.696846008300781e-05s
Believability | Calculation of trust value for Addgene took 1.621246337890625e-05s
INFO | --- Analysis for addgene took 1.8190293312072754s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 9.059906005859375e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.1553635597229004s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.021404504776000977s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 0.00010657310485839844s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.049041748046875e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 1.7157788276672363s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 4.76837158203125e-05s
Availability | VoID file availability check for AEMET metereological dataset took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.15507888793945312s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.022296905517578125s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.9114227294921875e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.049041748046875e-05s
INFO | --- Analysis for aemet took 1.7271435260772705s
Availability | SPARQL endpoint availability check for AgriNepalData took 7.128715515136719e-05s
Availability | VoID file availability check for AgriNepalData took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.1601550579071045s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02185654640197754s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 8.559226989746094e-05s
Believability | Calculation of trust value for AgriNepalData took 9.775161743164062e-06s
INFO | --- Analysis for agrinepaldata took 1.7359917163848877s
Availability | SPARQL endpoint availability check for AGRIS took 9.036064147949219e-05s
Availability | VoID file availability check for AGRIS took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for AGRIS took 0.15716147422790527s
Reputation | Calculation of the PageRank for AGRIS took 0.021117448806762695s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.487701416015625e-05s
Believability | Calculation of trust value for AGRIS took 1.5020370483398438e-05s
INFO | --- Analysis for agris took 1.7728502750396729s
Availability | SPARQL endpoint availability check for AGROVOC took 4.7206878662109375e-05s
Availability | VoID file availability check for AGROVOC took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.1644132137298584s
Reputation | Calculation of the PageRank for AGROVOC took 0.021134138107299805s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00012111663818359375s
Believability | Calculation of trust value for AGROVOC took 1.3113021850585938e-05s
INFO | --- Analysis for agrovoc took 1.7616393566131592s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 9.202957153320312e-05s
Availability | VoID file availability check for Analytics India Magazine took 0.0003120899200439453s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.16539549827575684s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.02552938461303711s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0009500980377197266s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 5.340576171875e-05s
Believability | Calculation of trust value for Analytics India Magazine took 1.5974044799804688e-05s
INFO | --- Analysis for AIM took 1.7536768913269043s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 5.984306335449219e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0003483295440673828s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.15719223022460938s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.02098679542541504s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.52587890625e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 4.363059997558594e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.049041748046875e-05s
INFO | --- Analysis for AISHE took 1.68129301071167s
Availability | SPARQL endpoint availability check for  equipment ontology took 5.221366882324219e-05s
Availability | VoID file availability check for  equipment ontology took 0.0003159046173095703s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.16486001014709473s
Reputation | Calculation of the PageRank for  equipment ontology took 0.022246837615966797s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 4.839897155761719e-05s
Believability | Calculation of trust value for  equipment ontology took 1.0728836059570312e-05s
INFO | --- Analysis for akash took 1.750535011291504s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.0125954151153564s
Availability | VoID file availability check for aliada-scanbit-net took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.16585063934326172s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.021649837493896484s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00012731552124023438s
Believability | Calculation of trust value for aliada-scanbit-net took 1.6927719116210938e-05s
INFO | --- Analysis for aliada-scanbit-net took 2.7945849895477295s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 5.245208740234375e-05s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.14773058891296387s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.021196603775024414s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 7.796287536621094e-05s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.0251998901367188e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 1.7794735431671143s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 6.413459777832031e-05s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.15610337257385254s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.021103382110595703s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.744529724121094e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 9.298324584960938e-06s
INFO | --- Analysis for alpino-rdf took 1.7207701206207275s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.76837158203125e-05s
Availability | VoID file availability check for AAT-atawil took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.15824055671691895s
Reputation | Calculation of the PageRank for AAT-atawil took 0.021630287170410156s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.52587890625e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 4.696846008300781e-05s
Believability | Calculation of trust value for AAT-atawil took 1.4781951904296875e-05s
INFO | --- Analysis for Altawil took 1.7930896282196045s
Availability | SPARQL endpoint availability check for Amer Nejma took 9.369850158691406e-05s
Availability | VoID file availability check for Amer Nejma took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.16765260696411133s
Reputation | Calculation of the PageRank for Amer Nejma took 0.02345728874206543s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 2.7179718017578125e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0012359619140625s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 6.246566772460938e-05s
Believability | Calculation of trust value for Amer Nejma took 1.3828277587890625e-05s
INFO | --- Analysis for Amer_Nejma took 1.783306360244751s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.6602869033813477s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.16523241996765137s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.021222829818725586s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00010371208190917969s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.5497207641601562e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 2.461822748184204s
Availability | SPARQL endpoint availability check for Anime Dataset took 5.030632019042969e-05s
Availability | VoID file availability check for Anime Dataset took 0.00036835670471191406s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.15911626815795898s
Reputation | Calculation of the PageRank for Anime Dataset took 0.021050453186035156s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 4.220008850097656e-05s
Believability | Calculation of trust value for Anime Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for Anime took 1.7976620197296143s
Availability | SPARQL endpoint availability check for ANNO took 0.00010538101196289062s
Availability | VoID file availability check for ANNO took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for ANNO took 0.1556839942932129s
Reputation | Calculation of the PageRank for ANNO took 0.021314382553100586s
Interlinking | Calculation of Degree of Connection for ANNO took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for ANNO took 4.935264587402344e-05s
Believability | Calculation of trust value for ANNO took 1.2159347534179688e-05s
INFO | --- Analysis for anno took 1.763157844543457s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 5.078315734863281e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.15263628959655762s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.02185964584350586s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 8.797645568847656e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.33514404296875e-05s
INFO | --- Analysis for AntiqueCarsCollection took 1.7302322387695312s
Availability | SPARQL endpoint availability check for apache took 9.202957153320312e-05s
Availability | VoID file availability check for apache took 0.0003590583801269531s
Completeness | Calculation of interlinking completeness for apache took 0.16367363929748535s
Reputation | Calculation of the PageRank for apache took 0.02267289161682129s
Interlinking | Calculation of Degree of Connection for apache took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for apache took 0.0013096332550048828s
Interlinking | Calculation of Clustering coefficient for apache took 9.369850158691406e-05s
Believability | Calculation of trust value for apache took 1.5735626220703125e-05s
INFO | --- Analysis for apache took 1.7505114078521729s
Availability | SPARQL endpoint availability check for Apertium RDF took 5.030632019042969e-05s
Availability | VoID file availability check for Apertium RDF took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.164947509765625s
Reputation | Calculation of the PageRank for Apertium RDF took 0.022316694259643555s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 5.841255187988281e-05s
Believability | Calculation of trust value for Apertium RDF took 1.5497207641601562e-05s
INFO | --- Analysis for apertium-rdf took 1.7916302680969238s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.7206878662109375e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.15401077270507812s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.021921634674072266s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 5.91278076171875e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.52587890625e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 1.7417283058166504s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 9.417533874511719e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.15607619285583496s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.02093052864074707s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 5.555152893066406e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 1.7416563034057617s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 6.723403930664062e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.16479015350341797s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.021847963333129883s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 5.91278076171875e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.4543533325195312e-05s
INFO | --- Analysis for apertium-rdf-en-es took 1.7888619899749756s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 9.012222290039062e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.16149449348449707s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.022717714309692383s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0008933544158935547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 6.747245788574219e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.5020370483398438e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 1.7370250225067139s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 8.96453857421875e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.151198148727417s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.021318674087524414s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 5.698204040527344e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 1.761018991470337s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.15657663345336914s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.021265029907226562s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 5.626678466796875e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 1.781829833984375s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 8.893013000488281e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0003376007080078125s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.16501450538635254s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.021322011947631836s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.984306335449219e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 1.7542495727539062s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 6.961822509765625e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.15978264808654785s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.021160125732421875s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 6.270408630371094e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.4543533325195312e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 1.752673625946045s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.839897155761719e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.15259194374084473s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.021928071975708008s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 5.626678466796875e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.621246337890625e-05s
INFO | --- Analysis for apertium-rdf-es-an took 1.7467756271362305s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 9.250640869140625e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.15430736541748047s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02129197120666504s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 6.4849853515625e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.4781951904296875e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 1.786911964416504s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 9.465217590332031e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.15642929077148438s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.0212399959564209s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0008571147918701172s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 6.127357482910156e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.4781951904296875e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 1.7557566165924072s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 5.054473876953125e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.16533946990966797s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.021221637725830078s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 5.602836608886719e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 1.753849744796753s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 8.893013000488281e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.27489304542541504s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.021195173263549805s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 5.6743621826171875e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.4543533325195312e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 1.892723560333252s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 9.107589721679688e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.1629645824432373s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.021333694458007812s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0008766651153564453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 6.651878356933594e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 1.7540647983551025s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.76837158203125e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.00039267539978027344s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.16121745109558105s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 5.745887756347656e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 1.7310056686401367s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 8.821487426757812e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.1616227626800537s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 5.650520324707031e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 9.775161743164062e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 1.7525503635406494s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.601478576660156e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.15032482147216797s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02161431312561035s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 6.151199340820312e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.4543533325195312e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 1.739694356918335s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 5.245208740234375e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.15853095054626465s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.021233081817626953s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 5.459785461425781e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 1.7636263370513916s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 8.821487426757812e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.1539168357849121s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02149677276611328s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 5.8650970458984375e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.5020370483398438e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 1.7501013278961182s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.7206878662109375e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.1633150577545166s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.021257877349853516s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0012469291687011719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 7.224082946777344e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.52587890625e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 1.7253639698028564s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.601478576660156e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.16254210472106934s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02108001708984375s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 5.6743621826171875e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.52587890625e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 1.7601580619812012s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.76837158203125e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.16656184196472168s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020886898040771484s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 5.841255187988281e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.5020370483398438e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 1.7955572605133057s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 8.678436279296875e-05s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 0.15761494636535645s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.021201610565185547s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 5.435943603515625e-05s
Believability | Calculation of trust value for AragoDBpedia - aragon open data took 1.4781951904296875e-05s
INFO | --- Analysis for aragodbpedia took 2.0229296684265137s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 0.00010371208190917969s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.1568901538848877s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.021068572998046875s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.507469177246094e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.5735626220703125e-05s
INFO | --- Analysis for archiveshub-linkeddata took 1.766024112701416s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 9.202957153320312e-05s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.1535780429840088s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02108287811279297s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 6.365776062011719e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0009386539459228516s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 4.9591064453125e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.52587890625e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 1.8021442890167236s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 8.988380432128906e-05s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.1761307716369629s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.021437406539916992s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 5.245208740234375e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.52587890625e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 1.7695443630218506s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.6253204345703125e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.1637282371520996s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.021813154220581055s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00011587142944335938s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.5020370483398438e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 1.7404606342315674s
Availability | SPARQL endpoint availability check for Arthroscopy community took 9.274482727050781e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.16157865524291992s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.021449804306030273s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.0001518726348876953s
Believability | Calculation of trust value for Arthroscopy community took 8.344650268554688e-06s
INFO | --- Analysis for arthroscopy took 1.8726000785827637s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 5.3882598876953125e-05s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0004222393035888672s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.15163516998291016s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.021048307418823242s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.8596649169921875e-05s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.0967254638671875e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 76.67459559440613s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.3911755084991455s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.16249561309814453s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020320415496826172s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.271766662597656e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.775161743164062e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 80.10010600090027s
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.346238136291504s
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.0004799365997314453s
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 0.152937650680542s
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.021831274032592773s
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 9.775161743164062e-06s
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.0007112026214599609s
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.224082946777344e-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 9.775161743164062e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 4.110283374786377s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.3298728466033936s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.19452905654907227s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.440017700195312e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.58306884765625e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 4.160152912139893s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.3340253829956055s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.15495944023132324s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.220008850097656e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC-CRB took 4.068107604980469s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.3273138999938965s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.16092276573181152s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.021180391311645508s
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.00069427490234375s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.630752563476562e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 4.07820725440979s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.3270885944366455s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.161423921585083s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.62396240234375e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 8.821487426757812e-06s
INFO | --- Analysis for ASCDC-DQOT took 4.065816164016724s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.330091714859009s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.1534287929534912s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.462501525878906e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 4.079864025115967s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.094871759414673s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.1608295440673828s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 9.417533874511719e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 4.841235399246216s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.3282992839813232s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.15517592430114746s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.022140026092529297s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 4.982948303222656e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 4.138357400894165s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.3266079425811768s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.1601262092590332s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.021695613861083984s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.245208740234375e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 4.062911033630371s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.776829719543457s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.15851950645446777s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.022234439849853516s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.792213439941406e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 8.821487426757812e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 5.5429298877716064s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.332608699798584s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.15945982933044434s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.022924184799194336s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.271766662597656e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.049041748046875e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 4.060151100158691s
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.3263754844665527s
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.00045180320739746094s
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 0.16175627708435059s
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.02021312713623047s
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.2159347534179688e-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.0007188320159912109s
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.748603820800781e-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 8.58306884765625e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 4.06359338760376s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.3397445678710938s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.16014385223388672s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 5.221366882324219e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.0967254638671875e-05s
INFO | --- Analysis for ASCDC_-_DNB took 4.111977577209473s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 8.249282836914062e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.15709209442138672s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.508827209472656e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.0251998901367188e-05s
INFO | --- Analysis for asit took 1.726874589920044s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 6.079673767089844e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.16025328636169434s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020093202590942383s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007035732269287109s
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.0013580322265625e-05s
INFO | --- Analysis for asjp took 1.7153913974761963s
Availability | SPARQL endpoint availability check for ASN:US took 8.0108642578125e-05s
Availability | VoID file availability check for ASN:US took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for ASN:US took 0.15859150886535645s
Reputation | Calculation of the PageRank for ASN:US took 0.020143508911132812s
Interlinking | Calculation of Degree of Connection for ASN:US took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.365776062011719e-05s
Believability | Calculation of trust value for ASN:US took 1.1444091796875e-05s
INFO | --- Analysis for asn-us took 1.7617087364196777s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 8.249282836914062e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.1558082103729248s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02093219757080078s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.123283386230469e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 1.0013580322265625e-05s
INFO | --- Analysis for aspire-mmu took 1.7639315128326416s
Availability | SPARQL endpoint availability check for associations took 8.58306884765625e-05s
Availability | VoID file availability check for associations took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for associations took 0.15801286697387695s
Reputation | Calculation of the PageRank for associations took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for associations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for associations took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for associations took 6.794929504394531e-05s
Believability | Calculation of trust value for associations took 1.3828277587890625e-05s
INFO | --- Analysis for associations took 1.7597863674163818s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 7.05718994140625e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.15729594230651855s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.940696716308594e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.2636184692382812e-05s
INFO | --- Analysis for athelia-rfid took 1.8053574562072754s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 4.172325134277344e-05s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.16167736053466797s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.021172285079956055s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.364418029785156e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for AugustiniConfessiones took 1.7436654567718506s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 8.249282836914062e-05s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.1516106128692627s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.726119995117188e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.0013580322265625e-05s
INFO | --- Analysis for austrian_ski_racers took 1.733198642730713s
Availability | SPARQL endpoint availability check for AVsOnto took 4.1484832763671875e-05s
Availability | VoID file availability check for AVsOnto took 0.0002124309539794922s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.15850281715393066s
Reputation | Calculation of the PageRank for AVsOnto took 0.020273447036743164s
Interlinking | Calculation of Degree of Connection for AVsOnto took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.123283386230469e-05s
Believability | Calculation of trust value for AVsOnto took 9.059906005859375e-06s
INFO | --- Analysis for AVsOnto took 1.7061450481414795s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24558639526367188s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0004868507385253906s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 215.38377046585083s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.44342756271362305s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1035301685333s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 203.93617868423462s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0610177516937s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.04494547843933s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4191741943359375s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3037235736846924s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15603280067443848s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10329318046569824s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 46.41368269920349s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0748944282532s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11175680160522461s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10031509399414s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.27340054512023926s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1015772819519043s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20851540565490723s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10001015663146973s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.518204927444458s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 6.842613220214844e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.08599114418029785s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.09596729278564s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17446160316467285s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11658668518066406s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12426638603210449s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.42600226402282715s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.252882719039917s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 859.3700487613678s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13127803802490234s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.560864925384521s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1254076957702637s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.744353532791138s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12032437324523926s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.19433546066284s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 26.466221809387207s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.194732189178467s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.47175788879395s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.771484136581421s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.33353376388549805s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0257790088653564s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5641810894012451s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.022024154663085938s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.295608520507812e-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 7.3909759521484375e-06s
INFO | --- Analysis for b3kat took 4436.379685640335s
Availability | SPARQL endpoint availability check for BabelNet took 8.153915405273438e-05s
Availability | VoID file availability check for BabelNet took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for BabelNet took 0.15821099281311035s
Reputation | Calculation of the PageRank for BabelNet took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for BabelNet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BabelNet took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00016427040100097656s
Believability | Calculation of trust value for BabelNet took 1.1920928955078125e-05s
INFO | --- Analysis for babelnet took 1.750471830368042s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.267692565917969e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.1544334888458252s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.170967102050781e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.1444091796875e-05s
INFO | --- Analysis for Bacevicius.lt took 1.726132869720459s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 8.440017700195312e-05s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.1547708511352539s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.00543212890625e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.0728836059570312e-05s
INFO | --- Analysis for bag took 1.745424509048462s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.463859558105469e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.15567946434020996s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02023601531982422s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.8371810913085938e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 9.775161743164062e-06s
INFO | --- Analysis for baixue took 1.7331080436706543s
Availability | SPARQL endpoint availability check for baixue composer took 8.440017700195312e-05s
Availability | VoID file availability check for baixue composer took 0.0003941059112548828s
Completeness | Calculation of interlinking completeness for baixue composer took 0.15395736694335938s
Reputation | Calculation of the PageRank for baixue composer took 0.022149324417114258s
Interlinking | Calculation of Degree of Connection for baixue composer took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for baixue composer took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for baixue composer took 2.9087066650390625e-05s
Believability | Calculation of trust value for baixue composer took 1.0251998901367188e-05s
INFO | --- Analysis for baixue_composer took 1.7486860752105713s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.124641418457031e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.1529989242553711s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.022440433502197266s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 4.4345855712890625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.0013580322265625e-05s
INFO | --- Analysis for baixue_imagery took 1.773386001586914s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.487701416015625e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.16088652610778809s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02205967903137207s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.7894973754882812e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 9.775161743164062e-06s
INFO | --- Analysis for baixue_imagery1 took 1.7437808513641357s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 3.7670135498046875e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.16942524909973145s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020169734954833984s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.719329833984375e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 4.7206878662109375e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 1.758171796798706s
Availability | SPARQL endpoint availability check for BBC Music took 0.474895715713501s
Availability | VoID file availability check for BBC Music took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for BBC Music took 0.15487146377563477s
Reputation | Calculation of the PageRank for BBC Music took 0.020279407501220703s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012302398681640625s
Believability | Calculation of trust value for BBC Music took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-music took 2.2558813095092773s
Availability | SPARQL endpoint availability check for BBC Programmes took 8.082389831542969e-05s
Availability | VoID file availability check for BBC Programmes took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.16048789024353027s
Reputation | Calculation of the PageRank for BBC Programmes took 0.021965503692626953s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 9.918212890625e-05s
Believability | Calculation of trust value for BBC Programmes took 1.239776611328125e-05s
INFO | --- Analysis for bbc-programmes took 1.7780723571777344s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.37185239791870117s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.15317416191101074s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.0218963623046875s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 9.751319885253906e-05s
Believability | Calculation of trust value for BBC Wildlife Finder took 9.5367431640625e-06s
INFO | --- Analysis for bbc-wildlife-finder took 2.148791790008545s
Availability | SPARQL endpoint availability check for BBOP took 8.296966552734375e-05s
Availability | VoID file availability check for BBOP took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for BBOP took 0.15926504135131836s
Reputation | Calculation of the PageRank for BBOP took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.0994415283203125e-05s
Believability | Calculation of trust value for BBOP took 1.2159347534179688e-05s
INFO | --- Analysis for bbop-selected took 1.7670369148254395s
Availability | SPARQL endpoint availability check for Bdgp took 4.0531158447265625e-05s
Availability | VoID file availability check for Bdgp took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Bdgp took 0.15985631942749023s
Reputation | Calculation of the PageRank for Bdgp took 0.02023601531982422s
Interlinking | Calculation of Degree of Connection for Bdgp took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bdgp took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.0517578125e-05s
Believability | Calculation of trust value for Bdgp took 1.0013580322265625e-05s
INFO | --- Analysis for bdgp took 1.7341833114624023s
Availability | SPARQL endpoint availability check for Bendev Junior took 9.298324584960938e-05s
Availability | VoID file availability check for Bendev Junior took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.17368459701538086s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020105838775634766s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.7894973754882812e-05s
Believability | Calculation of trust value for Bendev Junior took 5.7220458984375e-06s
INFO | --- Analysis for bendevoficial took 1.7821202278137207s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 8.20159912109375e-05s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.16163301467895508s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.604194641113281e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 1.1920928955078125e-05s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 1.7831461429595947s
Availability | SPARQL endpoint availability check for berlios took 8.654594421386719e-05s
Availability | VoID file availability check for berlios took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for berlios took 0.1615619659423828s
Reputation | Calculation of the PageRank for berlios took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for berlios took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for berlios took 8.630752563476562e-05s
Believability | Calculation of trust value for berlios took 1.0251998901367188e-05s
INFO | --- Analysis for berlios took 1.7567415237426758s
Availability | SPARQL endpoint availability check for Between Our Worlds took 8.153915405273438e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.1517472267150879s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.319450378417969e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.1920928955078125e-05s
INFO | --- Analysis for betweenourworlds took 1.712925672531128s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00021409988403320312s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.1666855812072754s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.630752563476562e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for bfs-linked-data took 1.7152099609375s
Availability | SPARQL endpoint availability check for BibBase took 5.364418029785156e-05s
Availability | VoID file availability check for BibBase took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for BibBase took 0.15836453437805176s
Reputation | Calculation of the PageRank for BibBase took 0.020102977752685547s
Interlinking | Calculation of Degree of Connection for BibBase took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.250640869140625e-05s
Believability | Calculation of trust value for BibBase took 5.7220458984375e-06s
INFO | --- Analysis for bibbase took 1.722508430480957s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.00543212890625e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.15300250053405762s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.560585021972656e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.3113021850585938e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 1.7238104343414307s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.416175842285156e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.16420745849609375s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.560585021972656e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 2.5510787963867188e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 1.8288209438323975s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 8.177757263183594e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.15714240074157715s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020156145095825195s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.457069396972656e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.0251998901367188e-05s
INFO | --- Analysis for BibSonomy took 1.7422244548797607s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 9.72747802734375e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.16040682792663574s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.02019333839416504s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.7894973754882812e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.1205673217773438e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 1.724463939666748s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 8.153915405273438e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.1565711498260498s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.022188663482666016s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007281303405761719s
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 5.0067901611328125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 1.7341365814208984s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 8.20159912109375e-05s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.15549111366271973s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020061254501342773s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.059906005859375e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1.744476556777954s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 8.344650268554688e-05s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.15378069877624512s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.021095752716064453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00010800361633300781s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1.7620515823364258s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 8.296966552734375e-05s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.16199183464050293s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02173471450805664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004017353057861328s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1.7416462898254395s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 8.416175842285156e-05s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.15940642356872559s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 4.982948303222656e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-chembl took 1.752026081085205s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 8.559226989746094e-05s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.15544390678405762s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.2438507080078125e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1.729550838470459s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.1520693302154541s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 5.8650970458984375e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-ctd took 1.7586371898651123s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 0.00010752677917480469s
Availability | VoID file availability check for bio2rdf-dataset took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.16382288932800293s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.022049427032470703s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.363059997558594e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-dataset took 1.76534104347229s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 6.341934204101562e-05s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.15337061882019043s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.022771358489990234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 5.936622619628906e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1.722419023513794s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.16654014587402344s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.02098822593688965s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 9.751319885253906e-05s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1.8087754249572754s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::Genage took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.1655259132385254s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.022204875946044922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.221366882324219e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-genage took 1.7623684406280518s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 8.535385131835938e-05s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.15521550178527832s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 4.673004150390625e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-gendr took 1.7452490329742432s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 3.814697265625e-05s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.14751815795898438s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.173683166503906e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-goa took 1.7146766185760498s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 7.319450378417969e-05s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.1561875343322754s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 9.894371032714844e-05s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1.7361891269683838s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 3.910064697265625e-05s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.1522371768951416s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020268917083740234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 4.482269287109375e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 5.4836273193359375e-06s
INFO | --- Analysis for bio2rdf-homologene took 1.7032861709594727s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 8.058547973632812e-05s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.15884041786193848s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 9.751319885253906e-05s
Believability | Calculation of trust value for Bio2RDF::Interpro took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-interpro took 1.73903226852417s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 8.225440979003906e-05s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0008757114410400391s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.15631747245788574s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02023601531982422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 8.344650268554688e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-iproclass took 1.9077868461608887s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 8.344650268554688e-05s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.15661191940307617s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.021546363830566406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.43865966796875e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1.727588176727295s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.14930462837219238s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020123720169067383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 5.0067901611328125e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 1.7256004810333252s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 8.177757263183594e-05s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.15197443962097168s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020139455795288086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 3.838539123535156e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-lsr took 1.7767441272735596s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.16265130043029785s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 6.604194641113281e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-mesh took 1.7398850917816162s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 7.963180541992188e-05s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.1561570167541504s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 8.416175842285156e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-mgi took 1.7413859367370605s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 6.413459777832031e-05s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.1557760238647461s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.021113157272338867s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011157989501953125s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1.7733802795410156s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 3.886222839355469e-05s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.16051745414733887s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.2438507080078125e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-ndc took 1.740936279296875s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 3.838539123535156e-05s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.16259336471557617s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02022838592529297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 2.86102294921875e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-nextprot took 1.7373356819152832s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 8.177757263183594e-05s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.16019582748413086s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020230531692504883s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00014328956604003906s
Believability | Calculation of trust value for Bio2RDF::Omim took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-omim took 1.7831127643585205s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 3.8623809814453125e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.15853548049926758s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.02009415626525879s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.504753112792969e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 1.738602876663208s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 8.273124694824219e-05s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.16368699073791504s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02098250389099121s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 6.723403930664062e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1.7503862380981445s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 7.963180541992188e-05s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.16107654571533203s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 2.7418136596679688e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 1.7999494075775146s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 8.249282836914062e-05s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.18097591400146484s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 6.842613220214844e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1.7220160961151123s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.15711212158203125s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001304149627685547s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1.8434176445007324s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 8.130073547363281e-05s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.1552104949951172s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.176399230957031e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-sabiork took 1.7591323852539062s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 4.410743713378906e-05s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.1548166275024414s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020518064498901367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 9.775161743164062e-05s
Believability | Calculation of trust value for Bio2RDF::Sgd took 5.7220458984375e-06s
INFO | --- Analysis for bio2rdf-sgd took 1.6832733154296875s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.076957702636719e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.15485262870788574s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020128250122070312s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.2901763916015625e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 5.7220458984375e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 1.6752829551696777s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 5.4836273193359375e-05s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.15740752220153809s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.021788835525512695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.076957702636719e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-sider took 1.748746395111084s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 8.463859558105469e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.16340875625610352s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.022548198699951172s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.00543212890625e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-taxon took 1.733935832977295s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.16463375091552734s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0008366107940673828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010776519775390625s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1.7375843524932861s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 7.987022399902344e-05s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.15679311752319336s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.026180744171142578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0013916492462158203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 4.482269287109375e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 1.706632137298584s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.15645813941955566s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02026224136352539s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.224082946777344e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1.708906888961792s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 8.440017700195312e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.16671037673950195s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020474672317504883s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.1682510375976562e-05s
Believability | Calculation of trust value for Biografías y Vidas took 1.1682510375976562e-05s
INFO | --- Analysis for biografiasyvidas took 1.7708148956298828s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 8.177757263183594e-05s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.16205596923828125s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020084857940673828s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 7.939338684082031e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.1920928955078125e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 1.7534019947052002s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 3.9577484130859375e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.15143299102783203s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.022138357162475586s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.7670135498046875e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.0013580322265625e-05s
INFO | --- Analysis for biolod-pdb took 1.8135180473327637s
Availability | SPARQL endpoint availability check for BioModels RDF took 4.00543212890625e-05s
Availability | VoID file availability check for BioModels RDF took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.1509990692138672s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.314018249511719e-05s
Believability | Calculation of trust value for BioModels RDF took 1.0013580322265625e-05s
INFO | --- Analysis for biomodels-rdf took 1.7560584545135498s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.9577484130859375e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.15256285667419434s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.021028518676757812s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.6941299438476562e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0251998901367188e-05s
INFO | --- Analysis for Biop took 1.7399814128875732s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.910064697265625e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.15808939933776855s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0251998901367188e-05s
INFO | --- Analysis for Bioportal took 1.7208356857299805s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 0.00010085105895996094s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.16139984130859375s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.02167510986328125s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006184577941894531s
Believability | Calculation of trust value for Amphibian gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-aao took 1.7439281940460205s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 8.320808410644531e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.1565546989440918s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.022199630737304688s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00029087066650390625s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-aba took 1.8039584159851074s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.15859770774841309s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015032291412353516s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-acgt took 1.764352798461914s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 8.106231689453125e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.15607380867004395s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020202159881591797s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003185272216796875s
Believability | Calculation of trust value for Animal natural history and life history took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-adw took 1.7348790168762207s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.159775972366333s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00046825408935546875s
Believability | Calculation of trust value for Anatomical Entity Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-aeo took 1.766233205795288s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 7.915496826171875e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.16946911811828613s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.021090030670166016s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009591579437255859s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-aero took 1.746323823928833s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.220008850097656e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.15152597427368164s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0008633136749267578s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004699230194091797s
Believability | Calculation of trust value for AI/RHEUM took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-air took 1.7616119384765625s
Availability | SPARQL endpoint availability check for Amino Acid took 4.267692565917969e-05s
Availability | VoID file availability check for Amino Acid took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.1506330966949463s
Reputation | Calculation of the PageRank for Amino Acid took 0.020235538482666016s
Interlinking | Calculation of Degree of Connection for Amino Acid took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00025343894958496094s
Believability | Calculation of trust value for Amino Acid took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-amino-acid took 1.692281723022461s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.15539932250976562s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.000278472900390625s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-apo took 1.7811279296875s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 9.274482727050781e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.15363097190856934s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.022515296936035156s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0009617805480957031s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0002892017364501953s
Believability | Calculation of trust value for African Traditional Medicine took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-atmo took 1.7398042678833008s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.029273986816406e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.19104933738708496s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.654594421386719e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-ato took 1.7529566287994385s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 6.556510925292969e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.16839075088500977s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0012972354888916016s
Believability | Calculation of trust value for BioAssay Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-bao took 1.7641336917877197s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 8.177757263183594e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.1685178279876709s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020236968994140625s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003783702850341797s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 1.7351319789886475s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 8.034706115722656e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.16531944274902344s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.021586179733276367s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.00032448768615722656s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bcgo took 1.7930529117584229s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 6.270408630371094e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.1675703525543213s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014286041259765625s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bdo took 1.7718150615692139s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.161423921585083s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020860910415649414s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004889965057373047s
Believability | Calculation of trust value for Basic Formal Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bfo took 1.7337753772735596s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 3.8623809814453125e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.16467070579528809s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007355213165283203s
Believability | Calculation of trust value for Bleeding History Phenotype took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bho took 1.726499319076538s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.1521766185760498s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020231962203979492s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00043272972106933594s
Believability | Calculation of trust value for Bilateria anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bila took 1.7595560550689697s
Availability | SPARQL endpoint availability check for BIRNLex took 4.029273986816406e-05s
Availability | VoID file availability check for BIRNLex took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.16004133224487305s
Reputation | Calculation of the PageRank for BIRNLex took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014498233795166016s
Believability | Calculation of trust value for BIRNLex took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-birnlex took 1.8235535621643066s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 6.175041198730469e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.17197942733764648s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02217555046081543s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007300376892089844s
Believability | Calculation of trust value for Gene Regulation Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bootstrep took 1.800788402557373s
Availability | SPARQL endpoint availability check for BioPAX took 8.654594421386719e-05s
Availability | VoID file availability check for BioPAX took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for BioPAX took 0.15185952186584473s
Reputation | Calculation of the PageRank for BioPAX took 0.021188735961914062s
Interlinking | Calculation of Degree of Connection for BioPAX took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.417533874511719e-05s
Believability | Calculation of trust value for BioPAX took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-bp took 1.7493503093719482s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.15899920463562012s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020251989364624023s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003306865692138672s
Believability | Calculation of trust value for Biomedical Resource Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bro_x1 took 1.7767999172210693s
Availability | SPARQL endpoint availability check for Spatial Ontology took 8.20159912109375e-05s
Availability | VoID file availability check for Spatial Ontology took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.16078901290893555s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00022649765014648438s
Believability | Calculation of trust value for Spatial Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-bspo took 1.7668943405151367s
Availability | SPARQL endpoint availability check for BioTop took 4.673004150390625e-05s
Availability | VoID file availability check for BioTop took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for BioTop took 0.16478586196899414s
Reputation | Calculation of the PageRank for BioTop took 0.022061824798583984s
Interlinking | Calculation of Degree of Connection for BioTop took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006313323974609375s
Believability | Calculation of trust value for BioTop took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bt took 1.7363295555114746s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.082389831542969e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.162567138671875s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008673667907714844s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-bto took 1.8005354404449463s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 8.0108642578125e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.16263270378112793s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02017974853515625s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018305778503417969s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-canco took 1.7570090293884277s
Availability | SPARQL endpoint availability check for CAO took 9.131431579589844e-05s
Availability | VoID file availability check for CAO took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for CAO took 0.15326714515686035s
Reputation | Calculation of the PageRank for CAO took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for CAO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CAO took 0.0011744499206542969s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006058216094970703s
Believability | Calculation of trust value for CAO took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-cao took 1.759047269821167s
Availability | SPARQL endpoint availability check for CareLex took 8.20159912109375e-05s
Availability | VoID file availability check for CareLex took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for CareLex took 0.1579573154449463s
Reputation | Calculation of the PageRank for CareLex took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for CareLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.9591064453125e-05s
Believability | Calculation of trust value for CareLex took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-carelex took 1.7412302494049072s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 7.915496826171875e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.16045427322387695s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007555484771728516s
Believability | Calculation of trust value for Cell Cycle Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cco took 1.8030943870544434s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 8.106231689453125e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.14984583854675293s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020328044891357422s
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.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025534629821777344s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cdao took 1.766599178314209s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.1484832763671875e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.00034332275390625s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.15445733070373535s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.021022319793701172s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0010175704956054688s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008835792541503906s
Believability | Calculation of trust value for Chemical entities of biological interest took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-chebi took 1.7129430770874023s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 8.082389831542969e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.17248296737670898s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.021979331970214844s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00024509429931640625s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-chem2bio2owl took 1.7534737586975098s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.1602327823638916s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020230770111083984s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007724761962890625s
Believability | Calculation of trust value for Chemical Information Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-cheminf took 1.7421667575836182s
Availability | SPARQL endpoint availability check for Cell type took 8.440017700195312e-05s
Availability | VoID file availability check for Cell type took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Cell type took 0.15430235862731934s
Reputation | Calculation of the PageRank for Cell type took 0.022136211395263672s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003941059112548828s
Believability | Calculation of trust value for Cell type took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cl took 1.743908405303955s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.15250229835510254s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008151531219482422s
Believability | Calculation of trust value for Cell Line Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-clo took 1.7065002918243408s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 3.7670135498046875e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.1597914695739746s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02398514747619629s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001857280731201172s
Believability | Calculation of trust value for Clinical Measurement Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-cmo took 1.7322015762329102s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.1679229736328125s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002052783966064453s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-cno took 1.7688288688659668s
Availability | SPARQL endpoint availability check for Wheat trait took 4.029273986816406e-05s
Availability | VoID file availability check for Wheat trait took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.1622941493988037s
Reputation | Calculation of the PageRank for Wheat trait took 0.020245790481567383s
Interlinking | Calculation of Degree of Connection for Wheat trait took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 7.152557373046875e-05s
Believability | Calculation of trust value for Wheat trait took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-co_wheat took 1.752089262008667s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 8.153915405273438e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.15369415283203125s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00034308433532714844s
Believability | Calculation of trust value for Cognitive Atlas took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cogat took 1.7600212097167969s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 7.987022399902344e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.1566784381866455s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020241975784301758s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007507801055908203s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cogpo took 1.7405965328216553s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 9.226799011230469e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.15796136856079102s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.021338939666748047s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004191398620605469s
Believability | Calculation of trust value for Current Procedural Terminology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-cpt took 1.7885019779205322s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 5.245208740234375e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.16199779510498047s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.02107381820678711s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017955303192138672s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-csp took 1.7447869777679443s
Availability | SPARQL endpoint availability check for COSTART took 3.9577484130859375e-05s
Availability | VoID file availability check for COSTART took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for COSTART took 0.16217899322509766s
Reputation | Calculation of the PageRank for COSTART took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009744167327880859s
Believability | Calculation of trust value for COSTART took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cst took 1.7382464408874512s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.273124694824219e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.1638624668121338s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004942417144775391s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-ctcae took 1.7401306629180908s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 8.058547973632812e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.15512776374816895s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02302861213684082s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00046515464782714844s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-ctx took 1.7123517990112305s
Availability | SPARQL endpoint availability check for Dendritic cell took 9.202957153320312e-05s
Availability | VoID file availability check for Dendritic cell took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.1542065143585205s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0002906322479248047s
Believability | Calculation of trust value for Dendritic cell took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-dc_cl took 1.8424961566925049s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 3.9577484130859375e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.15834760665893555s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02029109001159668s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.630752563476562e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ddanat took 1.7429938316345215s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 6.461143493652344e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.16754817962646484s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02030158042907715s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009274482727050781s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-ddi took 1.740299940109253s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 0.00010442733764648438s
Availability | VoID file availability check for Diagnostic Ontology took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.14930272102355957s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.106231689453125e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-diagnosticont took 1.7109124660491943s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 0.00013947486877441406s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.00021219253540039062s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.15258193016052246s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020281076431274414s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.000164031982421875s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-dikb-evidence took 1.7501556873321533s
Availability | SPARQL endpoint availability check for Human disease ontology took 8.20159912109375e-05s
Availability | VoID file availability check for Human disease ontology took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2075352668762207s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006182193756103516s
Believability | Calculation of trust value for Human disease ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-doid took 1.8200764656066895s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 3.886222839355469e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.14953231811523438s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007841587066650391s
Believability | Calculation of trust value for Electrocardiography Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ecg took 1.7263438701629639s
Availability | SPARQL endpoint availability check for Evidence codes took 8.225440979003906e-05s
Availability | VoID file availability check for Evidence codes took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.16440057754516602s
Reputation | Calculation of the PageRank for Evidence codes took 0.021365880966186523s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0010044574737548828s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.814697265625e-05s
Believability | Calculation of trust value for Evidence codes took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-eco took 1.7544147968292236s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.982948303222656e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.15450596809387207s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.021928071975708008s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0030596256256103516s
Believability | Calculation of trust value for Experimental Factor Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-efo took 1.7322797775268555s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 3.981590270996094e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.16233062744140625s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02240300178527832s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.00115966796875s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ehda took 1.733750343322754s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 3.933906555175781e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.15199756622314453s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007159709930419922s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-ehdaa took 1.7218852043151855s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 7.843971252441406e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.15041160583496094s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 3.3855438232421875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005204677581787109s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 1.7218122482299805s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 8.058547973632812e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.16329550743103027s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.9802322387695312e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 7.62939453125e-06s
INFO | --- Analysis for bioportal-emap took 1.772711992263794s
Availability | SPARQL endpoint availability check for Environment Ontology took 0.00011491775512695312s
Availability | VoID file availability check for Environment Ontology took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.16600441932678223s
Reputation | Calculation of the PageRank for Environment Ontology took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00039196014404296875s
Believability | Calculation of trust value for Environment Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-envo took 1.779782772064209s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 8.320808410644531e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.16017746925354004s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.022242069244384766s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00028824806213378906s
Believability | Calculation of trust value for Plant environmental conditions took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-eo took 1.809516191482544s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 3.910064697265625e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.16327691078186035s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.022372007369995117s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0011835098266601562s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-ep took 1.7641847133636475s
Availability | SPARQL endpoint availability check for Epilepsy took 4.0531158447265625e-05s
Availability | VoID file availability check for Epilepsy took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.19777131080627441s
Reputation | Calculation of the PageRank for Epilepsy took 0.022697925567626953s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00014448165893554688s
Believability | Calculation of trust value for Epilepsy took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-epileponto took 1.7825398445129395s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 8.392333984375e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.1629331111907959s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011477470397949219s
Believability | Calculation of trust value for eagle-i research resource ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-ero took 1.8279516696929932s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 8.225440979003906e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.1534583568572998s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011277198791503906s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-ev took 1.7516484260559082s
Availability | SPARQL endpoint availability check for ExO took 8.177757263183594e-05s
Availability | VoID file availability check for ExO took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for ExO took 0.15719008445739746s
Reputation | Calculation of the PageRank for ExO took 0.021407127380371094s
Interlinking | Calculation of Degree of Connection for ExO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0002532005310058594s
Believability | Calculation of trust value for ExO took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-exo took 1.7734861373901367s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.100799560546875e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.16541433334350586s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011992454528808594s
Believability | Calculation of trust value for Fungal gross anatomy took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-fao took 1.7706878185272217s
Availability | SPARQL endpoint availability check for Biological imaging methods took 0.00010442733764648438s
Availability | VoID file availability check for Biological imaging methods took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.1524491310119629s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00020313262939453125s
Believability | Calculation of trust value for Biological imaging methods took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-fbbi took 1.7224969863891602s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 8.0108642578125e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.15805983543395996s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006420612335205078s
Believability | Calculation of trust value for Drosophila gross anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-fbbt took 1.7278826236724854s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.124641418457031e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.15655112266540527s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004222393035888672s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-fbcv took 1.7450780868530273s
Availability | SPARQL endpoint availability check for Drosophila development took 8.320808410644531e-05s
Availability | VoID file availability check for Drosophila development took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.1646733283996582s
Reputation | Calculation of the PageRank for Drosophila development took 0.022136211395263672s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0009055137634277344s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 5.3882598876953125e-05s
Believability | Calculation of trust value for Drosophila development took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-fbdv took 1.764190673828125s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.124641418457031e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.1627800464630127s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.00036787986755371094s
Believability | Calculation of trust value for Fly taxonomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-fbsp took 1.7252883911132812s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.0531158447265625e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.15738296508789062s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020180225372314453s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002491474151611328s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 1.6900839805603027s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.14876461029052734s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020195722579956055s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00040149688720703125s
Believability | Calculation of trust value for Family Health History Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-fhho took 1.662442684173584s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Influenza Ontology took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.15411806106567383s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02010965347290039s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010242462158203125s
Believability | Calculation of trust value for Influenza Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-flu took 1.6742360591888428s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 3.9577484130859375e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.1542201042175293s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020121335983276367s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 5.91278076171875e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-fma took 1.677534818649292s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.1552741527557373s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001285076141357422s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-fypo took 1.7093722820281982s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 5.507469177246094e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.14518427848815918s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0009708404541015625s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 0.00010561943054199219s
Believability | Calculation of trust value for GeoSpecies Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-geospecies took 1.6935160160064697s
Availability | SPARQL endpoint availability check for General Formal Ontology took 5.888938903808594e-05s
Availability | VoID file availability check for General Formal Ontology took 0.00031876564025878906s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.16301202774047852s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001590251922607422s
Believability | Calculation of trust value for General Formal Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gfo took 1.6885120868682861s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.601478576660156e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.1455395221710205s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020175933837890625s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.000629425048828125s
Believability | Calculation of trust value for General Formal Ontology: Biology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-gfo-bio took 1.6703169345855713s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.1484832763671875e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.14724993705749512s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020091772079467773s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008635520935058594s
Believability | Calculation of trust value for Gene Ontology Extension took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-go_x1 took 1.6727757453918457s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Gene Ontology took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.15433216094970703s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008559226989746094s
Believability | Calculation of trust value for Gene Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-go_x2 took 1.7269346714019775s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.1484832763671875e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.15535616874694824s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 2.765655517578125e-05s
Believability | Calculation of trust value for Cereal Plant Development took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-gro took 1.713674783706665s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 3.933906555175781e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.20986485481262207s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020182132720947266s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004508495330810547s
Believability | Calculation of trust value for Cereal plant gross anatomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-gro_x1 took 1.790196180343628s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.1472163200378418s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.0201723575592041s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0008797645568847656s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0008137226104736328s
Believability | Calculation of trust value for Gene Regulation Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-gro_x2 took 1.6853349208831787s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.1483016014099121s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005733966827392578s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-hao took 1.74873948097229s
Availability | SPARQL endpoint availability check for HCPCS took 3.981590270996094e-05s
Availability | VoID file availability check for HCPCS took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for HCPCS took 0.15982532501220703s
Reputation | Calculation of the PageRank for HCPCS took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for HCPCS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00021982192993164062s
Believability | Calculation of trust value for HCPCS took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-hcpcs took 1.7070679664611816s
Availability | SPARQL endpoint availability check for Health Level Seven took 7.2479248046875e-05s
Availability | VoID file availability check for Health Level Seven took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.15110540390014648s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020130395889282227s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012729167938232422s
Believability | Calculation of trust value for Health Level Seven took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-hl7 took 1.7423672676086426s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 8.106231689453125e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.16690444946289062s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.021017789840698242s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003483295440673828s
Believability | Calculation of trust value for HEALTH_INDICATORS took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-hlth_indics took 1.7160718441009521s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 8.296966552734375e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.16442489624023438s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.02203536033630371s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 2.7418136596679688e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-hom took 1.7402384281158447s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 0.00011515617370605469s
Availability | VoID file availability check for HOM-HARVARD took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.16077494621276855s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.4332275390625e-05s
Believability | Calculation of trust value for HOM-HARVARD took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-hom_harvard took 1.7454330921173096s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.16835284233093262s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020223379135131836s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006289482116699219s
Believability | Calculation of trust value for Human Phenotype Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-hp_x1 took 1.8021745681762695s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.1668388843536377s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.0205078125s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010142326354980469s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-hpio took 1.7567553520202637s
Availability | SPARQL endpoint availability check for HUGO took 8.392333984375e-05s
Availability | VoID file availability check for HUGO took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for HUGO took 0.1696782112121582s
Reputation | Calculation of the PageRank for HUGO took 0.022878170013427734s
Interlinking | Calculation of Degree of Connection for HUGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.249282836914062e-05s
Believability | Calculation of trust value for HUGO took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-hugo took 1.8174419403076172s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.15146374702453613s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006382465362548828s
Believability | Calculation of trust value for Information Artifact Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-iao took 1.7699611186981201s
Availability | SPARQL endpoint availability check for ICD10 took 8.225440979003906e-05s
Availability | VoID file availability check for ICD10 took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for ICD10 took 0.1647787094116211s
Reputation | Calculation of the PageRank for ICD10 took 0.021117210388183594s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008223056793212891s
Believability | Calculation of trust value for ICD10 took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-icd10 took 1.8025922775268555s
Availability | SPARQL endpoint availability check for ICD10CM took 4.1961669921875e-05s
Availability | VoID file availability check for ICD10CM took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.15610146522521973s
Reputation | Calculation of the PageRank for ICD10CM took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006055831909179688s
Believability | Calculation of trust value for ICD10CM took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-icd10cm took 1.7732429504394531s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 8.249282836914062e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.16190695762634277s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015234947204589844s
Believability | Calculation of trust value for ICD-10-PCS took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-icd10pcs took 1.8016276359558105s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.076957702636719e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.17120647430419922s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.021475791931152344s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006351470947265625s
Believability | Calculation of trust value for International Classification of Diseases took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-icd9cm took 1.829638957977295s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 8.940696716308594e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.15270662307739258s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.02023625373840332s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.00046253204345703125s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-icf_x1 took 1.7758066654205322s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 0.00010538101196289062s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.15851569175720215s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02128434181213379s
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.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012278556823730469s
Believability | Calculation of trust value for International Classification for Nursing Practice took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-icnp took 1.730778455734253s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 8.678436279296875e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.15757513046264648s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.0212247371673584s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00043582916259765625s
Believability | Calculation of trust value for International Classification of Primary Care took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-icpc took 1.7581725120544434s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 6.67572021484375e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.16319537162780762s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008530616760253906s
Believability | Calculation of trust value for ICPC-2 PLUS took 7.62939453125e-06s
INFO | --- Analysis for bioportal-icpc2p took 1.689650058746338s
Availability | SPARQL endpoint availability check for ICPS Network took 7.319450378417969e-05s
Availability | VoID file availability check for ICPS Network took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.15955352783203125s
Reputation | Calculation of the PageRank for ICPS Network took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00021767616271972656s
Believability | Calculation of trust value for ICPS Network took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icps took 1.7096621990203857s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.00021338462829589844s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.1495494842529297s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020286083221435547s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008592605590820312s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ido took 1.6791698932647705s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.16341018676757812s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02252960205078125s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011103153228759766s
Believability | Calculation of trust value for Brucellosis Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-idobru took 1.756620168685913s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.1692812442779541s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.001264810562133789s
Believability | Calculation of trust value for Malaria Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-idomal took 1.7426884174346924s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 3.8623809814453125e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.152740478515625s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020123720169067383s
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.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003020763397216797s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-iev took 1.7048656940460205s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 8.678436279296875e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.16049671173095703s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0009622573852539062s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00018477439880371094s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-imgt took 1.7296407222747803s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 8.177757263183594e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.16109132766723633s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020241260528564453s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005145072937011719s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-imr took 1.746584415435791s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.15842175483703613s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02016305923461914s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007541179656982422s
Believability | Calculation of trust value for Interaction Network Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ino took 1.7387385368347168s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 3.9577484130859375e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.15480899810791016s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.021066665649414062s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 2.86102294921875e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-invertebrata took 1.6930031776428223s
Availability | SPARQL endpoint availability check for IxnO took 8.273124694824219e-05s
Availability | VoID file availability check for IxnO took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for IxnO took 0.15183115005493164s
Reputation | Calculation of the PageRank for IxnO took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IxnO took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018739700317382812s
Believability | Calculation of trust value for IxnO took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ixno took 1.74094820022583s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.00543212890625e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0002186298370361328s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.15618658065795898s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.02171945571899414s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00037288665771484375s
Believability | Calculation of trust value for SysMO-JERM took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-jerm took 1.7207331657409668s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 0.00011277198791503906s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.15933823585510254s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.021474599838256836s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-kisao took 1.7514920234680176s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.0531158447265625e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0002105236053466797s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.1514875888824463s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0001952648162841797s
Believability | Calculation of trust value for Loggerhead nesting took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lhn took 1.7208831310272217s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.1534428596496582s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0002028942108154297s
Believability | Calculation of trust value for Lipid Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-lipro took 1.7578308582305908s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 8.368492126464844e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.15898799896240234s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.02079606056213379s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018455982208251953s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-lnc took 1.7462713718414307s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 8.20159912109375e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.1591804027557373s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006673336029052734s
Believability | Calculation of trust value for Mouse adult gross anatomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ma took 1.776338815689087s
Availability | SPARQL endpoint availability check for Multiple alignment took 8.630752563476562e-05s
Availability | VoID file availability check for Multiple alignment took 0.00048828125s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.15234851837158203s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02227473258972168s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0011453628540039062s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00026679039001464844s
Believability | Calculation of trust value for Multiple alignment took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-mao took 1.765284538269043s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.029273986816406e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.1531083583831787s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.02146768569946289s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006837844848632812s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mat took 1.8426778316497803s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.4345855712890625e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.00021386146545410156s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.15487194061279297s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.02017354965209961s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004076957702636719s
Believability | Calculation of trust value for Breast tissue cell lines took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-mcbcc took 1.7324581146240234s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Cell line ontology took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.1446521282196045s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02011895179748535s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007481575012207031s
Believability | Calculation of trust value for Cell line ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mccl took 1.6850676536560059s
Availability | SPARQL endpoint availability check for Cell line ontology took 8.082389831542969e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.1551835536956787s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0013930797576904297s
Believability | Calculation of trust value for Cell line ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mccl_x1 took 1.711721658706665s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 3.933906555175781e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.16652679443359375s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02025747299194336s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00023221969604492188s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mcv took 1.7494843006134033s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 8.487701416015625e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.15974211692810059s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017118453979492188s
Believability | Calculation of trust value for Master Drug Data Base took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-mddb took 1.7251324653625488s
Availability | SPARQL endpoint availability check for MedDRA took 8.797645568847656e-05s
Availability | VoID file availability check for MedDRA took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for MedDRA took 0.15525364875793457s
Reputation | Calculation of the PageRank for MedDRA took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for MedDRA took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011157989501953125s
Believability | Calculation of trust value for MedDRA took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-mdr took 1.7289330959320068s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.1484832763671875e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.15399861335754395s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02013564109802246s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008881092071533203s
Believability | Calculation of trust value for MedlinePlus Health Topics took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-medlineplus took 1.7571241855621338s
Availability | SPARQL endpoint availability check for MeGO took 4.124641418457031e-05s
Availability | VoID file availability check for MeGO took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for MeGO took 0.15279793739318848s
Reputation | Calculation of the PageRank for MeGO took 0.02207326889038086s
Interlinking | Calculation of Degree of Connection for MeGO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014543533325195312s
Believability | Calculation of trust value for MeGO took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mego took 1.9703800678253174s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.100799560546875e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.15254807472229004s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.001806497573852539s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mesh-owl took 1.700657606124878s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.1565864086151123s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006170272827148438s
Believability | Calculation of trust value for Mental Functioning Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-mf took 1.7272813320159912s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 8.249282836914062e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.1623837947845459s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.000583648681640625s
Believability | Calculation of trust value for Medaka fish anatomy and development took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-mfo took 1.7349631786346436s
Availability | SPARQL endpoint availability check for Emotion Ontology took 9.5367431640625e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.1542356014251709s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007388591766357422s
Believability | Calculation of trust value for Emotion Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mfoem took 1.7726306915283203s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.982948303222656e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.1520371437072754s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02029252052307129s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00011181831359863281s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-mhc took 1.7246837615966797s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.076957702636719e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.15220904350280762s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006573200225830078s
Believability | Calculation of trust value for Protein-protein interaction took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-mi took 1.7901332378387451s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.267692565917969e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.16056108474731445s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.023004531860351562s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007205009460449219s
Believability | Calculation of trust value for Mosquito insecticide resistance took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-miro took 1.7310304641723633s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.15284109115600586s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013685226440429688s
Believability | Calculation of trust value for Measurement Method Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-mmo took 1.7201805114746094s
Availability | SPARQL endpoint availability check for MGED Ontology took 3.814697265625e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.15504789352416992s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020193815231323242s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0004048347473144531s
Believability | Calculation of trust value for MGED Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mo took 1.7390570640563965s
Availability | SPARQL endpoint availability check for Protein modification took 6.580352783203125e-05s
Availability | VoID file availability check for Protein modification took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Protein modification took 0.1629650592803955s
Reputation | Calculation of the PageRank for Protein modification took 0.020215272903442383s
Interlinking | Calculation of Degree of Connection for Protein modification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002186298370361328s
Believability | Calculation of trust value for Protein modification took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mod took 1.7483909130096436s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.076957702636719e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.16313672065734863s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.022716045379638672s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006518363952636719s
Believability | Calculation of trust value for Mammalian phenotype took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mp took 1.7416183948516846s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.100799560546875e-05s
Availability | VoID file availability check for Mouse pathology took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.16857481002807617s
Reputation | Calculation of the PageRank for Mouse pathology took 0.02281641960144043s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00047850608825683594s
Believability | Calculation of trust value for Mouse pathology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mpath took 1.7257943153381348s
Availability | SPARQL endpoint availability check for Mass spectrometry took 8.320808410644531e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.1582930088043213s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.02024674415588379s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00034999847412109375s
Believability | Calculation of trust value for Mass spectrometry took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-ms took 1.7061798572540283s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 3.886222839355469e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.15455293655395508s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018677711486816406s
Believability | Calculation of trust value for Medical Subject Headings took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-msh took 1.6817474365234375s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.0531158447265625e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.16603469848632812s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020265817642211914s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001678466796875s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mthch took 1.690887451171875s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.15918731689453125s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020155906677246094s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007801055908203125s
Believability | Calculation of trust value for Natural Products Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-natpro took 1.723557472229004s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 3.910064697265625e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.1665351390838623s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.021658658981323242s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0007903575897216797s
Believability | Calculation of trust value for NCBI organismal classification took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-ncbitaxon took 1.7410216331481934s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 6.4849853515625e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.162703275680542s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0020246505737304688s
Believability | Calculation of trust value for NCI Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-ncit took 1.7309386730194092s
Availability | SPARQL endpoint availability check for National Drug Data File took 8.344650268554688e-05s
Availability | VoID file availability check for National Drug Data File took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.16033244132995605s
Reputation | Calculation of the PageRank for National Drug Data File took 0.021205663681030273s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006291866302490234s
Believability | Calculation of trust value for National Drug Data File took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-nddf took 1.7143561840057373s
Availability | SPARQL endpoint availability check for National Drug File took 8.726119995117188e-05s
Availability | VoID file availability check for National Drug File took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for National Drug File took 0.17952394485473633s
Reputation | Calculation of the PageRank for National Drug File took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for National Drug File took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012106895446777344s
Believability | Calculation of trust value for National Drug File took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-ndfrt took 1.76641845703125s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.100799560546875e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.15375399589538574s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.021404027938842773s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0008068084716796875s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0012488365173339844s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-nemo_x1 took 1.7444922924041748s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.15449810028076172s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020233154296875s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006518363952636719s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-neomark took 1.697014570236206s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.15088725090026855s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02098536491394043s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012373924255371094s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-neomarkontology took 1.7065191268920898s
Availability | SPARQL endpoint availability check for NIFSTD took 4.172325134277344e-05s
Availability | VoID file availability check for NIFSTD took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.14836406707763672s
Reputation | Calculation of the PageRank for NIFSTD took 0.02133631706237793s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.002229452133178711s
Believability | Calculation of trust value for NIFSTD took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-nif took 1.7381410598754883s
Availability | SPARQL endpoint availability check for NIF Cell took 8.559226989746094e-05s
Availability | VoID file availability check for NIF Cell took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.1649010181427002s
Reputation | Calculation of the PageRank for NIF Cell took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013294219970703125s
Believability | Calculation of trust value for NIF Cell took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-nif_cell took 1.749842882156372s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.7206878662109375e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.16336393356323242s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014781951904296875s
Believability | Calculation of trust value for NIF Dysfunction took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-nif_dysfunction took 1.7509331703186035s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 9.608268737792969e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.15742897987365723s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02183985710144043s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005464553833007812s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-nigo took 1.7425472736358643s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 8.177757263183594e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.15445828437805176s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005488395690917969s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-nmr took 1.7390687465667725s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.15343070030212402s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020267724990844727s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010704994201660156s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-nonrctontology took 1.7323436737060547s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.15485477447509766s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012078285217285156s
Believability | Calculation of trust value for NanoParticle Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-npo took 1.769554615020752s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.9591064453125e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.15339159965515137s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007307529449462891s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-oae took 1.7703890800476074s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 8.630752563476562e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0010554790496826172s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.161454439163208s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014476776123046875s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-obi took 1.7219011783599854s
Availability | SPARQL endpoint availability check for OBOE took 8.702278137207031e-05s
Availability | VoID file availability check for OBOE took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for OBOE took 0.1515352725982666s
Reputation | Calculation of the PageRank for OBOE took 0.021963119506835938s
Interlinking | Calculation of Degree of Connection for OBOE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010800361633300781s
Believability | Calculation of trust value for OBOE took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-oboe took 1.7327885627746582s
Availability | SPARQL endpoint availability check for OBOE SBC took 8.130073547363281e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.1472764015197754s
Reputation | Calculation of the PageRank for OBOE SBC took 0.021080732345581055s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007686614990234375s
Believability | Calculation of trust value for OBOE SBC took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-oboe-sbc took 1.7576348781585693s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 8.153915405273438e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.153123140335083s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005850791931152344s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ocre took 1.7344324588775635s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 8.368492126464844e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.1554698944091797s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02154850959777832s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008423328399658203s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-odgi took 1.7423045635223389s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 6.556510925292969e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.16231942176818848s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008585453033447266s
Believability | Calculation of trust value for Ontology for Genetic Interval took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-ogi took 1.7322711944580078s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.15407299995422363s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.022134780883789062s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00029397010803222656s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-ogmd took 1.7311389446258545s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.16488099098205566s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02710437774658203s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006730556488037109s
Believability | Calculation of trust value for Ontology for General Medical Science took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-ogms took 1.7545504570007324s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 8.320808410644531e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.15285468101501465s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011522769927978516s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-omim took 1.7274858951568604s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 8.440017700195312e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.15932178497314453s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020829439163208008s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003724098205566406s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-omit took 1.7260572910308838s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 8.893013000488281e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.15144014358520508s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.021361589431762695s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006251335144042969s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-omrse took 1.756779670715332s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.029273986816406e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.1618337631225586s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.022580623626708984s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.000759124755859375s
Believability | Calculation of trust value for Ontology of Data Mining took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ontodm took 1.7656605243682861s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 8.463859558105469e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.15935039520263672s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020418167114257812s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00023698806762695312s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ontodt took 1.7325279712677002s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 5.841255187988281e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.15346479415893555s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.02202296257019043s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0009891986846923828s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0007622241973876953s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-ontoorpha took 1.7065699100494385s
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.0004444122314453125s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.17661237716674805s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009126663208007812s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-opl took 1.8011887073516846s
Availability | SPARQL endpoint availability check for Phenotypic quality took 8.153915405273438e-05s
Availability | VoID file availability check for Phenotypic quality took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.1556849479675293s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.021408796310424805s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.00089263916015625s
Believability | Calculation of trust value for Phenotypic quality took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-pato took 1.7704334259033203s
Availability | SPARQL endpoint availability check for Physician Data Query took 8.273124694824219e-05s
Availability | VoID file availability check for Physician Data Query took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.15217351913452148s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008280277252197266s
Believability | Calculation of trust value for Physician Data Query took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-pdq took 1.7200067043304443s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 8.487701416015625e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.15565776824951172s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020597219467163086s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007958412170410156s
Believability | Calculation of trust value for Pediatric Terminology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-pedterm took 1.7161223888397217s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.16157889366149902s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019621849060058594s
Believability | Calculation of trust value for Parasite Experiment Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-peo took 1.7906665802001953s
Availability | SPARQL endpoint availability check for PHARE took 8.320808410644531e-05s
Availability | VoID file availability check for PHARE took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for PHARE took 0.1603834629058838s
Reputation | Calculation of the PageRank for PHARE took 0.020751953125s
Interlinking | Calculation of Degree of Connection for PHARE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006241798400878906s
Believability | Calculation of trust value for PHARE took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-phare took 1.7214877605438232s
Availability | SPARQL endpoint availability check for PKO_Re took 4.267692565917969e-05s
Availability | VoID file availability check for PKO_Re took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.16036319732666016s
Reputation | Calculation of the PageRank for PKO_Re took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00016832351684570312s
Believability | Calculation of trust value for PKO_Re took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-pko took 1.7583539485931396s
Availability | SPARQL endpoint availability check for PMA 2010 took 8.034706115722656e-05s
Availability | VoID file availability check for PMA 2010 took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.1596357822418213s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020462989807128906s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009248256683349609s
Believability | Calculation of trust value for PMA 2010 took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-pma took 1.739389419555664s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 6.651878356933594e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.1499156951904297s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00017499923706054688s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-pmr took 1.781966209411621s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.225440979003906e-05s
Availability | VoID file availability check for Plant Anatomy took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.1510460376739502s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0009925365447998047s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0004596710205078125s
Believability | Calculation of trust value for Plant Anatomy took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-po took 1.7326161861419678s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.177757263183594e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.15639400482177734s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.021654605865478516s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.699562072753906e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-po_x1 took 1.7715001106262207s
Availability | SPARQL endpoint availability check for Plant Ontology took 8.106231689453125e-05s
Availability | VoID file availability check for Plant Ontology took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.1608753204345703s
Reputation | Calculation of the PageRank for Plant Ontology took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004343986511230469s
Believability | Calculation of trust value for Plant Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-po_x2 took 1.7535607814788818s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 8.273124694824219e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.15170860290527344s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.022199153900146484s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006704330444335938s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-pr took 1.7461726665496826s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.57763671875e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.1535499095916748s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002541542053222656s
Believability | Calculation of trust value for Proteomics data and process provenance took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-propreo took 1.776421308517456s
Availability | SPARQL endpoint availability check for Pathway ontology took 0.00010466575622558594s
Availability | VoID file availability check for Pathway ontology took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.15947198867797852s
Reputation | Calculation of the PageRank for Pathway ontology took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012111663818359375s
Believability | Calculation of trust value for Pathway ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pw took 1.7809419631958008s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.15701079368591309s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.02125835418701172s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-qibo took 1.7628166675567627s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.172325134277344e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.15514636039733887s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017976760864257812s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-rcd took 1.7191839218139648s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 6.604194641113281e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.16018319129943848s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.0001266002655029297s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-rctontology took 1.7996587753295898s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 8.392333984375e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.1569373607635498s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.021131277084350586s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.679794311523438e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-repo took 1.7404427528381348s
Availability | SPARQL endpoint availability check for Physico-chemical process took 8.249282836914062e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.16020941734313965s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.02276611328125s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0001888275146484375s
Believability | Calculation of trust value for Physico-chemical process took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rex took 1.7408537864685059s
Availability | SPARQL endpoint availability check for RadLex took 3.886222839355469e-05s
Availability | VoID file availability check for RadLex took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for RadLex took 0.15282559394836426s
Reputation | Calculation of the PageRank for RadLex took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for RadLex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015079975128173828s
Believability | Calculation of trust value for RadLex took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-rid took 1.6814439296722412s
Availability | SPARQL endpoint availability check for RNA ontology took 4.220008850097656e-05s
Availability | VoID file availability check for RNA ontology took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.16347551345825195s
Reputation | Calculation of the PageRank for RNA ontology took 0.021259546279907227s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005502700805664062s
Believability | Calculation of trust value for RNA ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-rnao took 1.7629637718200684s
Availability | SPARQL endpoint availability check for Role Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Role Ontology took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.15762066841125488s
Reputation | Calculation of the PageRank for Role Ontology took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00020647048950195312s
Believability | Calculation of trust value for Role Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-roleo took 1.7579388618469238s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 6.556510925292969e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.1630997657775879s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001747608184814453s
Believability | Calculation of trust value for Rat Strain Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-rs took 1.7804067134857178s
Availability | SPARQL endpoint availability check for RxNORM took 4.291534423828125e-05s
Availability | VoID file availability check for RxNORM took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for RxNORM took 0.15872836112976074s
Reputation | Calculation of the PageRank for RxNORM took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0008475780487060547s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0007097721099853516s
Believability | Calculation of trust value for RxNORM took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-rxnorm took 1.7500388622283936s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 8.225440979003906e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.15369820594787598s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.022379398345947266s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010366439819335938s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-sao took 1.7517266273498535s
Availability | SPARQL endpoint availability check for Systems Biology took 0.00012826919555664062s
Availability | VoID file availability check for Systems Biology took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.15187788009643555s
Reputation | Calculation of the PageRank for Systems Biology took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00044727325439453125s
Believability | Calculation of trust value for Systems Biology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-sbo took 1.7433278560638428s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.16245293617248535s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010228157043457031s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-sbro took 1.7521157264709473s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0002193450927734375s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.16668128967285156s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013325214385986328s
Believability | Calculation of trust value for Sleep Domain Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-sdo took 1.7314581871032715s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 8.177757263183594e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.15590333938598633s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003371238708496094s
Believability | Calculation of trust value for Sample processing and separation techniques took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-sep took 1.7597005367279053s
Availability | SPARQL endpoint availability check for Student Health Record took 8.177757263183594e-05s
Availability | VoID file availability check for Student Health Record took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.16011261940002441s
Reputation | Calculation of the PageRank for Student Health Record took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.00047516822814941406s
Believability | Calculation of trust value for Student Health Record took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-shr took 1.7443110942840576s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 8.296966552734375e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.15141081809997559s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.02110886573791504s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012035369873046875s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-sio took 1.7424571514129639s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 8.106231689453125e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.15819597244262695s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.022729873657226562s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.000202178955078125s
Believability | Calculation of trust value for Situation-Based Access Control took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-sitbac took 1.745720386505127s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.100799560546875e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.1667628288269043s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019278526306152344s
Believability | Calculation of trust value for SNOMED Clinical Terms took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-snomedct took 1.7397363185882568s
Availability | SPARQL endpoint availability check for SNP-Ontology took 8.20159912109375e-05s
Availability | VoID file availability check for SNP-Ontology took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.15740656852722168s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.00066375732421875s
Believability | Calculation of trust value for SNP-Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-snpo took 1.7685396671295166s
Availability | SPARQL endpoint availability check for Sequence types and features took 8.273124694824219e-05s
Availability | VoID file availability check for Sequence types and features took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.15794062614440918s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020673513412475586s
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.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005717277526855469s
Believability | Calculation of trust value for Sequence types and features took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-so_x1 took 1.7798683643341064s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 0.00010037422180175781s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.15419626235961914s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015633106231689453s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-sopharm took 1.7790544033050537s
Availability | SPARQL endpoint availability check for SoyOntology took 4.220008850097656e-05s
Availability | VoID file availability check for SoyOntology took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.14766788482666016s
Reputation | Calculation of the PageRank for SoyOntology took 0.022394895553588867s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001304149627685547s
Believability | Calculation of trust value for SoyOntology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-soy took 1.7579131126403809s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Spider Ontology took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.15073251724243164s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003161430358886719s
Believability | Calculation of trust value for Spider Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-spd took 1.7904331684112549s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.1621837615966797s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0002684593200683594s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-spto took 1.7556424140930176s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 8.058547973632812e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.1574246883392334s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004336833953857422s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-sso took 1.7737791538238525s
Availability | SPARQL endpoint availability check for Software Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Software Ontology took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.16893887519836426s
Reputation | Calculation of the PageRank for Software Ontology took 0.021689891815185547s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00042629241943359375s
Believability | Calculation of trust value for Software Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-swo took 1.7527194023132324s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.0531158447265625e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.15210628509521484s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00024628639221191406s
Believability | Calculation of trust value for Tick gross anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tads took 1.7365541458129883s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.225440979003906e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.14526748657226562s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0009059906005859375s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-tao took 1.6966631412506104s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.00543212890625e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.15512442588806152s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.393692016601562e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-taxrank took 1.735323190689087s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 8.440017700195312e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.16585373878479004s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.023071765899658203s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.462501525878906e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-teddy took 1.7571399211883545s
Availability | SPARQL endpoint availability check for Time Event Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.15756607055664062s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008156299591064453s
Believability | Calculation of trust value for Time Event Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-teo took 1.7245409488677979s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.106231689453125e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.1590421199798584s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003859996795654297s
Believability | Calculation of trust value for Mosquito gross anatomy took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-tgma took 1.7245018482208252s
Availability | SPARQL endpoint availability check for thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for thesaurus took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for thesaurus took 0.15517640113830566s
Reputation | Calculation of the PageRank for thesaurus took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.580352783203125e-05s
Believability | Calculation of trust value for thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-thesaurus took 1.787135124206543s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.076957702636719e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.15355134010314941s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02067279815673828s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00034236907958984375s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 1.7388420104980469s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.15625762939453125s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008220672607421875s
Believability | Calculation of trust value for Translational Medicine Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-tmo took 1.7190113067626953s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.15493202209472656s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015211105346679688s
Believability | Calculation of trust value for Plant Trait Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-to took 1.720285177230835s
Availability | SPARQL endpoint availability check for TOK_Ontology took 8.153915405273438e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.1528918743133545s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001761913299560547s
Believability | Calculation of trust value for TOK_Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-tok took 1.7307994365692139s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 8.082389831542969e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.15090465545654297s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019741058349609375s
Believability | Calculation of trust value for Teleost taxonomy took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-tto took 1.7465143203735352s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 8.344650268554688e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.15891718864440918s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010564327239990234s
Believability | Calculation of trust value for Uber anatomy ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-uberon took 1.73982572555542s
Availability | SPARQL endpoint availability check for Units Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for Units Ontology took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.15970587730407715s
Reputation | Calculation of the PageRank for Units Ontology took 0.021273136138916016s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00021958351135253906s
Believability | Calculation of trust value for Units Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-unitsontology took 1.7801365852355957s
Availability | SPARQL endpoint availability check for Units of measurement took 4.124641418457031e-05s
Availability | VoID file availability check for Units of measurement took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.15092778205871582s
Reputation | Calculation of the PageRank for Units of measurement took 0.03117203712463379s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0014159679412841797s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0004398822784423828s
Believability | Calculation of trust value for Units of measurement took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-uo took 1.7502710819244385s
Availability | SPARQL endpoint availability check for VANDF took 8.320808410644531e-05s
Availability | VoID file availability check for VANDF took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for VANDF took 0.15282464027404785s
Reputation | Calculation of the PageRank for VANDF took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for VANDF took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for VANDF took 0.001027822494506836s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007879734039306641s
Believability | Calculation of trust value for VANDF took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-vandf took 1.8024744987487793s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.16102170944213867s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02211737632751465s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00042510032653808594s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-vao took 1.746243953704834s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 3.8623809814453125e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.16607999801635742s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.021470069885253906s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006198883056640625s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-vhog took 1.7634520530700684s
Availability | SPARQL endpoint availability check for VIVO took 7.82012939453125e-05s
Availability | VoID file availability check for VIVO took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for VIVO took 0.16159296035766602s
Reputation | Calculation of the PageRank for VIVO took 0.02021312713623047s
Interlinking | Calculation of Degree of Connection for VIVO took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003478527069091797s
Believability | Calculation of trust value for VIVO took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-vivo took 1.7308664321899414s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.15225863456726074s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.021114826202392578s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012285709381103516s
Believability | Calculation of trust value for Vaccine Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-vo took 1.7340633869171143s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.14708161354064941s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.021265268325805664s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020956993103027344s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-vt took 1.7416894435882568s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.15874934196472168s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.02210259437561035s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.000507354736328125s
Believability | Calculation of trust value for C. elegans gross anatomy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-wbbt took 1.7739241123199463s
Availability | SPARQL endpoint availability check for C. elegans development took 7.987022399902344e-05s
Availability | VoID file availability check for C. elegans development took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.15358757972717285s
Reputation | Calculation of the PageRank for C. elegans development took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 5.650520324707031e-05s
Believability | Calculation of trust value for C. elegans development took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-wbls took 1.8563003540039062s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 7.510185241699219e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.16413354873657227s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02246403694152832s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.893013000488281e-05s
Believability | Calculation of trust value for C. elegans phenotype took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-wbphenotype took 1.745534896850586s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 8.416175842285156e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.16753149032592773s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.022351741790771484s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005817413330078125s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-who took 1.7291693687438965s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 8.273124694824219e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.1652541160583496s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020453453063964844s
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.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006654262542724609s
Believability | Calculation of trust value for Xenopus anatomy and development took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-xao took 1.7325108051300049s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.16540908813476562s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002334117889404297s
Believability | Calculation of trust value for Experimental Conditions Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-xco took 1.7679836750030518s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 8.249282836914062e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.15504717826843262s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002636909484863281s
Believability | Calculation of trust value for Yeast phenotypes took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ypo took 1.7500464916229248s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.130073547363281e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.16259002685546875s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.021117210388183594s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007719993591308594s
Believability | Calculation of trust value for Zebrafish anatomy and development took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-zfa took 1.7531061172485352s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 8.153915405273438e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.16133642196655273s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.86102294921875e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.1682510375976562e-05s
INFO | --- Analysis for Bioportal_link took 1.7454593181610107s
Availability | SPARQL endpoint availability check for BioSamples RDF took 4.38690185546875e-05s
Availability | VoID file availability check for BioSamples RDF took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.154188871383667s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.021850109100341797s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0012226104736328125s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 4.124641418457031e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.2159347534179688e-05s
INFO | --- Analysis for biosamples-rdf took 1.728581190109253s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 8.225440979003906e-05s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.15734601020812988s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020355701446533203s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011420249938964844s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for bis-linked-data took 1.76713228225708s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.96453857421875e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.16004037857055664s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.886222839355469e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for bll-thesaurus took 1.7276160717010498s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.1937763690948486s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.15808558464050293s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.021131038665771484s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.961822509765625e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for bluk-bnb took 3.1183865070343018s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.3125944137573242s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006182193756103516s
Extra | Recovery of all triples for Thesaurus BNCF took 44.77395534515381s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5736477375030518s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6721725463867188s
Interoperability | New terms check for Thesaurus BNCF took 1.4907057285308838s
Versatility | Languages check for Thesaurus BNCF took 6.6818859577178955s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.838615894317627s
Security | Check HTTPS for Thesaurus BNCF took 0.08214282989501953s
Interpretability | RDF structures check for Thesaurus BNCF took 0.10390734672546387s
Versatility | Serialization formats check for Thesaurus BNCF took 0.10575723648071289s
Availability | RDF dump link check for Thesaurus BNCF took 0.10150790214538574s
License | MR license check for Thesaurus BNCF took 0.10289120674133301s
License | HR license check for Thesaurus BNCF took 0.18367576599121094s
Amount of data | Number of property check for Thesaurus BNCF took 0.10702633857727051s
Understandability | Number of label check for Thesaurus BNCF took 0.23975801467895508s
Understandability | URI regex check for Thesaurus BNCF took 0.20912480354309082s
Understandability | Vocabs check for Thesaurus BNCF took 0.10513806343078613s
Verifiability | Authors check for Thesaurus BNCF took 0.10690069198608398s
Verifiability | Publishers check for Thesaurus BNCF took 0.10679197311401367s
Performance | Throughput check for Thesaurus BNCF took 10.366629838943481s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.224082946777344e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.10785365104675293s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.1072688102722168s
Interlinking | skos check for Thesaurus BNCF took 0.1612839698791504s
Interlinking | skos check for Thesaurus BNCF took 0.14442753791809082s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.10690665245056152s
Currency | Creation date check for Thesaurus BNCF took 0.2206425666809082s
Currency | Modification date check for Thesaurus BNCF took 0.21277141571044922s
Rep.Conc. | URIs length for Thesaurus BNCF took 25.58602547645569s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.1081998348236084s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.1048898696899414s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.10365819931030273s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.509201526641846s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4870283603668213s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.800976037979126s
Consistency | Disjoint class check for Thesaurus BNCF took 0.10819053649902344s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.946868896484375s
Consistency | Misplaced classes for Thesaurus BNCF took 6.544574022293091s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.764038801193237s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4989371299743652s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.32487154006958s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.347728729248047s
Security | Sign check for Thesaurus BNCF took 0.12292337417602539s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 20.913252592086792s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.18021941184997559s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.2479248046875e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.1457672119140625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.239776611328125e-05s
INFO | --- Analysis for bncf-ns took 173.64289355278015s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.9577484130859375e-05s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.16213488578796387s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.022802352905273438s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.9577484130859375e-05s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0251998901367188e-05s
INFO | --- Analysis for bpr took 1.7808420658111572s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 8.487701416015625e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.00020623207092285156s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.15279173851013184s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020595550537109375s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.915496826171875e-05s
Believability | Calculation of trust value for Brazilian Politicians took 1.2159347534179688e-05s
INFO | --- Analysis for brazilian-politicians took 1.763648509979248s
Availability | SPARQL endpoint availability check for Bricklink took 9.131431579589844e-05s
Availability | VoID file availability check for Bricklink took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Bricklink took 0.16301465034484863s
Reputation | Calculation of the PageRank for Bricklink took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0010137557983398438s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.963180541992188e-05s
Believability | Calculation of trust value for Bricklink took 1.239776611328125e-05s
INFO | --- Analysis for bricklink took 1.8458619117736816s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.17945694923401s
Availability | VoID file availability check for British Museum Collection took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.15790843963623047s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02236485481262207s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 2.7179718017578125e-05s
Believability | Calculation of trust value for British Museum Collection took 1.0251998901367188e-05s
INFO | --- Analysis for british-museum-collection took 62.0198700428009s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 0.00015091896057128906s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.15373015403747559s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020474910736083984s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.4345855712890625e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.2159347534179688e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 1.8125240802764893s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 8.726119995117188e-05s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.28539514541625977s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.020449399948120117s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3828277587890625e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2636184692382812e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 1.8561608791351318s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 4.029273986816406e-05s
Availability | VoID file availability check for business.data.gov.uk took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.16075849533081055s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.021585941314697266s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.3882598876953125e-05s
Believability | Calculation of trust value for business.data.gov.uk took 1.33514404296875e-05s
INFO | --- Analysis for business-data-gov-uk took 1.821723222732544s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5968019962310791s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0004901885986328125s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 4.002267837524414s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.5453870296478271s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.391268253326416s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.721705436706543s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 48.55420994758606s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.27785825729370117s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.16116547584533691s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.4249718189239502s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.27050328254699707s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.2610323429107666s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.38742637634277344s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.518852472305298s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.31116223335266113s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.5931735038757324s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.5658199787139893s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.264667272567749s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.4077928066253662s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.5791409015655518s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 12.459299564361572s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 8.845329284667969e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.38056325912475586s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3577444553375244s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.37324070930480957s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 1.3175454139709473s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.26655101776123047s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.6393141746520996s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5703580379486084s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.547398090362549s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.26549863815307617s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.41509461402893066s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4118778705596924s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.5291380882263184s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.033278465270996094s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.028031349182128906s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.3050351142883301s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.397120475769043s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.36380863189697266s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.719440460205078s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2708709239959717s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.4331421852111816s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.033980607986450195s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.28399229049682617s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.2730562686920166s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 2380.590349674225s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.4223787784576416s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02124190330505371s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.239776611328125e-05s
INFO | --- Analysis for BVMC took 2517.231466293335s
Availability | SPARQL endpoint availability check for cablegate took 9.918212890625e-05s
Availability | VoID file availability check for cablegate took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for cablegate took 0.15295958518981934s
Reputation | Calculation of the PageRank for cablegate took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for cablegate took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.628036499023438e-05s
Believability | Calculation of trust value for cablegate took 1.0967254638671875e-05s
INFO | --- Analysis for cablegate took 1.768064022064209s
Availability | SPARQL endpoint availability check for Calames took 8.940696716308594e-05s
Availability | VoID file availability check for Calames took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Calames took 0.16291284561157227s
Reputation | Calculation of the PageRank for Calames took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for Calames took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Calames took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Calames took 3.314018249511719e-05s
Believability | Calculation of trust value for Calames took 9.298324584960938e-06s
INFO | --- Analysis for calames took 1.750227689743042s
Availability | SPARQL endpoint availability check for CaLiGraph took 8.225440979003906e-05s
Availability | VoID file availability check for CaLiGraph took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.15890026092529297s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 2.8848648071289062e-05s
Believability | Calculation of trust value for CaLiGraph took 9.5367431640625e-06s
INFO | --- Analysis for CaLiGraph took 1.7439336776733398s
Availability | SPARQL endpoint availability check for CaLiGraph took 8.416175842285156e-05s
Availability | VoID file availability check for CaLiGraph took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.15897488594055176s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.128715515136719e-05s
Believability | Calculation of trust value for CaLiGraph took 9.298324584960938e-06s
INFO | --- Analysis for caligraph took 1.7277708053588867s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 8.153915405273438e-05s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.1611950397491455s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020266056060791016s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.239776611328125e-05s
INFO | --- Analysis for cap-italy-rdf took 1.756324291229248s
Availability | SPARQL endpoint availability check for person took 8.225440979003906e-05s
Availability | VoID file availability check for person took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for person took 0.15742921829223633s
Reputation | Calculation of the PageRank for person took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for person took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for person took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for person took 3.0517578125e-05s
Believability | Calculation of trust value for person took 1.1682510375976562e-05s
INFO | --- Analysis for card took 1.7405846118927002s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 8.153915405273438e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.1728992462158203s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.910064697265625e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.3113021850585938e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 1.7633092403411865s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 3.9577484130859375e-05s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.150374174118042s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 3.62396240234375e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.049041748046875e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 1.724151611328125s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.100799560546875e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.1502704620361328s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.02035379409790039s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.846687316894531e-05s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0728836059570312e-05s
INFO | --- Analysis for ce4r took 1.7512946128845215s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.442547082901001s
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.9872064590454102s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.893444299697876s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2824084758758545s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6654777526855469s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.141191482543945s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17567825317382812s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3814396858215332s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16605281829833984s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15963411331176758s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3275144100189209s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1967308521270752s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23784947395324707s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3263983726501465s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.32601284980773926s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1521749496459961s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1896648406982422s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2653074264526367s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.62964940071106s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 0.00010323524475097656s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2640695571899414s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3266587257385254s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6253552436828613s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14774298667907715s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15971612930297852s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6631193161010742s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4574856758117676s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.0427355766296387s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16885828971862793s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.5725841522216797s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028795242309570312s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.027932167053222656s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3545503616333008s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2639756202697754s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9766724109649658s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.319401741027832s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5333144664764404s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03262734413146973s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.19511866569519043s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14543437957763672s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2389.768620491028s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.27261853218078613s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.021538734436035156s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 3.719329833984375e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 9.5367431640625e-06s
INFO | --- Analysis for ceo took 2512.3556139469147s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.1484832763671875e-05s
Availability | VoID file availability check for Chat Game corpus took 0.00021791458129882812s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.15592646598815918s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.552436828613281e-05s
Believability | Calculation of trust value for Chat Game corpus took 8.344650268554688e-06s
INFO | --- Analysis for chat-game-corpus took 1.7406673431396484s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.172325134277344e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.15040206909179688s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.1021575927734375e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 7.62939453125e-06s
INFO | --- Analysis for chem2bio2rdf took 1.7144017219543457s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 4.076957702636719e-05s
Availability | VoID file availability check for ChEMBL RDF took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.1653902530670166s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02243947982788086s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.626678466796875e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.33514404296875e-05s
INFO | --- Analysis for chembl-rdf took 1.74906587600708s
Availability | SPARQL endpoint availability check for chemdb  dataset took 6.4849853515625e-05s
Availability | VoID file availability check for chemdb  dataset took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.1569516658782959s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.02183389663696289s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.534027099609375e-05s
Believability | Calculation of trust value for chemdb  dataset took 1.239776611328125e-05s
INFO | --- Analysis for chemdb-basicInfo took 1.747523546218872s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 8.296966552734375e-05s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.15744423866271973s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.076957702636719e-05s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.2874603271484375e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 1.7591545581817627s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 6.437301635742188e-05s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.16088080406188965s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.02076244354248047s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.4345855712890625e-05s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.3113021850585938e-05s
INFO | --- Analysis for chemdb-phaseTransition took 1.7036912441253662s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 8.440017700195312e-05s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.15156841278076172s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.023102998733520508s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0010013580322265625s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 7.963180541992188e-05s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.3113021850585938e-05s
INFO | --- Analysis for chemdb-thermochemistry took 1.7256073951721191s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 8.845329284667969e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.16852807998657227s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02242302894592285s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for ChemPedia RDF took 7.62939453125e-06s
INFO | --- Analysis for chempedia-rdf took 1.7460675239562988s
Availability | SPARQL endpoint availability check for Chiman Maru took 8.225440979003906e-05s
Availability | VoID file availability check for Chiman Maru took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.15479373931884766s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.075599670410156e-05s
Believability | Calculation of trust value for Chiman Maru took 1.3113021850585938e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 1.7732672691345215s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.2677249908447s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.1991724967956543s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.172325134277344e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 9.775161743164062e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 664.964574098587s
Availability | SPARQL endpoint availability check for Chronicling America took 0.00011539459228515625s
Availability | VoID file availability check for Chronicling America took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.15852808952331543s
Reputation | Calculation of the PageRank for Chronicling America took 0.021124839782714844s
Interlinking | Calculation of Degree of Connection for Chronicling America took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 9.775161743164062e-05s
Believability | Calculation of trust value for Chronicling America took 9.059906005859375e-06s
INFO | --- Analysis for chronicling-america took 1.8646008968353271s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.577139139175415s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0005049705505371094s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 79.33629941940308s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.485853672027588s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6676936149597168s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.4877452850341797s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.4378256797790527s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.6427578926086426s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.317033052444458s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.26584720611572266s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 8.081485509872437s
License | MR license check for Cultural Heritage Thesaurus took 0.305403470993042s
License | HR license check for Cultural Heritage Thesaurus took 0.34383344650268555s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.2678797245025635s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.32637953758239746s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5280258655548096s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3075222969055176s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.2637338638305664s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.2649831771850586s
Performance | Throughput check for Cultural Heritage Thesaurus took 10.695606231689453s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.319450378417969e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2657740116119385s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.2686004638671875s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.2679026126861572s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.27443790435791016s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.29564881324768066s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5357377529144287s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5306987762451172s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 34.875762939453125s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 2.887085199356079s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.2584712505340576s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.26213979721069336s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2881491184234619s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 4.77418851852417s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21748709678649902s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.2615041732788086s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 0.9425384998321533s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2571749687194824s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.374448537826538s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.116150140762329s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001537799835205078s
Security | Sign check for Cultural Heritage Thesaurus took 0.25939416885375977s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 279.6332778930664s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 1.327249526977539s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.028052806854248047s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 2.9802322387695312e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0008981227874755859s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00012540817260742188s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 3.1683170795440674s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for cht took 469.0033977031708s
Availability | SPARQL endpoint availability check for ciard-ring took 8.20159912109375e-05s
Availability | VoID file availability check for ciard-ring took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.16246938705444336s
Reputation | Calculation of the PageRank for ciard-ring took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for ciard-ring took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.7206878662109375e-05s
Believability | Calculation of trust value for ciard-ring took 1.2874603271484375e-05s
INFO | --- Analysis for ciard-ring took 1.787982702255249s
Availability | SPARQL endpoint availability check for Cine Figure took 6.723403930664062e-05s
Availability | VoID file availability check for Cine Figure took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.15639066696166992s
Reputation | Calculation of the PageRank for Cine Figure took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for Cine Figure took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.553794860839844e-05s
Believability | Calculation of trust value for Cine Figure took 9.5367431640625e-06s
INFO | --- Analysis for Cine_Figure took 1.7515652179718018s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 2.781829595565796s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.1612701416015625s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.02250075340270996s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.792213439941406e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 9.298324584960938e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 6.362417221069336s
Availability | SPARQL endpoint availability check for CIPFA took 8.463859558105469e-05s
Availability | VoID file availability check for CIPFA took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for CIPFA took 0.173919677734375s
Reputation | Calculation of the PageRank for CIPFA took 0.020784616470336914s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for CIPFA took 4.029273986816406e-05s
Believability | Calculation of trust value for CIPFA took 1.2159347534179688e-05s
INFO | --- Analysis for cipfa took 1.7817192077636719s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 4.5299530029296875e-05s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.1775827407836914s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003845691680908203s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.2159347534179688e-05s
INFO | --- Analysis for ckan took 1.8070533275604248s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 8.940696716308594e-05s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0002257823944091797s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.15182828903198242s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0009393692016601562s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.1961669921875e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1444091796875e-05s
INFO | --- Analysis for CLaSSES took 1.7384588718414307s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 7.677078247070312e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.16232633590698242s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02092742919921875s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.123283386230469e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.0967254638671875e-05s
INFO | --- Analysis for classical_temples took 1.7550394535064697s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 7.486343383789062e-05s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.151871919631958s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.022188186645507812s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 7.748603820800781e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 1.2159347534179688e-05s
INFO | --- Analysis for clean-energy-data-reegle took 2.303192377090454s
Availability | SPARQL endpoint availability check for CLLD-afbo took 8.296966552734375e-05s
Availability | VoID file availability check for CLLD-afbo took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.1563882827758789s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.677078247070312e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.2159347534179688e-05s
INFO | --- Analysis for clld-afbo took 1.7706432342529297s
Availability | SPARQL endpoint availability check for CLLD-APICS took 7.867813110351562e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.15696406364440918s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.021076679229736328s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.486343383789062e-05s
Believability | Calculation of trust value for CLLD-APICS took 8.58306884765625e-06s
INFO | --- Analysis for clld-apics took 1.815875768661499s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 8.082389831542969e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.15365147590637207s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.00543212890625e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.2159347534179688e-05s
INFO | --- Analysis for clld-ewave took 1.7528586387634277s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.19142413139343262s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.022719144821166992s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010013580322265625s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.1682510375976562e-05s
INFO | --- Analysis for clld-glottolog took 1.826927661895752s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.106231689453125e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.1611788272857666s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02130270004272461s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0010297298431396484s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 9.584426879882812e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.2159347534179688e-05s
INFO | --- Analysis for clld-phoible took 1.7462928295135498s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.130073547363281e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.1627652645111084s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.700920104980469e-05s
Believability | Calculation of trust value for CLLD-SAILS took 9.298324584960938e-06s
INFO | --- Analysis for clld-sails took 1.7544395923614502s
Availability | SPARQL endpoint availability check for CLLD-WALS took 7.987022399902344e-05s
Availability | VoID file availability check for CLLD-WALS took 0.00041747093200683594s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.16057825088500977s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.130073547363281e-05s
Believability | Calculation of trust value for CLLD-WALS took 9.298324584960938e-06s
INFO | --- Analysis for clld-wals took 1.7668979167938232s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 8.0108642578125e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.15656113624572754s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.677078247070312e-05s
Believability | Calculation of trust value for CLLD-WOLD took 9.775161743164062e-06s
INFO | --- Analysis for clld-wold took 1.7239971160888672s
Availability | SPARQL endpoint availability check for Cooperation Databank took 6.365776062011719e-05s
Availability | VoID file availability check for Cooperation Databank took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.164811372756958s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.528594970703125e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.0013580322265625e-05s
INFO | --- Analysis for CoDa took 1.753065824508667s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 8.034706115722656e-05s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.1569838523864746s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.022365570068359375s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 1.0251998901367188e-05s
INFO | --- Analysis for coins-openuplabs took 1.7408735752105713s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 4.1961669921875e-05s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.1611640453338623s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.022195816040039062s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.96453857421875e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 9.775161743164062e-06s
INFO | --- Analysis for CoLChina_sp2000 took 1.7449150085449219s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 7.987022399902344e-05s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.15300989151000977s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.790855407714844e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for colinda took 1.7329261302947998s
Availability | SPARQL endpoint availability check for CN  2012 took 8.130073547363281e-05s
Availability | VoID file availability check for CN  2012 took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.16154098510742188s
Reputation | Calculation of the PageRank for CN  2012 took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for CN  2012 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.457069396972656e-05s
Believability | Calculation of trust value for CN  2012 took 1.1444091796875e-05s
INFO | --- Analysis for combined-nomenclature-2012 took 1.9753592014312744s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 8.058547973632812e-05s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.1619126796722412s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for CompHistSem took 1.7556631565093994s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 8.273124694824219e-05s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.1643056869506836s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.000993967056274414s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.1484832763671875e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.2636184692382812e-05s
INFO | --- Analysis for comsode-d3-2 took 1.7730145454406738s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 8.273124694824219e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.15911626815795898s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.392333984375e-05s
Believability | Calculation of trust value for 2011 US Congress People took 1.239776611328125e-05s
INFO | --- Analysis for congresspeople took 1.7715630531311035s
Availability | SPARQL endpoint availability check for MIMO took 4.076957702636719e-05s
Availability | VoID file availability check for MIMO took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for MIMO took 0.17036080360412598s
Reputation | Calculation of the PageRank for MIMO took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for MIMO took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.1205673217773438e-05s
Believability | Calculation of trust value for MIMO took 1.2159347534179688e-05s
INFO | --- Analysis for CONNECTED took 1.7818841934204102s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.267692565917969e-05s
Availability | VoID file availability check for Copyright Free Music took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.15827345848083496s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.9325485229492188e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.1920928955078125e-05s
INFO | --- Analysis for Copyright_Free_Music took 1.7461490631103516s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 6.556510925292969e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.15233874320983887s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.021464824676513672s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.699562072753906e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.1682510375976562e-05s
INFO | --- Analysis for copyrighttermbank took 1.7391057014465332s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 8.368492126464844e-05s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.1527853012084961s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.647804260253906e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.239776611328125e-05s
INFO | --- Analysis for core took 1.7420697212219238s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.00012063980102539062s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.15699386596679688s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.02183246612548828s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0011374950408935547s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.910064697265625e-05s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.2636184692382812e-05s
INFO | --- Analysis for Corine_linked_dataset took 1.7868564128875732s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 8.606910705566406e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.15444493293762207s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.650520324707031e-05s
Believability | Calculation of trust value for Cornetto1.2 took 7.152557373046875e-06s
INFO | --- Analysis for cornetto took 1.7470567226409912s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 8.249282836914062e-05s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.1539325714111328s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.020321130752563477s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 4.553794860839844e-05s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 7.152557373046875e-06s
INFO | --- Analysis for corporate-body took 1.7419345378875732s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.00010061264038085938s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.1575608253479004s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.022619962692260742s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for CorpusFibonacci took 1.7321665287017822s
Availability | SPARQL endpoint availability check for Country Name Authority List took 8.153915405273438e-05s
Availability | VoID file availability check for Country Name Authority List took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.16265416145324707s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 4.8160552978515625e-05s
Believability | Calculation of trust value for Country Name Authority List took 7.62939453125e-06s
INFO | --- Analysis for country-authority-list took 1.7321383953094482s
Availability | SPARQL endpoint availability check for Courts thesaurus took 8.654594421386719e-05s
Availability | VoID file availability check for Courts thesaurus took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2203052043914795s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.028750896453857422s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0011897087097167969s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 8.869171142578125e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for courts-thesaurus took 1.8366222381591797s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 8.249282836914062e-05s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.1626415252685547s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.987022399902344e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Covid-on-the-Web took 1.73695969581604s
Availability | SPARQL endpoint availability check for CPA 2008 took 8.225440979003906e-05s
Availability | VoID file availability check for CPA 2008 took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.15966129302978516s
Reputation | Calculation of the PageRank for CPA 2008 took 0.020983457565307617s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.457069396972656e-05s
Believability | Calculation of trust value for CPA 2008 took 1.3589859008789062e-05s
INFO | --- Analysis for cpa-2008 took 1.7650110721588135s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 8.797645568847656e-05s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.1594855785369873s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02011871337890625s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 3.0994415283203125e-05s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.239776611328125e-05s
INFO | --- Analysis for CPC took 1.7572340965270996s
Availability | SPARQL endpoint availability check for CPC 2008 took 6.580352783203125e-05s
Availability | VoID file availability check for CPC 2008 took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.15658187866210938s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.361701965332031e-05s
Believability | Calculation of trust value for CPC 2008 took 6.9141387939453125e-06s
INFO | --- Analysis for cpc-2008 took 1.7137417793273926s
Availability | SPARQL endpoint availability check for CPV  2003 took 8.535385131835938e-05s
Availability | VoID file availability check for CPV  2003 took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.15395569801330566s
Reputation | Calculation of the PageRank for CPV  2003 took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.361701965332031e-05s
Believability | Calculation of trust value for CPV  2003 took 1.1682510375976562e-05s
INFO | --- Analysis for cpv-2003 took 1.7271311283111572s
Availability | SPARQL endpoint availability check for CPV 2008 took 4.506111145019531e-05s
Availability | VoID file availability check for CPV 2008 took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.16621971130371094s
Reputation | Calculation of the PageRank for CPV 2008 took 0.021548748016357422s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.3392181396484375e-05s
Believability | Calculation of trust value for CPV 2008 took 1.1444091796875e-05s
INFO | --- Analysis for cpv-2008 took 1.7481334209442139s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 7.963180541992188e-05s
Availability | VoID file availability check for crowdsourcing-fb took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.1588001251220703s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 3.4332275390625e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.1920928955078125e-05s
INFO | --- Analysis for crowdsourcing-fb took 1.7705025672912598s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 0.00010013580322265625s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.15488600730895996s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.792213439941406e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 1.2874603271484375e-05s
INFO | --- Analysis for ctic-public-dataset took 1.7584822177886963s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.4072880744934082s
Availability | VoID file availability check for CulturaLinkedData took 0.0004968643188476562s
Extra | Recovery of all triples for CulturaLinkedData took 114.71546840667725s
Performance | Total latancy measurement for CulturaLinkedData took 4.32559609413147s
Amount of data | Number of triples check for CulturaLinkedData took 0.7174863815307617s
Interoperability | New terms check for CulturaLinkedData took 2.2893621921539307s
Versatility | Languages check for CulturaLinkedData took 60.94169354438782s
Interpretability | Number of blank nodes check for CulturaLinkedData took 1.8888769149780273s
Interpretability | RDF structures check for CulturaLinkedData took 0.4588789939880371s
Versatility | Serialization formats check for CulturaLinkedData took 2.2608988285064697s
Availability | RDF dump link check for CulturaLinkedData took 1.9545278549194336s
License | MR license check for CulturaLinkedData took 0.54803466796875s
License | HR license check for CulturaLinkedData took 60.318745374679565s
Amount of data | Number of property check for CulturaLinkedData took 0.17843031883239746s
Understandability | Number of label check for CulturaLinkedData took 2.7666561603546143s
Understandability | URI regex check for CulturaLinkedData took 0.5385839939117432s
Understandability | Vocabs check for CulturaLinkedData took 0.24559855461120605s
Verifiability | Authors check for CulturaLinkedData took 0.25540924072265625s
Verifiability | Publishers check for CulturaLinkedData took 1.9697654247283936s
Performance | Throughput check for CulturaLinkedData took 19.623271942138672s
Amount of data | Check the number of entities for CulturaLinkedData took 6.842613220214844e-05s
Verifiability | Contribs. check for CulturaLinkedData took 1.9716691970825195s
Interlinking | sameAs chians check for CulturaLinkedData took 0.307187557220459s
Interlinking | skos check for CulturaLinkedData took 0.4024646282196045s
Interlinking | skos check for CulturaLinkedData took 1.8898274898529053s
Timeliness | dataset update frequency check for CulturaLinkedData took 2.011323928833008s
Currency | Creation date check for CulturaLinkedData took 2.111912727355957s
Currency | Modification date check for CulturaLinkedData took 3.8671467304229736s
Rep.Conc. | URIs length for CulturaLinkedData took 53.93134617805481s
Interoperability | New vocabularies check for CulturaLinkedData took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.16618108749389648s
Accuracy | Check Functional Property for CulturaLinkedData took 1.9421229362487793s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 1.9205925464630127s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 38.5660285949707s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6040589809417725s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.26019287109375s
Consistency | Disjoint class check for CulturaLinkedData took 0.20016264915466309s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.040153980255127s
Consistency | Misplaced classes for CulturaLinkedData took 5.908010005950928s
Consistency | Check Ontology hijacking for CulturaLinkedData took 41.12981986999512s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3637418746948242s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 11.127657175064087s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3907856941223145s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 1.9803335666656494s
Security | Sign check for CulturaLinkedData took 0.9167885780334473s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 10.827327728271484s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.22592568397521973s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021018505096435547s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.2901763916015625e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.1457672119140625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 9.775161743164062e-06s
INFO | --- Analysis for culturalinkeddata took 583.781628370285s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 4.076957702636719e-05s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.16065406799316406s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.600120544433594e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-ares-or took 1.748896598815918s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.1484832763671875e-05s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.16597580909729004s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020097970962524414s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.337860107421875e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.1920928955078125e-05s
INFO | --- Analysis for cz-ares-rzp took 1.7541773319244385s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 3.8623809814453125e-05s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.18891286849975586s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.021979093551635742s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.0517578125e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 1.239776611328125e-05s
INFO | --- Analysis for cz-cenia-irz-chemicals took 1.809298038482666s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 4.00543212890625e-05s
Availability | VoID file availability check for Integrated pollution registry took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.161665678024292s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02011418342590332s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.838539123535156e-05s
Believability | Calculation of trust value for Integrated pollution registry took 6.9141387939453125e-06s
INFO | --- Analysis for cz-cenia-pollution took 1.8273489475250244s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 8.153915405273438e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.16076135635375977s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.719329833984375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 1.1205673217773438e-05s
INFO | --- Analysis for cz-contracts took 1.7371304035186768s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 8.654594421386719e-05s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.15526580810546875s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.022844791412353516s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.409385681152344e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 5.7220458984375e-06s
INFO | --- Analysis for cz-ctia-bans took 1.7157108783721924s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 8.440017700195312e-05s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.1545581817626953s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.3855438232421875e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
INFO | --- Analysis for cz-ctia-confiscations took 1.726905345916748s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 4.0531158447265625e-05s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.00020313262939453125s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.17131567001342773s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02048182487487793s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.600120544433594e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 1.0251998901367188e-05s
INFO | --- Analysis for cz-ctia-focus took 1.7774009704589844s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 6.151199340820312e-05s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.159226655960083s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.021813154220581055s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.267692565917969e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ctia-inspections took 1.7641119956970215s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 3.9577484130859375e-05s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.16098809242248535s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.021634340286254883s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.528594970703125e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 1.049041748046875e-05s
INFO | --- Analysis for cz-ctia-sanctions took 1.732548475265503s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 6.270408630371094e-05s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.16200017929077148s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.02033090591430664s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.695487976074219e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 1.0013580322265625e-05s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 1.8991599082946777s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 4.00543212890625e-05s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.16048717498779297s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 5.173683166503906e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 9.059906005859375e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 1.7556126117706299s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 8.130073547363281e-05s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.16203546524047852s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.022369861602783203s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.814697265625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 1.0251998901367188e-05s
INFO | --- Analysis for cz-czso-average-salaries took 1.7518656253814697s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 9.226799011230469e-05s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.1524519920349121s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 1.2159347534179688e-05s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 1.7918009757995605s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.7206878662109375e-05s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.16290616989135742s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.02164745330810547s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.172325134277344e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.239776611328125e-05s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 1.7465925216674805s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 4.00543212890625e-05s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.1682441234588623s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 7.62939453125e-06s
INFO | --- Analysis for cz-czso-job-applicants took 1.750192642211914s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 8.20159912109375e-05s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.15783214569091797s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.0218045711517334s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007097721099853516s
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 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 1.7127265930175781s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 4.3392181396484375e-05s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.15903329849243164s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.504753112792969e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 1.1205673217773438e-05s
INFO | --- Analysis for cz-czso-regions took 1.8092255592346191s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 7.987022399902344e-05s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.165543794631958s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.021918058395385742s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.814697265625e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 1.7701804637908936s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 4.100799560546875e-05s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.15639877319335938s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02018570899963379s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.552436828613281e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 1.1444091796875e-05s
INFO | --- Analysis for cz-czso-social-service-facilities took 1.7401635646820068s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 8.392333984375e-05s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.1558704376220703s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020149946212768555s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.457069396972656e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 1.1205673217773438e-05s
INFO | --- Analysis for cz-czso-unemployment-rate took 1.75681734085083s
Availability | SPARQL endpoint availability check for ATC groups took 8.416175842285156e-05s
Availability | VoID file availability check for ATC groups took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for ATC groups took 0.16282200813293457s
Reputation | Calculation of the PageRank for ATC groups took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.009506225585938e-05s
Believability | Calculation of trust value for ATC groups took 1.1920928955078125e-05s
INFO | --- Analysis for cz-eh-1-atc took 1.7324776649475098s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 8.392333984375e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.16457891464233398s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.021053314208984375s
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.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.647804260253906e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 1.2159347534179688e-05s
INFO | --- Analysis for cz-fulfillments took 1.743265151977539s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 8.344650268554688e-05s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.1542348861694336s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.022072553634643555s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.8160552978515625e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 1.1682510375976562e-05s
INFO | --- Analysis for cz-ic took 1.7493395805358887s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 6.127357482910156e-05s
Availability | VoID file availability check for List of Czech data boxes took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.16074156761169434s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02163100242614746s
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.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 2.956390380859375e-05s
Believability | Calculation of trust value for List of Czech data boxes took 1.0728836059570312e-05s
INFO | --- Analysis for cz-list-of-databoxes took 1.7334699630737305s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.440017700195312e-05s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1609950065612793s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02100396156311035s
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.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0517578125e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0967254638671875e-05s
INFO | --- Analysis for cz-nace took 1.7308523654937744s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.273124694824219e-05s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15347599983215332s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.022351503372192383s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.409385681152344e-05s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.1920928955078125e-05s
INFO | --- Analysis for cz-nkod took 1.7472007274627686s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 4.267692565917969e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.15860438346862793s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.02206254005432129s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.719329833984375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 9.775161743164062e-06s
INFO | --- Analysis for cz-orders took 1.7401609420776367s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 8.177757263183594e-05s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.000202178955078125s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.1565549373626709s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.220008850097656e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ovm took 1.7398617267608643s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 6.556510925292969e-05s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.15528392791748047s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.02104496955871582s
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.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-ovm-agendas took 1.991856336593628s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.441375732421875e-05s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16341471672058105s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.021222352981567383s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.1444091796875e-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.628036499023438e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-ruian took 1.744415521621704s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.00011777877807617188s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.15252351760864258s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.414817810058594e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-sao-audited-subjects took 1.7287988662719727s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 4.5299530029296875e-05s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.1514453887939453s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 1.239776611328125e-05s
INFO | --- Analysis for cz-sao-check-actions took 1.7640612125396729s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 8.440017700195312e-05s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.1668558120727539s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 2.8848648071289062e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 6.4373016357421875e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 1.7834336757659912s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 8.130073547363281e-05s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.15417766571044922s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.0040740966796875e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.1682510375976562e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 1.742929458618164s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 8.869171142578125e-05s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.1527233123779297s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020195722579956055s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 2.8848648071289062e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 1.2636184692382812e-05s
INFO | --- Analysis for cz-sidc-drug-prices took 1.7356326580047607s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 5.054473876953125e-05s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.00020623207092285156s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.1563425064086914s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-sidc-drugs took 1.742842674255371s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 8.487701416015625e-05s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.16037201881408691s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.023495197296142578s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.8623809814453125e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 1.2159347534179688e-05s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 1.761247158050537s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 8.082389831542969e-05s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.16245269775390625s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.3855438232421875e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 1.0013580322265625e-05s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 1.7607996463775635s
Availability | SPARQL endpoint availability check for State funding providers took 8.440017700195312e-05s
Availability | VoID file availability check for State funding providers took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for State funding providers took 0.1602954864501953s
Reputation | Calculation of the PageRank for State funding providers took 0.021126747131347656s
Interlinking | Calculation of Degree of Connection for State funding providers took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for State funding providers took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.7670135498046875e-05s
Believability | Calculation of trust value for State funding providers took 1.239776611328125e-05s
INFO | --- Analysis for cz-vavai-funding-providers took 1.7930092811584473s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.00010395050048828125s
Availability | VoID file availability check for Organizations active in R&D took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.15288543701171875s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.933906555175781e-05s
Believability | Calculation of trust value for Organizations active in R&D took 1.2874603271484375e-05s
INFO | --- Analysis for cz-vavai-organizations took 1.7888493537902832s
Availability | SPARQL endpoint availability check for R&D Programmes took 6.556510925292969e-05s
Availability | VoID file availability check for R&D Programmes took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.16472792625427246s
Reputation | Calculation of the PageRank for R&D Programmes took 0.021443605422973633s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.029273986816406e-05s
Believability | Calculation of trust value for R&D Programmes took 1.1920928955078125e-05s
INFO | --- Analysis for cz-vavai-programmes took 1.7595980167388916s
Availability | SPARQL endpoint availability check for R&D Projects took 8.535385131835938e-05s
Availability | VoID file availability check for R&D Projects took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.17189311981201172s
Reputation | Calculation of the PageRank for R&D Projects took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.910064697265625e-05s
Believability | Calculation of trust value for R&D Projects took 1.2159347534179688e-05s
INFO | --- Analysis for cz-vavai-projects took 1.7827329635620117s
Availability | SPARQL endpoint availability check for Institutional research plans took 8.273124694824219e-05s
Availability | VoID file availability check for Institutional research plans took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.17983412742614746s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.838539123535156e-05s
Believability | Calculation of trust value for Institutional research plans took 1.0013580322265625e-05s
INFO | --- Analysis for cz-vavai-research-plans took 1.8495895862579346s
Availability | SPARQL endpoint availability check for Results of R&D took 4.100799560546875e-05s
Availability | VoID file availability check for Results of R&D took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.15438485145568848s
Reputation | Calculation of the PageRank for Results of R&D took 0.02278757095336914s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.8623809814453125e-05s
Believability | Calculation of trust value for Results of R&D took 1.0251998901367188e-05s
INFO | --- Analysis for cz-vavai-results took 1.7666895389556885s
Availability | SPARQL endpoint availability check for Tenders in R&D took 8.320808410644531e-05s
Availability | VoID file availability check for Tenders in R&D took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.17310619354248047s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.021681547164916992s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.695487976074219e-05s
Believability | Calculation of trust value for Tenders in R&D took 1.0728836059570312e-05s
INFO | --- Analysis for cz-vavai-tenders took 1.809358835220337s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 9.226799011230469e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.1621556282043457s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.1948089599609375e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.049041748046875e-05s
INFO | --- Analysis for czech_addresses took 1.7300453186035156s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 7.939338684082031e-05s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.1776580810546875s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 5.4836273193359375e-06s
INFO | --- Analysis for DanteLatinLoanwords took 1.8129491806030273s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.35495734214782715s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.00046181678771972656s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 129.5197455883026s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 0.9045901298522949s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 15.28556776046753s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.352751731872559s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.28034830093384s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.211181640625s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.10812854766845703s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.23096895217895508s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.22278833389282227s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2030808925628662s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.22868657112121582s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.29884433746338s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.26593804359436035s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 2.5986719131469727s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4300978183746338s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.2224900722503662s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.5391502380371094s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.7227661609649658s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 10.530163288116455s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.176399230957031e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.20783543586730957s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.5581481456756592s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.0281853675842285s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.21938323974609375s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.21321749687194824s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.121669054031372s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.3390624523162842s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 89.13279557228088s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.21229338645935059s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.25359225273132324s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.40961432456970215s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 49.84475898742676s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.221780300140381s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.6235275268554688s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.4117543697357178s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 22.963622570037842s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.385815143585205s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 37.994011640548706s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5355911254882812s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.43860363960266s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8024423122406006s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.21290254592895508s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.21715235710144043s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 8.44044804573059s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.28588390350341797s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00013017654418945312s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.9073486328125e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.0728836059570312e-05s
INFO | --- Analysis for data-bnf-fr took 754.7923121452332s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 8.249282836914062e-05s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.15838027000427246s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.022606849670410156s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.222724914550781e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 1.1444091796875e-05s
INFO | --- Analysis for data-cnr-it took 1.7201316356658936s
Availability | SPARQL endpoint availability check for Data.gov took 0.00010013580322265625s
Availability | VoID file availability check for Data.gov took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Data.gov took 0.1502678394317627s
Reputation | Calculation of the PageRank for Data.gov took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for Data.gov took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Data.gov took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Data.gov took 2.7179718017578125e-05s
Believability | Calculation of trust value for Data.gov took 1.1444091796875e-05s
INFO | --- Analysis for data-gov took 1.761946678161621s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 6.461143493652344e-05s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.15288090705871582s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020345687866210938s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.198883056640625e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 1.1682510375976562e-05s
INFO | --- Analysis for data-gov-ie took 1.7404382228851318s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 8.702278137207031e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.1650526523590088s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020186662673950195s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 6.890296936035156e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 1.1682510375976562e-05s
INFO | --- Analysis for data-gov-uk-time-intervals took 1.7992722988128662s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.841103315353394s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.16008234024047852s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.021253108978271484s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 5.817413330078125e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 9.5367431640625e-06s
INFO | --- Analysis for data-hnm-hu took 53.70629048347473s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.09696507453918457s
Availability | VoID file availability check for Climb Dataincubator took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.1605832576751709s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.022066354751586914s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 6.866455078125e-05s
Believability | Calculation of trust value for Climb Dataincubator took 9.298324584960938e-06s
INFO | --- Analysis for data-incubator-climb took 1.8425869941711426s
Availability | SPARQL endpoint availability check for Discogs in RDF took 3.981590270996094e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.15555572509765625s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 8.630752563476562e-05s
Believability | Calculation of trust value for Discogs in RDF took 8.821487426757812e-06s
INFO | --- Analysis for data-incubator-discogs took 2.7798359394073486s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 8.034706115722656e-05s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.14912080764770508s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.1975250244140625e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 9.5367431640625e-06s
INFO | --- Analysis for data-incubator-metoffice took 1.731177806854248s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.0500485897064209s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.15822219848632812s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.021256446838378906s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.177757263183594e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 9.5367431640625e-06s
INFO | --- Analysis for data-incubator-moseley took 3.6357786655426025s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.04840683937072754s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.15632343292236328s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.440017700195312e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 9.298324584960938e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 1.760101318359375s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 3.981590270996094e-05s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.15177464485168457s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020350933074951172s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.225440979003906e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 4.76837158203125e-06s
INFO | --- Analysis for data-incubator-nasa took 1.7176692485809326s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 8.177757263183594e-05s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.15900635719299316s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0010333061218261719s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 8.654594421386719e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.3589859008789062e-05s
INFO | --- Analysis for data-incubator-our-airports took 1.7509832382202148s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 4.029273986816406e-05s
Availability | VoID file availability check for Pokedex data in RDF took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.15207982063293457s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.012222290039062e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.0728836059570312e-05s
INFO | --- Analysis for data-incubator-pokedex took 1.7445991039276123s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 6.270408630371094e-05s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.15110278129577637s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.02108478546142578s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.821487426757812e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.0251998901367188e-05s
INFO | --- Analysis for data-incubator-smcjournals took 1.7292356491088867s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 4.124641418457031e-05s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.16921591758728027s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.200241088867188e-05s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.2874603271484375e-05s
INFO | --- Analysis for data-open-ac-uk took 1.7315864562988281s
Availability | SPARQL endpoint availability check for Persée in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Persée in RDF took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.1496288776397705s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010156631469726562s
Believability | Calculation of trust value for Persée in RDF took 1.239776611328125e-05s
INFO | --- Analysis for data-persee-fr took 1.8227248191833496s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.0000801086425781s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.15956640243530273s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011229515075683594s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 9.059906005859375e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 3.2259819507598877s
Availability | SPARQL endpoint availability check for Open Data Web took 6.437301635742188e-05s
Availability | VoID file availability check for Open Data Web took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.1550438404083252s
Reputation | Calculation of the PageRank for Open Data Web took 0.02028822898864746s
Interlinking | Calculation of Degree of Connection for Open Data Web took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 2.86102294921875e-05s
Believability | Calculation of trust value for Open Data Web took 1.0251998901367188e-05s
INFO | --- Analysis for data.odw.tw took 1.7467961311340332s
Availability | SPARQL endpoint availability check for datahub took 8.034706115722656e-05s
Availability | VoID file availability check for datahub took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for datahub took 0.1587049961090088s
Reputation | Calculation of the PageRank for datahub took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for datahub took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for datahub took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for datahub took 4.6253204345703125e-05s
Believability | Calculation of trust value for datahub took 1.1444091796875e-05s
INFO | --- Analysis for datahub took 1.9211199283599854s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 8.726119995117188e-05s
Availability | VoID file availability check for Open Datasets in South Korea took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.15500807762145996s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.022162437438964844s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 2.956390380859375e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.0251998901367188e-05s
INFO | --- Analysis for datahub-kr-datamap took 1.7125236988067627s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.177757263183594e-05s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.15570616722106934s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.021376848220825195s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.747245788574219e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0013580322265625e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 1.7950408458709717s
Availability | SPARQL endpoint availability check for datos-artium-org took 20.925795793533325s
Availability | VoID file availability check for datos-artium-org took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.1674351692199707s
Reputation | Calculation of the PageRank for datos-artium-org took 0.0208282470703125s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00010919570922851562s
Believability | Calculation of trust value for datos-artium-org took 1.0728836059570312e-05s
INFO | --- Analysis for datos-artium-org took 52.757838010787964s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 6.866455078125e-05s
Availability | VoID file availability check for Datos.bcn.cl took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.15668582916259766s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.319450378417969e-05s
Believability | Calculation of trust value for Datos.bcn.cl took 5.4836273193359375e-06s
INFO | --- Analysis for datos-bcn-cl took 1.7254493236541748s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.26967930793762207s
Availability | VoID file availability check for datos.bne.es took 0.0005011558532714844s
Extra | Recovery of all triples for datos.bne.es took 115.47233176231384s
Performance | Total latancy measurement for datos.bne.es took 6.604386806488037s
Amount of data | Number of triples check for datos.bne.es took 0.8962271213531494s
Interoperability | New terms check for datos.bne.es took 4.113853693008423s
Versatility | Languages check for datos.bne.es took 62.09434413909912s
Interpretability | Number of blank nodes check for datos.bne.es took 0.2698783874511719s
Security | Check HTTPS for datos.bne.es took 0.16349053382873535s
Interpretability | RDF structures check for datos.bne.es took 0.6189725399017334s
Versatility | Serialization formats check for datos.bne.es took 0.6201224327087402s
Availability | RDF dump link check for datos.bne.es took 2.063577651977539s
License | MR license check for datos.bne.es took 2.551816701889038s
License | HR license check for datos.bne.es took 60.43825387954712s
Amount of data | Number of property check for datos.bne.es took 2.137131929397583s
Understandability | Number of label check for datos.bne.es took 2.957882881164551s
Understandability | URI regex check for datos.bne.es took 2.5827393531799316s
Understandability | Vocabs check for datos.bne.es took 0.36824560165405273s
Verifiability | Authors check for datos.bne.es took 2.133045196533203s
Verifiability | Publishers check for datos.bne.es took 2.1156423091888428s
Performance | Throughput check for datos.bne.es took 19.59239411354065s
Amount of data | Check the number of entities for datos.bne.es took 6.937980651855469e-05s
Verifiability | Contribs. check for datos.bne.es took 0.3702583312988281s
Interlinking | sameAs chians check for datos.bne.es took 2.1855950355529785s
Interlinking | skos check for datos.bne.es took 2.3021833896636963s
Interlinking | skos check for datos.bne.es took 0.2549588680267334s
Timeliness | dataset update frequency check for datos.bne.es took 2.2237331867218018s
Currency | Creation date check for datos.bne.es took 4.096991539001465s
Currency | Modification date check for datos.bne.es took 4.0604565143585205s
Rep.Conc. | URIs length for datos.bne.es took 47.90704154968262s
Interoperability | New vocabularies check for datos.bne.es took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 2.0245134830474854s
Accuracy | Check Functional Property for datos.bne.es took 2.0039594173431396s
Accuracy | Check Inverse Functional Property for datos.bne.es took 2.068392753601074s
Accuracy | Check Empty annotation labels for datos.bne.es took 37.585113286972046s
Accuracy | Check White space in annotation for datos.bne.es took 1.6042819023132324s
Accuracy | Check Datatype consistency for datos.bne.es took 1.2594025135040283s
Consistency | Disjoint class check for datos.bne.es took 2.068516492843628s
Consistency | Check Misplaced properties for datos.bne.es took 10.353596210479736s
Consistency | Misplaced classes for datos.bne.es took 4.266802072525024s
Consistency | Check Ontology hijacking for datos.bne.es took 38.3211395740509s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.3634116649627686s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 9.592696905136108s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.3633599281311035s
Conciseness | Check Intensional conciseness for datos.bne.es took 2.10752272605896s
Security | Sign check for datos.bne.es took 2.8765316009521484s
Availability | Check URIs Dereferenciability for datos.bne.es took 9.438511371612549s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.24978852272033691s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020653486251831055s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.0001125335693359375s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 5.4836273193359375e-06s
Believability | Calculation of trust value for datos.bne.es took 1.2636184692382812e-05s
INFO | --- Analysis for datos-bne-es took 598.1157486438751s
Availability | SPARQL endpoint availability check for dbacademic took 4.291534423828125e-05s
Availability | VoID file availability check for dbacademic took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for dbacademic took 0.15929794311523438s
Reputation | Calculation of the PageRank for dbacademic took 0.022046804428100586s
Interlinking | Calculation of Degree of Connection for dbacademic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dbacademic took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.218650817871094e-05s
Believability | Calculation of trust value for dbacademic took 6.9141387939453125e-06s
INFO | --- Analysis for dbacademic took 1.767935037612915s
Availability | SPARQL endpoint availability check for DBkWik took 4.029273986816406e-05s
Availability | VoID file availability check for DBkWik took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for DBkWik took 0.1665177345275879s
Reputation | Calculation of the PageRank for DBkWik took 0.02201080322265625s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for DBkWik took 6.4849853515625e-05s
Believability | Calculation of trust value for DBkWik took 1.1205673217773438e-05s
INFO | --- Analysis for dbkwik took 1.7664129734039307s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 8.153915405273438e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.15713143348693848s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010418891906738281s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.2874603271484375e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 1.7311265468597412s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 7.939338684082031e-05s
Availability | VoID file availability check for dblp Knowledge Graph took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.1588115692138672s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.0967254638671875e-05s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.1682510375976562e-05s
INFO | --- Analysis for dblp-kg took 1.7575697898864746s
Availability | SPARQL endpoint availability check for DBnary took 3.981590270996094e-05s
Availability | VoID file availability check for DBnary took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for DBnary took 0.1591475009918213s
Reputation | Calculation of the PageRank for DBnary took 0.023179292678833008s
Interlinking | Calculation of Degree of Connection for DBnary took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBnary took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for DBnary took 5.14984130859375e-05s
Believability | Calculation of trust value for DBnary took 1.0967254638671875e-05s
INFO | --- Analysis for dbnary took 1.836693286895752s
Availability | SPARQL endpoint availability check for DBpedia took 7.987022399902344e-05s
Availability | VoID file availability check for DBpedia took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for DBpedia took 0.18780755996704102s
Reputation | Calculation of the PageRank for DBpedia took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008723735809326172s
Believability | Calculation of trust value for DBpedia took 1.0728836059570312e-05s
INFO | --- Analysis for dbpedia took 1.806039571762085s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.267692565917969e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.16013741493225098s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.437301635742188e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.1444091796875e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 1.7818608283996582s
Availability | SPARQL endpoint availability check for DBpedia Commons took 7.987022399902344e-05s
Availability | VoID file availability check for DBpedia Commons took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.16247129440307617s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.651878356933594e-05s
Believability | Calculation of trust value for DBpedia Commons took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-commons took 1.7702932357788086s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 3.910064697265625e-05s
Availability | VoID file availability check for DBpedia in Greek took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.1571650505065918s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00018548965454101562s
Believability | Calculation of trust value for DBpedia in Greek took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-el took 1.732686996459961s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 7.939338684082031e-05s
Availability | VoID file availability check for DBpedia in Spanish took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.1612381935119629s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 9.894371032714844e-05s
Believability | Calculation of trust value for DBpedia in Spanish took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-es took 1.742732286453247s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 8.0108642578125e-05s
Availability | VoID file availability check for DBpedia in Basque took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.16071271896362305s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.021413803100585938s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.457069396972656e-05s
Believability | Calculation of trust value for DBpedia in Basque took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-eu took 1.7378871440887451s
Availability | SPARQL endpoint availability check for DBpedia in French took 4.124641418457031e-05s
Availability | VoID file availability check for DBpedia in French took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.14952397346496582s
Reputation | Calculation of the PageRank for DBpedia in French took 0.021141529083251953s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 8.58306884765625e-05s
Believability | Calculation of trust value for DBpedia in French took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-fr took 1.7351553440093994s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 4.1484832763671875e-05s
Availability | VoID file availability check for DBpedia in Japanese took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.1606156826019287s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.022156476974487305s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 9.560585021972656e-05s
Believability | Calculation of trust value for DBpedia in Japanese took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-ja took 1.746422290802002s
Availability | SPARQL endpoint availability check for dbpedia lite took 8.511543273925781e-05s
Availability | VoID file availability check for dbpedia lite took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.1546614170074463s
Reputation | Calculation of the PageRank for dbpedia lite took 0.021425485610961914s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.822845458984375e-05s
Believability | Calculation of trust value for dbpedia lite took 1.1682510375976562e-05s
INFO | --- Analysis for dbpedia-lite took 1.733752727508545s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 6.365776062011719e-05s
Availability | VoID file availability check for DBpedia in Dutch took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.15707659721374512s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.021103382110595703s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001652240753173828s
Believability | Calculation of trust value for DBpedia in Dutch took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-nl took 1.718493938446045s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 8.082389831542969e-05s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.1539630889892578s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.02205038070678711s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.034706115722656e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-pt took 1.7309861183166504s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 8.082389831542969e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.16188263893127441s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.413459777832031e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.1920928955078125e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 1.7478840351104736s
Availability | SPARQL endpoint availability check for DBTropes took 4.315376281738281e-05s
Availability | VoID file availability check for DBTropes took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for DBTropes took 0.1532881259918213s
Reputation | Calculation of the PageRank for DBTropes took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for DBTropes took 8.988380432128906e-05s
Believability | Calculation of trust value for DBTropes took 1.1444091796875e-05s
INFO | --- Analysis for dbtropes took 1.9667048454284668s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.267692565917969e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.15277385711669922s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.021778583526611328s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.745887756347656e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 9.5367431640625e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 1.8119478225708008s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 9.131431579589844e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.16147828102111816s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.021187543869018555s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.266334533691406e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 1.745222806930542s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.73950719833374s
Availability | VoID file availability check for DBTune.org/classical took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.1593930721282959s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.021509885787963867s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.700920104980469e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.1920928955078125e-05s
INFO | --- Analysis for dbtune-classical took 7.813507080078125s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.5421295166015625s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.15369343757629395s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.318092346191406e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 9.298324584960938e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 7.591393947601318s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.49592399597168s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.1584322452545166s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.4849853515625e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.049041748046875e-05s
INFO | --- Analysis for dbtune-magnatune took 7.504482984542847s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.37192034721375s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.1704244613647461s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.021358251571655273s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00013375282287597656s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 9.775161743164062e-06s
INFO | --- Analysis for dbtune-musicbrainz took 312.45604252815247s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.3208432197570801s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.16007399559020996s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02242588996887207s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 6.890296936035156e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 9.059906005859375e-06s
INFO | --- Analysis for dbtune-myspace took 2.3819057941436768s
Availability | SPARQL endpoint availability check for data.dcs took 4.1484832763671875e-05s
Availability | VoID file availability check for data.dcs took 0.00020551681518554688s
Completeness | Calculation of interlinking completeness for data.dcs took 0.1490955352783203s
Reputation | Calculation of the PageRank for data.dcs took 0.021435260772705078s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.771087646484375e-05s
Believability | Calculation of trust value for data.dcs took 1.2874603271484375e-05s
INFO | --- Analysis for dcs-sheffield took 1.7996423244476318s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 8.082389831542969e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.15634989738464355s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02093672752380371s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.029273986816406e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 4.76837158203125e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 1.731560230255127s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 8.177757263183594e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.16056251525878906s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.022098064422607422s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.4345855712890625e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.0251998901367188e-05s
INFO | --- Analysis for debian-package-tracking-system took 1.7668921947479248s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.100799560546875e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.16226458549499512s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.022145986557006836s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.504753112792969e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.1205673217773438e-05s
INFO | --- Analysis for desaparecidos took 1.7572035789489746s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0001010894775390625s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.1518230438232422s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02035069465637207s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.632110595703125e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.0251998901367188e-05s
INFO | --- Analysis for deustoentrepreneurship took 1.7112712860107422s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 8.511543273925781e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.16013765335083008s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020180940628051758s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010395050048828125s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 5.4836273193359375e-06s
INFO | --- Analysis for deustotech took 1.7908282279968262s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.2348175048828125s
Availability | VoID file availability check for Deutsche Biographie took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.16448020935058594s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02092719078063965s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.0531158447265625e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.0013580322265625e-05s
INFO | --- Analysis for deutsche-biographie took 3.365689992904663s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 8.654594421386719e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.1596393585205078s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.022326946258544922s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.650520324707031e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 9.059906005859375e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 1.7642474174499512s
Availability | SPARQL endpoint availability check for dev8d took 4.0531158447265625e-05s
Availability | VoID file availability check for dev8d took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for dev8d took 0.1601417064666748s
Reputation | Calculation of the PageRank for dev8d took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for dev8d took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for dev8d took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.580352783203125e-05s
Believability | Calculation of trust value for dev8d took 1.0013580322265625e-05s
INFO | --- Analysis for dev8d took 1.7373545169830322s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 8.225440979003906e-05s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.15280437469482422s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020418167114257812s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007236003875732422s
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.0251998901367188e-05s
INFO | --- Analysis for dewey_decimal_classification took 1.7605717182159424s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 8.225440979003906e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.15625596046447754s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020179033279418945s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.0517578125e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 9.5367431640625e-06s
INFO | --- Analysis for DHSVM took 1.7399816513061523s
Availability | SPARQL endpoint availability check for Diavgeia took 8.177757263183594e-05s
Availability | VoID file availability check for Diavgeia took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.15982866287231445s
Reputation | Calculation of the PageRank for Diavgeia took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.320808410644531e-05s
Believability | Calculation of trust value for Diavgeia took 1.0251998901367188e-05s
INFO | --- Analysis for diavgeia took 1.7703759670257568s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.15424728393554688s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011301040649414062s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 9.775161743164062e-06s
INFO | --- Analysis for didactalia took 1.7392523288726807s
Availability | SPARQL endpoint availability check for DisGeNET took 8.678436279296875e-05s
Availability | VoID file availability check for DisGeNET took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.15813851356506348s
Reputation | Calculation of the PageRank for DisGeNET took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015091896057128906s
Believability | Calculation of trust value for DisGeNET took 1.1444091796875e-05s
INFO | --- Analysis for disgenet took 1.8103461265563965s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 0.0001285076141357422s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.1483759880065918s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02070331573486328s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.147125244140625e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.1444091796875e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 1.7378859519958496s
Availability | SPARQL endpoint availability check for DM2E took 8.58306884765625e-05s
Availability | VoID file availability check for DM2E took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for DM2E took 0.16060328483581543s
Reputation | Calculation of the PageRank for DM2E took 0.02135634422302246s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011610984802246094s
Believability | Calculation of trust value for DM2E took 9.5367431640625e-06s
INFO | --- Analysis for dm2e took 2.4307310581207275s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 4.410743713378906e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.15656208992004395s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.021717071533203125s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015115737915039062s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 9.298324584960938e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 1.7593975067138672s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 8.320808410644531e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.15464186668395996s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.341934204101562e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 1.0013580322265625e-05s
INFO | --- Analysis for doi took 1.74430251121521s
Availability | SPARQL endpoint availability check for Driggu Florentino took 8.153915405273438e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.1600632667541504s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.02249431610107422s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.123283386230469e-05s
Believability | Calculation of trust value for Driggu Florentino took 3.266334533691406e-05s
INFO | --- Analysis for Driggu took 1.7773780822753906s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 6.175041198730469e-05s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.17415332794189453s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.886222839355469e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.0251998901367188e-05s
INFO | --- Analysis for drug-data-hifm took 1.7610650062561035s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 8.296966552734375e-05s
Availability | VoID file availability check for MetaLex Document Server took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.15452098846435547s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.0211946964263916s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.1948089599609375e-05s
Believability | Calculation of trust value for MetaLex Document Server took 5.245208740234375e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 1.7782552242279053s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.3608245849609375s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.16266942024230957s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.1961669921875e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 5.9604644775390625e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 6.120100498199463s
Availability | SPARQL endpoint availability check for DWS-Group took 4.029273986816406e-05s
Availability | VoID file availability check for DWS-Group took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.15440964698791504s
Reputation | Calculation of the PageRank for DWS-Group took 0.020844697952270508s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010514259338378906s
Believability | Calculation of trust value for DWS-Group took 1.0013580322265625e-05s
INFO | --- Analysis for dws-group took 1.738936424255371s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 9.202957153320312e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.19211769104003906s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.022090673446655273s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.147125244140625e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.1205673217773438e-05s
INFO | --- Analysis for E1 took 1.8121676445007324s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 4.5299530029296875e-05s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.1630847454071045s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011372566223144531s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-alaska took 1.7762737274169922s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 4.863739013671875e-05s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.15365862846374512s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.021266460418701172s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 6.318092346191406e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-cau took 1.750138759613037s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 8.296966552734375e-05s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.15378808975219727s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 1.7404839992523193s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 8.273124694824219e-05s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.15227913856506348s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.655952453613281e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-cdrewu took 1.7417218685150146s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 8.487701416015625e-05s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.1575329303741455s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.021294355392456055s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013589859008789062s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-dartmouth took 1.746896743774414s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 4.267692565917969e-05s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.16187667846679688s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.021611928939819336s
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.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.440017700195312e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-famu took 1.7817680835723877s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 6.556510925292969e-05s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.1520709991455078s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.02138996124267578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013113021850585938s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-harvard took 1.7206807136535645s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 4.363059997558594e-05s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.16042327880859375s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.02126455307006836s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012969970703125s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-hawaii took 1.7855689525604248s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 4.673004150390625e-05s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.16144800186157227s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02080559730529785s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.461143493652344e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 9.775161743164062e-06s
INFO | --- Analysis for eagle-i-howard took 1.7618012428283691s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 9.465217590332031e-05s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.000457763671875s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.1629962921142578s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.2178025245666504s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 8.559226989746094e-05s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.15486979484558105s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011801719665527344s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-jsu took 1.7706990242004395s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 6.341934204101562e-05s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.15516281127929688s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02066802978515625s
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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.1484832763671875e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-meharry took 1.7777433395385742s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 8.153915405273438e-05s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.15735673904418945s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020961523056030273s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.799003601074219e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-montana took 1.766983985900879s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 8.559226989746094e-05s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.1609029769897461s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.023085594177246094s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.441375732421875e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-msm took 1.7938892841339111s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 4.1484832763671875e-05s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.1574420928955078s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00012803077697753906s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-ohsu took 1.77858304977417s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 4.744529724121094e-05s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.16319537162780762s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.29425048828125e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-psm took 1.8275132179260254s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 3.981590270996094e-05s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0002124309539794922s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.16187024116516113s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020361900329589844s
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.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.771087646484375e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 5.4836273193359375e-06s
INFO | --- Analysis for eagle-i-tsu took 1.7235417366027832s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 8.177757263183594e-05s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.1474897861480713s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020293474197387695s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.413459777832031e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 5.9604644775390625e-06s
INFO | --- Analysis for eagle-i-tuskegee took 1.7679779529571533s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 3.886222839355469e-05s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.17693161964416504s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.965896606445312e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 9.775161743164062e-06s
INFO | --- Analysis for eagle-i-uccaribe took 1.801079273223877s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 3.981590270996094e-05s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.16717076301574707s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0001239776611328125s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-upr took 1.8033068180084229s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 4.506111145019531e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.15351080894470215s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 5.9604644775390625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.5020370483398438e-05s
INFO | --- Analysis for eagle-i-utep took 1.7928807735443115s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 8.344650268554688e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.16533493995666504s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.818771362304688e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-utsa took 1.8025548458099365s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 8.416175842285156e-05s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.15950679779052734s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.012222290039062e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 1.7754125595092773s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 8.678436279296875e-05s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.15999341011047363s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.022370338439941406s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007181167602539062s
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.2636184692382812e-05s
INFO | --- Analysis for eagle-i-xula took 1.7768590450286865s
Availability | SPARQL endpoint availability check for Emergency situation took 8.344650268554688e-05s
Availability | VoID file availability check for Emergency situation took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.15923118591308594s
Reputation | Calculation of the PageRank for Emergency situation took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 5.1021575927734375e-05s
Believability | Calculation of trust value for Emergency situation took 1.0013580322265625e-05s
INFO | --- Analysis for Earthquake took 1.766127586364746s
Availability | SPARQL endpoint availability check for ESO took 4.1484832763671875e-05s
Availability | VoID file availability check for ESO took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for ESO took 0.1614818572998047s
Reputation | Calculation of the PageRank for ESO took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for ESO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ESO took 8.535385131835938e-05s
Believability | Calculation of trust value for ESO took 1.049041748046875e-05s
INFO | --- Analysis for Earthquake_case took 1.7443807125091553s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 6.628036499023438e-05s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.15857815742492676s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010776519775390625s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for ecb-linked-data took 1.8198974132537842s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 8.392333984375e-05s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.15757989883422852s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.021702051162719727s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.1961669921875e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 1.4543533325195312e-05s
INFO | --- Analysis for ecb-statistics-linked-data took 1.7706048488616943s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.4574344158172607s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.1648874282836914s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020931720733642578s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 7.200241088867188e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 4.068969011306763s
Availability | SPARQL endpoint availability check for ECLAP took 20.47944474220276s
Availability | VoID file availability check for ECLAP took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for ECLAP took 0.15750575065612793s
Reputation | Calculation of the PageRank for ECLAP took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.0531158447265625e-05s
Believability | Calculation of trust value for ECLAP took 9.5367431640625e-06s
INFO | --- Analysis for eclap took 52.28779435157776s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 8.177757263183594e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.16357040405273438s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.021697044372558594s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.2159347534179688e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.049041748046875e-05s
INFO | --- Analysis for ECNU-GISer took 1.767035961151123s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.00543212890625e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0002014636993408203s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.16040587425231934s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.021294593811035156s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.412101745605469e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.1682510375976562e-05s
INFO | --- Analysis for ecs took 1.760662317276001s
Availability | SPARQL endpoint availability check for Edublogs took 8.177757263183594e-05s
Availability | VoID file availability check for Edublogs took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Edublogs took 0.16010522842407227s
Reputation | Calculation of the PageRank for Edublogs took 0.020762920379638672s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010204315185546875s
Believability | Calculation of trust value for Edublogs took 1.3113021850585938e-05s
INFO | --- Analysis for edublogs took 1.73506498336792s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 8.320808410644531e-05s
Availability | VoID file availability check for education.data.gov.uk took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.16092538833618164s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02153491973876953s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.845329284667969e-05s
Believability | Calculation of trust value for education.data.gov.uk took 9.5367431640625e-06s
INFO | --- Analysis for education-data-gov-uk took 1.77994704246521s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 4.0531158447265625e-05s
Availability | VoID file availability check for Educational programs - SISVU took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.1583082675933838s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 4.601478576660156e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.049041748046875e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1.7260448932647705s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 8.344650268554688e-05s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0004062652587890625s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.15090513229370117s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.981590270996094e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 1.2636184692382812e-05s
INFO | --- Analysis for eea took 1.7183055877685547s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 5.3882598876953125e-05s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.15191245079040527s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.02205801010131836s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.245208740234375e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.245208740234375e-06s
INFO | --- Analysis for eea-rod took 1.7448484897613525s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 8.058547973632812e-05s
Availability | VoID file availability check for EEA Vocabularies took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.15525102615356445s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.082389831542969e-05s
Believability | Calculation of trust value for EEA Vocabularies took 7.62939453125e-06s
INFO | --- Analysis for eea-vocabularies took 1.738506555557251s
Availability | SPARQL endpoint availability check for E-Government Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for E-Government Ontology took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.15503859519958496s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.021335840225219727s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.4809112548828125e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.33514404296875e-05s
INFO | --- Analysis for EGovOntology took 1.8096632957458496s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 8.130073547363281e-05s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.15147781372070312s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.020700931549072266s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 4.553794860839844e-05s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 1.049041748046875e-05s
INFO | --- Analysis for ei2a took 1.755922794342041s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.363059997558594e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.15936803817749023s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.021799564361572266s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.0001068115234375s
Believability | Calculation of trust value for EIONET RDF Data took 1.33514404296875e-05s
INFO | --- Analysis for eionet-rdf took 1.7448091506958008s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 9.1552734375e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.15723180770874023s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.02169656753540039s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.4809112548828125e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.1920928955078125e-05s
INFO | --- Analysis for ElgooG_ took 1.865053653717041s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.15874695777893066s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.653236389160156e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.3828277587890625e-05s
INFO | --- Analysis for elviajero took 1.7329075336456299s
Availability | SPARQL endpoint availability check for EMN took 6.532669067382812e-05s
Availability | VoID file availability check for EMN took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for EMN took 0.1643683910369873s
Reputation | Calculation of the PageRank for EMN took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for EMN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for EMN took 4.100799560546875e-05s
Believability | Calculation of trust value for EMN took 1.2636184692382812e-05s
INFO | --- Analysis for emn took 1.751636028289795s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 8.296966552734375e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0002155303955078125s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.15481042861938477s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.022483348846435547s
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.000720977783203125s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.221366882324219e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 9.775161743164062e-06s
INFO | --- Analysis for enakting-co2emission took 1.7614827156066895s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 8.344650268554688e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0002048015594482422s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.1595914363861084s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02076578140258789s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.3392181396484375e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for enakting-crime took 1.8245482444763184s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 8.130073547363281e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.15811514854431152s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.1484832763671875e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 1.049041748046875e-05s
INFO | --- Analysis for enakting-energy took 1.736586570739746s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 8.034706115722656e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.15886521339416504s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.02213263511657715s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 0.00010824203491210938s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 9.775161743164062e-06s
INFO | --- Analysis for enakting-mortality took 1.7680940628051758s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.029273986816406e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.15872836112976074s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.933906555175781e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for enakting-nhs took 1.7631664276123047s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 8.058547973632812e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.15706253051757812s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020479202270507812s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.316734313964844e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for enakting-population took 1.8252696990966797s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.8772573471069336s
Availability | VoID file availability check for English Heritage Periods List took 0.0005102157592773438s
Extra | Recovery of all triples for English Heritage Periods List took 0.3587319850921631s
Performance | Total latancy measurement for English Heritage Periods List took 1.4256877899169922s
Amount of data | Number of triples check for English Heritage Periods List took 0.4347846508026123s
Versatility | Languages check for English Heritage Periods List took 0.2564866542816162s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.45331287384033203s
Security | Check HTTPS for English Heritage Periods List took 0.19206452369689941s
Interpretability | RDF structures check for English Heritage Periods List took 0.2509183883666992s
Versatility | Serialization formats check for English Heritage Periods List took 0.4446096420288086s
Availability | RDF dump link check for English Heritage Periods List took 0.28737401962280273s
License | MR license check for English Heritage Periods List took 0.40802884101867676s
License | HR license check for English Heritage Periods List took 0.3101370334625244s
Amount of data | Number of property check for English Heritage Periods List took 0.33955883979797363s
Understandability | Number of label check for English Heritage Periods List took 0.4189419746398926s
Understandability | URI regex check for English Heritage Periods List took 0.5589585304260254s
Understandability | Vocabs check for English Heritage Periods List took 0.3416101932525635s
Verifiability | Authors check for English Heritage Periods List took 0.3448014259338379s
Verifiability | Publishers check for English Heritage Periods List took 0.3111705780029297s
Performance | Throughput check for English Heritage Periods List took 11.567251920700073s
Amount of data | Check the number of entities for English Heritage Periods List took 6.961822509765625e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.31392741203308105s
Interlinking | sameAs chians check for English Heritage Periods List took 0.29926323890686035s
Interlinking | skos check for English Heritage Periods List took 0.3079676628112793s
Interlinking | skos check for English Heritage Periods List took 0.28939270973205566s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.3927905559539795s
Currency | Creation date check for English Heritage Periods List took 0.6057560443878174s
Currency | Modification date check for English Heritage Periods List took 0.6377551555633545s
Rep.Conc. | URIs length for English Heritage Periods List took 0.5897359848022461s
Interoperability | New vocabularies check for English Heritage Periods List took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.3077878952026367s
Accuracy | Check Functional Property for English Heritage Periods List took 0.30876851081848145s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3848230838775635s
Consistency | Disjoint class check for English Heritage Periods List took 0.2951958179473877s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3247051239013672s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6392207145690918s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00014281272888183594s
Security | Sign check for English Heritage Periods List took 0.30974841117858887s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.17324519157409668s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.022026777267456055s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.291534423828125e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 9.059906005859375e-06s
INFO | --- Analysis for english-heritage-periods-list took 44.271947622299194s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 4.172325134277344e-05s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.1771256923675537s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020963668823242188s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.552436828613281e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 1.0967254638671875e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 1.8197999000549316s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 4.076957702636719e-05s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.15310120582580566s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.504753112792969e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 1.0013580322265625e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 1.7187674045562744s
Availability | SPARQL endpoint availability check for English WordNet took 4.100799560546875e-05s
Availability | VoID file availability check for English WordNet took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for English WordNet took 0.14964890480041504s
Reputation | Calculation of the PageRank for English WordNet took 0.021326541900634766s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.528594970703125e-05s
Believability | Calculation of trust value for English WordNet took 1.33514404296875e-05s
INFO | --- Analysis for english-wordnet took 1.7730529308319092s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 8.225440979003906e-05s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.1626734733581543s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.024257421493530273s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.250640869140625e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.2636184692382812e-05s
INFO | --- Analysis for enipedia took 1.813096284866333s
Availability | SPARQL endpoint availability check for Enslaved.org took 0.00016498565673828125s
Availability | VoID file availability check for Enslaved.org took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.16899991035461426s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02354598045349121s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.001199960708618164s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 4.0531158447265625e-05s
Believability | Calculation of trust value for Enslaved.org took 1.239776611328125e-05s
INFO | --- Analysis for enslaved.org took 2.6222290992736816s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 8.296966552734375e-05s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.15534615516662598s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.14984130859375e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for entice-graph took 1.8371706008911133s
Availability | SPARQL endpoint availability check for Entrez Gene took 3.981590270996094e-05s
Availability | VoID file availability check for Entrez Gene took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.17271709442138672s
Reputation | Calculation of the PageRank for Entrez Gene took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.647804260253906e-05s
Believability | Calculation of trust value for Entrez Gene took 1.3589859008789062e-05s
INFO | --- Analysis for entrez_gene took 1.8060290813446045s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 6.67572021484375e-05s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.16362214088439941s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.022272586822509766s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.316734313964844e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 1.1920928955078125e-05s
INFO | --- Analysis for environment-agency-bathing-water-quality took 1.7572665214538574s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 9.179115295410156e-05s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.15458130836486816s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.021086931228637695s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.839897155761719e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 1.049041748046875e-05s
INFO | --- Analysis for environment-data-gov-uk took 1.7574305534362793s
Availability | SPARQL endpoint availability check for EARTh took 6.4849853515625e-05s
Availability | VoID file availability check for EARTh took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for EARTh took 0.17811799049377441s
Reputation | Calculation of the PageRank for EARTh took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for EARTh took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.369850158691406e-05s
Believability | Calculation of trust value for EARTh took 1.1205673217773438e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 1.7743704319000244s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 4.0531158447265625e-05s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.15854191780090332s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.0040740966796875e-05s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for EO_metadata took 1.7511382102966309s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.076957702636719e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.15683269500732422s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.361701965332031e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.0967254638671875e-05s
INFO | --- Analysis for EOKP-Datasets took 1.7456486225128174s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.124641418457031e-05s
Availability | VoID file availability check for EPA-CDR took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.16430163383483887s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.8623809814453125e-05s
Believability | Calculation of trust value for EPA-CDR took 1.0251998901367188e-05s
INFO | --- Analysis for epa-cdr took 1.733795404434204s
Availability | SPARQL endpoint availability check for EPA-FRS took 0.00010919570922851562s
Availability | VoID file availability check for EPA-FRS took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.15337228775024414s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02200460433959961s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.677078247070312e-05s
Believability | Calculation of trust value for EPA-FRS took 1.0013580322265625e-05s
INFO | --- Analysis for epa-frs took 1.7187309265136719s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.100799560546875e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.15271472930908203s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.02060079574584961s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.552436828613281e-05s
Believability | Calculation of trust value for EPA-RCRA took 1.0251998901367188e-05s
INFO | --- Analysis for epa-rcra took 1.7277452945709229s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.1484832763671875e-05s
Availability | VoID file availability check for EPA-SRS took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.152968168258667s
Reputation | Calculation of the PageRank for EPA-SRS took 0.021254301071166992s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.653236389160156e-05s
Believability | Calculation of trust value for EPA-SRS took 9.775161743164062e-06s
INFO | --- Analysis for epa-srs took 1.82918381690979s
Availability | SPARQL endpoint availability check for EPA-TRI took 8.034706115722656e-05s
Availability | VoID file availability check for EPA-TRI took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.1615431308746338s
Reputation | Calculation of the PageRank for EPA-TRI took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.528594970703125e-05s
Believability | Calculation of trust value for EPA-TRI took 1.2874603271484375e-05s
INFO | --- Analysis for epa-tri took 1.7749948501586914s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.16361379623413086s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001266002655029297s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 1.7675526142120361s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 8.177757263183594e-05s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.15937042236328125s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 7.987022399902344e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.1682510375976562e-05s
INFO | --- Analysis for eprtr took 1.7443411350250244s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 8.20159912109375e-05s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.15571165084838867s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.02221512794494629s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0009016990661621094s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.6716461181640625e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.1444091796875e-05s
INFO | --- Analysis for ERAKG took 1.7594232559204102s
Availability | SPARQL endpoint availability check for reg took 4.220008850097656e-05s
Availability | VoID file availability check for reg took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for reg took 0.16433167457580566s
Reputation | Calculation of the PageRank for reg took 0.021254777908325195s
Interlinking | Calculation of Degree of Connection for reg took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for reg took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for reg took 1.2636184692382812e-05s
Believability | Calculation of trust value for reg took 1.2159347534179688e-05s
INFO | --- Analysis for erg took 1.7672929763793945s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 8.153915405273438e-05s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.1635279655456543s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020440340042114258s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.743171691894531e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 1.0013580322265625e-05s
INFO | --- Analysis for es-msssi-drug-prices took 1.7519214153289795s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 8.177757263183594e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.00020575523376464844s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.1545703411102295s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.726119995117188e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 1.1920928955078125e-05s
INFO | --- Analysis for esd-standards took 1.752094030380249s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 0.000110626220703125s
Availability | VoID file availability check for ESD-Toolkit took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.16530823707580566s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.021182537078857422s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.43865966796875e-05s
Believability | Calculation of trust value for ESD-Toolkit took 1.0013580322265625e-05s
INFO | --- Analysis for esd-toolkit took 1.7556076049804688s
Availability | SPARQL endpoint availability check for Dataset Esis took 8.7738037109375e-05s
Availability | VoID file availability check for Dataset Esis took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.15919709205627441s
Reputation | Calculation of the PageRank for Dataset Esis took 0.022168874740600586s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.24249267578125e-05s
Believability | Calculation of trust value for Dataset Esis took 1.3589859008789062e-05s
INFO | --- Analysis for esislearning took 1.7470245361328125s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.076957702636719e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.1530618667602539s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.021755695343017578s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.3855438232421875e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 9.775161743164062e-06s
INFO | --- Analysis for ESV took 1.7392661571502686s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 4.267692565917969e-05s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.1575005054473877s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02230978012084961s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 9.5367431640625e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 1.7817914485931396s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 3.933906555175781e-05s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.15329217910766602s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.390975952148438e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 5.4836273193359375e-06s
INFO | --- Analysis for eu-agencies-bodies took 1.721078872680664s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.058547973632812e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.160719633102417s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.02234673500061035s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.414817810058594e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 1.0013580322265625e-05s
INFO | --- Analysis for eu-institutions took 1.7639825344085693s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 7.915496826171875e-05s
Availability | VoID file availability check for EU Parliament Media Library took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.15328669548034668s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.021481037139892578s
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.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.838539123535156e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 1.0251998901367188e-05s
INFO | --- Analysis for eu-parliament-media took 1.773667335510254s
Availability | SPARQL endpoint availability check for EU Who Is Who took 6.389617919921875e-05s
Availability | VoID file availability check for EU Who Is Who took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.16213679313659668s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.695487976074219e-05s
Believability | Calculation of trust value for EU Who Is Who took 1.0728836059570312e-05s
INFO | --- Analysis for eu-who-is-who took 1.8536126613616943s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 3.981590270996094e-05s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.1593036651611328s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020381927490234375s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.124641418457031e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for eumida-linked-data took 1.7881152629852295s
Availability | SPARQL endpoint availability check for European Nature Information System took 8.296966552734375e-05s
Availability | VoID file availability check for European Nature Information System took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.1679978370666504s
Reputation | Calculation of the PageRank for European Nature Information System took 0.021643638610839844s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010633468627929688s
Believability | Calculation of trust value for European Nature Information System took 1.049041748046875e-05s
INFO | --- Analysis for eunis took 1.8054735660552979s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 8.130073547363281e-05s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.1646108627319336s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.128715515136719e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for eur-lex-rdf took 1.728125810623169s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 8.177757263183594e-05s
Availability | VoID file availability check for Standard Eurobarometer took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.17146039009094238s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.021857738494873047s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.863739013671875e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 1.0251998901367188e-05s
INFO | --- Analysis for eurobarometer-standard took 1.7402386665344238s
Availability | SPARQL endpoint availability check for European Election Results took 4.00543212890625e-05s
Availability | VoID file availability check for European Election Results took 0.0002048015594482422s
Completeness | Calculation of interlinking completeness for European Election Results took 0.15054726600646973s
Reputation | Calculation of the PageRank for European Election Results took 0.021993398666381836s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.647804260253906e-05s
Believability | Calculation of trust value for European Election Results took 1.0013580322265625e-05s
INFO | --- Analysis for european-election-results took 1.743445634841919s
Availability | SPARQL endpoint availability check for EPO patents took 8.988380432128906e-05s
Availability | VoID file availability check for EPO patents took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for EPO patents took 0.1585402488708496s
Reputation | Calculation of the PageRank for EPO patents took 0.020360708236694336s
Interlinking | Calculation of Degree of Connection for EPO patents took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPO patents took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for EPO patents took 3.719329833984375e-05s
Believability | Calculation of trust value for EPO patents took 6.198883056640625e-06s
INFO | --- Analysis for European_Patent_Information took 1.7689478397369385s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.220008850097656e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.15267300605773926s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02118515968322754s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.512901306152344e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 9.298324584960938e-06s
INFO | --- Analysis for europeana-lod-v1 took 1.8079731464385986s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.34727907180786133s
Availability | VoID file availability check for Europeana SPARQL took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.15773963928222656s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.02203083038330078s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.316734313964844e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.0013580322265625e-05s
INFO | --- Analysis for europeana-sparql took 2.552877902984619s
Availability | SPARQL endpoint availability check for EuroSentiment took 8.082389831542969e-05s
Availability | VoID file availability check for EuroSentiment took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.16000819206237793s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.9577484130859375e-05s
Believability | Calculation of trust value for EuroSentiment took 1.1682510375976562e-05s
INFO | --- Analysis for eurosentiment took 1.7727611064910889s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 7.987022399902344e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.15591907501220703s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.02198195457458496s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.748603820800781e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.7220458984375e-06s
INFO | --- Analysis for eurostat-rdf took 1.7427165508270264s
Availability | SPARQL endpoint availability check for EuroVoc took 4.0531158447265625e-05s
Availability | VoID file availability check for EuroVoc took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.15314865112304688s
Reputation | Calculation of the PageRank for EuroVoc took 0.020273208618164062s
Interlinking | Calculation of Degree of Connection for EuroVoc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 6.818771362304688e-05s
Believability | Calculation of trust value for EuroVoc took 1.0251998901367188e-05s
INFO | --- Analysis for eurovoc took 1.7629163265228271s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 3.886222839355469e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.15425443649291992s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.022333145141601562s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.649162292480469e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 9.059906005859375e-06s
INFO | --- Analysis for euskadi-farmacias took 1.7278261184692383s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 4.029273986816406e-05s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0002071857452392578s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.17976164817810059s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 2.8371810913085938e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 9.5367431640625e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 1.769115924835205s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 8.130073547363281e-05s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.1545722484588623s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.200241088867188e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.2874603271484375e-05s
INFO | --- Analysis for eutc-productions took 1.7524142265319824s
Availability | SPARQL endpoint availability check for EventMedia took 0.32544684410095215s
Availability | VoID file availability check for EventMedia took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for EventMedia took 0.16211390495300293s
Reputation | Calculation of the PageRank for EventMedia took 0.02205181121826172s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010776519775390625s
Believability | Calculation of trust value for EventMedia took 4.291534423828125e-06s
INFO | --- Analysis for event-media took 2.341191530227661s
Availability | SPARQL endpoint availability check for EventKG took 4.3392181396484375e-05s
Availability | VoID file availability check for EventKG took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for EventKG took 0.1691570281982422s
Reputation | Calculation of the PageRank for EventKG took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for EventKG took 9.131431579589844e-05s
Believability | Calculation of trust value for EventKG took 1.1682510375976562e-05s
INFO | --- Analysis for eventkg took 3.1277999877929688s
Availability | SPARQL endpoint availability check for Eventseer took 4.1484832763671875e-05s
Availability | VoID file availability check for Eventseer took 0.00020194053649902344s
Completeness | Calculation of interlinking completeness for Eventseer took 0.1496448516845703s
Reputation | Calculation of the PageRank for Eventseer took 0.022443771362304688s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.792213439941406e-05s
Believability | Calculation of trust value for Eventseer took 1.239776611328125e-05s
INFO | --- Analysis for eventseer took 1.6927828788757324s
Availability | SPARQL endpoint availability check for Face Link took 6.67572021484375e-05s
Availability | VoID file availability check for Face Link took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Face Link took 0.16605758666992188s
Reputation | Calculation of the PageRank for Face Link took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Face Link took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.361701965332031e-05s
Believability | Calculation of trust value for Face Link took 1.3113021850585938e-05s
INFO | --- Analysis for Face_Link took 1.7495667934417725s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.153915405273438e-05s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1692180633544922s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.022466659545898438s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0010666847229003906s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.890296936035156e-05s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for FADN_(2019) took 1.7869904041290283s
Availability | SPARQL endpoint availability check for FAMEData took 4.1484832763671875e-05s
Availability | VoID file availability check for FAMEData took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for FAMEData took 0.1531543731689453s
Reputation | Calculation of the PageRank for FAMEData took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for FAMEData took 2.8848648071289062e-05s
Believability | Calculation of trust value for FAMEData took 1.239776611328125e-05s
INFO | --- Analysis for famedata took 1.7428276538848877s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 8.392333984375e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.16036462783813477s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020250558853149414s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.584426879882812e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 1.1444091796875e-05s
INFO | --- Analysis for fao-geopolitical-ontology took 1.7775940895080566s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 8.392333984375e-05s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.1526334285736084s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0211944580078125s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010132789611816406s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for fao-linked-data took 1.751218318939209s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.410743713378906e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.15267586708068848s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.022376060485839844s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.0994415283203125e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.2636184692382812e-05s
INFO | --- Analysis for FAO_species took 1.728008508682251s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 8.416175842285156e-05s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.16121196746826172s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02111339569091797s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007135868072509766s
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 1.7594592571258545s
Availability | SPARQL endpoint availability check for I4.0-Onto took 8.177757263183594e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.15850090980529785s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.021448135375976562s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.0040740966796875e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.2159347534179688e-05s
INFO | --- Analysis for fatimazahra took 1.7533581256866455s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.1484832763671875e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.15097999572753906s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.956390380859375e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.2159347534179688e-05s
INFO | --- Analysis for FHIR_STU3 took 1.7443737983703613s
Availability | SPARQL endpoint availability check for FiESTA took 4.1961669921875e-05s
Availability | VoID file availability check for FiESTA took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for FiESTA took 0.15202069282531738s
Reputation | Calculation of the PageRank for FiESTA took 0.0218961238861084s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.981590270996094e-05s
Believability | Calculation of trust value for FiESTA took 5.9604644775390625e-06s
INFO | --- Analysis for fiesta took 1.7517602443695068s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.225440979003906e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.16071176528930664s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.075599670410156e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.775161743164062e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 1.7718572616577148s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 8.20159912109375e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.1635432243347168s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.771087646484375e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 1.0013580322265625e-05s
INFO | --- Analysis for finnish-municipalities took 1.7233390808105469s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 4.2438507080078125e-05s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.15600109100341797s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.022572755813598633s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.528594970703125e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 1.7312695980072021s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.124641418457031e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.1547098159790039s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.225440979003906e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.0013580322265625e-05s
INFO | --- Analysis for fishes-of-texas took 1.7406489849090576s
Availability | SPARQL endpoint availability check for flickr? wrappr took 6.508827209472656e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.16477274894714355s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.489059448242188e-05s
Believability | Calculation of trust value for flickr? wrappr took 1.0013580322265625e-05s
INFO | --- Analysis for flickr-wrappr took 1.749100685119629s
Availability | SPARQL endpoint availability check for Future land use simulation model took 8.440017700195312e-05s
Availability | VoID file availability check for Future land use simulation model took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.16368484497070312s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.021575450897216797s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.337860107421875e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.0967254638671875e-05s
INFO | --- Analysis for FLUS took 1.7582979202270508s
Availability | SPARQL endpoint availability check for Flybase took 4.744529724121094e-05s
Availability | VoID file availability check for Flybase took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Flybase took 0.16334867477416992s
Reputation | Calculation of the PageRank for Flybase took 0.02141737937927246s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.5762786865234375e-05s
Believability | Calculation of trust value for Flybase took 1.0967254638671875e-05s
INFO | --- Analysis for flybase took 1.7464964389801025s
Availability | SPARQL endpoint availability check for Flyted took 4.0531158447265625e-05s
Availability | VoID file availability check for Flyted took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for Flyted took 0.1630110740661621s
Reputation | Calculation of the PageRank for Flyted took 0.022147655487060547s
Interlinking | Calculation of Degree of Connection for Flyted took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.0517578125e-05s
Believability | Calculation of trust value for Flyted took 1.049041748046875e-05s
INFO | --- Analysis for flyted took 1.761765956878662s
Availability | SPARQL endpoint availability check for Foodista took 8.225440979003906e-05s
Availability | VoID file availability check for Foodista took 0.00041794776916503906s
Completeness | Calculation of interlinking completeness for Foodista took 0.15235185623168945s
Reputation | Calculation of the PageRank for Foodista took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for Foodista took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9087066650390625e-05s
Believability | Calculation of trust value for Foodista took 1.1920928955078125e-05s
INFO | --- Analysis for foodista took 1.7511894702911377s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 8.440017700195312e-05s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.15129518508911133s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0216214656829834s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.05718994140625e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 8.106231689453125e-06s
INFO | --- Analysis for foodpedia took 1.7647390365600586s
Availability | SPARQL endpoint availability check for FrameBase schema took 6.437301635742188e-05s
Availability | VoID file availability check for FrameBase schema took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.16532421112060547s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020976543426513672s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.57763671875e-05s
Believability | Calculation of trust value for FrameBase schema took 1.2159347534179688e-05s
INFO | --- Analysis for framebase-schema took 1.7843594551086426s
Availability | SPARQL endpoint availability check for Framester took 8.20159912109375e-05s
Availability | VoID file availability check for Framester took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Framester took 0.16124248504638672s
Reputation | Calculation of the PageRank for Framester took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for Framester took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Framester took 7.486343383789062e-05s
Believability | Calculation of trust value for Framester took 1.2636184692382812e-05s
INFO | --- Analysis for framester took 1.7620134353637695s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 8.726119995117188e-05s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.1630859375s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0009992122650146484s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 0.00010800361633300781s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for frb-linked-data took 1.753523588180542s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 4.267692565917969e-05s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.15004205703735352s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.0002665519714355469s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.1920928955078125e-05s
INFO | --- Analysis for freebase took 1.7409989833831787s
Availability | SPARQL endpoint availability check for Freeyork took 8.368492126464844e-05s
Availability | VoID file availability check for Freeyork took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Freeyork took 0.15825653076171875s
Reputation | Calculation of the PageRank for Freeyork took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010466575622558594s
Believability | Calculation of trust value for Freeyork took 1.1920928955078125e-05s
INFO | --- Analysis for freeyork-org took 1.7966208457946777s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 8.320808410644531e-05s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.1742703914642334s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.390975952148438e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-cordis took 1.7983205318450928s
Availability | SPARQL endpoint availability check for DailyMed took 4.1484832763671875e-05s
Availability | VoID file availability check for DailyMed took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for DailyMed took 0.1688861846923828s
Reputation | Calculation of the PageRank for DailyMed took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00011467933654785156s
Believability | Calculation of trust value for DailyMed took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-dailymed took 1.7416906356811523s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 8.440017700195312e-05s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.15411901473999023s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.021636247634887695s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.630752563476562e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-dblp took 1.7392592430114746s
Availability | SPARQL endpoint availability check for Diseasome took 4.172325134277344e-05s
Availability | VoID file availability check for Diseasome took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Diseasome took 0.16257524490356445s
Reputation | Calculation of the PageRank for Diseasome took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011181831359863281s
Believability | Calculation of trust value for Diseasome took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-diseasome took 1.7586348056793213s
Availability | SPARQL endpoint availability check for DrugBank took 0.00010323524475097656s
Availability | VoID file availability check for DrugBank took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for DrugBank took 0.1597576141357422s
Reputation | Calculation of the PageRank for DrugBank took 0.022089719772338867s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011324882507324219s
Believability | Calculation of trust value for DrugBank took 1.2874603271484375e-05s
INFO | --- Analysis for fu-berlin-drugbank took 1.7499110698699951s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 6.508827209472656e-05s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.15283608436584473s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020981311798095703s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.170967102050781e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.0251998901367188e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 1.7343699932098389s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 4.100799560546875e-05s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.15604662895202637s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.021258831024169922s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.2479248046875e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 1.0013580322265625e-05s
INFO | --- Analysis for fu-berlin-euraxess took 1.7316834926605225s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 3.981590270996094e-05s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.15439844131469727s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.0204925537109375s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.176399230957031e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 9.775161743164062e-06s
INFO | --- Analysis for fu-berlin-eures took 1.722672700881958s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 4.029273986816406e-05s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.16466665267944336s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.417533874511719e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 1.7535715103149414s
Availability | SPARQL endpoint availability check for MediCare took 4.0531158447265625e-05s
Availability | VoID file availability check for MediCare took 0.0004146099090576172s
Completeness | Calculation of interlinking completeness for MediCare took 0.15860724449157715s
Reputation | Calculation of the PageRank for MediCare took 0.0216829776763916s
Interlinking | Calculation of Degree of Connection for MediCare took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.2438507080078125e-05s
Believability | Calculation of trust value for MediCare took 1.0013580322265625e-05s
INFO | --- Analysis for fu-berlin-medicare took 1.7310872077941895s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 8.153915405273438e-05s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.1526784896850586s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.022203922271728516s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.319450378417969e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 9.5367431640625e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 1.7602345943450928s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 7.891654968261719e-05s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0004131793975830078s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.1532578468322754s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.274482727050781e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.0251998901367188e-05s
INFO | --- Analysis for fu-berlin-sider took 1.7523672580718994s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 8.344650268554688e-05s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.15177178382873535s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.02118825912475586s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.557868957519531e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.1682510375976562e-05s
INFO | --- Analysis for fu-berlin-stitch took 1.7539763450622559s
Availability | SPARQL endpoint availability check for fvdb took 4.172325134277344e-05s
Availability | VoID file availability check for fvdb took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for fvdb took 0.16352224349975586s
Reputation | Calculation of the PageRank for fvdb took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for fvdb took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.9087066650390625e-05s
Believability | Calculation of trust value for fvdb took 1.1920928955078125e-05s
INFO | --- Analysis for fv took 1.8631384372711182s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.1484832763671875e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.15398335456848145s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.022766828536987305s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.9325485229492188e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.2636184692382812e-05s
INFO | --- Analysis for GACS took 1.7432427406311035s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 8.535385131835938e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.16857481002807617s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020335912704467773s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.933906555175781e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.239776611328125e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 1.7361886501312256s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 8.344650268554688e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.16471266746520996s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010371208190917969s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 5.4836273193359375e-06s
INFO | --- Analysis for garnicaplywood took 1.8029415607452393s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00010323524475097656s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.14674162864685059s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020658493041992188s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.584426879882812e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.0251998901367188e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 1.7353217601776123s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 8.058547973632812e-05s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.15384960174560547s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.02233409881591797s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 8.96453857421875e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.049041748046875e-05s
INFO | --- Analysis for gemet took 1.7458720207214355s
Availability | SPARQL endpoint availability check for gemet-annotated took 8.320808410644531e-05s
Availability | VoID file availability check for gemet-annotated took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.1579148769378662s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020503759384155273s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.647804260253906e-05s
Believability | Calculation of trust value for gemet-annotated took 1.0728836059570312e-05s
INFO | --- Analysis for gemet-annotated took 1.7488088607788086s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 4.00543212890625e-05s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.15916156768798828s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.022656917572021484s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.933906555175781e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.0967254638671875e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 1.7840335369110107s
Availability | SPARQL endpoint availability check for Super Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Super Ontology took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.16089391708374023s
Reputation | Calculation of the PageRank for Super Ontology took 0.022256135940551758s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Super Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 1.7325749397277832s
Availability | SPARQL endpoint availability check for Geographic detector model took 8.392333984375e-05s
Availability | VoID file availability check for Geographic detector model took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.16110467910766602s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 2.9802322387695312e-05s
Believability | Calculation of trust value for Geographic detector model took 1.239776611328125e-05s
INFO | --- Analysis for GeoDetector took 1.8121263980865479s
Availability | SPARQL endpoint availability check for geodomainwn took 8.296966552734375e-05s
Availability | VoID file availability check for geodomainwn took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.1541595458984375s
Reputation | Calculation of the PageRank for geodomainwn took 0.0214846134185791s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.696846008300781e-05s
Believability | Calculation of trust value for geodomainwn took 1.2874603271484375e-05s
INFO | --- Analysis for geodomainwn took 1.74690842628479s
Availability | SPARQL endpoint availability check for GeoEcuador took 8.296966552734375e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.16284871101379395s
Reputation | Calculation of the PageRank for GeoEcuador took 0.022162914276123047s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0011138916015625s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 8.463859558105469e-05s
Believability | Calculation of trust value for GeoEcuador took 6.9141387939453125e-06s
INFO | --- Analysis for geoecuador took 1.850029468536377s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.1247687339782715s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.16500401496887207s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.02209782600402832s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.67572021484375e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.1920928955078125e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 6.329364061355591s
Availability | SPARQL endpoint availability check for GeoLinkedData took 8.869171142578125e-05s
Availability | VoID file availability check for GeoLinkedData took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.1544942855834961s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.0200650691986084s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.320808410644531e-05s
Believability | Calculation of trust value for GeoLinkedData took 1.2874603271484375e-05s
INFO | --- Analysis for geolinkeddata took 1.7169811725616455s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 8.082389831542969e-05s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.15821027755737305s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.022423267364501953s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 7.891654968261719e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 9.5367431640625e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 1.7328462600708008s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 8.630752563476562e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.1527872085571289s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.021828889846801758s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004801750183105469s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.1682510375976562e-05s
INFO | --- Analysis for geonames-semantic-web took 1.7331817150115967s
Availability | SPARQL endpoint availability check for Geospatial World  took 7.987022399902344e-05s
Availability | VoID file availability check for Geospatial World  took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.15258121490478516s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010204315185546875s
Believability | Calculation of trust value for Geospatial World  took 9.5367431640625e-06s
INFO | --- Analysis for geospatialworld-net took 1.7921411991119385s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 7.343292236328125e-05s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.1589064598083496s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.02097344398498535s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.0001392364501953125s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.239776611328125e-05s
INFO | --- Analysis for geospecies took 1.7543201446533203s
Availability | SPARQL endpoint availability check for GeoWordNet took 8.273124694824219e-05s
Availability | VoID file availability check for GeoWordNet took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.17728686332702637s
Reputation | Calculation of the PageRank for GeoWordNet took 0.021106719970703125s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.030632019042969e-05s
Believability | Calculation of trust value for GeoWordNet took 8.58306884765625e-06s
INFO | --- Analysis for geowordnet took 1.8739080429077148s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for German labor law thesaurus took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.1502695083618164s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02126169204711914s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.963180541992188e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 1.723292350769043s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.16155076026916504s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.1961669921875e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.1920928955078125e-05s
INFO | --- Analysis for germlex took 1.7474138736724854s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 4.291534423828125e-05s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.15155720710754395s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.107589721679688e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.2874603271484375e-05s
INFO | --- Analysis for gesis-thesoz took 1.7464728355407715s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.826390027999878s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.16233515739440918s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.021585941314697266s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.510185241699219e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for getty-aat took 7.162847280502319s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.7096021175384521s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.1629958152770996s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.022046566009521484s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.8650970458984375e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.1682510375976562e-05s
INFO | --- Analysis for getty-tgn took 5.189885377883911s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 4.3392181396484375e-05s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.1503911018371582s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02076244354248047s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.266334533691406e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 1.0013580322265625e-05s
INFO | --- Analysis for gipuzkoademografia took 1.7408101558685303s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 8.368492126464844e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.1557598114013672s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.170967102050781e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.0013580322265625e-05s
INFO | --- Analysis for glastonbury-2011 took 1.7237341403961182s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 8.034706115722656e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.15377330780029297s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.792213439941406e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.0728836059570312e-05s
INFO | --- Analysis for global-hunger-index-2011 took 1.7654986381530762s
Availability | SPARQL endpoint availability check for Glottolog took 4.220008850097656e-05s
Availability | VoID file availability check for Glottolog took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Glottolog took 0.15584945678710938s
Reputation | Calculation of the PageRank for Glottolog took 0.021148204803466797s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.412101745605469e-05s
Believability | Calculation of trust value for Glottolog took 8.106231689453125e-06s
INFO | --- Analysis for glottolog took 1.732193946838379s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 8.296966552734375e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.15506720542907715s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010967254638671875s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.239776611328125e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 1.7226665019989014s
Availability | SPARQL endpoint availability check for 1121 took 4.220008850097656e-05s
Availability | VoID file availability check for 1121 took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for 1121 took 0.15259265899658203s
Reputation | Calculation of the PageRank for 1121 took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for 1121 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.409385681152344e-05s
Believability | Calculation of trust value for 1121 took 1.1920928955078125e-05s
INFO | --- Analysis for God_ took 1.7745838165283203s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.1484832763671875e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.15072965621948242s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020682811737060547s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 7.891654968261719e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.1682510375976562e-05s
INFO | --- Analysis for gold took 1.8240654468536377s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 8.273124694824219e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.15427160263061523s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020833730697631836s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.842613220214844e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 8.821487426757812e-06s
INFO | --- Analysis for googleart-wrapper took 1.7465240955352783s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 3.981590270996094e-05s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.15499353408813477s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.022286415100097656s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.218650817871094e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 9.775161743164062e-06s
INFO | --- Analysis for govagribus-denmark took 1.797466516494751s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 8.225440979003906e-05s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.1575336456298828s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020926237106323242s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.487701416015625e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 1.7195334434509277s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 8.559226989746094e-05s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.15491080284118652s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.511543273925781e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 9.298324584960938e-06s
INFO | --- Analysis for govtrack took 1.79457426071167s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 9.036064147949219e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.16013097763061523s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.022760391235351562s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.008148193359375e-05s
Believability | Calculation of trust value for greek-administrative-geography took 9.059906005859375e-06s
INFO | --- Analysis for greek-administrative-geography took 1.7405486106872559s
Availability | SPARQL endpoint availability check for Greek Wordnet took 8.0108642578125e-05s
Availability | VoID file availability check for Greek Wordnet took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.15575695037841797s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020472288131713867s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.696846008300781e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.2159347534179688e-05s
INFO | --- Analysis for greek-wordnet took 1.7478594779968262s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 8.606910705566406e-05s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.15430426597595215s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.3113021850585938e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 1.0251998901367188e-05s
INFO | --- Analysis for greek_prisons_releases took 1.7572057247161865s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.7781672477722168s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.15506482124328613s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.021808624267578125s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.915496826171875e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 9.5367431640625e-06s
INFO | --- Analysis for greekchildrensartmuseum took 2.9003565311431885s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.15356850624084473s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02149367332458496s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0010395050048828125s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00012946128845214844s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 1.7765424251556396s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 7.891654968261719e-05s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00020742416381835938s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.1635727882385254s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.506111145019531e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.0728836059570312e-05s
INFO | --- Analysis for grrp took 1.7554748058319092s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 4.267692565917969e-05s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.15381431579589844s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.021279096603393555s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.961822509765625e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.4836273193359375e-06s
INFO | --- Analysis for grrt took 1.7349224090576172s
Availability | SPARQL endpoint availability check for Geological Timescale took 7.891654968261719e-05s
Availability | VoID file availability check for Geological Timescale took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.15558695793151855s
Reputation | Calculation of the PageRank for Geological Timescale took 0.021448612213134766s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 6.508827209472656e-05s
Believability | Calculation of trust value for Geological Timescale took 9.298324584960938e-06s
INFO | --- Analysis for GTS took 1.7765791416168213s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 8.0108642578125e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.15067219734191895s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 8.344650268554688e-06s
INFO | --- Analysis for GTS-ont took 1.7361688613891602s
Availability | SPARQL endpoint availability check for GUTSTOK  took 6.628036499023438e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.1547098159790039s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.1948089599609375e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.1682510375976562e-05s
INFO | --- Analysis for Guillaume_Forget took 1.7241790294647217s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.267692565917969e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0012488365173339844s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.15453362464904785s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020226716995239258s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.651878356933594e-05s
Believability | Calculation of trust value for Project Gutenberg took 9.5367431640625e-06s
INFO | --- Analysis for gutenberg took 2.69647216796875s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.029273986816406e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.19184350967407227s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.24249267578125e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 9.775161743164062e-06s
INFO | --- Analysis for gwa-ili took 1.769176721572876s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 8.320808410644531e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.1527085304260254s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.0213315486907959s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.170967102050781e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 1.0728836059570312e-05s
INFO | --- Analysis for GWR took 1.7635776996612549s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 7.939338684082031e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.18056964874267578s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.02086615562438965s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.0994415283203125e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.1205673217773438e-05s
INFO | --- Analysis for HASM took 1.784264087677002s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for HealthCare Ontology took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.1553337574005127s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.021451473236083984s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.743171691894531e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for HealthCare_Ontology took 1.741654634475708s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 7.82012939453125e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.15873241424560547s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.021112918853759766s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.103515625e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.5020370483398438e-05s
INFO | --- Analysis for heartfailure took 1.816251516342163s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.405576467514038s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.15516281127929688s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020410537719726562s
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.430511474609375e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.743171691894531e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 8.821487426757812e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 53.20483469963074s
Availability | SPARQL endpoint availability check for Hedatuz took 0.2859809398651123s
Availability | VoID file availability check for Hedatuz took 0.0010592937469482422s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.1559281349182129s
Reputation | Calculation of the PageRank for Hedatuz took 0.021225690841674805s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0010857582092285156s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 5.1021575927734375e-05s
Believability | Calculation of trust value for Hedatuz took 1.1444091796875e-05s
INFO | --- Analysis for hedatuz took 2.1924211978912354s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 8.082389831542969e-05s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.15875816345214844s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012254714965820312s
Believability | Calculation of trust value for Hellenic Fire Brigade took 1.0251998901367188e-05s
INFO | --- Analysis for hellenic-fire-brigade took 1.7619209289550781s
Availability | SPARQL endpoint availability check for Hellenic Police took 4.00543212890625e-05s
Availability | VoID file availability check for Hellenic Police took 0.0004172325134277344s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.1497201919555664s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001227855682373047s
Believability | Calculation of trust value for Hellenic Police took 1.0013580322265625e-05s
INFO | --- Analysis for hellenic-police took 1.7388262748718262s
Availability | SPARQL endpoint availability check for Hermos took 7.963180541992188e-05s
Availability | VoID file availability check for Hermos took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for Hermos took 0.1611778736114502s
Reputation | Calculation of the PageRank for Hermos took 0.022333145141601562s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.8848648071289062e-05s
Believability | Calculation of trust value for Hermos took 9.5367431640625e-06s
INFO | --- Analysis for Hermos took 1.750415325164795s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.506111145019531e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.16431879997253418s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.02158498764038086s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.123283386230469e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.1920928955078125e-05s
INFO | --- Analysis for Himanshu_Mahawar took 1.7504932880401611s
Availability | SPARQL endpoint availability check for HITO took 8.344650268554688e-05s
Availability | VoID file availability check for HITO took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for HITO took 0.1524655818939209s
Reputation | Calculation of the PageRank for HITO took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for HITO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for HITO took 7.05718994140625e-05s
Believability | Calculation of trust value for HITO took 1.0251998901367188e-05s
INFO | --- Analysis for hito took 1.7449009418487549s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 4.220008850097656e-05s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.15938973426818848s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.021715641021728516s
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.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 2.9087066650390625e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 9.5367431640625e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 1.749502420425415s
Availability | SPARQL endpoint availability check for gseg took 6.389617919921875e-05s
Availability | VoID file availability check for gseg took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for gseg took 0.14632701873779297s
Reputation | Calculation of the PageRank for gseg took 0.02036738395690918s
Interlinking | Calculation of Degree of Connection for gseg took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for gseg took 3.0517578125e-05s
Believability | Calculation of trust value for gseg took 9.5367431640625e-06s
INFO | --- Analysis for hongse took 1.797628402709961s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.4676778316497803s
Availability | VoID file availability check for COURAGE Dataset took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.153580904006958s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020252466201782227s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for COURAGE Dataset took 8.821487426757812e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 3.7372939586639404s
Availability | SPARQL endpoint availability check for RoadTrb took 4.0531158447265625e-05s
Availability | VoID file availability check for RoadTrb took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.17609882354736328s
Reputation | Calculation of the PageRank for RoadTrb took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.9802322387695312e-05s
Believability | Calculation of trust value for RoadTrb took 9.298324584960938e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 1.7403514385223389s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0004150867462158203s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.15954828262329102s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 1.7734992504119873s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 7.939338684082031e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.16230416297912598s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.956390380859375e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.3113021850585938e-05s
INFO | --- Analysis for http:pakistan.com took 1.7485558986663818s
Availability | SPARQL endpoint availability check for CEDICT took 4.1961669921875e-05s
Availability | VoID file availability check for CEDICT took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for CEDICT took 0.1530168056488037s
Reputation | Calculation of the PageRank for CEDICT took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.0040740966796875e-05s
Believability | Calculation of trust value for CEDICT took 9.5367431640625e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 1.758711338043213s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.987022399902344e-05s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004146099090576172s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.15744781494140625s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02055525779724121s
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.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.532669067382812e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.76837158203125e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 1.7377800941467285s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 7.939338684082031e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.15900707244873047s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020335912704467773s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 2.7894973754882812e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.3113021850585938e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 1.7586636543273926s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 8.440017700195312e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.15231776237487793s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.02260136604309082s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.001062154769897461s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 4.57763671875e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.33514404296875e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 1.7521393299102783s
Availability | SPARQL endpoint availability check for Soccer Dataset took 9.012222290039062e-05s
Availability | VoID file availability check for Soccer Dataset took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.15295886993408203s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020173072814941406s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for http:www.msm.com took 1.7038383483886719s
Availability | SPARQL endpoint availability check for Game Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Game Ontology took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.15887069702148438s
Reputation | Calculation of the PageRank for Game Ontology took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Game Ontology took 1.049041748046875e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 1.721891164779663s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.393692016601562e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.1607828140258789s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0013580322265625e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 1.749410629272461s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.1961669921875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00021123886108398438s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.15621232986450195s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.021230459213256836s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.075599670410156e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 5.4836273193359375e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 1.6934139728546143s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.7206878662109375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.1579596996307373s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0040740966796875e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.67572021484375e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 1.7057178020477295s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.2438507080078125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.1601099967956543s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9325485229492188e-05s
Believability | Calculation of trust value for Indian Biodiversity took 8.344650268554688e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 1.753377914428711s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.726119995117188e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.18352937698364258s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.956390380859375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1205673217773438e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 1.7772305011749268s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 6.437301635742188e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.15148615837097168s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8133392333984375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0967254638671875e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 1.7358062267303467s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.249282836914062e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.15535879135131836s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020344018936157227s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.1948089599609375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.049041748046875e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 1.7537810802459717s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 8.58306884765625e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.15132737159729004s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.673004150390625e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0251998901367188e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 1.7432036399841309s
Availability | SPARQL endpoint availability check for Bookkeeping took 8.273124694824219e-05s
Availability | VoID file availability check for Bookkeeping took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.15991902351379395s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.123283386230469e-05s
Believability | Calculation of trust value for Bookkeeping took 7.62939453125e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 1.7622060775756836s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Legal Ontology took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.161484956741333s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020463228225708008s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for Legal Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 1.71919584274292s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 8.535385131835938e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.15692377090454102s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.022022247314453125s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.557868957519531e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 9.5367431640625e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 1.7345240116119385s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 8.034706115722656e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.16314411163330078s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020266056060791016s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 2.8133392333984375e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.4543533325195312e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 1.7465927600860596s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.2078287601470947s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.16660714149475098s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010204315185546875s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.1205673217773438e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 3.356966972351074s
Availability | SPARQL endpoint availability check for IATE RDF took 4.00543212890625e-05s
Availability | VoID file availability check for IATE RDF took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.15272140502929688s
Reputation | Calculation of the PageRank for IATE RDF took 0.02269148826599121s
Interlinking | Calculation of Degree of Connection for IATE RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.266334533691406e-05s
Believability | Calculation of trust value for IATE RDF took 5.7220458984375e-06s
INFO | --- Analysis for iate-rdf took 1.756856918334961s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 8.249282836914062e-05s
Availability | VoID file availability check for IATI as Linked Data took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.15091586112976074s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02231287956237793s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.034706115722656e-05s
Believability | Calculation of trust value for IATI as Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for iati-as-linked-data took 1.7787728309631348s
Availability | SPARQL endpoint availability check for ICANE took 8.440017700195312e-05s
Availability | VoID file availability check for ICANE took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for ICANE took 0.15052533149719238s
Reputation | Calculation of the PageRank for ICANE took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for ICANE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.130073547363281e-05s
Believability | Calculation of trust value for ICANE took 1.0013580322265625e-05s
INFO | --- Analysis for icane took 1.7432506084442139s
Availability | SPARQL endpoint availability check for ichoose took 4.029273986816406e-05s
Availability | VoID file availability check for ichoose took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for ichoose took 0.15872669219970703s
Reputation | Calculation of the PageRank for ichoose took 0.022516489028930664s
Interlinking | Calculation of Degree of Connection for ichoose took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ichoose took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.127357482910156e-05s
Believability | Calculation of trust value for ichoose took 9.775161743164062e-06s
INFO | --- Analysis for ichoose took 1.6924474239349365s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 8.392333984375e-05s
Availability | VoID file availability check for The Iconology Dataset took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.153181791305542s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.1920928955078125e-05s
Believability | Calculation of trust value for The Iconology Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for iconology-dataset took 1.736053228378296s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 7.987022399902344e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.16144204139709473s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.700920104980469e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 9.775161743164062e-06s
INFO | --- Analysis for idreffr took 1.7459805011749268s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 8.153915405273438e-05s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.16800642013549805s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.078315734863281e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 9.775161743164062e-06s
INFO | --- Analysis for ids took 1.736023187637329s
Availability | SPARQL endpoint availability check for ietflang took 8.0108642578125e-05s
Availability | VoID file availability check for ietflang took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for ietflang took 0.1515214443206787s
Reputation | Calculation of the PageRank for ietflang took 0.0223848819732666s
Interlinking | Calculation of Degree of Connection for ietflang took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.482269287109375e-05s
Believability | Calculation of trust value for ietflang took 9.775161743164062e-06s
INFO | --- Analysis for ietflang took 1.7403500080108643s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 8.0108642578125e-05s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.16301608085632324s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.504753112792969e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for IGVLL took 1.7359740734100342s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.15598297119140625s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for IHE took 1.7839610576629639s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.4862589836120605s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0004706382751464844s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 7.201801300048828s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 7.882083892822266s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 19.95623230934143s
Interoperability | New terms check for Test Site, LOD Lab 317 took 8.329163789749146s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.578689098358154s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.6916224956512451s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.0562987327575684s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 1.7332382202148438s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.5952489376068115s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.591111660003662s
License | MR license check for Test Site, LOD Lab 317 took 1.681295394897461s
License | HR license check for Test Site, LOD Lab 317 took 1.8970277309417725s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.6551008224487305s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.75797438621521s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.162222146987915s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.6189515590667725s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.6230525970458984s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.6059246063232422s
Performance | Throughput check for Test Site, LOD Lab 317 took 15.784035921096802s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 6.604194641113281e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.5801029205322266s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.6120097637176514s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.6103200912475586s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.5987932682037354s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.612549066543579s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.200502395629883s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.23453950881958s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 33.51193594932556s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.5966670513153076s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.5674846172332764s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.570049524307251s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 3.1210126876831055s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.029767513275146484s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.028184890747070312s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.5688271522521973s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 23.10196828842163s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 1.9720511436462402s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 4.691923379898071s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.349574089050293s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 23.76644802093506s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.034668684005737305s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.381683111190796s
Security | Sign check for Test Site, LOD Lab 317 took 1.5903947353363037s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 9.361908435821533s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.521507978439331s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.0211944580078125s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.124641418457031e-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 9.298324584960938e-06s
INFO | --- Analysis for iislod-test took 497.08804059028625s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.1961669921875e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.16783475875854492s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020039796829223633s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.24249267578125e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 9.775161743164062e-06s
INFO | --- Analysis for ILUSOC took 1.7370362281799316s
Availability | SPARQL endpoint availability check for im@sparql took 4.887580871582031e-05s
Availability | VoID file availability check for im@sparql took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for im@sparql took 0.15158653259277344s
Reputation | Calculation of the PageRank for im@sparql took 0.02258920669555664s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.956390380859375e-05s
Believability | Calculation of trust value for im@sparql took 9.298324584960938e-06s
INFO | --- Analysis for im@sparql took 1.7695090770721436s
Availability | SPARQL endpoint availability check for imagery bailingniao took 7.939338684082031e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.1562175750732422s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.123283386230469e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.2874603271484375e-05s
INFO | --- Analysis for imagery_bailingniao took 1.8551077842712402s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 8.177757263183594e-05s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.15564250946044922s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.0224149227142334s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.012222290039062e-05s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.0251998901367188e-05s
INFO | --- Analysis for imagesnippets took 1.7514119148254395s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 8.320808410644531e-05s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.1585681438446045s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020669221878051758s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.96453857421875e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for imf-linked-data took 1.7372236251831055s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 8.058547973632812e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.00020575523376464844s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.157196044921875s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.02184748649597168s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.1920928955078125e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 5.7220458984375e-06s
INFO | --- Analysis for Imtiaz took 1.738224744796753s
Availability | SPARQL endpoint availability check for Royalty Free Music took 8.058547973632812e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.15759563446044922s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.24249267578125e-05s
Believability | Calculation of trust value for Royalty Free Music took 9.775161743164062e-06s
INFO | --- Analysis for inaudio.org took 1.7414419651031494s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 6.651878356933594e-05s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.15477705001831055s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.023584842681884766s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 9.298324584960938e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 1.732729434967041s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 8.034706115722656e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.15935111045837402s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020535707473754883s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00012373924255371094s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 9.298324584960938e-06s
INFO | --- Analysis for ineverycrea took 1.728785514831543s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.106231689453125e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.15692925453186035s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.02190232276916504s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.632110595703125e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0013580322265625e-05s
INFO | --- Analysis for ineverycrea-argentina took 1.7549679279327393s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 6.842613220214844e-05s
Availability | VoID file availability check for Influence Tracker Dataset took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.16386866569519043s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.021817445755004883s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 6.842613220214844e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for influence-tracker-dataset took 1.743105173110962s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.0531158447265625e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.15868091583251953s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.337860107421875e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 1.7117481231689453s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 8.7738037109375e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.15861725807189941s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.022912979125976562s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.846687316894531e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for interactivemaps-gnoss took 1.7748706340789795s
Availability | SPARQL endpoint availability check for intervalue took 4.220008850097656e-05s
Availability | VoID file availability check for intervalue took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for intervalue took 0.16078782081604004s
Reputation | Calculation of the PageRank for intervalue took 0.020993471145629883s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for intervalue took 7.05718994140625e-05s
Believability | Calculation of trust value for intervalue took 1.1444091796875e-05s
INFO | --- Analysis for intervalue took 1.7437312602996826s
Availability | SPARQL endpoint availability check for Inztrow took 8.58306884765625e-05s
Availability | VoID file availability check for Inztrow took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Inztrow took 0.15178370475769043s
Reputation | Calculation of the PageRank for Inztrow took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.170967102050781e-05s
Believability | Calculation of trust value for Inztrow took 1.1682510375976562e-05s
INFO | --- Analysis for Inztrow took 1.786137580871582s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 8.225440979003906e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.15458035469055176s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.02313065528869629s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.239776611328125e-05s
INFO | --- Analysis for ipbes took 1.7614750862121582s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 6.4849853515625e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.16150712966918945s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020823955535888672s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.220008850097656e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.049041748046875e-05s
INFO | --- Analysis for iptc-newscodes took 1.7724900245666504s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 7.867813110351562e-05s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.15856099128723145s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020328283309936523s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.274482727050781e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.0013580322265625e-05s
INFO | --- Analysis for iserve took 1.7489569187164307s
Availability | SPARQL endpoint availability check for ISIC V4 took 9.369850158691406e-05s
Availability | VoID file availability check for ISIC V4 took 0.00020623207092285156s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.1522359848022461s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.552436828613281e-05s
Believability | Calculation of trust value for ISIC V4 took 9.775161743164062e-06s
INFO | --- Analysis for isic-v4 took 1.7897937297821045s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 8.225440979003906e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.16157174110412598s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 6.961822509765625e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 1.0013580322265625e-05s
INFO | --- Analysis for isil-dbpedia took 1.7551865577697754s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 8.368492126464844e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.16118192672729492s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.02153468132019043s
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.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.790855407714844e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.0967254638671875e-05s
INFO | --- Analysis for iso-639-oasis took 1.7543671131134033s
Availability | SPARQL endpoint availability check for ISOcat took 8.392333984375e-05s
Availability | VoID file availability check for ISOcat took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for ISOcat took 0.16892361640930176s
Reputation | Calculation of the PageRank for ISOcat took 0.020897865295410156s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.151199340820312e-05s
Believability | Calculation of trust value for ISOcat took 9.5367431640625e-06s
INFO | --- Analysis for isocat took 1.8076393604278564s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 8.845329284667969e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.15459513664245605s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.021409034729003906s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.743171691894531e-05s
Believability | Calculation of trust value for ISOcat-metadata took 9.5367431640625e-06s
INFO | --- Analysis for isocat-metadata took 1.8070390224456787s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.012222290039062e-05s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15410447120666504s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.022039413452148438s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.001062154769897461s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0001125335693359375s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.344650268554688e-06s
INFO | --- Analysis for ispra-lod-place took 1.7513298988342285s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 8.177757263183594e-05s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.16303396224975586s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.266334533691406e-05s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 9.298324584960938e-06s
INFO | --- Analysis for ispra-lod-ron took 1.7613029479980469s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 4.220008850097656e-05s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.16319012641906738s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.02154541015625s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 0.00011515617370605469s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for issa-agritrop took 1.7369539737701416s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.315376281738281e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.15998077392578125s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.9802322387695312e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 8.821487426757812e-06s
INFO | --- Analysis for ISSN:0080-3626 took 1.7565972805023193s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.38690185546875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.15198421478271484s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.457069396972656e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 9.5367431640625e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 1.751572847366333s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 9.179115295410156e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.15091300010681152s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.075599670410156e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 9.5367431640625e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 1.7221336364746094s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 8.296966552734375e-05s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.15871644020080566s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.021262645721435547s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.726119995117188e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.0067901611328125e-06s
INFO | --- Analysis for istat-immigration took 1.722116470336914s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 8.225440979003906e-05s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.14773869514465332s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007221698760986328s
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 1.0967254638671875e-05s
INFO | --- Analysis for it-aifa-drug-prices took 1.79240083694458s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 3.838539123535156e-05s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.15767669677734375s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020362138748168945s
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.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.176399230957031e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.1920928955078125e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 1.7956714630126953s
Availability | SPARQL endpoint availability check for IWN took 4.3392181396484375e-05s
Availability | VoID file availability check for IWN took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for IWN took 0.16150355339050293s
Reputation | Calculation of the PageRank for IWN took 0.021750450134277344s
Interlinking | Calculation of Degree of Connection for IWN took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for IWN took 0.0010535717010498047s
Interlinking | Calculation of Clustering coefficient for IWN took 5.078315734863281e-05s
Believability | Calculation of trust value for IWN took 8.106231689453125e-06s
INFO | --- Analysis for iwn took 1.837184190750122s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.663101673126221s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.15559148788452148s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.723403930664062e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 9.059906005859375e-06s
INFO | --- Analysis for jamendo-dbtune took 7.756465435028076s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 8.320808410644531e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.14750337600708008s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.6253204345703125e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for japan-radioactivity-stat took 1.7189249992370605s
Availability | SPARQL endpoint availability check for JEL Classification took 3.814697265625e-05s
Availability | VoID file availability check for JEL Classification took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.18256068229675293s
Reputation | Calculation of the PageRank for JEL Classification took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.8371810913085938e-05s
Believability | Calculation of trust value for JEL Classification took 9.5367431640625e-06s
INFO | --- Analysis for jel-classification took 1.783287525177002s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.058673620223999s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.00020766258239746094s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.15947675704956055s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.022713899612426758s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.123283386230469e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 9.059906005859375e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 2.9619455337524414s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.5142593383789s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.16219377517700195s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 6.890296936035156e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 9.775161743164062e-06s
INFO | --- Analysis for jita took 536.0264492034912s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.04534602165222s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.15379834175109863s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.535385131835938e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.0967254638671875e-05s
INFO | --- Analysis for john-goodwins-family-tree took 21.777940273284912s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 3.9577484130859375e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.15625905990600586s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.3855438232421875e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 1.1444091796875e-05s
INFO | --- Analysis for jp-cos took 1.7172691822052002s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 8.249282836914062e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.00034928321838378906s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.15592217445373535s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.02606797218322754s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.933906555175781e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.0251998901367188e-05s
INFO | --- Analysis for jp-textbook took 1.8115386962890625s
Availability | SPARQL endpoint availability check for JRC-Names took 8.0108642578125e-05s
Availability | VoID file availability check for JRC-Names took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.1531825065612793s
Reputation | Calculation of the PageRank for JRC-Names took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.4332275390625e-05s
Believability | Calculation of trust value for JRC-Names took 9.298324584960938e-06s
INFO | --- Analysis for jrc-names-ec took 1.846944808959961s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 6.461143493652344e-05s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004165172576904297s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.152693510055542s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.02113795280456543s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.508827209472656e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 9.775161743164062e-06s
INFO | --- Analysis for jrc-names-mlode took 1.7394981384277344s
Availability | SPARQL endpoint availability check for JudaicaLink took 8.487701416015625e-05s
Availability | VoID file availability check for JudaicaLink took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.15739941596984863s
Reputation | Calculation of the PageRank for JudaicaLink took 0.02127695083618164s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010180473327636719s
Believability | Calculation of trust value for JudaicaLink took 8.821487426757812e-06s
INFO | --- Analysis for judaicalink took 1.7700982093811035s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 8.177757263183594e-05s
Availability | VoID file availability check for Kallikratis municipalities took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.1545886993408203s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.083747863769531e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 1.0251998901367188e-05s
INFO | --- Analysis for kallikratis-municipalities took 1.7505342960357666s
Availability | SPARQL endpoint availability check for EU Soccer League took 7.987022399902344e-05s
Availability | VoID file availability check for EU Soccer League took 0.00041747093200683594s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.15210580825805664s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.337860107421875e-05s
Believability | Calculation of trust value for EU Soccer League took 1.2159347534179688e-05s
INFO | --- Analysis for KG:Course_Submission took 1.7794325351715088s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 3.933906555175781e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.15570402145385742s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02036738395690918s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.1920928955078125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.239776611328125e-05s
INFO | --- Analysis for KING took 1.6990430355072021s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 8.440017700195312e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.15616750717163086s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.461143493652344e-05s
Believability | Calculation of trust value for Klappstuhlclub took 1.2159347534179688e-05s
INFO | --- Analysis for klappstuhlclub took 1.757086992263794s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 8.082389831542969e-05s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.15360474586486816s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020189523696899414s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 5.698204040527344e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.3113021850585938e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 1.7243454456329346s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.220008850097656e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.1597003936767578s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.021661043167114258s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.337860107421875e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.1682510375976562e-05s
INFO | --- Analysis for KnowledgeFusion took 1.7188923358917236s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 8.368492126464844e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.15433716773986816s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 7.152557373046875e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.1682510375976562e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 1.7412950992584229s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0001201629638671875s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.16288518905639648s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.170967102050781e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0967254638671875e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 1.7674641609191895s
Availability | SPARQL endpoint availability check for Informatics Studies took 6.437301635742188e-05s
Availability | VoID file availability check for Informatics Studies took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.15816950798034668s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.24249267578125e-05s
Believability | Calculation of trust value for Informatics Studies took 1.1920928955078125e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 1.7741761207580566s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 8.20159912109375e-05s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.15064787864685059s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020431041717529297s
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.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.910064697265625e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 1.2636184692382812e-05s
INFO | --- Analysis for kupkb took 1.7275259494781494s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 8.368492126464844e-05s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.15105891227722168s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02194046974182129s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.176399230957031e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 9.298324584960938e-06s
INFO | --- Analysis for l3s-dblp took 1.740405797958374s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.15346145629882812s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.866455078125e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for lak-dataset took 1.7225186824798584s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 4.1484832763671875e-05s
Availability | VoID file availability check for  Language Name Authority List  took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.16058588027954102s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.022454500198364258s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 8.058547973632812e-05s
Believability | Calculation of trust value for  Language Name Authority List  took 1.2159347534179688e-05s
INFO | --- Analysis for language-authority-list took 1.7630467414855957s
Availability | SPARQL endpoint availability check for Lark took 4.1484832763671875e-05s
Availability | VoID file availability check for Lark took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Lark took 0.15377092361450195s
Reputation | Calculation of the PageRank for Lark took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for Lark took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Lark took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Lark took 6.651878356933594e-05s
Believability | Calculation of trust value for Lark took 9.5367431640625e-06s
INFO | --- Analysis for LARK took 1.7268054485321045s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 8.034706115722656e-05s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.1642441749572754s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.02148604393005371s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.528594970703125e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for LASLA took 1.8276286125183105s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 4.1961669921875e-05s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.16161513328552246s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.02182745933532715s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.291534423828125e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 1.7640550136566162s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 8.654594421386719e-05s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.15848207473754883s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.021697282791137695s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for LatinAffectus took 1.7483041286468506s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 7.843971252441406e-05s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.16631197929382324s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.2438507080078125e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for LatinWordnetLiLa took 1.7407855987548828s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 8.702278137207031e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0007603168487548828s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.1542048454284668s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0009560585021972656s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.0001361370086669922s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.1682510375976562e-05s
INFO | --- Analysis for lcsh took 2.284595012664795s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.315376281738281e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.15671300888061523s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.177757263183594e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.152557373046875e-06s
INFO | --- Analysis for lcsubjects took 2.206270217895508s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.998542070388794s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.15726089477539062s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.022150754928588867s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.172325134277344e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.049041748046875e-05s
INFO | --- Analysis for ldt@library took 15.265724182128906s
Availability | SPARQL endpoint availability check for U ime Legije took 3.981590270996094e-05s
Availability | VoID file availability check for U ime Legije took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.16242718696594238s
Reputation | Calculation of the PageRank for U ime Legije took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for U ime Legije took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.123283386230469e-05s
Believability | Calculation of trust value for U ime Legije took 1.0251998901367188e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 1.755786418914795s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 3.910064697265625e-05s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0004105567932128906s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.15134501457214355s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.021268367767333984s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.200241088867188e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.049041748046875e-05s
INFO | --- Analysis for LemmaBank took 1.7445306777954102s
Availability | SPARQL endpoint availability check for lemonUby took 4.00543212890625e-05s
Availability | VoID file availability check for lemonUby took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for lemonUby took 0.15946412086486816s
Reputation | Calculation of the PageRank for lemonUby took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for lemonUby took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for lemonUby took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.318092346191406e-05s
Believability | Calculation of trust value for lemonUby took 1.049041748046875e-05s
INFO | --- Analysis for lemonuby took 1.7628378868103027s
Availability | SPARQL endpoint availability check for LemonWiktionary took 8.20159912109375e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.1515793800354004s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.337860107421875e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.0251998901367188e-05s
INFO | --- Analysis for lemonwiktionary took 1.8011481761932373s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 8.273124694824219e-05s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.152754545211792s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02108454704284668s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 9.775161743164062e-06s
INFO | --- Analysis for LewisShort took 1.7413702011108398s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 4.1961669921875e-05s
Availability | VoID file availability check for LEXIN-RDF took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.1532273292541504s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 6.127357482910156e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.2636184692382812e-05s
INFO | --- Analysis for lexin-rdf took 1.759444236755371s
Availability | SPARQL endpoint availability check for lexinfo took 8.749961853027344e-05s
Availability | VoID file availability check for lexinfo took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for lexinfo took 0.15265607833862305s
Reputation | Calculation of the PageRank for lexinfo took 0.021103858947753906s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0009059906005859375s
Interlinking | Calculation of Clustering coefficient for lexinfo took 9.632110595703125e-05s
Believability | Calculation of trust value for lexinfo took 1.2159347534179688e-05s
INFO | --- Analysis for lexinfo took 1.7654712200164795s
Availability | SPARQL endpoint availability check for Lexvo took 8.416175842285156e-05s
Availability | VoID file availability check for Lexvo took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Lexvo took 0.15353703498840332s
Reputation | Calculation of the PageRank for Lexvo took 0.020639657974243164s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00018715858459472656s
Believability | Calculation of trust value for Lexvo took 1.239776611328125e-05s
INFO | --- Analysis for lexvo took 1.8628549575805664s
Availability | SPARQL endpoint availability check for Lexvo.org took 8.463859558105469e-05s
Availability | VoID file availability check for Lexvo.org took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.15980935096740723s
Reputation | Calculation of the PageRank for Lexvo.org took 0.022137165069580078s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 6.890296936035156e-05s
Believability | Calculation of trust value for Lexvo.org took 1.1920928955078125e-05s
INFO | --- Analysis for lexvo-org took 1.7580904960632324s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3621218204498291s
Availability | VoID file availability check for LIBRIS took 0.0005197525024414062s
Extra | Recovery of all triples for LIBRIS took 7.834772109985352s
Performance | Total latancy measurement for LIBRIS took 0.689185380935669s
Amount of data | Number of triples check for LIBRIS took 22.9764986038208s
Interoperability | New terms check for LIBRIS took 14.920812606811523s
Versatility | Languages check for LIBRIS took 0.17339634895324707s
Interpretability | Number of blank nodes check for LIBRIS took 300.0842216014862s
Security | Check HTTPS for LIBRIS took 0.37593722343444824s
Interpretability | RDF structures check for LIBRIS took 0.22411251068115234s
Versatility | Serialization formats check for LIBRIS took 0.19309687614440918s
Availability | RDF dump link check for LIBRIS took 0.1280989646911621s
License | MR license check for LIBRIS took 0.2670137882232666s
License | HR license check for LIBRIS took 0.21387171745300293s
Amount of data | Number of property check for LIBRIS took 0.17415475845336914s
Understandability | Number of label check for LIBRIS took 0.326413631439209s
Understandability | URI regex check for LIBRIS took 0.3427085876464844s
Understandability | Vocabs check for LIBRIS took 0.1273941993713379s
Verifiability | Authors check for LIBRIS took 0.15952515602111816s
Verifiability | Publishers check for LIBRIS took 0.14210844039916992s
Performance | Throughput check for LIBRIS took 10.354901552200317s
Amount of data | Check the number of entities for LIBRIS took 6.771087646484375e-05s
Verifiability | Contribs. check for LIBRIS took 0.12531423568725586s
Interlinking | sameAs chians check for LIBRIS took 0.12760567665100098s
Interlinking | skos check for LIBRIS took 0.1954212188720703s
Interlinking | skos check for LIBRIS took 0.12670564651489258s
Timeliness | dataset update frequency check for LIBRIS took 0.12640380859375s
Currency | Creation date check for LIBRIS took 0.3288309574127197s
Currency | Modification date check for LIBRIS took 0.6267850399017334s
Rep.Conc. | URIs length for LIBRIS took 78.4964451789856s
Interoperability | New vocabularies check for LIBRIS took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.17831134796142578s
Accuracy | Check Functional Property for LIBRIS took 0.18682622909545898s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.12705588340759277s
Accuracy | Check Datatype consistency for LIBRIS took 0.2634587287902832s
Consistency | Disjoint class check for LIBRIS took 0.17626476287841797s
Consistency | Check Misplaced properties for LIBRIS took 60.696866512298584s
Consistency | Misplaced classes for LIBRIS took 1.0923430919647217s
Consistency | Check Ontology hijacking for LIBRIS took 3.162121295928955s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.2898619174957275s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 61.790414333343506s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2769968509674072s
Conciseness | Check Intensional conciseness for LIBRIS took 0.3858006000518799s
Security | Sign check for LIBRIS took 0.15992307662963867s
Availability | Check URIs Dereferenciability for LIBRIS took 9.76659870147705s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.20526599884033203s
Reputation | Calculation of the PageRank for LIBRIS took 0.02014303207397461s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006773471832275391s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 8.893013000488281e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.430511474609375e-06s
Believability | Calculation of trust value for LIBRIS took 1.2874603271484375e-05s
INFO | --- Analysis for libris took 1056.5849387645721s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.16182923316955566s
Availability | VoID file availability check for Public Library of Veroia took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.1552751064300537s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 6.914138793945312e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.0013580322265625e-05s
INFO | --- Analysis for libver took 1.917750358581543s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 3.9577484130859375e-05s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.15455055236816406s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02129530906677246s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 7.677078247070312e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 1.0251998901367188e-05s
INFO | --- Analysis for lichfield-spending took 1.7362983226776123s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 0.00010323524475097656s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.1523270606994629s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02231621742248535s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.075599670410156e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.0728836059570312e-05s
INFO | --- Analysis for lime took 1.7209925651550293s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.172325134277344e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0002079010009765625s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.15655303001403809s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010085105895996094s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 5.7220458984375e-06s
INFO | --- Analysis for lingvoj took 1.712876319885254s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 3.7670135498046875e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.16016077995300293s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.605552673339844e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.0013580322265625e-05s
INFO | --- Analysis for linked-crunchbase took 1.9450292587280273s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.654594421386719e-05s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.15452241897583008s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.771087646484375e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.0013580322265625e-05s
INFO | --- Analysis for linked-drugs took 1.7703561782836914s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 8.20159912109375e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.1649003028869629s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.00010228157043457031s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 1.0013580322265625e-05s
INFO | --- Analysis for linked-edgar took 1.7641313076019287s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.00543212890625e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.15581989288330078s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02120804786682129s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.5367431640625e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.0967254638671875e-05s
INFO | --- Analysis for linked-eurostat took 1.7434227466583252s
Availability | SPARQL endpoint availability check for linked hypernyms took 3.8623809814453125e-05s
Availability | VoID file availability check for linked hypernyms took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.1624438762664795s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02184152603149414s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 6.890296936035156e-05s
Believability | Calculation of trust value for linked hypernyms took 1.1444091796875e-05s
INFO | --- Analysis for linked-hypernyms took 1.7582061290740967s
Availability | SPARQL endpoint availability check for Linked Life Data took 8.273124694824219e-05s
Availability | VoID file availability check for Linked Life Data took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.16042470932006836s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020151853561401367s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 3.647804260253906e-05s
Believability | Calculation of trust value for Linked Life Data took 1.2159347534179688e-05s
INFO | --- Analysis for linked-life-data took 1.7504684925079346s
Availability | SPARQL endpoint availability check for Linked Logainm took 8.320808410644531e-05s
Availability | VoID file availability check for Linked Logainm took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.15246272087097168s
Reputation | Calculation of the PageRank for Linked Logainm took 0.021106481552124023s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 6.937980651855469e-05s
Believability | Calculation of trust value for Linked Logainm took 1.0967254638671875e-05s
INFO | --- Analysis for linked-logainm took 1.7491698265075684s
Availability | SPARQL endpoint availability check for Linked NUTS took 8.20159912109375e-05s
Availability | VoID file availability check for Linked NUTS took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.1587996482849121s
Reputation | Calculation of the PageRank for Linked NUTS took 0.021724224090576172s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0010828971862792969s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 6.103515625e-05s
Believability | Calculation of trust value for Linked NUTS took 1.1444091796875e-05s
INFO | --- Analysis for linked-nuts took 1.7595930099487305s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 8.225440979003906e-05s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.1512448787689209s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.021122455596923828s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.314018249511719e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 1.0251998901367188e-05s
INFO | --- Analysis for linked-open-camera took 1.720125436782837s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.00543212890625e-05s
Availability | VoID file availability check for Linked Open Commerce took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.14847064018249512s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 4.00543212890625e-05s
Believability | Calculation of trust value for Linked Open Commerce took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-commerce took 1.6930043697357178s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 8.392333984375e-05s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.16212987899780273s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 9.655952453613281e-05s
Believability | Calculation of trust value for Linked Open Data of Ecology took 4.76837158203125e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 1.7473642826080322s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 7.915496826171875e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.16384124755859375s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020239830017089844s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.344650268554688e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.239776611328125e-05s
INFO | --- Analysis for linked-open-numbers took 1.7584872245788574s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 8.20159912109375e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.15990996360778809s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020168304443359375s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Open Piracy took 9.5367431640625e-06s
INFO | --- Analysis for linked-open-piracy took 1.7429747581481934s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 4.029273986816406e-05s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.15523576736450195s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020943880081176758s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.506111145019531e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.2159347534179688e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 1.9032363891601562s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 7.987022399902344e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.1599884033203125s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.266334533691406e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 1.1920928955078125e-05s
INFO | --- Analysis for linked-periodicals took 1.744438886642456s
Availability | SPARQL endpoint availability check for Linked Index took 4.7206878662109375e-05s
Availability | VoID file availability check for Linked Index took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Linked Index took 0.1628739833831787s
Reputation | Calculation of the PageRank for Linked Index took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for Linked Index took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Index took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.058547973632812e-05s
Believability | Calculation of trust value for Linked Index took 9.775161743164062e-06s
INFO | --- Analysis for linked-stockindex took 1.7726609706878662s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 8.0108642578125e-05s
Availability | VoID file availability check for Linked Structured Product Labels took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.16661977767944336s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.62396240234375e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.0013580322265625e-05s
INFO | --- Analysis for linked-structured-product-labels took 1.794586420059204s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 4.029273986816406e-05s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.16057038307189941s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020734786987304688s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 9.775161743164062e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 1.7554786205291748s
Availability | SPARQL endpoint availability check for Linked TCGA took 8.463859558105469e-05s
Availability | VoID file availability check for Linked TCGA took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.1573808193206787s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.320808410644531e-05s
Believability | Calculation of trust value for Linked TCGA took 1.0013580322265625e-05s
INFO | --- Analysis for linked-tcga took 1.745513916015625s
Availability | SPARQL endpoint availability check for Linked User Feedback took 4.076957702636719e-05s
Availability | VoID file availability check for Linked User Feedback took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.15410208702087402s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020293474197387695s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.647804260253906e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.0251998901367188e-05s
INFO | --- Analysis for linked-user-feedback took 1.7473547458648682s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.00543212890625e-05s
Availability | VoID file availability check for USPTO Patent data took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.15644049644470215s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.021725893020629883s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.510185241699219e-05s
Believability | Calculation of trust value for USPTO Patent data took 9.5367431640625e-06s
INFO | --- Analysis for linked-uspto-patent-data took 1.7339742183685303s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 4.76837158203125e-05s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.1617264747619629s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020560741424560547s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.2874603271484375e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 1.753467082977295s
Availability | SPARQL endpoint availability check for LinkedCT took 3.8623809814453125e-05s
Availability | VoID file availability check for LinkedCT took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.15774321556091309s
Reputation | Calculation of the PageRank for LinkedCT took 0.020968914031982422s
Interlinking | Calculation of Degree of Connection for LinkedCT took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.584426879882812e-05s
Believability | Calculation of trust value for LinkedCT took 9.775161743164062e-06s
INFO | --- Analysis for linkedct took 1.7276341915130615s
Availability | SPARQL endpoint availability check for LinkedGeoData took 8.606910705566406e-05s
Availability | VoID file availability check for LinkedGeoData took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.1538245677947998s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00011420249938964844s
Believability | Calculation of trust value for LinkedGeoData took 1.0013580322265625e-05s
INFO | --- Analysis for linkedgeodata took 1.7045605182647705s
Availability | SPARQL endpoint availability check for LinkedLCCN took 0.9961709976196289s
Availability | VoID file availability check for LinkedLCCN took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.16265058517456055s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 9.846687316894531e-05s
Believability | Calculation of trust value for LinkedLCCN took 9.775161743164062e-06s
INFO | --- Analysis for linkedlccn took 2.7764291763305664s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 0.00010037422180175781s
Availability | VoID file availability check for LinkedMarkMail took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.16088080406188965s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.021362781524658203s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.504753112792969e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.33514404296875e-05s
INFO | --- Analysis for linkedmarkmail took 1.7179992198944092s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.959843158721924s
Availability | VoID file availability check for Linked Movie DataBase took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.15550899505615234s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00012564659118652344s
Believability | Calculation of trust value for Linked Movie DataBase took 1.049041748046875e-05s
INFO | --- Analysis for linkedmdb took 102.7821364402771s
Availability | SPARQL endpoint availability check for LinkedSpending took 8.058547973632812e-05s
Availability | VoID file availability check for LinkedSpending took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for LinkedSpending took 0.15078401565551758s
Reputation | Calculation of the PageRank for LinkedSpending took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for LinkedSpending took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LinkedSpending took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for LinkedSpending took 6.747245788574219e-05s
Believability | Calculation of trust value for LinkedSpending took 1.0251998901367188e-05s
INFO | --- Analysis for linkedspending took 1.7248682975769043s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 8.106231689453125e-05s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.15673089027404785s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02132248878479004s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010013580322265625s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.0013580322265625e-05s
INFO | --- Analysis for linklion took 1.7311630249023438s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 36.263683557510376s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.15713191032409668s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020345687866210938s
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.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 4.649162292480469e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.0251998901367188e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 74.32156896591187s
Availability | SPARQL endpoint availability check for lobid-organisations took 8.58306884765625e-05s
Availability | VoID file availability check for lobid-organisations took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.1641855239868164s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 0.00010180473327636719s
Believability | Calculation of trust value for lobid-organisations took 1.0251998901367188e-05s
INFO | --- Analysis for lobid-organisations took 1.7484166622161865s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 8.153915405273438e-05s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.17996621131896973s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.02041769027709961s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.894371032714844e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 5.245208740234375e-06s
INFO | --- Analysis for lobid-resources took 1.7741267681121826s
Availability | SPARQL endpoint availability check for Linked Open Colors took 8.225440979003906e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.15546417236328125s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.021631240844726562s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.200241088867188e-05s
Believability | Calculation of trust value for Linked Open Colors took 9.5367431640625e-06s
INFO | --- Analysis for loc took 1.7572789192199707s
Availability | SPARQL endpoint availability check for Location Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Location Ontology took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.15834403038024902s
Reputation | Calculation of the PageRank for Location Ontology took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for Location Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Location_Ontology took 1.7178282737731934s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 9.202957153320312e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.00020813941955566406s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.15297198295593262s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020661354064941406s
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.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 9.5367431640625e-06s
INFO | --- Analysis for locv took 1.736755609512329s
Availability | SPARQL endpoint availability check for LOD-a-lot took 6.270408630371094e-05s
Availability | VoID file availability check for LOD-a-lot took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.16161346435546875s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.021624326705932617s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.0040740966796875e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.0728836059570312e-05s
INFO | --- Analysis for lod-a-lot took 1.7697525024414062s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 3.910064697265625e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.16159558296203613s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.021108627319335938s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.559226989746094e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.0013580322265625e-05s
INFO | --- Analysis for lod2-project-wiki took 1.7510416507720947s
Availability | SPARQL endpoint availability check for LODAC BDLS took 4.029273986816406e-05s
Availability | VoID file availability check for LODAC BDLS took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.15192127227783203s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.200241088867188e-05s
Believability | Calculation of trust value for LODAC BDLS took 9.775161743164062e-06s
INFO | --- Analysis for lodac-bdls took 1.731858730316162s
Availability | SPARQL endpoint availability check for lofd took 8.20159912109375e-05s
Availability | VoID file availability check for lofd took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for lofd took 0.15486717224121094s
Reputation | Calculation of the PageRank for lofd took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for lofd took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for lofd took 3.1948089599609375e-05s
Believability | Calculation of trust value for lofd took 1.1205673217773438e-05s
INFO | --- Analysis for lofd took 1.745765209197998s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 8.535385131835938e-05s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.16062235832214355s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 4.9591064453125e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 1.0251998901367188e-05s
INFO | --- Analysis for loius took 1.7710444927215576s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 8.130073547363281e-05s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.15450644493103027s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.022209644317626953s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.245208740234375e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 1.049041748046875e-05s
INFO | --- Analysis for london-gazette took 1.7277581691741943s
Availability | SPARQL endpoint availability check for Weather Stations took 8.058547973632812e-05s
Availability | VoID file availability check for Weather Stations took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.15446853637695312s
Reputation | Calculation of the PageRank for Weather Stations took 0.021837949752807617s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.106231689453125e-05s
Believability | Calculation of trust value for Weather Stations took 1.0728836059570312e-05s
INFO | --- Analysis for los_metar took 1.7471821308135986s
Availability | SPARQL endpoint availability check for Lotico took 3.910064697265625e-05s
Availability | VoID file availability check for Lotico took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for Lotico took 0.16317462921142578s
Reputation | Calculation of the PageRank for Lotico took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for Lotico took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.678436279296875e-05s
Believability | Calculation of trust value for Lotico took 1.2159347534179688e-05s
INFO | --- Analysis for lotico took 1.7534842491149902s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 4.5299530029296875e-05s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.16131973266601562s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.218650817871094e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.2636184692382812e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 1.7345824241638184s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.177757263183594e-05s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.16380620002746582s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.0994415283203125e-05s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.0013580322265625e-05s
INFO | --- Analysis for LPIS_(Poland) took 1.7573175430297852s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.368492126464844e-05s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.15149188041687012s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.021777868270874023s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.337860107421875e-05s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 1.9353241920471191s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.1961669921875e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.16367530822753906s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.123283386230469e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.239776611328125e-05s
INFO | --- Analysis for lremap-auth took 1.7478981018066406s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.267692565917969e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.15586566925048828s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.314018249511719e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.1920928955078125e-05s
INFO | --- Analysis for lremap-conf took 1.7894937992095947s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 8.487701416015625e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.00032711029052734375s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.1561872959136963s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.1948089599609375e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.2636184692382812e-05s
INFO | --- Analysis for lremap-ri took 1.7583656311035156s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 9.775161743164062e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.16588640213012695s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.266334533691406e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.2874603271484375e-05s
INFO | --- Analysis for lremap-sub took 1.742940902709961s
Availability | SPARQL endpoint availability check for LSQ took 8.58306884765625e-05s
Availability | VoID file availability check for LSQ took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for LSQ took 0.1544957160949707s
Reputation | Calculation of the PageRank for LSQ took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for LSQ took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.2901763916015625e-05s
Believability | Calculation of trust value for LSQ took 1.33514404296875e-05s
INFO | --- Analysis for lsq took 1.7350842952728271s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6396000385284424s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.16343951225280762s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.02073359489440918s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.291534423828125e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for LucaniPharsalia took 2.7552642822265625s
Availability | SPARQL endpoint availability check for Linked rules took 8.225440979003906e-05s
Availability | VoID file availability check for Linked rules took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Linked rules took 0.16657376289367676s
Reputation | Calculation of the PageRank for Linked rules took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Linked rules took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked rules took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Linked rules took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linked rules took 1.239776611328125e-05s
INFO | --- Analysis for Luminaires_senlis took 1.7459800243377686s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 8.440017700195312e-05s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.15025997161865234s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.021931886672973633s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 2.9325485229492188e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.2159347534179688e-05s
INFO | --- Analysis for makg took 1.7271754741668701s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 8.320808410644531e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.15970134735107422s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.022396087646484375s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.600120544433594e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 9.5367431640625e-06s
INFO | --- Analysis for manchester-university-reading-lists took 1.709601879119873s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.15606474876403809s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02163982391357422s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.0251998901367188e-05s
INFO | --- Analysis for manish took 1.7226788997650146s
Availability | SPARQL endpoint availability check for MARC Codes List took 8.296966552734375e-05s
Availability | VoID file availability check for MARC Codes List took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.15906953811645508s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012040138244628906s
Believability | Calculation of trust value for MARC Codes List took 1.1920928955078125e-05s
INFO | --- Analysis for marc-codes took 1.7597270011901855s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 6.67572021484375e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.15913629531860352s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.933906555175781e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.239776611328125e-05s
INFO | --- Analysis for masc took 1.7615323066711426s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 8.273124694824219e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.1748640537261963s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.743171691894531e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.2159347534179688e-05s
INFO | --- Analysis for masc-bn-nif took 1.8297159671783447s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.148183822631836s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.15349888801574707s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.022258758544921875s
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.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.147125244140625e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 1.3113021850585938e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 2.9524645805358887s
Availability | SPARQL endpoint availability check for medline took 8.630752563476562e-05s
Availability | VoID file availability check for medline took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for medline took 0.206679105758667s
Reputation | Calculation of the PageRank for medline took 0.021780014038085938s
Interlinking | Calculation of Degree of Connection for medline took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for medline took 0.0011179447174072266s
Interlinking | Calculation of Clustering coefficient for medline took 4.887580871582031e-05s
Believability | Calculation of trust value for medline took 1.2636184692382812e-05s
INFO | --- Analysis for medline took 1.866093397140503s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 8.416175842285156e-05s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.1549527645111084s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.961822509765625e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.3113021850585938e-05s
INFO | --- Analysis for meducator took 1.835371494293213s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 8.606910705566406e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.15543460845947266s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.022110939025878906s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.295608520507812e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.2636184692382812e-05s
INFO | --- Analysis for metashare took 1.7910921573638916s
Availability | SPARQL endpoint availability check for MExiCo took 4.220008850097656e-05s
Availability | VoID file availability check for MExiCo took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for MExiCo took 0.1600635051727295s
Reputation | Calculation of the PageRank for MExiCo took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.054473876953125e-05s
Believability | Calculation of trust value for MExiCo took 1.2874603271484375e-05s
INFO | --- Analysis for mexico took 1.7229273319244385s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 4.1961669921875e-05s
Availability | VoID file availability check for Coronavirus dataset took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.1560828685760498s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.02286815643310547s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 6.031990051269531e-05s
Believability | Calculation of trust value for Coronavirus dataset took 1.33514404296875e-05s
INFO | --- Analysis for micro-coronavirus took 1.765636920928955s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 6.4849853515625e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.1548614501953125s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.021044492721557617s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010085105895996094s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for miguiadeviajes-gnoss took 1.7861104011535645s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.6253204345703125e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.15793323516845703s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.021900177001953125s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010991096496582031s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.0013580322265625e-05s
INFO | --- Analysis for mismuseos-gnoss took 1.7438335418701172s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 8.726119995117188e-05s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.16168642044067383s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.021082162857055664s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.696846008300781e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 5.4836273193359375e-06s
INFO | --- Analysis for mlsa took 1.758450984954834s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 8.177757263183594e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.16323590278625488s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 2.956390380859375e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.4066696166992188e-05s
INFO | --- Analysis for model took 1.772298812866211s
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.00543212890625e-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.0004315376281738281s
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.15307354927062988s
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.02039957046508789s
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 9.775161743164062e-06s
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.0007414817810058594s
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 3.0040740966796875e-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 9.775161743164062e-06s
INFO | --- Analysis for model1 took 1.7479350566864014s
Availability | SPARQL endpoint availability check for MORElab took 8.392333984375e-05s
Availability | VoID file availability check for MORElab took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for MORElab took 0.1597583293914795s
Reputation | Calculation of the PageRank for MORElab took 0.020836353302001953s
Interlinking | Calculation of Degree of Connection for MORElab took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MORElab took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.249282836914062e-05s
Believability | Calculation of trust value for MORElab took 5.0067901611328125e-06s
INFO | --- Analysis for morelab took 1.7045080661773682s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 0.00010442733764648438s
Availability | VoID file availability check for Mathematics Subject Classification took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.15768098831176758s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.021461009979248047s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 0.00010991096496582031s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.1682510375976562e-05s
INFO | --- Analysis for msc took 1.7754950523376465s
Availability | SPARQL endpoint availability check for Multext-East took 3.910064697265625e-05s
Availability | VoID file availability check for Multext-East took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Multext-East took 0.16475677490234375s
Reputation | Calculation of the PageRank for Multext-East took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for Multext-East took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multext-East took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.4809112548828125e-05s
Believability | Calculation of trust value for Multext-East took 1.0967254638671875e-05s
INFO | --- Analysis for multext-east took 1.768495798110962s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.315376281738281e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.16127252578735352s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.02184319496154785s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.838539123535156e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.2636184692382812e-05s
INFO | --- Analysis for multimedia-lab took 1.7674200534820557s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.6546509265899658s
Availability | VoID file availability check for Muninn World War I took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.16332721710205078s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02165842056274414s
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.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.654594421386719e-05s
Believability | Calculation of trust value for Muninn World War I took 1.1920928955078125e-05s
INFO | --- Analysis for muninn-world-war-i took 5.15226674079895s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 9.059906005859375e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.1576218605041504s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.022162675857543945s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010728836059570312s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.239776611328125e-05s
INFO | --- Analysis for museosespania-gnoss took 1.7704782485961914s
Availability | SPARQL endpoint availability check for Italian Museums took 0.3333137035369873s
Availability | VoID file availability check for Italian Museums took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.1652696132659912s
Reputation | Calculation of the PageRank for Italian Museums took 0.021874189376831055s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.106231689453125e-05s
Believability | Calculation of trust value for Italian Museums took 1.1444091796875e-05s
INFO | --- Analysis for museums-in-italy took 2.1075949668884277s
Availability | SPARQL endpoint availability check for Muziekweb took 0.6869997978210449s
Availability | VoID file availability check for Muziekweb took 0.00046563148498535156s
Extra | Recovery of all triples for Muziekweb took 1.532588005065918s
Performance | Total latancy measurement for Muziekweb took 1.4606010913848877s
Amount of data | Number of triples check for Muziekweb took 0.38532233238220215s
Interoperability | New terms check for Muziekweb took 1.7213082313537598s
Versatility | Languages check for Muziekweb took 52.025883436203s
Interpretability | Number of blank nodes check for Muziekweb took 0.28729724884033203s
Interpretability | RDF structures check for Muziekweb took 0.3039567470550537s
Versatility | Serialization formats check for Muziekweb took 1.3749518394470215s
Availability | RDF dump link check for Muziekweb took 0.7360701560974121s
License | MR license check for Muziekweb took 2.209367275238037s
License | HR license check for Muziekweb took 12.975242376327515s
Amount of data | Number of property check for Muziekweb took 0.2876467704772949s
Understandability | Number of label check for Muziekweb took 0.35842204093933105s
Understandability | URI regex check for Muziekweb took 1.7574827671051025s
Understandability | Vocabs check for Muziekweb took 0.28252482414245605s
Verifiability | Authors check for Muziekweb took 1.272552490234375s
Verifiability | Publishers check for Muziekweb took 0.6824660301208496s
Performance | Throughput check for Muziekweb took 11.767028570175171s
Amount of data | Check the number of entities for Muziekweb took 7.510185241699219e-05s
Verifiability | Contribs. check for Muziekweb took 0.7193431854248047s
Interlinking | sameAs chians check for Muziekweb took 0.7603263854980469s
Interlinking | skos check for Muziekweb took 0.2955586910247803s
Interlinking | skos check for Muziekweb took 0.3407862186431885s
Timeliness | dataset update frequency check for Muziekweb took 0.2918376922607422s
Currency | Creation date check for Muziekweb took 0.595008373260498s
Currency | Modification date check for Muziekweb took 0.6222360134124756s
Rep.Conc. | URIs length for Muziekweb took 1.8227486610412598s
Interoperability | New vocabularies check for Muziekweb took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.29764771461486816s
Accuracy | Check Empty annotation labels for Muziekweb took 0.8015644550323486s
Accuracy | Check White space in annotation for Muziekweb took 0.02746105194091797s
Accuracy | Check Datatype consistency for Muziekweb took 0.02839970588684082s
Consistency | Disjoint class check for Muziekweb took 0.3403449058532715s
Consistency | Check Misplaced properties for Muziekweb took 1.1486995220184326s
Consistency | Check Ontology hijacking for Muziekweb took 2.1264231204986572s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.333601951599121s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.6133241653442383s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03485441207885742s
Conciseness | Check Intensional conciseness for Muziekweb took 0.32030510902404785s
Security | Sign check for Muziekweb took 0.3080928325653076s
Availability | Check URIs Dereferenciability for Muziekweb took 1886.6797409057617s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.5279691219329834s
Reputation | Calculation of the PageRank for Muziekweb took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.9073486328125e-06s
Believability | Calculation of trust value for Muziekweb took 1.1444091796875e-05s
INFO | --- Analysis for muziekweb took 2014.0579562187195s
Availability | SPARQL endpoint availability check for myExperiment took 5.53131103515625e-05s
Availability | VoID file availability check for myExperiment took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for myExperiment took 0.15871000289916992s
Reputation | Calculation of the PageRank for myExperiment took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010275840759277344s
Believability | Calculation of trust value for myExperiment took 1.2874603271484375e-05s
INFO | --- Analysis for my-experiment took 1.7686190605163574s
Availability | SPARQL endpoint availability check for My Family Lineage took 8.368492126464844e-05s
Availability | VoID file availability check for My Family Lineage took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.16349363327026367s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.702278137207031e-05s
Believability | Calculation of trust value for My Family Lineage took 1.3113021850585938e-05s
INFO | --- Analysis for my-family-lineage took 1.7596673965454102s
Availability | SPARQL endpoint availability check for My ontology test took 4.124641418457031e-05s
Availability | VoID file availability check for My ontology test took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for My ontology test took 0.16300511360168457s
Reputation | Calculation of the PageRank for My ontology test took 0.020612001419067383s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.1948089599609375e-05s
Believability | Calculation of trust value for My ontology test took 1.0251998901367188e-05s
INFO | --- Analysis for myontologytest took 1.7484633922576904s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.100799560546875e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.15376591682434082s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00010013580322265625s
Believability | Calculation of trust value for myopenlink dataspaces took 1.0013580322265625e-05s
INFO | --- Analysis for myopenlink-dataspaces took 1.7366838455200195s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 8.249282836914062e-05s
Availability | VoID file availability check for N-Lex as Linked Data took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.15693044662475586s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02113199234008789s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.651878356933594e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for n-lex-as-linked-data took 1.722214698791504s
Availability | SPARQL endpoint availability check for NAICS 2007 took 8.392333984375e-05s
Availability | VoID file availability check for NAICS 2007 took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.14996767044067383s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.647804260253906e-05s
Believability | Calculation of trust value for NAICS 2007 took 1.239776611328125e-05s
INFO | --- Analysis for naics-2007 took 1.7216784954071045s
Availability | SPARQL endpoint availability check for NAICS 2012 took 4.2438507080078125e-05s
Availability | VoID file availability check for NAICS 2012 took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.16028189659118652s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.02019023895263672s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 4.649162292480469e-05s
Believability | Calculation of trust value for NAICS 2012 took 1.2636184692382812e-05s
INFO | --- Analysis for naics-2012 took 1.7603943347930908s
Availability | SPARQL endpoint availability check for Usernames  took 4.3392181396484375e-05s
Availability | VoID file availability check for Usernames  took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Usernames  took 0.16689205169677734s
Reputation | Calculation of the PageRank for Usernames  took 0.021394968032836914s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.2901763916015625e-05s
Believability | Calculation of trust value for Usernames  took 9.775161743164062e-06s
INFO | --- Analysis for Names took 1.7494003772735596s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 9.679794311523438e-05s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.18869256973266602s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 5.507469177246094e-05s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 1.0967254638671875e-05s
INFO | --- Analysis for national-diet-library-authorities took 1.776869773864746s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 4.38690185546875e-05s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.16478371620178223s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.078315734863281e-05s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.2159347534179688e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 1.814012050628662s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.9224202632904053s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.15433764457702637s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.0203092098236084s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.220008850097656e-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 3.540771484375s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.654594421386719e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.16047143936157227s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.027028560638427734s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0010974407196044922s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.202957153320312e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2874603271484375e-05s
INFO | --- Analysis for Naturopathy took 1.7537391185760498s
Availability | SPARQL endpoint availability check for COVID-19 Data took 4.0531158447265625e-05s
Availability | VoID file availability check for COVID-19 Data took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.16074705123901367s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020960569381713867s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for COVID-19 Data took 9.5367431640625e-06s
INFO | --- Analysis for NCMI-COVID-19 took 1.7559707164764404s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 6.771087646484375e-05s
Availability | VoID file availability check for NCMI-COVID-19 took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.15883517265319824s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.021425485610961914s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.1444091796875e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.1205673217773438e-05s
INFO | --- Analysis for NCMICOVID-19 took 1.7252781391143799s
Availability | SPARQL endpoint availability check for Near took 4.315376281738281e-05s
Availability | VoID file availability check for Near took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Near took 0.15581536293029785s
Reputation | Calculation of the PageRank for Near took 0.020328998565673828s
Interlinking | Calculation of Degree of Connection for Near took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Near took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Near took 8.7738037109375e-05s
Believability | Calculation of trust value for Near took 1.2159347534179688e-05s
INFO | --- Analysis for near took 1.7249164581298828s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 8.273124694824219e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.15451574325561523s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.021997451782226562s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.0994415283203125e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.0013580322265625e-05s
INFO | --- Analysis for neurolex-wiki took 1.7715795040130615s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 8.58306884765625e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.1591041088104248s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.601478576660156e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.0251998901367188e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 1.7575798034667969s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.00543212890625e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.15780043601989746s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.723403930664062e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 9.5367431640625e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 1.7841415405273438s
Availability | SPARQL endpoint availability check for neXtProt took 5.6743621826171875e-05s
Availability | VoID file availability check for neXtProt took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for neXtProt took 0.16095662117004395s
Reputation | Calculation of the PageRank for neXtProt took 0.02261042594909668s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.001016378402709961s
Interlinking | Calculation of Clustering coefficient for neXtProt took 4.363059997558594e-05s
Believability | Calculation of trust value for neXtProt took 7.152557373046875e-06s
INFO | --- Analysis for nextprot took 1.7202949523925781s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.220008850097656e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00021219253540039062s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.21033596992492676s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.022191286087036133s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010538101196289062s
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 1.7693276405334473s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.00543212890625e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.1942155361175537s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.027923583984375s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.392333984375e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 1.2874603271484375e-05s
INFO | --- Analysis for nhs-jargon took 1.780167579650879s
Availability | SPARQL endpoint availability check for NIT Patna took 8.368492126464844e-05s
Availability | VoID file availability check for NIT Patna took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.16051650047302246s
Reputation | Calculation of the PageRank for NIT Patna took 0.02102494239807129s
Interlinking | Calculation of Degree of Connection for NIT Patna took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.747245788574219e-05s
Believability | Calculation of trust value for NIT Patna took 1.1444091796875e-05s
INFO | --- Analysis for NITP took 1.7790381908416748s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 8.511543273925781e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.1562492847442627s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.743171691894531e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for nlr-dataset-mod took 1.7222399711608887s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 6.389617919921875e-05s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.1536414623260498s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.409385681152344e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for NLW took 1.7235524654388428s
Availability | SPARQL endpoint availability check for Nobel Prizes took 0.00010895729064941406s
Availability | VoID file availability check for Nobel Prizes took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.14711403846740723s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.022217512130737305s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.465217590332031e-05s
Believability | Calculation of trust value for Nobel Prizes took 1.239776611328125e-05s
INFO | --- Analysis for nobelprizes took 1.711256742477417s
Availability | SPARQL endpoint availability check for NoiPA took 8.106231689453125e-05s
Availability | VoID file availability check for NoiPA took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for NoiPA took 0.1618640422821045s
Reputation | Calculation of the PageRank for NoiPA took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for NoiPA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NoiPA took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for NoiPA took 2.8133392333984375e-05s
Believability | Calculation of trust value for NoiPA took 9.5367431640625e-06s
INFO | --- Analysis for NoiPA took 1.7895402908325195s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 0.997124433517456s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.1604175567626953s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02261829376220703s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 8.535385131835938e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 9.298324584960938e-06s
INFO | --- Analysis for nom took 3.2657647132873535s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 6.437301635742188e-05s
Availability | VoID file availability check for Nomenclator Asturias took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.17224359512329102s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.02142643928527832s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 7.557868957519531e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 1.0728836059570312e-05s
INFO | --- Analysis for nomenclator-asturias took 1.7509987354278564s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.4230365753173828s
Availability | VoID file availability check for Nomisma.org  took 0.0004904270172119141s
Extra | Recovery of all triples for Nomisma.org  took 1077.8090193271637s
Performance | Total latancy measurement for Nomisma.org  took 1.749009132385254s
Amount of data | Number of triples check for Nomisma.org  took 39.43795680999756s
Interoperability | New terms check for Nomisma.org  took 8.783570051193237s
Versatility | Languages check for Nomisma.org  took 95.61797595024109s
Interpretability | Number of blank nodes check for Nomisma.org  took 33.01710224151611s
Security | Check HTTPS for Nomisma.org  took 0.733534574508667s
Interpretability | RDF structures check for Nomisma.org  took 0.3734700679779053s
Versatility | Serialization formats check for Nomisma.org  took 0.3699636459350586s
Availability | RDF dump link check for Nomisma.org  took 917.0913200378418s
License | MR license check for Nomisma.org  took 0.4436936378479004s
License | HR license check for Nomisma.org  took 59.64717888832092s
Amount of data | Number of property check for Nomisma.org  took 0.4087104797363281s
Understandability | Number of label check for Nomisma.org  took 15.208820104598999s
Understandability | URI regex check for Nomisma.org  took 0.7135896682739258s
Understandability | Vocabs check for Nomisma.org  took 0.3248414993286133s
Verifiability | Authors check for Nomisma.org  took 0.3273582458496094s
Verifiability | Publishers check for Nomisma.org  took 0.3538858890533447s
Performance | Throughput check for Nomisma.org  took 11.714959383010864s
Amount of data | Check the number of entities for Nomisma.org  took 59.159101486206055s
Verifiability | Contribs. check for Nomisma.org  took 0.348604679107666s
Interlinking | sameAs chians check for Nomisma.org  took 0.3674793243408203s
Interlinking | skos check for Nomisma.org  took 1.176499366760254s
Interlinking | skos check for Nomisma.org  took 0.5070867538452148s
Timeliness | dataset update frequency check for Nomisma.org  took 0.3376302719116211s
Currency | Creation date check for Nomisma.org  took 0.7340447902679443s
Currency | Modification date check for Nomisma.org  took 0.6969029903411865s
Rep.Conc. | URIs length for Nomisma.org  took 388.9314615726471s
Interoperability | New vocabularies check for Nomisma.org  took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.39938902854919434s
Accuracy | Check Functional Property for Nomisma.org  took 0.3530001640319824s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3360111713409424s
Accuracy | Check Empty annotation labels for Nomisma.org  took 313.4212996959686s
Accuracy | Check White space in annotation for Nomisma.org  took 2.740344524383545s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.351741313934326s
Consistency | Disjoint class check for Nomisma.org  took 0.38161253929138184s
Consistency | Check Misplaced properties for Nomisma.org  took 26.50649094581604s
Consistency | Check Ontology hijacking for Nomisma.org  took 318.0467998981476s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 1.9435131549835205s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 33.28423619270325s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.7830121517181396s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.37279725074768066s
Security | Sign check for Nomisma.org  took 0.3579847812652588s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1675.598256111145s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.314882516860962s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.022670269012451172s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 7.033348083496094e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0008189678192138672s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 0.00011324882507324219s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 4.76837158203125e-06s
Believability | Calculation of trust value for Nomisma.org  took 9.775161743164062e-06s
INFO | --- Analysis for nomisma_org took 8437.538089752197s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 8.106231689453125e-05s
Availability | VoID file availability check for Curriculum Vitae took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.16017770767211914s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.022085189819335938s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.170967102050781e-05s
Believability | Calculation of trust value for Curriculum Vitae took 1.0728836059570312e-05s
INFO | --- Analysis for Nordine_Bittich took 1.753810167312622s
Availability | SPARQL endpoint availability check for NorPark took 8.177757263183594e-05s
Availability | VoID file availability check for NorPark took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for NorPark took 0.1566162109375s
Reputation | Calculation of the PageRank for NorPark took 0.020845413208007812s
Interlinking | Calculation of Degree of Connection for NorPark took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NorPark took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.363059997558594e-05s
Believability | Calculation of trust value for NorPark took 1.1444091796875e-05s
INFO | --- Analysis for norpark took 1.7853760719299316s
Availability | SPARQL endpoint availability check for Parking Dataset took 8.296966552734375e-05s
Availability | VoID file availability check for Parking Dataset took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.16496753692626953s
Reputation | Calculation of the PageRank for Parking Dataset took 0.020992279052734375s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.38690185546875e-05s
Believability | Calculation of trust value for Parking Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for norpark2 took 1.7868199348449707s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 8.0108642578125e-05s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.15787887573242188s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.02096843719482422s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 2.9087066650390625e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.0251998901367188e-05s
INFO | --- Analysis for Norway_Fishery_ took 1.7602875232696533s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 7.939338684082031e-05s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.15207195281982422s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.02118659019470215s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.649162292480469e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.0251998901367188e-05s
INFO | --- Analysis for norwegian-geo-divisions took 1.7373790740966797s
Availability | SPARQL endpoint availability check for NITP took 4.124641418457031e-05s
Availability | VoID file availability check for NITP took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for NITP took 0.1589665412902832s
Reputation | Calculation of the PageRank for NITP took 0.021848201751708984s
Interlinking | Calculation of Degree of Connection for NITP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NITP took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for NITP took 6.508827209472656e-05s
Believability | Calculation of trust value for NITP took 1.0967254638671875e-05s
INFO | --- Analysis for notIdentifier took 1.8148231506347656s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 7.987022399902344e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.1625351905822754s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.4809112548828125e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.3589859008789062e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 1.7514536380767822s
Availability | SPARQL endpoint availability check for NPM took 8.177757263183594e-05s
Availability | VoID file availability check for NPM took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for NPM took 0.15541934967041016s
Reputation | Calculation of the PageRank for NPM took 0.020897388458251953s
Interlinking | Calculation of Degree of Connection for NPM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for NPM took 3.409385681152344e-05s
Believability | Calculation of trust value for NPM took 1.0728836059570312e-05s
INFO | --- Analysis for npm took 1.7454261779785156s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.03246021270751953s
Availability | VoID file availability check for NTNU special collections took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.16021466255187988s
Reputation | Calculation of the PageRank for NTNU special collections took 0.021640777587890625s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.340576171875e-05s
Believability | Calculation of trust value for NTNU special collections took 1.0251998901367188e-05s
INFO | --- Analysis for ntnusc took 1.7939209938049316s
Availability | SPARQL endpoint availability check for links took 6.341934204101562e-05s
Availability | VoID file availability check for links took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for links took 0.15555334091186523s
Reputation | Calculation of the PageRank for links took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for links took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for links took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for links took 1.1205673217773438e-05s
Believability | Calculation of trust value for links took 1.0013580322265625e-05s
INFO | --- Analysis for nugmyanmar took 1.7607946395874023s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 7.963180541992188e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00041484832763671875s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.1506485939025879s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.250640869140625e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 1.2159347534179688e-05s
INFO | --- Analysis for nuts-geovocab took 1.7507977485656738s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 7.891654968261719e-05s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.15281152725219727s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.021965503692626953s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.341934204101562e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.0728836059570312e-05s
INFO | --- Analysis for nvd took 1.7564136981964111s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 7.653236389160156e-05s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.00042748451232910156s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.15908312797546387s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.367134094238281e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 4.291534423828125e-06s
INFO | --- Analysis for nvs took 1.7471327781677246s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 6.508827209472656e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.15520167350769043s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018143653869628906s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.0967254638671875e-05s
INFO | --- Analysis for nytimes-linked-open-data took 1.7520489692687988s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 7.891654968261719e-05s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.1539313793182373s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02064204216003418s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 9.202957153320312e-05s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 9.5367431640625e-06s
INFO | --- Analysis for ocd took 1.7609550952911377s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 8.130073547363281e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.15370583534240723s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.02029705047607422s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.7670135498046875e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.0251998901367188e-05s
INFO | --- Analysis for oceandrilling-borehole took 1.7285711765289307s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 8.96453857421875e-05s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.16687464714050293s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.02043890953063965s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 7.748603820800781e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 9.5367431640625e-06s
INFO | --- Analysis for oceandrilling-codices took 1.7751169204711914s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 0.00011658668518066406s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.15924835205078125s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02190423011779785s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.361701965332031e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.049041748046875e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 1.7672200202941895s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 8.082389831542969e-05s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.15781903266906738s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02113175392150879s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.361701965332031e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.1205673217773438e-05s
INFO | --- Analysis for oceandrilling-forams took 1.7527415752410889s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 8.177757263183594e-05s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.1608438491821289s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.02022862434387207s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-janus took 1.785132884979248s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 4.1961669921875e-05s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.15526938438415527s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.2901763916015625e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.0013580322265625e-05s
INFO | --- Analysis for oceandrilling-janusamp took 1.7364003658294678s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.9577484130859375e-05s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.15246915817260742s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.02046346664428711s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.049041748046875e-05s
INFO | --- Analysis for oceandrilling-ldeo took 1.8118088245391846s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 7.963180541992188e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.15640473365783691s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.021294116973876953s
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.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.435943603515625e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.0967254638671875e-05s
INFO | --- Analysis for oclc-fast took 1.744499921798706s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.506111145019531e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.1631450653076172s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020375728607177734s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.8371810913085938e-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 1.776918888092041s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 7.82012939453125e-05s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.15512704849243164s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.266334533691406e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 1.049041748046875e-05s
INFO | --- Analysis for odc-lsoa took 1.7515463829040527s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 8.296966552734375e-05s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.15295696258544922s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.02218770980834961s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.72747802734375e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for oecd-linked-data took 1.7497873306274414s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 7.963180541992188e-05s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.16548442840576172s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.022168874740600586s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 3.647804260253906e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.0967254638671875e-05s
INFO | --- Analysis for ogolod took 1.7596993446350098s
Availability | SPARQL endpoint availability check for OLAC Metadata took 8.392333984375e-05s
Availability | VoID file availability check for OLAC Metadata took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.1623096466064453s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.021285295486450195s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.0531158447265625e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.1205673217773438e-05s
INFO | --- Analysis for olac took 1.7676324844360352s
Availability | SPARQL endpoint availability check for OLiA took 8.20159912109375e-05s
Availability | VoID file availability check for OLiA took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for OLiA took 0.1519913673400879s
Reputation | Calculation of the PageRank for OLiA took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for OLiA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012135505676269531s
Believability | Calculation of trust value for OLiA took 1.0728836059570312e-05s
INFO | --- Analysis for olia took 1.7277252674102783s
Availability | SPARQL endpoint availability check for OLiA Discourse took 7.891654968261719e-05s
Availability | VoID file availability check for OLiA Discourse took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.15151476860046387s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.9577484130859375e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.0013580322265625e-05s
INFO | --- Analysis for olia-discourse took 1.7306127548217773s
Availability | SPARQL endpoint availability check for Open Land Use took 5.53131103515625e-05s
Availability | VoID file availability check for Open Land Use took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.15524649620056152s
Reputation | Calculation of the PageRank for Open Land Use took 0.02120828628540039s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 3.0517578125e-05s
Believability | Calculation of trust value for Open Land Use took 6.4373016357421875e-06s
INFO | --- Analysis for OLU took 1.7371785640716553s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 8.797645568847656e-05s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.15361499786376953s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-als took 1.7099330425262451s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00014543533325195312s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.166168212890625s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.02202463150024414s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
INFO | --- Analysis for omwn-arb took 1.7647476196289062s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 8.225440979003906e-05s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.1676311492919922s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-bul took 1.7834992408752441s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 8.0108642578125e-05s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.1586899757385254s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-cow took 1.728485107421875s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 7.987022399902344e-05s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.16423773765563965s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020407438278198242s
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.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-cwn took 1.7972421646118164s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.16259980201721191s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.02165842056274414s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-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 1.8469066619873047s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.00010275840759277344s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.001313924789428711s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.16036200523376465s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.021112918853759766s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-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 1.771639108657837s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.00041484832763671875s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.16220855712890625s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.021216392517089844s
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.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-eng took 1.745363473892212s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 7.987022399902344e-05s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.16127896308898926s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.023022174835205078s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-fas took 1.7618486881256104s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.000331878662109375s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.1623079776763916s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-fin took 1.7513847351074219s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 8.034706115722656e-05s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.15147161483764648s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-fra took 1.7729871273040771s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 6.794929504394531e-05s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.16896820068359375s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020940303802490234s
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.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
INFO | --- Analysis for omwn-heb took 1.786320686340332s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00041794776916503906s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.17321515083312988s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.022169113159179688s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 5.4836273193359375e-06s
INFO | --- Analysis for omwn-hrv took 1.7569472789764404s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 7.939338684082031e-05s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.00021338462829589844s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.15220117568969727s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020936250686645508s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-isl took 1.7959823608398438s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 6.699562072753906e-05s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.15874576568603516s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-ita took 1.7946984767913818s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 8.034706115722656e-05s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.16355156898498535s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.022030353546142578s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-iwn took 1.7430508136749268s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 7.963180541992188e-05s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.15788912773132324s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.021599769592285156s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.430511474609375e-05s
INFO | --- Analysis for omwn-jpn took 1.7675487995147705s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 7.700920104980469e-05s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.15253233909606934s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.02089238166809082s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-mcr took 1.8330707550048828s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 8.034706115722656e-05s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.1686112880706787s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.022110462188720703s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
INFO | --- Analysis for omwn-msa took 1.7623052597045898s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 7.963180541992188e-05s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.2037191390991211s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.0220792293548584s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
INFO | --- Analysis for omwn-nld took 1.8363666534423828s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 8.034706115722656e-05s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.15194129943847656s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
INFO | --- Analysis for omwn-nor took 1.7846789360046387s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004134178161621094s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.16017460823059082s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-pol took 1.7763707637786865s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 4.57763671875e-05s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.15613794326782227s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-por took 1.7634034156799316s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.17076754570007324s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-ron took 1.7760076522827148s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 8.177757263183594e-05s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.16075348854064941s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 5.9604644775390625e-06s
INFO | --- Analysis for omwn-slk took 1.7438223361968994s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 6.127357482910156e-05s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.16563940048217773s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-slv took 1.723947525024414s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 8.082389831542969e-05s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.15150070190429688s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-swe took 1.7652556896209717s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 6.556510925292969e-05s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.16031122207641602s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-tha took 1.7376220226287842s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 0.00011038780212402344s
Availability | VoID file availability check for OntoBeef Domain took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.15846943855285645s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.02148914337158203s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.458427429199219e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.3589859008789062e-05s
INFO | --- Analysis for ontobeef-domain took 1.7337117195129395s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.029273986816406e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.1593012809753418s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.021856307983398438s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.036064147949219e-05s
Believability | Calculation of trust value for Ontos News Portal took 1.0013580322265625e-05s
INFO | --- Analysis for ontos-news-portal took 1.742551565170288s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 6.0558319091796875e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.159348726272583s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.218650817871094e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 6.198883056640625e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 1.761589527130127s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.2438507080078125e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.15543293952941895s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.743171691894531e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 9.5367431640625e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 1.740795373916626s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 3.9577484130859375e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.16081976890563965s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.5299530029296875e-05s
Believability | Calculation of trust value for Open Data Euskadi took 1.0013580322265625e-05s
INFO | --- Analysis for open-data-euskadi took 1.716559886932373s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 7.724761962890625e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.1610565185546875s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020505189895629883s
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.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 9.751319885253906e-05s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 9.298324584960938e-06s
INFO | --- Analysis for open-data-risp took 1.7631988525390625s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 8.440017700195312e-05s
Availability | VoID file availability check for Open Data Thesaurus took 0.002350330352783203s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.16280674934387207s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.02144598960876465s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.867813110351562e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for open-data-thesaurus took 1.77695631980896s
Availability | SPARQL endpoint availability check for Open Election Data Project took 8.630752563476562e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.18044781684875488s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020972251892089844s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.4849853515625e-05s
Believability | Calculation of trust value for Open Election Data Project took 1.239776611328125e-05s
INFO | --- Analysis for open-election-data-project took 1.7512571811676025s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 6.29425048828125e-05s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.16925907135009766s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.320808410644531e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 1.0013580322265625e-05s
INFO | --- Analysis for open-energy-info-wiki took 1.8101038932800293s
Availability | SPARQL endpoint availability check for Open Library took 9.250640869140625e-05s
Availability | VoID file availability check for Open Library took 0.0001990795135498047s
Completeness | Calculation of interlinking completeness for Open Library took 0.15308904647827148s
Reputation | Calculation of the PageRank for Open Library took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for Open Library took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Library took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.818771362304688e-05s
Believability | Calculation of trust value for Open Library took 8.821487426757812e-06s
INFO | --- Analysis for open-library took 1.7512366771697998s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 4.029273986816406e-05s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.15868306159973145s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.020396709442138672s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.0013580322265625e-05s
INFO | --- Analysis for Open_Land_Use took 1.7322101593017578s
Availability | SPARQL endpoint availability check for flyatlas took 4.0531158447265625e-05s
Availability | VoID file availability check for flyatlas took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for flyatlas took 0.16237640380859375s
Reputation | Calculation of the PageRank for flyatlas took 0.020449399948120117s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.075599670410156e-05s
Believability | Calculation of trust value for flyatlas took 1.0013580322265625e-05s
INFO | --- Analysis for openbiomed-flyatlas took 1.735414981842041s
Availability | SPARQL endpoint availability check for OpenCalais took 8.0108642578125e-05s
Availability | VoID file availability check for OpenCalais took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.15757036209106445s
Reputation | Calculation of the PageRank for OpenCalais took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for OpenCalais took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010514259338378906s
Believability | Calculation of trust value for OpenCalais took 1.0728836059570312e-05s
INFO | --- Analysis for opencalais took 1.7709879875183105s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 3.933906555175781e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.16001057624816895s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.677078247070312e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 1.0013580322265625e-05s
INFO | --- Analysis for opencorporates took 1.7873806953430176s
Availability | SPARQL endpoint availability check for OpenCyc took 8.177757263183594e-05s
Availability | VoID file availability check for OpenCyc took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.15541815757751465s
Reputation | Calculation of the PageRank for OpenCyc took 0.021948575973510742s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00011372566223144531s
Believability | Calculation of trust value for OpenCyc took 1.2636184692382812e-05s
INFO | --- Analysis for opencyc took 1.7765803337097168s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 6.580352783203125e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.15978169441223145s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.022497177124023438s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 0.00012063980102539062s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.647804260253906e-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 1.7425916194915771s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 8.320808410644531e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.15040349960327148s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 1.7611064910888672s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.16387176513671875s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.021716594696044922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.7571842670440674s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 6.008148193359375e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.16139793395996094s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 1.74098801612854s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 6.532669067382812e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.15010666847229004s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.021703720092773438s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 4.5299530029296875e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 1.7484028339385986s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 8.058547973632812e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.15184545516967773s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 1.7102646827697754s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.15920615196228027s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.020813941955566406s
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.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 1.7372868061065674s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00010251998901367188s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.22413039207458496s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0202944278717041s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.8970239162445068s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 8.702278137207031e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.16171622276306152s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.021547317504882812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0009632110595703125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.8320097923278809s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 8.273124694824219e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.1630864143371582s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.021201372146606445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 1.8298287391662598s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.1592264175415039s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 1.7881910800933838s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.9591064453125e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.15441107749938965s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 1.7323925495147705s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.00041604042053222656s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.1596524715423584s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 1.751107931137085s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 8.106231689453125e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.15285778045654297s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02188420295715332s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 1.7126660346984863s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 8.416175842285156e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.15773653984069824s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 1.7495231628417969s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 8.0108642578125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.00041937828063964844s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.15263652801513672s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.021999120712280273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 1.7782196998596191s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 8.20159912109375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.15872454643249512s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02142500877380371s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.787099838256836s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.16373848915100098s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 1.7520172595977783s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.15349721908569336s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02202010154724121s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 1.8367908000946045s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0005421638488769531s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.15566444396972656s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.021596908569335938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.775161743164062e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.792337417602539s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 8.0108642578125e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.00041961669921875s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.1520395278930664s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 1.7493529319763184s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 7.915496826171875e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.16080522537231445s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.022641658782958984s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 1.7597613334655762s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 8.678436279296875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.15254569053649902s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.021066904067993164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.7636094093322754s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.16877007484436035s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.7741904258728027s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.1530470848083496s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.7377479076385498s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.00042319297790527344s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.16406607627868652s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.022466659545898438s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 7.081031799316406e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.7701356410980225s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 6.437301635742188e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.15283966064453125s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.022719621658325195s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0008475780487060547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.7479939460754395s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 7.939338684082031e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.15847539901733398s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02065587043762207s
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.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.767077922821045s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.00011491775512695312s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.15881562232971191s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020821571350097656s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.7885479927062988s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.15265846252441406s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.021242618560791016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.7936286926269531s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 8.7738037109375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.15127897262573242s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.022119998931884766s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.742692470550537s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 8.0108642578125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.15926146507263184s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.8321993350982666s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 3.981590270996094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.18601775169372559s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.839897155761719e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.8319668769836426s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.15909767150878906s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.7612788677215576s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.1538529396057129s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.000995635986328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 5.1975250244140625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.8004252910614014s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 7.963180541992188e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.20920753479003906s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 1.8211874961853027s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 8.463859558105469e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.16331744194030762s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.021264076232910156s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.1484832763671875e-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 1.7327337265014648s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.160078763961792s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020250320434570312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 1.7477543354034424s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.273124694824219e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.1632835865020752s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.022797346115112305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.7413330078125s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.7738037109375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.1578361988067627s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.7415835857391357s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 8.130073547363281e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.1666882038116455s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02040266990661621s
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.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.7615060806274414s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 8.392333984375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.18003487586975098s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.7558095455169678s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 5.459785461425781e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.16350102424621582s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.0203092098236084s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 1.756681203842163s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 3.8623809814453125e-05s
Availability | VoID file availability check for Open Data of Ecuador took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.15219640731811523s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 7.939338684082031e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.1920928955078125e-05s
INFO | --- Analysis for opendataec took 1.7143428325653076s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.1599109172821045s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.1682510375976562e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.7755157947540283s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.9591064453125e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.15582633018493652s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.1920928955078125e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 1.714226245880127s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.124641418457031e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.15946078300476074s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020452499389648438s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.1682510375976562e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 1.7528796195983887s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.16036391258239746s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.02274179458618164s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 1.7643465995788574s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 8.249282836914062e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.15839076042175293s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 1.7388043403625488s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 0.00022721290588378906s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.1543867588043213s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007414817810058594s
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 9.5367431640625e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 1.7626574039459229s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 8.296966552734375e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.1524066925048828s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.021828651428222656s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 1.7661616802215576s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 8.273124694824219e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.15308094024658203s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.239776611328125e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 1.7562975883483887s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 8.320808410644531e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.16013026237487793s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 1.7575159072875977s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 6.604194641113281e-05s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.15584897994995117s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020177602767944336s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 2.8371810913085938e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.1682510375976562e-05s
INFO | --- Analysis for openlink-lod-cache took 1.7595629692077637s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.1484832763671875e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.15344691276550293s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.226799011230469e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.2159347534179688e-05s
INFO | --- Analysis for openlinksw-dataspaces took 1.864539384841919s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 5.316734313964844e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.16289496421813965s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.1552734375e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 1.1920928955078125e-05s
INFO | --- Analysis for openlylocal took 1.7536060810089111s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 4.076957702636719e-05s
Availability | VoID file availability check for OpenMobileNetwork took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.16064834594726562s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.033348083496094e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.0013580322265625e-05s
INFO | --- Analysis for openmobilenetwork took 1.7719640731811523s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 3.910064697265625e-05s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.1624295711517334s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02090144157409668s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.131431579589844e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 1.8089470863342285s
Availability | SPARQL endpoint availability check for oreilly took 8.034706115722656e-05s
Availability | VoID file availability check for oreilly took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for oreilly took 0.16499567031860352s
Reputation | Calculation of the PageRank for oreilly took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for oreilly took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for oreilly took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.6253204345703125e-05s
Believability | Calculation of trust value for oreilly took 1.1205673217773438e-05s
INFO | --- Analysis for oreilly took 1.8307015895843506s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 8.225440979003906e-05s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.20349860191345215s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.022368907928466797s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.00072479248046875s
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.239776611328125e-05s
INFO | --- Analysis for Organchem-Data took 1.7942736148834229s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 4.124641418457031e-05s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.15747404098510742s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.532669067382812e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for organic-edunet took 1.7908351421356201s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 8.130073547363281e-05s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.15167546272277832s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.02274775505065918s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.1205673217773438e-05s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.2636184692382812e-05s
INFO | --- Analysis for orkg took 1.7805984020233154s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.8691024780273438s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.17078948020935059s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 7.581710815429688e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.0251998901367188e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 7.040635585784912s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 8.20159912109375e-05s
Availability | VoID file availability check for OSM Semantic Network took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.1568131446838379s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.02016758918762207s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.4332275390625e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.1444091796875e-05s
INFO | --- Analysis for osm-semantic-network took 1.7265381813049316s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 8.392333984375e-05s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.16028189659118652s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.02233123779296875s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 2.765655517578125e-05s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for OTM took 1.7427055835723877s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.4978106021881104s
Availability | VoID file availability check for Pali English Lexicon took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.1597898006439209s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020154237747192383s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.6464462280273438e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.1682510375976562e-05s
INFO | --- Analysis for pali-english-lexicon took 4.4774370193481445s
Availability | SPARQL endpoint availability check for PanLex took 8.058547973632812e-05s
Availability | VoID file availability check for PanLex took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for PanLex took 0.16343259811401367s
Reputation | Calculation of the PageRank for PanLex took 0.020806074142456055s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0008306503295898438s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.295608520507812e-05s
Believability | Calculation of trust value for PanLex took 1.1682510375976562e-05s
INFO | --- Analysis for panlex took 1.7445068359375s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 8.0108642578125e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.1551201343536377s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.62396240234375e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.2159347534179688e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 1.768207311630249s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 8.106231689453125e-05s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.15334177017211914s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.021498918533325195s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.935264587402344e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 1.1444091796875e-05s
INFO | --- Analysis for patents-data-gov-uk took 1.9515142440795898s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 8.654594421386719e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.1520376205444336s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.552436828613281e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.1444091796875e-05s
INFO | --- Analysis for pdev-lemon took 1.7291064262390137s
Availability | SPARQL endpoint availability check for pdevlemon took 8.368492126464844e-05s
Availability | VoID file availability check for pdevlemon took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2626008987426758s
Reputation | Calculation of the PageRank for pdevlemon took 0.020328521728515625s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.7894973754882812e-05s
Believability | Calculation of trust value for pdevlemon took 1.1682510375976562e-05s
INFO | --- Analysis for pdevlemon took 1.8514630794525146s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.1484832763671875e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.15335655212402344s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020390987396240234s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.606910705566406e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.0728836059570312e-05s
INFO | --- Analysis for periodo took 1.756131649017334s
Availability | SPARQL endpoint availability check for Personal_Homepages took 8.344650268554688e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.1555788516998291s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.02195453643798828s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00039386749267578125s
Believability | Calculation of trust value for Personal_Homepages took 1.1205673217773438e-05s
INFO | --- Analysis for personal-homepages took 1.7936100959777832s
Availability | SPARQL endpoint availability check for Ontology of University People took 8.296966552734375e-05s
Availability | VoID file availability check for Ontology of University People took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.23004889488220215s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 2.8133392333984375e-05s
Believability | Calculation of trust value for Ontology of University People took 1.1682510375976562e-05s
INFO | --- Analysis for PersonOnto took 1.8274013996124268s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 9.632110595703125e-05s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.15149545669555664s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0967254638671875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1682510375976562e-05s
INFO | --- Analysis for PFKHS took 1.7077367305755615s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.029273986816406e-05s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.1617107391357422s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.022307395935058594s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.049041748046875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0967254638671875e-05s
INFO | --- Analysis for PFRPPH took 1.7444558143615723s
Availability | SPARQL endpoint availability check for PGxLOD took 8.344650268554688e-05s
Availability | VoID file availability check for PGxLOD took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.15929245948791504s
Reputation | Calculation of the PageRank for PGxLOD took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for PGxLOD took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 3.910064697265625e-05s
Believability | Calculation of trust value for PGxLOD took 1.1205673217773438e-05s
INFO | --- Analysis for PGxLOD took 1.7496843338012695s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 9.608268737792969e-05s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.1531352996826172s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020218372344970703s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.170967102050781e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1444091796875e-05s
INFO | --- Analysis for phoible took 1.7972931861877441s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 8.463859558105469e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.1625514030456543s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.02019643783569336s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 2.7418136596679688e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 6.4373016357421875e-06s
INFO | --- Analysis for PISM took 1.769625186920166s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 8.130073547363281e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.15337300300598145s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.535385131835938e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.2159347534179688e-05s
INFO | --- Analysis for planetdata-project-wiki took 1.7587077617645264s
Availability | SPARQL endpoint availability check for digitized plant specimen took 8.249282836914062e-05s
Availability | VoID file availability check for digitized plant specimen took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.16279911994934082s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020254135131835938s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.389617919921875e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.1682510375976562e-05s
INFO | --- Analysis for plant-specimen took 1.766998529434204s
Availability | SPARQL endpoint availability check for Pleiades took 4.220008850097656e-05s
Availability | VoID file availability check for Pleiades took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Pleiades took 0.17798686027526855s
Reputation | Calculation of the PageRank for Pleiades took 0.02161121368408203s
Interlinking | Calculation of Degree of Connection for Pleiades took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pleiades took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.273124694824219e-05s
Believability | Calculation of trust value for Pleiades took 1.0728836059570312e-05s
INFO | --- Analysis for pleiades took 1.7768135070800781s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 3.910064697265625e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.15602421760559082s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.021308183670043945s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.361701965332031e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.4066696166992188e-05s
INFO | --- Analysis for podorozhnyk took 1.7437031269073486s
Availability | SPARQL endpoint availability check for Poképédia took 8.058547973632812e-05s
Availability | VoID file availability check for Poképédia took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Poképédia took 0.15874075889587402s
Reputation | Calculation of the PageRank for Poképédia took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Poképédia took 6.842613220214844e-05s
Believability | Calculation of trust value for Poképédia took 1.0728836059570312e-05s
INFO | --- Analysis for pokepedia-fr took 1.8224859237670898s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.57763671875e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.1695404052734375s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020247936248779297s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.128715515136719e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.2159347534179688e-05s
INFO | --- Analysis for polymath-virtual-library took 1.7969093322753906s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4.029273986816406e-05s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.15456533432006836s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2874603271484375e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.0728836059570312e-05s
INFO | --- Analysis for portuguese_prisons_releases took 1.7599701881408691s
Availability | SPARQL endpoint availability check for prefix.cc took 4.029273986816406e-05s
Availability | VoID file availability check for prefix.cc took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.1548302173614502s
Reputation | Calculation of the PageRank for prefix.cc took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for prefix.cc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.6716461181640625e-05s
Believability | Calculation of trust value for prefix.cc took 3.504753112792969e-05s
INFO | --- Analysis for prefix-cc took 1.7741732597351074s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 8.463859558105469e-05s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.17241215705871582s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.6253204345703125e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.2159347534179688e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 1.7751922607421875s
Availability | SPARQL endpoint availability check for PreLex took 8.273124694824219e-05s
Availability | VoID file availability check for PreLex took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for PreLex took 0.17538690567016602s
Reputation | Calculation of the PageRank for PreLex took 0.02204108238220215s
Interlinking | Calculation of Degree of Connection for PreLex took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for PreLex took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for PreLex took 6.556510925292969e-05s
Believability | Calculation of trust value for PreLex took 9.5367431640625e-06s
INFO | --- Analysis for prelex took 1.803215503692627s
Availability | SPARQL endpoint availability check for Prelinger Archives took 3.1950578689575195s
Availability | VoID file availability check for Prelinger Archives took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.15533685684204102s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.02167057991027832s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 2.7179718017578125e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.0967254638671875e-05s
INFO | --- Analysis for prelinger_archives took 5.725826740264893s
Availability | SPARQL endpoint availability check for PreMOn took 8.130073547363281e-05s
Availability | VoID file availability check for PreMOn took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for PreMOn took 0.16095519065856934s
Reputation | Calculation of the PageRank for PreMOn took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for PreMOn took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for PreMOn took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for PreMOn took 4.887580871582031e-05s
Believability | Calculation of trust value for PreMOn took 1.049041748046875e-05s
INFO | --- Analysis for premon took 1.7369146347045898s
Availability | SPARQL endpoint availability check for Previsible took 8.320808410644531e-05s
Availability | VoID file availability check for Previsible took 0.00020051002502441406s
Completeness | Calculation of interlinking completeness for Previsible took 0.15714192390441895s
Reputation | Calculation of the PageRank for Previsible took 0.020200490951538086s
Interlinking | Calculation of Degree of Connection for Previsible took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.0728836059570312e-05s
Believability | Calculation of trust value for Previsible took 1.049041748046875e-05s
INFO | --- Analysis for Previsible took 1.727586269378662s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.220008850097656e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.15816783905029297s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.364418029785156e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.1682510375976562e-05s
INFO | --- Analysis for princeton-library-findingaids took 1.7233781814575195s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 4.3392181396484375e-05s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.1542034149169922s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.021338939666748047s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for PrinParLat took 1.7180588245391846s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.28995275497436523s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.1535346508026123s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.700920104980469e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1205673217773438e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 2.088912010192871s
Availability | SPARQL endpoint availability check for Prior Panel took 8.058547973632812e-05s
Availability | VoID file availability check for Prior Panel took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.1629776954650879s
Reputation | Calculation of the PageRank for Prior Panel took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for Prior Panel took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.075599670410156e-05s
Believability | Calculation of trust value for Prior Panel took 1.1682510375976562e-05s
INFO | --- Analysis for Prior_Panel took 1.777012586593628s
Availability | SPARQL endpoint availability check for ProductDB took 5.507469177246094e-05s
Availability | VoID file availability check for ProductDB took 0.00021004676818847656s
Completeness | Calculation of interlinking completeness for ProductDB took 0.15884137153625488s
Reputation | Calculation of the PageRank for ProductDB took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for ProductDB took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ProductDB took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.152557373046875e-05s
Believability | Calculation of trust value for ProductDB took 1.239776611328125e-05s
INFO | --- Analysis for productdb took 1.7851343154907227s
Availability | SPARQL endpoint availability check for Product Types Ontology took 8.058547973632812e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.15982961654663086s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.104873657226562e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.239776611328125e-05s
INFO | --- Analysis for productontology took 1.7231106758117676s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 5.245208740234375e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.1609969139099121s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020434141159057617s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 9.918212890625e-05s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.0013580322265625e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 1.7480156421661377s
Availability | SPARQL endpoint availability check for provenanceweb took 4.887580871582031e-05s
Availability | VoID file availability check for provenanceweb took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.16402411460876465s
Reputation | Calculation of the PageRank for provenanceweb took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for provenanceweb took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 6.961822509765625e-05s
Believability | Calculation of trust value for provenanceweb took 1.0251998901367188e-05s
INFO | --- Analysis for provenanceweb took 1.7351229190826416s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 5.0067901611328125e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.15668439865112305s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010251998901367188s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.239776611328125e-05s
INFO | --- Analysis for proyectoapadrina took 1.760718584060669s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 6.103515625e-05s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.15642619132995605s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.0994415283203125e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 1.0967254638671875e-05s
INFO | --- Analysis for pscs-catalogue took 1.7435884475708008s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 3.981590270996094e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.15104889869689941s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.02230238914489746s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 6.866455078125e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.4066696166992188e-05s
INFO | --- Analysis for psh-subject-headings took 1.766200304031372s
Availability | SPARQL endpoint availability check for Depression took 8.20159912109375e-05s
Availability | VoID file availability check for Depression took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Depression took 0.1567225456237793s
Reputation | Calculation of the PageRank for Depression took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for Depression took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Depression took 2.7179718017578125e-05s
Believability | Calculation of trust value for Depression took 1.049041748046875e-05s
INFO | --- Analysis for Psychology took 1.7463548183441162s
Availability | SPARQL endpoint availability check for PubChem RDF took 8.034706115722656e-05s
Availability | VoID file availability check for PubChem RDF took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.1590101718902588s
Reputation | Calculation of the PageRank for PubChem RDF took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.1484832763671875e-05s
Believability | Calculation of trust value for PubChem RDF took 1.049041748046875e-05s
INFO | --- Analysis for PubChem_RDF took 1.7534270286560059s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 7.987022399902344e-05s
Availability | VoID file availability check for Public Spending in Greece took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.16936206817626953s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 7.891654968261719e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.049041748046875e-05s
INFO | --- Analysis for public-spending-in-greece took 1.7745697498321533s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 8.153915405273438e-05s
Availability | VoID file availability check for Publications Office Authority tables took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.1626269817352295s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 3.3855438232421875e-05s
Believability | Calculation of trust value for Publications Office Authority tables took 1.2874603271484375e-05s
INFO | --- Analysis for publications_office_authority_tables took 1.7763240337371826s
Availability | SPARQL endpoint availability check for QBOAirbase took 8.058547973632812e-05s
Availability | VoID file availability check for QBOAirbase took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.16469955444335938s
Reputation | Calculation of the PageRank for QBOAirbase took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.510185241699219e-05s
Believability | Calculation of trust value for QBOAirbase took 1.0728836059570312e-05s
INFO | --- Analysis for qboairbase took 1.7779529094696045s
Availability | SPARQL endpoint availability check for Qualité de l'air took 6.794929504394531e-05s
Availability | VoID file availability check for Qualité de l'air took 0.00020766258239746094s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.16054201126098633s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.86102294921875e-05s
Believability | Calculation of trust value for Qualité de l'air took 9.775161743164062e-06s
INFO | --- Analysis for Qualité_de_l'air took 1.7633004188537598s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 8.463859558105469e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.158919095993042s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.021670818328857422s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.0279159545898438e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.1444091796875e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 1.7695040702819824s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5733613967895508s
Availability | VoID file availability check for Querolus in LiLa took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.17197704315185547s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Querolus in LiLa took 9.298324584960938e-06s
INFO | --- Analysis for Querolus took 2.6895363330841064s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.5299530029296875e-05s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15278029441833496s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.02123546600341797s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.649162292480469e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.4836273193359375e-06s
INFO | --- Analysis for racai-legalnero took 1.7274081707000732s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.506111145019531e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.15237116813659668s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.02127385139465332s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 2.956390380859375e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.1444091796875e-05s
INFO | --- Analysis for racai-llod-corola-we took 1.9083030223846436s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 8.20159912109375e-05s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.15144634246826172s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.075599670410156e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.2159347534179688e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 1.7537662982940674s
Availability | SPARQL endpoint availability check for RoLEX took 8.082389831542969e-05s
Availability | VoID file availability check for RoLEX took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for RoLEX took 0.15410804748535156s
Reputation | Calculation of the PageRank for RoLEX took 0.020467758178710938s
Interlinking | Calculation of Degree of Connection for RoLEX took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for RoLEX took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for RoLEX took 2.7179718017578125e-05s
Believability | Calculation of trust value for RoLEX took 1.0967254638671875e-05s
INFO | --- Analysis for racai-llod-rolex took 1.7234487533569336s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.106231689453125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.15274286270141602s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020231246948242188s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 2.6226043701171875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.049041748046875e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 1.7119438648223877s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.00543212890625e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.15969181060791016s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020337820053100586s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.765655517578125e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.0967254638671875e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 1.7799875736236572s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 8.249282836914062e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.163285493850708s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 2.7418136596679688e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 1.777510643005371s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 8.177757263183594e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.159759521484375s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.021446704864501953s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007178783416748047s
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 1.7397778034210205s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 8.392333984375e-05s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.16274189949035645s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 2.956390380859375e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.0728836059570312e-05s
INFO | --- Analysis for racai-llod-rtasc took 1.7830305099487305s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.00010013580322265625s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.16842436790466309s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.02078700065612793s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 2.8848648071289062e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.0251998901367188e-05s
INFO | --- Analysis for racai-llod-simonero took 1.828275442123413s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.12265419960021973s
Availability | VoID file availability check for Rådata nå! took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.1566915512084961s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 7.867813110351562e-05s
Believability | Calculation of trust value for Rådata nå! took 9.5367431640625e-06s
INFO | --- Analysis for radatana took 1.8960144519805908s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 8.606910705566406e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.1597001552581787s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.814697265625e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 9.775161743164062e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 1.7423169612884521s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 0.00010657310485839844s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.15742897987365723s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02061748504638672s
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.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.933906555175781e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.0967254638671875e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 1.7633495330810547s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 0.00010371208190917969s
Availability | VoID file availability check for Polish LGU financial statements took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.16165566444396973s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.022569656372070312s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 2.8133392333984375e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 1.0728836059570312e-05s
INFO | --- Analysis for Rb_PL_LGU took 1.7506442070007324s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 5.4836273193359375e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.000457763671875s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.1540358066558838s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.106231689453125e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.0251998901367188e-05s
INFO | --- Analysis for rdf-book-mashup took 1.8540024757385254s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 8.58306884765625e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.16336584091186523s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.021977901458740234s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.001108407974243164s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00012063980102539062s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 1.1920928955078125e-05s
INFO | --- Analysis for rdfize-lastfm took 1.7783408164978027s
Availability | SPARQL endpoint availability check for RDFLicense took 9.250640869140625e-05s
Availability | VoID file availability check for RDFLicense took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.15929174423217773s
Reputation | Calculation of the PageRank for RDFLicense took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for RDFLicense took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 2.6226043701171875e-05s
Believability | Calculation of trust value for RDFLicense took 1.239776611328125e-05s
INFO | --- Analysis for rdflicense took 1.746086597442627s
Availability | SPARQL endpoint availability check for RDFohloh took 8.034706115722656e-05s
Availability | VoID file availability check for RDFohloh took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.1585221290588379s
Reputation | Calculation of the PageRank for RDFohloh took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for RDFohloh took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 8.893013000488281e-05s
Believability | Calculation of trust value for RDFohloh took 1.0967254638671875e-05s
INFO | --- Analysis for rdfohloh took 1.7317445278167725s
Availability | SPARQL endpoint availability check for Reactome RDF took 3.838539123535156e-05s
Availability | VoID file availability check for Reactome RDF took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.1524336338043213s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.337860107421875e-05s
Believability | Calculation of trust value for Reactome RDF took 6.198883056640625e-06s
INFO | --- Analysis for reactome-rdf took 1.7436730861663818s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 8.153915405273438e-05s
Availability | VoID file availability check for Rechtspraak.nl took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.1514873504638672s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 8.916854858398438e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 1.0251998901367188e-05s
INFO | --- Analysis for rechtspraak took 1.7680962085723877s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.029273986816406e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.1586306095123291s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02023935317993164s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.177757263183594e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.3828277587890625e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 1.746619462966919s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 8.320808410644531e-05s
Availability | VoID file availability check for reference.data.gov.uk took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.1505124568939209s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.021908044815063477s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00016379356384277344s
Believability | Calculation of trust value for reference.data.gov.uk took 1.239776611328125e-05s
INFO | --- Analysis for reference-data-gov-uk took 1.7475006580352783s
Availability | SPARQL endpoint availability check for RELD took 7.939338684082031e-05s
Availability | VoID file availability check for RELD took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for RELD took 0.16450262069702148s
Reputation | Calculation of the PageRank for RELD took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for RELD took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for RELD took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for RELD took 2.765655517578125e-05s
Believability | Calculation of trust value for RELD took 1.0013580322265625e-05s
INFO | --- Analysis for RELD took 1.7594130039215088s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 8.177757263183594e-05s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.18795228004455566s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.2636184692382812e-05s
INFO | --- Analysis for reload took 1.7781941890716553s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.16026663780212402s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 2.8848648071289062e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.239776611328125e-05s
INFO | --- Analysis for remote_Sensing took 1.7762112617492676s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 4.0531158447265625e-05s
Availability | VoID file availability check for Renewable Energy Generators took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.15196681022644043s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.267692565917969e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 1.049041748046875e-05s
INFO | --- Analysis for renewable_energy_generators took 1.7353310585021973s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 7.963180541992188e-05s
Availability | VoID file availability check for research.data.gov.uk took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.15370440483093262s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020892620086669922s
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.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 8.845329284667969e-05s
Believability | Calculation of trust value for research.data.gov.uk took 1.0967254638671875e-05s
INFO | --- Analysis for research-data-gov-uk took 1.7475271224975586s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.076957702636719e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.15466022491455078s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020922183990478516s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.365776062011719e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.2874603271484375e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 1.7433888912200928s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 8.58306884765625e-05s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.16124653816223145s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.02040386199951172s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 2.7179718017578125e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.2159347534179688e-05s
INFO | --- Analysis for revistas_turismo took 1.757538080215454s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 8.940696716308594e-05s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.15380859375s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011396408081054688s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.33514404296875e-05s
INFO | --- Analysis for revyu took 1.7564873695373535s
Availability | SPARQL endpoint availability check for sdafsadf took 3.9577484130859375e-05s
Availability | VoID file availability check for sdafsadf took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.1517167091369629s
Reputation | Calculation of the PageRank for sdafsadf took 0.02021026611328125s
Interlinking | Calculation of Degree of Connection for sdafsadf took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for sdafsadf took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 2.6941299438476562e-05s
Believability | Calculation of trust value for sdafsadf took 1.2636184692382812e-05s
INFO | --- Analysis for rgsdfg took 1.7501680850982666s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 8.940696716308594e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.16347289085388184s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.022006750106811523s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0011203289031982422s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 5.984306335449219e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.1682510375976562e-05s
INFO | --- Analysis for riese took 1.776413917541504s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.2648954391479492s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0004782676696777344s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 21.61304521560669s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.4530160427093506s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 56.37836813926697s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 1.9746782779693604s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 179.16322898864746s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 50.79019021987915s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.20889759063720703s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.14222955703735352s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.10906362533569336s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.08171987533569336s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.08327603340148926s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.04531264305115s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.1085813045501709s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 12.80603814125061s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.18941855430603027s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.08313989639282227s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.10109353065490723s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.08209371566772461s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.389299154281616s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 3.1948089599609375e-05s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.08381986618041992s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.544724464416504s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.11689376831054688s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.08543610572814941s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.09871101379394531s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.20422148704528809s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.20362544059753418s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 74.74620938301086s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.10825586318969727s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.10650110244750977s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.08226799964904785s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 12.074068069458008s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.3698720932006836s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.7029333114624023s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.08287763595581055s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 47.59882378578186s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 4.886007785797119s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.4058289527893066s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 47.38309025764465s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.7169854640960693s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.08243608474731445s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 0.9074089527130127s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.257767915725708s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 6.270408630371094e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 1.1920928955078125e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 5.0067901611328125e-06s
INFO | --- Analysis for rism took 1260.9489212036133s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.08155465126037598s
Availability | VoID file availability check for RISM Authority data took 0.0002453327178955078s
Extra | Recovery of all triples for RISM Authority data took 22.46318244934082s
Performance | Total latancy measurement for RISM Authority data took 0.4431931972503662s
Amount of data | Number of triples check for RISM Authority data took 51.997984409332275s
Interoperability | New terms check for RISM Authority data took 1.9010589122772217s
Versatility | Languages check for RISM Authority data took 160.67786574363708s
Interpretability | Number of blank nodes check for RISM Authority data took 49.38891649246216s
Security | Check HTTPS for RISM Authority data took 0.12886667251586914s
Interpretability | RDF structures check for RISM Authority data took 0.11019492149353027s
Versatility | Serialization formats check for RISM Authority data took 0.11107182502746582s
Availability | RDF dump link check for RISM Authority data took 0.09192800521850586s
License | MR license check for RISM Authority data took 0.10799336433410645s
License | HR license check for RISM Authority data took 300.00622749328613s
Amount of data | Number of property check for RISM Authority data took 0.1090691089630127s
Understandability | Number of label check for RISM Authority data took 7.671468257904053s
Understandability | URI regex check for RISM Authority data took 0.19940948486328125s
Understandability | Vocabs check for RISM Authority data took 0.08248448371887207s
Verifiability | Authors check for RISM Authority data took 0.09926438331604004s
Verifiability | Publishers check for RISM Authority data took 0.08254671096801758s
Performance | Throughput check for RISM Authority data took 10.545195817947388s
Amount of data | Check the number of entities for RISM Authority data took 0.00011420249938964844s
Verifiability | Contribs. check for RISM Authority data took 0.08324694633483887s
Interlinking | sameAs chians check for RISM Authority data took 0.9357101917266846s
Interlinking | skos check for RISM Authority data took 0.10631370544433594s
Interlinking | skos check for RISM Authority data took 0.09406280517578125s
Timeliness | dataset update frequency check for RISM Authority data took 0.0828700065612793s
Currency | Creation date check for RISM Authority data took 0.19507527351379395s
Currency | Modification date check for RISM Authority data took 0.20105338096618652s
Rep.Conc. | URIs length for RISM Authority data took 73.74614238739014s
Interoperability | New vocabularies check for RISM Authority data took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.12774896621704102s
Accuracy | Check Functional Property for RISM Authority data took 0.10554623603820801s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.10316848754882812s
Accuracy | Check Empty annotation labels for RISM Authority data took 11.353564262390137s
Accuracy | Check White space in annotation for RISM Authority data took 2.3811118602752686s
Accuracy | Check Datatype consistency for RISM Authority data took 3.7496840953826904s
Consistency | Disjoint class check for RISM Authority data took 0.09429526329040527s
Consistency | Check Misplaced properties for RISM Authority data took 47.68573307991028s
Consistency | Check Ontology hijacking for RISM Authority data took 4.8294360637664795s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.3459751605987549s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 46.71879577636719s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.8167836666107178s
Security | Sign check for RISM Authority data took 0.0841226577758789s
Availability | Check URIs Dereferenciability for RISM Authority data took 0.9197585582733154s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.2984492778778076s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020728111267089844s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 1.6689300537109375e-06s
Believability | Calculation of trust value for RISM Authority data took 7.62939453125e-06s
INFO | --- Analysis for rism-authorities took 1027.1762080192566s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.368492126464844e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.17111992835998535s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.4332275390625e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.3113021850585938e-05s
INFO | --- Analysis for rk took 1.775550365447998s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.16971397399902344s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02100825309753418s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002448558807373047s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-acm took 1.822204351425171s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 4.029273986816406e-05s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.15825200080871582s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.000133514404296875s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-budapest took 1.7731359004974365s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 8.177757263183594e-05s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.16496753692626953s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00019741058349609375s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 1.7639994621276855s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 4.673004150390625e-05s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.15756654739379883s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.021281957626342773s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0001544952392578125s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-cordis took 1.78859281539917s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 8.082389831542969e-05s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.15493440628051758s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015282630920410156s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-courseware took 1.8010118007659912s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 8.177757263183594e-05s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.17573142051696777s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.021049022674560547s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.62396240234375e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-crime took 1.7674977779388428s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 8.296966552734375e-05s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.15607357025146484s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011610984802246094s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 1.7680163383483887s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 4.458427429199219e-05s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.15365815162658691s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.022710800170898438s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.650520324707031e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 1.7234621047973633s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 8.344650268554688e-05s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.1508331298828125s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00023674964904785156s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-dblp took 1.8251221179962158s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 9.012222290039062e-05s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.16609978675842285s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.021739721298217773s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.001142740249633789s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 9.131431579589844e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 1.7864253520965576s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.1518571376800537s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.34600830078125e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-deploy took 1.72165846824646s
Availability | SPARQL endpoint availability check for digitaleconomy took 8.440017700195312e-05s
Availability | VoID file availability check for digitaleconomy took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.15398097038269043s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.075599670410156e-05s
Believability | Calculation of trust value for digitaleconomy took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 1.7592699527740479s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 8.034706115722656e-05s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.1627650260925293s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014257431030273438s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-dotac took 1.7665855884552002s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 8.20159912109375e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.1547558307647705s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02216315269470215s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.38690185546875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-ecs took 1.7472209930419922s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 7.748603820800781e-05s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.1484699249267578s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00017404556274414062s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.621246337890625e-05s
INFO | --- Analysis for rkb-explorer-eprints took 1.737419843673706s
Availability | SPARQL endpoint availability check for epsrc took 4.267692565917969e-05s
Availability | VoID file availability check for epsrc took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for epsrc took 0.1588897705078125s
Reputation | Calculation of the PageRank for epsrc took 0.0218961238861084s
Interlinking | Calculation of Degree of Connection for epsrc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for epsrc took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.5789947509765625e-05s
Believability | Calculation of trust value for epsrc took 1.52587890625e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 1.7722418308258057s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 4.4345855712890625e-05s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.164567232131958s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.02284979820251465s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.059906005859375e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-era took 1.7296886444091797s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.00011324882507324219s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.1579747200012207s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010156631469726562s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 1.8480172157287598s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 8.177757263183594e-05s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.16097807884216309s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.036064147949219e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-ft took 1.7799913883209229s
Availability | SPARQL endpoint availability check for fun took 8.058547973632812e-05s
Availability | VoID file availability check for fun took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for fun took 0.15331649780273438s
Reputation | Calculation of the PageRank for fun took 0.0230863094329834s
Interlinking | Calculation of Degree of Connection for fun took 3.9577484130859375e-05s
Interlinking | Calculation of Centrality for fun took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for fun took 7.605552673339844e-05s
Believability | Calculation of trust value for fun took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-fun took 1.7913856506347656s
Availability | SPARQL endpoint availability check for gdlc took 8.630752563476562e-05s
Availability | VoID file availability check for gdlc took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for gdlc took 0.15512418746948242s
Reputation | Calculation of the PageRank for gdlc took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.818771362304688e-05s
Believability | Calculation of trust value for gdlc took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 1.80464768409729s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.15086817741394043s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011491775512695312s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-ibm took 1.7271785736083984s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 3.981590270996094e-05s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.17112064361572266s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001373291015625s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-ieee took 1.7661676406860352s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 4.100799560546875e-05s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.1690380573272705s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020359516143798828s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0001361370086669922s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-irit took 1.7934367656707764s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 8.296966552734375e-05s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.16197991371154785s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.021413803100585938s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.389617919921875e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-italy took 1.795316457748413s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 8.463859558105469e-05s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.1528456211090088s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.43865966796875e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-jisc took 1.8710658550262451s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.4345855712890625e-05s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.15534019470214844s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.38690185546875e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 1.7511160373687744s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.15628576278686523s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016236305236816406s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-kisti took 1.7770516872406006s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 8.654594421386719e-05s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.15218806266784668s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00014591217041015625s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-laas took 1.7237639427185059s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 8.249282836914062e-05s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.1888744831085205s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.020660400390625s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.604194641113281e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 1.8026957511901855s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 8.296966552734375e-05s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.16745543479919434s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001552104949951172s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 1.7821950912475586s
Availability | SPARQL endpoint availability check for notube took 7.987022399902344e-05s
Availability | VoID file availability check for notube took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for notube took 0.17516565322875977s
Reputation | Calculation of the PageRank for notube took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for notube took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for notube took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for notube took 4.172325134277344e-05s
Believability | Calculation of trust value for notube took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-notube took 1.747736930847168s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 4.315376281738281e-05s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.15850281715393066s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02140188217163086s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.0001304149627685547s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-nsf took 1.7909481525421143s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 4.1484832763671875e-05s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.1643385887145996s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015211105346679688s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-oai took 1.773777961730957s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.15211272239685059s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.295608520507812e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-os took 1.7511670589447021s
Availability | SPARQL endpoint availability check for photos took 8.463859558105469e-05s
Availability | VoID file availability check for photos took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for photos took 0.15300321578979492s
Reputation | Calculation of the PageRank for photos took 0.02278447151184082s
Interlinking | Calculation of Degree of Connection for photos took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for photos took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for photos took 7.581710815429688e-05s
Believability | Calculation of trust value for photos took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-photos took 1.8174505233764648s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 8.988380432128906e-05s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.16060519218444824s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.02147817611694336s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011134147644042969s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-pisa took 1.8702199459075928s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00010156631469726562s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.16214632987976074s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.022829294204711914s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019669532775878906s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 1.7578849792480469s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 4.172325134277344e-05s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.15494799613952637s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.022779464721679688s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00013589859008789062s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-resex took 1.7779712677001953s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 4.076957702636719e-05s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.16414117813110352s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.083747863769531e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-risks took 1.7259864807128906s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 8.511543273925781e-05s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.16701483726501465s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.022028684616088867s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012636184692382812s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-roma took 1.787447452545166s
Availability | SPARQL endpoint availability check for roni took 0.00012254714965820312s
Availability | VoID file availability check for roni took 0.00041222572326660156s
Completeness | Calculation of interlinking completeness for roni took 0.16505813598632812s
Reputation | Calculation of the PageRank for roni took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for roni took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for roni took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for roni took 2.9325485229492188e-05s
Believability | Calculation of trust value for roni took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-roni took 1.989548683166504s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 8.153915405273438e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.1665356159210205s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.000213623046875s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-southampton took 1.7815868854522705s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 4.029273986816406e-05s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.1600651741027832s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010538101196289062s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-ulm took 1.74554443359375s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 3.8623809814453125e-05s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.15778183937072754s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.703636169433594e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 1.713576316833496s
Availability | SPARQL endpoint availability check for webconf took 0.00015306472778320312s
Availability | VoID file availability check for webconf took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for webconf took 0.15427279472351074s
Reputation | Calculation of the PageRank for webconf took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for webconf took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for webconf took 0.000102996826171875s
Believability | Calculation of trust value for webconf took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-webconf took 1.809046745300293s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 8.416175842285156e-05s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.1526639461517334s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 6.961822509765625e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-webscience took 1.7510960102081299s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 4.076957702636719e-05s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.15948987007141113s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002048015594482422s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-wiki took 1.7791738510131836s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 8.0108642578125e-05s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.1645059585571289s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.34600830078125e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 1.8231472969055176s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.3261873722076416s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0005638599395751953s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 43.61040782928467s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.5464951992034912s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.5721192359924316s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.7406165599822998s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 4.6045777797698975s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.2861287593841553s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.08112502098083496s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.10070443153381348s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.07742834091186523s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.07856488227844238s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.08108377456665039s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.0781855583190918s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.08308029174804688s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.15656471252441406s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.07849311828613281s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.07891154289245605s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.07858657836914062s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.212667226791382s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 6.604194641113281e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.07941937446594238s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.07928299903869629s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.07925629615783691s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08068609237670898s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.07978510856628418s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.160369873046875s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.1598193645477295s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 18.530872583389282s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.09869933128356934s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.0776517391204834s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.07660865783691406s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.817383050918579s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.08212566375732422s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 2.967759609222412s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 7.464192867279053s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.5248026847839355s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.394743919372559s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.0226800441741943s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.09576869010925293s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 476.1810357570648s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.23272919654846191s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.021346330642700195s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 7.987022399902344e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 2.1457672119140625e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.0013580322265625e-05s
INFO | --- Analysis for roceeh-road took 601.2195603847504s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 8.487701416015625e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.15183067321777344s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 2.9802322387695312e-05s
Believability | Calculation of trust value for ontology terrorist attack took 5.245208740234375e-06s
INFO | --- Analysis for ROSHANI took 1.7727246284484863s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 8.463859558105469e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.16002941131591797s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.314018249511719e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.049041748046875e-05s
INFO | --- Analysis for ROSHANI_SAHU took 1.8036158084869385s
Availability | SPARQL endpoint availability check for x took 8.988380432128906e-05s
Availability | VoID file availability check for x took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for x took 0.15943312644958496s
Reputation | Calculation of the PageRank for x took 0.02146768569946289s
Interlinking | Calculation of Degree of Connection for x took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for x took 0.0011014938354492188s
Interlinking | Calculation of Clustering coefficient for x took 5.8650970458984375e-05s
Believability | Calculation of trust value for x took 1.3113021850585938e-05s
INFO | --- Analysis for Rozprawa,_artykuł took 1.7681810855865479s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 8.463859558105469e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.1520545482635498s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02197265625s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.747245788574219e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.52587890625e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 1.7881371974945068s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 8.988380432128906e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.00021600723266601562s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.15956687927246094s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020816326141357422s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 9.679794311523438e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 1.0967254638671875e-05s
INFO | --- Analysis for rubentaelman took 1.7497761249542236s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.172325134277344e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.15812897682189941s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020798206329345703s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.177757263183594e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.1444091796875e-05s
INFO | --- Analysis for rubenverborgh took 1.7584199905395508s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 6.723403930664062e-05s
Availability | VoID file availability check for Russian Universities Specialities took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.17141461372375488s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.022003889083862305s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 3.409385681152344e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 5.9604644775390625e-06s
INFO | --- Analysis for russian-universities-specialities took 1.7319960594177246s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.220008850097656e-05s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.1507718563079834s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.02083897590637207s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.0040740966796875e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 9.775161743164062e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 1.71522855758667s
Availability | SPARQL endpoint availability check for SALDO-RDF took 5.245208740234375e-05s
Availability | VoID file availability check for SALDO-RDF took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.15180206298828125s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02122044563293457s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.504753112792969e-05s
Believability | Calculation of trust value for SALDO-RDF took 1.1682510375976562e-05s
INFO | --- Analysis for saldo-rdf took 1.807586669921875s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 4.38690185546875e-05s
Availability | VoID file availability check for SALDOM-RDF took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.15504717826843262s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.049041748046875e-05s
INFO | --- Analysis for saldom-rdf took 1.748187780380249s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 8.511543273925781e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.15315723419189453s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010895729064941406s
Believability | Calculation of trust value for Salzburgerland DE took 1.0251998901367188e-05s
INFO | --- Analysis for salzburgerland-com-de took 1.7510426044464111s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.1484832763671875e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.16975712776184082s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.0001049041748046875s
Believability | Calculation of trust value for Salzburgerland EN took 1.049041748046875e-05s
INFO | --- Analysis for salzburgerland-com-en took 1.7378838062286377s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.553794860839844e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.17049932479858398s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.021181583404541016s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.0001087188720703125s
Believability | Calculation of trust value for Salzburgerland IT took 1.3113021850585938e-05s
INFO | --- Analysis for salzburgerland-com-it took 1.7989375591278076s
Availability | SPARQL endpoint availability check for sandrart.net took 0.00010180473327636719s
Availability | VoID file availability check for sandrart.net took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.2619743347167969s
Reputation | Calculation of the PageRank for sandrart.net took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.914138793945312e-05s
Believability | Calculation of trust value for sandrart.net took 9.298324584960938e-06s
INFO | --- Analysis for sandrart-net took 1.8520629405975342s
Availability | SPARQL endpoint availability check for Taxons  took 4.363059997558594e-05s
Availability | VoID file availability check for Taxons  took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Taxons  took 0.1631181240081787s
Reputation | Calculation of the PageRank for Taxons  took 0.021238088607788086s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Taxons  took 6.604194641113281e-05s
Believability | Calculation of trust value for Taxons  took 1.3113021850585938e-05s
INFO | --- Analysis for sandre took 1.7904605865478516s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 4.172325134277344e-05s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.15808439254760742s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.0279159545898438e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 5.245208740234375e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 1.7353827953338623s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for Santillana Guide Dataset took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.15487003326416016s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.02228713035583496s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.266334533691406e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 9.059906005859375e-06s
INFO | --- Analysis for santillana_guide_dataset took 1.7039599418640137s
Availability | SPARQL endpoint availability check for SATAR test  took 4.2438507080078125e-05s
Availability | VoID file availability check for SATAR test  took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.1556541919708252s
Reputation | Calculation of the PageRank for SATAR test  took 0.02260613441467285s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.9802322387695312e-05s
Believability | Calculation of trust value for SATAR test  took 6.4373016357421875e-06s
INFO | --- Analysis for SATAR_test took 1.7333459854125977s
Availability | SPARQL endpoint availability check for SCBG Data took 4.124641418457031e-05s
Availability | VoID file availability check for SCBG Data took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.16328692436218262s
Reputation | Calculation of the PageRank for SCBG Data took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0008068084716796875s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.654594421386719e-05s
Believability | Calculation of trust value for SCBG Data took 1.0967254638671875e-05s
INFO | --- Analysis for SCBG-Data took 1.7504169940948486s
Availability | SPARQL endpoint availability check for Schemantra took 8.344650268554688e-05s
Availability | VoID file availability check for Schemantra took 0.0002048015594482422s
Completeness | Calculation of interlinking completeness for Schemantra took 0.15460753440856934s
Reputation | Calculation of the PageRank for Schemantra took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Schemantra took 2.9087066650390625e-05s
Believability | Calculation of trust value for Schemantra took 1.1920928955078125e-05s
INFO | --- Analysis for Schemantra took 1.7212169170379639s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 4.291534423828125e-05s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.15741610527038574s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020922422409057617s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.361701965332031e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 7.3909759521484375e-06s
INFO | --- Analysis for schemapedia took 1.754974603652954s
Availability | SPARQL endpoint availability check for Scholarometer took 4.9114227294921875e-05s
Availability | VoID file availability check for Scholarometer took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.14931488037109375s
Reputation | Calculation of the PageRank for Scholarometer took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.463859558105469e-05s
Believability | Calculation of trust value for Scholarometer took 8.58306884765625e-06s
INFO | --- Analysis for scholarometer took 2.136709213256836s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 8.344650268554688e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.16755366325378418s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.0040740966796875e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 1.1682510375976562e-05s
INFO | --- Analysis for scoreboard took 1.768951177597046s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.320808410644531e-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.0004520416259765625s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.15182709693908691s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.021275758743286133s
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.0967254638671875e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.075599670410156e-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.049041748046875e-05s
INFO | --- Analysis for SDDEC took 1.741872787475586s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 6.198883056640625e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.15192198753356934s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.021118640899658203s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007245540618896484s
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 1.2159347534179688e-05s
INFO | --- Analysis for SDG took 1.8451545238494873s
Availability | SPARQL endpoint availability check for sears.com took 8.392333984375e-05s
Availability | VoID file availability check for sears.com took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for sears.com took 0.1536271572113037s
Reputation | Calculation of the PageRank for sears.com took 0.022005558013916016s
Interlinking | Calculation of Degree of Connection for sears.com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.890296936035156e-05s
Believability | Calculation of trust value for sears.com took 1.1205673217773438e-05s
INFO | --- Analysis for sears took 1.726806640625s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 4.315376281738281e-05s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.1629197597503662s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.021734952926635742s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.535385131835938e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0251998901367188e-05s
INFO | --- Analysis for sec-rdfabout took 1.7520496845245361s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 4.863739013671875e-05s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.16107606887817383s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.02166271209716797s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 0.00010466575622558594s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for secold took 1.774322748184204s
Availability | SPARQL endpoint availability check for semanlink took 8.296966552734375e-05s
Availability | VoID file availability check for semanlink took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for semanlink took 0.14870119094848633s
Reputation | Calculation of the PageRank for semanlink took 0.020937442779541016s
Interlinking | Calculation of Degree of Connection for semanlink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014162063598632812s
Believability | Calculation of trust value for semanlink took 1.1682510375976562e-05s
INFO | --- Analysis for semanlink took 1.7553625106811523s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 4.220008850097656e-05s
Availability | VoID file availability check for Semantic Universe Data took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.16648578643798828s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.022398710250854492s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.1920928955078125e-05s
INFO | --- Analysis for semantic-universe took 1.7493822574615479s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 4.124641418457031e-05s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.16108012199401855s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.02060842514038086s
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.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011467933654785156s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.2874603271484375e-05s
INFO | --- Analysis for semantic-web-dog-food took 1.7839605808258057s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 8.320808410644531e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.15554594993591309s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.410743713378906e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.239776611328125e-05s
INFO | --- Analysis for semantic-web-grundlagen took 1.8132941722869873s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 8.225440979003906e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.15581345558166504s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.021842479705810547s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.273124694824219e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 1.1682510375976562e-05s
INFO | --- Analysis for semantic-xbrl took 1.7437796592712402s
Availability | SPARQL endpoint availability check for Semantic Quran took 8.106231689453125e-05s
Availability | VoID file availability check for Semantic Quran took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for Semantic Quran took 0.16446375846862793s
Reputation | Calculation of the PageRank for Semantic Quran took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic Quran took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 7.677078247070312e-05s
Believability | Calculation of trust value for Semantic Quran took 1.0013580322265625e-05s
INFO | --- Analysis for semanticquran took 1.7616665363311768s
Availability | SPARQL endpoint availability check for SemanticTweet took 8.0108642578125e-05s
Availability | VoID file availability check for SemanticTweet took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.1628720760345459s
Reputation | Calculation of the PageRank for SemanticTweet took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.602836608886719e-05s
Believability | Calculation of trust value for SemanticTweet took 1.0013580322265625e-05s
INFO | --- Analysis for semantictweet took 1.735976219177246s
Availability | SPARQL endpoint availability check for semanticweb.org took 8.153915405273438e-05s
Availability | VoID file availability check for semanticweb.org took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.1613461971282959s
Reputation | Calculation of the PageRank for semanticweb.org took 0.021087646484375s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.82012939453125e-05s
Believability | Calculation of trust value for semanticweb.org took 1.1920928955078125e-05s
INFO | --- Analysis for semanticweb-org took 1.7389492988586426s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 4.076957702636719e-05s
Availability | VoID file availability check for Semantic CrunchBase took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.16709399223327637s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 7.390975952148438e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.0251998901367188e-05s
INFO | --- Analysis for semsol-crunchbase took 1.754810094833374s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 7.033348083496094e-05s
Availability | VoID file availability check for SentimentWortschatz took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.1569499969482422s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.021070241928100586s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.1961669921875e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.2636184692382812e-05s
INFO | --- Analysis for sentiws took 1.72926926612854s
Availability | SPARQL endpoint availability check for seoul-bike-data took 4.172325134277344e-05s
Availability | VoID file availability check for seoul-bike-data took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.15603137016296387s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 2.9087066650390625e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.049041748046875e-05s
INFO | --- Analysis for seoul-bike-data took 1.8170156478881836s
Availability | SPARQL endpoint availability check for Serendipity took 8.463859558105469e-05s
Availability | VoID file availability check for Serendipity took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Serendipity took 0.15703272819519043s
Reputation | Calculation of the PageRank for Serendipity took 0.021486520767211914s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.128715515136719e-05s
Believability | Calculation of trust value for Serendipity took 1.0967254638671875e-05s
INFO | --- Analysis for serendipity took 1.7805302143096924s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 7.224082946777344e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.16291117668151855s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02295398712158203s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.218650817871094e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 9.298324584960938e-06s
INFO | --- Analysis for Sherry_Wine took 1.747683048248291s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.2438507080078125e-05s
Availability | VoID file availability check for Sherry Wine took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.16412568092346191s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.123283386230469e-05s
Believability | Calculation of trust value for Sherry Wine took 9.5367431640625e-06s
INFO | --- Analysis for Sherry_Wine_ took 1.75982666015625s
Availability | SPARQL endpoint availability check for Shoah victims? names took 7.987022399902344e-05s
Availability | VoID file availability check for Shoah victims? names took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.15359711647033691s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.022223234176635742s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.00543212890625e-05s
Believability | Calculation of trust value for Shoah victims? names took 1.0967254638671875e-05s
INFO | --- Analysis for shoah-victims-names took 1.735555648803711s
Availability | SPARQL endpoint availability check for Person took 8.535385131835938e-05s
Availability | VoID file availability check for Person took 0.00021386146545410156s
Completeness | Calculation of interlinking completeness for Person took 0.15312767028808594s
Reputation | Calculation of the PageRank for Person took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for Person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Person took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Person took 2.956390380859375e-05s
Believability | Calculation of trust value for Person took 5.7220458984375e-06s
INFO | --- Analysis for Shripriya_Dubey took 1.7510125637054443s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 8.225440979003906e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.1643376350402832s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.049041748046875e-05s
INFO | --- Analysis for Shutterstock took 1.7813069820404053s
Availability | SPARQL endpoint availability check for SIMPLE took 8.082389831542969e-05s
Availability | VoID file availability check for SIMPLE took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.15496110916137695s
Reputation | Calculation of the PageRank for SIMPLE took 0.022266387939453125s
Interlinking | Calculation of Degree of Connection for SIMPLE took 3.266334533691406e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 3.933906555175781e-05s
Believability | Calculation of trust value for SIMPLE took 1.0967254638671875e-05s
INFO | --- Analysis for simple took 1.7725682258605957s
Availability | SPARQL endpoint availability check for SITC-V4 took 8.249282836914062e-05s
Availability | VoID file availability check for SITC-V4 took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.15032196044921875s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02234363555908203s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.5762786865234375e-05s
Believability | Calculation of trust value for SITC-V4 took 1.049041748046875e-05s
INFO | --- Analysis for sitc-v4 took 1.8025379180908203s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.410743713378906e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.15891122817993164s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.021549224853515625s
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.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 6.103515625e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 5.245208740234375e-06s
INFO | --- Analysis for sli_galnet_rdf took 1.7487781047821045s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 8.320808410644531e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.15878677368164062s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.075599670410156e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.049041748046875e-05s
INFO | --- Analysis for slideshare2rdf took 1.747220516204834s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.39925551414489746s
Availability | VoID file availability check for Linked Stage Graph took 0.0004897117614746094s
Extra | Recovery of all triples for Linked Stage Graph took 1.977515697479248s
Performance | Total latancy measurement for Linked Stage Graph took 0.9602582454681396s
Amount of data | Number of triples check for Linked Stage Graph took 0.2051863670349121s
Interoperability | New terms check for Linked Stage Graph took 1.6239750385284424s
Versatility | Languages check for Linked Stage Graph took 0.6344351768493652s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.22208833694458008s
Security | Check HTTPS for Linked Stage Graph took 0.12355542182922363s
Interpretability | RDF structures check for Linked Stage Graph took 0.2818031311035156s
Versatility | Serialization formats check for Linked Stage Graph took 0.19567441940307617s
Availability | RDF dump link check for Linked Stage Graph took 0.1923370361328125s
License | MR license check for Linked Stage Graph took 0.23701930046081543s
License | HR license check for Linked Stage Graph took 1.7741432189941406s
Amount of data | Number of property check for Linked Stage Graph took 0.19738149642944336s
Understandability | Number of label check for Linked Stage Graph took 0.235335111618042s
Understandability | URI regex check for Linked Stage Graph took 0.3845076560974121s
Understandability | Vocabs check for Linked Stage Graph took 0.19928669929504395s
Verifiability | Authors check for Linked Stage Graph took 0.19485878944396973s
Verifiability | Publishers check for Linked Stage Graph took 0.19329428672790527s
Performance | Throughput check for Linked Stage Graph took 11.276975870132446s
Amount of data | Check the number of entities for Linked Stage Graph took 8.058547973632812e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.19330978393554688s
Interlinking | sameAs chians check for Linked Stage Graph took 0.2656285762786865s
Interlinking | skos check for Linked Stage Graph took 0.1946244239807129s
Interlinking | skos check for Linked Stage Graph took 0.19465208053588867s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.22101163864135742s
Currency | Creation date check for Linked Stage Graph took 0.3957250118255615s
Currency | Modification date check for Linked Stage Graph took 0.39148521423339844s
Rep.Conc. | URIs length for Linked Stage Graph took 1.4234893321990967s
Interoperability | New vocabularies check for Linked Stage Graph took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.19191312789916992s
Accuracy | Check Functional Property for Linked Stage Graph took 0.425187349319458s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.1917874813079834s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.757498025894165s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.023546695709228516s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.027637243270874023s
Consistency | Disjoint class check for Linked Stage Graph took 0.19522929191589355s
Consistency | Check Misplaced properties for Linked Stage Graph took 0.8581855297088623s
Consistency | Misplaced classes for Linked Stage Graph took 0.493149995803833s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.217578411102295s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.4057745933532715s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.8892691135406494s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.028353452682495117s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.6873104572296143s
Security | Sign check for Linked Stage Graph took 0.19562745094299316s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 889.3838708400726s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.4078660011291504s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.021572351455688477s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.1205673217773438e-05s
INFO | --- Analysis for slod took 951.4810285568237s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.00010228157043457031s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.1531846523284912s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.021746397018432617s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 9.441375732421875e-05s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for Smart_POI_dataset took 1.7713778018951416s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.14984130859375e-05s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.15668702125549316s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.552436828613281e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.0251998901367188e-05s
INFO | --- Analysis for smartlink took 1.753016471862793s
Availability | SPARQL endpoint availability check for SNIK took 8.249282836914062e-05s
Availability | VoID file availability check for SNIK took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for SNIK took 0.16038823127746582s
Reputation | Calculation of the PageRank for SNIK took 0.021484375s
Interlinking | Calculation of Degree of Connection for SNIK took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for SNIK took 6.985664367675781e-05s
Believability | Calculation of trust value for SNIK took 1.4543533325195312e-05s
INFO | --- Analysis for snik took 1.7731983661651611s
Availability | SPARQL endpoint availability check for SocialLink took 0.00010085105895996094s
Availability | VoID file availability check for SocialLink took 0.00020313262939453125s
Completeness | Calculation of interlinking completeness for SocialLink took 0.1609330177307129s
Reputation | Calculation of the PageRank for SocialLink took 0.020961999893188477s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.295608520507812e-05s
Believability | Calculation of trust value for SocialLink took 8.58306884765625e-06s
INFO | --- Analysis for SocialLink took 1.755333662033081s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 8.487701416015625e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.15668869018554688s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.022521257400512695s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0011365413665771484s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 4.3392181396484375e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.2874603271484375e-05s
INFO | --- Analysis for SocialRoles took 1.766526460647583s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.00010037422180175781s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.15561413764953613s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 8.702278137207031e-05s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 1.7234768867492676s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.893013000488281e-05s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.15317106246948242s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.7418136596679688e-05s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.430511474609375e-05s
INFO | --- Analysis for Soil_maps took 1.7065083980560303s
Availability | SPARQL endpoint availability check for terrorrist ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.16595196723937988s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 2.6464462280273438e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.0251998901367188e-05s
INFO | --- Analysis for somya_omer took 1.7527508735656738s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.076957702636719e-05s
Availability | VoID file availability check for Sonclubcx took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.16934752464294434s
Reputation | Calculation of the PageRank for Sonclubcx took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.0728836059570312e-05s
Believability | Calculation of trust value for Sonclubcx took 1.0728836059570312e-05s
INFO | --- Analysis for sonclubcx took 1.766937494277954s
Availability | SPARQL endpoint availability check for SORS took 8.153915405273438e-05s
Availability | VoID file availability check for SORS took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for SORS took 0.15457916259765625s
Reputation | Calculation of the PageRank for SORS took 0.020188093185424805s
Interlinking | Calculation of Degree of Connection for SORS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SORS took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for SORS took 4.601478576660156e-05s
Believability | Calculation of trust value for SORS took 1.0013580322265625e-05s
INFO | --- Analysis for sors took 1.753350019454956s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 8.225440979003906e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.15485763549804688s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.021898269653320312s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 8.702278137207031e-05s
Believability | Calculation of trust value for southampton-ac-uk took 1.0013580322265625e-05s
INFO | --- Analysis for southampton-ac-uk took 1.7574470043182373s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 6.413459777832031e-05s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.15233755111694336s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02137589454650879s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 2.6464462280273438e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 5.9604644775390625e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 1.744077444076538s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 3.981590270996094e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.15321874618530273s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020277738571166992s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 8.7738037109375e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.0967254638671875e-05s
INFO | --- Analysis for southampton-ecs-eprints took 1.8048100471496582s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 8.177757263183594e-05s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.1588304042816162s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021143198013305664s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 2.9087066650390625e-05s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.1920928955078125e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 1.7923026084899902s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 3.933906555175781e-05s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.15940260887145996s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.02327418327331543s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.5299530029296875e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 1.2159347534179688e-05s
INFO | --- Analysis for sparql-endpoint-status took 1.7244274616241455s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 8.225440979003906e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.15362787246704102s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.021088123321533203s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.535385131835938e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.1682510375976562e-05s
INFO | --- Analysis for springernaturescigraph took 1.772582769393921s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 8.416175842285156e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.1529548168182373s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.075599670410156e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 9.775161743164062e-06s
INFO | --- Analysis for srcmf took 1.7653653621673584s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 5.53131103515625e-05s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.15565276145935059s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 4.506111145019531e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.33514404296875e-05s
INFO | --- Analysis for ssf took 1.7337570190429688s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 0.00012111663818359375s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.1705763339996338s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 4.029273986816406e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 1.0967254638671875e-05s
INFO | --- Analysis for st-andrews-resource-lists took 1.7943222522735596s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.9577484130859375e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.1655111312866211s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.02239227294921875s
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.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.361701965332031e-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 1.8045077323913574s
Availability | SPARQL endpoint availability check for Stammbuch took 8.678436279296875e-05s
Availability | VoID file availability check for Stammbuch took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.16269874572753906s
Reputation | Calculation of the PageRank for Stammbuch took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.600120544433594e-05s
Believability | Calculation of trust value for Stammbuch took 1.049041748046875e-05s
INFO | --- Analysis for Stammbuch took 1.7881958484649658s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 8.344650268554688e-05s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.17035436630249023s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00011682510375976562s
Believability | Calculation of trust value for statistics.data.gov.uk took 1.0728836059570312e-05s
INFO | --- Analysis for statistics-data-gov-uk took 1.816866397857666s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 7.963180541992188e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.15903210639953613s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.0001049041748046875s
Believability | Calculation of trust value for statusnet-1w6-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-1w6-org took 1.7545878887176514s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 8.273124694824219e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.15957164764404297s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.021525144577026367s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-20100-org took 1.7664494514465332s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.16955280303955078s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.794929504394531e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 1.8007338047027588s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 8.20159912109375e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.15816473960876465s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.02050328254699707s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.130073547363281e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 1.760376214981079s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.000457763671875s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.16533660888671875s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.1552734375e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-belfalas-org took 1.7553112506866455s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.1658492088317871s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011396408081054688s
Believability | Calculation of trust value for statusnet-bka-li took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-bka-li took 1.7633891105651855s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 7.200241088867188e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.18041777610778809s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.886222839355469e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 1.864635944366455s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 0.0001010894775390625s
Availability | VoID file availability check for statusnet-ced117-net took 0.00019979476928710938s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.15023231506347656s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.02069234848022461s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.744529724121094e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-ced117-net took 1.7591240406036377s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 8.034706115722656e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.16036009788513184s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.02139425277709961s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.054473876953125e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 1.7769074440002441s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 8.106231689453125e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0004200935363769531s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.15635466575622559s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.022225379943847656s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011610984802246094s
Believability | Calculation of trust value for statusnet-chromic-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-chromic-org took 1.7478864192962646s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 8.273124694824219e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.15432977676391602s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.915496826171875e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 1.726593255996704s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 6.341934204101562e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.1641843318939209s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.2928924560546875e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 1.750474452972412s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 0.00010061264038085938s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.17134618759155273s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02167057991027832s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 1.777740478515625s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.15538859367370605s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02273082733154297s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010061264038085938s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 1.8108298778533936s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 8.20159912109375e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.1569056510925293s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.021010398864746094s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.127357482910156e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 1.7277045249938965s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 8.20159912109375e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.15993237495422363s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.021646976470947266s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 3.6716461181640625e-05s
INFO | --- Analysis for statusnet-doomicile-de took 1.8736937046051025s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.1605851650238037s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.151199340820312e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-dtdns-net took 1.7730181217193604s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 0.00013518333435058594s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.1812303066253662s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.021728038787841797s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.600120544433594e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 2.4642796516418457s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.1589527130126953s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020856857299804688s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.62939453125e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-exdc-net took 1.762380838394165s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 7.963180541992188e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.15459609031677246s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.021541833877563477s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.393692016601562e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-fcac-com took 1.7306408882141113s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 8.106231689453125e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.00041961669921875s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.15623140335083008s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 1.7457637786865234s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 8.296966552734375e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.15403294563293457s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018286705017089844s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-fragdev-com took 1.741523265838623s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 7.891654968261719e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.15250039100646973s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020624160766601562s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.557868957519531e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-freelish-us took 1.7710895538330078s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.15096664428710938s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.022322416305541992s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010585784912109375s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 1.742741346359253s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 8.249282836914062e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.16375446319580078s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.699562072753906e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-glou-org took 1.7415332794189453s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 8.296966552734375e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.16197514533996582s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.02109694480895996s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00013113021850585938s
Believability | Calculation of trust value for statusnet-gomertronic-com took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-gomertronic-com took 1.7624526023864746s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 8.106231689453125e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.15878772735595703s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010466575622558594s
Believability | Calculation of trust value for statusnet-hackerposse-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 1.8657081127166748s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 8.034706115722656e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.1627194881439209s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.76837158203125e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-hii-co-il took 1.7343802452087402s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 8.153915405273438e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.1611464023590088s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.022485017776489258s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.059906005859375e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 1.7453341484069824s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 7.963180541992188e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.15671753883361816s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 5.626678466796875e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 1.7082598209381104s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.1577301025390625s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.021094560623168945s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0008327960968017578s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.696846008300781e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-integralblue-com took 1.7922918796539307s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 0.00012350082397460938s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.00041365623474121094s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.15681028366088867s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 1.7647755146026611s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 9.369850158691406e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.17134356498718262s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.021189451217651367s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011396408081054688s
Believability | Calculation of trust value for statusnet-jonkman-ca took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-jonkman-ca took 1.7875220775604248s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.16190004348754883s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.02091526985168457s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.001001119613647461s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 0.00011014938354492188s
Believability | Calculation of trust value for statusnet-kaimi-cc took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 1.7552845478057861s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 8.034706115722656e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.15164446830749512s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.8160552978515625e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 1.7772939205169678s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 6.413459777832031e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.1531374454498291s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.021384000778198242s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.814697265625e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 1.7670753002166748s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.16177988052368164s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-keuser-fr took 1.7850451469421387s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 0.0001232624053955078s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.15688157081604004s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020798683166503906s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.054473876953125e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 1.7835972309112549s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.15752243995666504s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 5.8650970458984375e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 1.7660751342773438s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 9.417533874511719e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.000209808349609375s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.15647244453430176s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020259618759155273s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.012222290039062e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 1.7479078769683838s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.15233135223388672s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020506620407104492s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011658668518066406s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 1.7260017395019531s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 3.910064697265625e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.16534781455993652s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02182173728942871s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.125999450683594e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-ludost-net took 1.7421760559082031s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 3.933906555175781e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.15559053421020508s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02146291732788086s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.369850158691406e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 1.7584333419799805s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.00020647048950195312s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.16096711158752441s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.021114587783813477s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 4.935264587402344e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 1.7261438369750977s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.16321659088134766s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014781951904296875s
Believability | Calculation of trust value for statusnet-macno-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-macno-org took 1.7512626647949219s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 3.886222839355469e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.1671433448791504s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02031707763671875s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 5.936622619628906e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 1.7433807849884033s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 3.910064697265625e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.15564799308776855s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020140409469604492s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 7.700920104980469e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-maymay-net took 1.748471736907959s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.16003060340881348s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.0001575946807861328s
Believability | Calculation of trust value for statusnet-morphtown-de took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-morphtown-de took 1.7518970966339111s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.15417265892028809s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.022935867309570312s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.989738464355469e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 1.7513391971588135s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.00543212890625e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.15829992294311523s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.023017168045043945s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.4836273193359375e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-mulestable-net took 1.7333378791809082s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 7.891654968261719e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.15588021278381348s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.245208740234375e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-my-status-tk took 1.7249162197113037s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 9.632110595703125e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.1524050235748291s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.0001068115234375s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 1.7566213607788086s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 8.153915405273438e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.15918183326721191s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.626678466796875e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 1.7383649349212646s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 7.963180541992188e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.00041961669921875s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.15115642547607422s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02223515510559082s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-otbm-fr took 1.7529966831207275s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 0.00015234947204589844s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.1641542911529541s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.296966552734375e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 1.7331147193908691s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 8.034706115722656e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.15472674369812012s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.57763671875e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-panda-id-au took 1.7595534324645996s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 3.981590270996094e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0004200935363769531s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.153228759765625s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.608268737792969e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-piana-eu took 1.7646260261535645s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 8.0108642578125e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.15322113037109375s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.021040678024291992s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.271766662597656e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 1.793907642364502s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.15309405326843262s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00023603439331054688s
Believability | Calculation of trust value for statusnet-postblue-info took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-postblue-info took 1.705761432647705s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.1594252586364746s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.02075338363647461s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.628036499023438e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-progval-net took 1.7450306415557861s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 6.937980651855469e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.15178632736206055s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00012683868408203125s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-qdnx-org took 1.7465393543243408s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.16268682479858398s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-qth-fr took 1.8325576782226562s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.15445995330810547s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.021245241165161133s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021958351135253906s
Believability | Calculation of trust value for statusnet-quitter-se took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-quitter-se took 1.719423532485962s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 7.796287536621094e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.15697550773620605s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010538101196289062s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 1.7423920631408691s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.00543212890625e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.16192102432250977s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020920753479003906s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-recit-org took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-recit-org took 1.738203763961792s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 8.273124694824219e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.16169190406799316s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020159006118774414s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00016617774963378906s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-russwurm-org took 1.7581896781921387s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.15379762649536133s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.02182769775390625s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 0.00014519691467285156s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-samnoble-org took 1.72176194190979s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 3.981590270996094e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.15635132789611816s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020822525024414062s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.20159912109375e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-schiessle-org took 1.7525112628936768s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 3.981590270996094e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00041794776916503906s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.15741729736328125s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.441375732421875e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 1.7344436645507812s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 8.0108642578125e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.1596531867980957s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.022155284881591797s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 1.7643258571624756s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.16008830070495605s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.05718994140625e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 1.77168869972229s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 9.942054748535156e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.1577599048614502s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.02034783363342285s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.0002090930938720703s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 1.7060039043426514s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 3.814697265625e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.20659542083740234s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020286083221435547s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010919570922851562s
Believability | Calculation of trust value for statusnet-somsants-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-somsants-net took 1.8045704364776611s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 8.058547973632812e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.15407514572143555s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00013208389282226562s
Believability | Calculation of trust value for statusnet-soucy-cc took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-soucy-cc took 1.9297702312469482s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 3.933906555175781e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.16056513786315918s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020920515060424805s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-spip-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-spip-org took 1.7892076969146729s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.1600341796875s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.02197575569152832s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-spraci-org took 1.7694330215454102s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 6.580352783203125e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.1627519130706787s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00010991096496582031s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 1.7520701885223389s
Availability | SPARQL endpoint availability check for statusnet-status-net took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0002090930938720703s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.1605532169342041s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.0002224445343017578s
Believability | Calculation of trust value for statusnet-status-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-status-net took 1.7727153301239014s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 8.153915405273438e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.1633920669555664s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.698204040527344e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 1.7674577236175537s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.1526627540588379s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.059906005859375e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 1.7542378902435303s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 7.867813110351562e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.16122698783874512s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001232624053955078s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 1.7615787982940674s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.14975953102111816s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.02031707763671875s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.534027099609375e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-thornton2-com took 1.7710785865783691s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 7.915496826171875e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.15204334259033203s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.02303147315979004s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.0001068115234375s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 1.7554590702056885s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 8.487701416015625e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.1561427116394043s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-tl1n-com took 1.7601087093353271s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.15625500679016113s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.02031087875366211s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.699562072753906e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 1.7173106670379639s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 7.939338684082031e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.16824650764465332s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020282983779907227s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.814697265625e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 1.7475323677062988s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 8.392333984375e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.17212533950805664s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.021782636642456055s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.7894973754882812e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for steak took 1.7731261253356934s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 8.940696716308594e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.1542823314666748s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 4.982948303222656e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.239776611328125e-05s
INFO | --- Analysis for stitch-rameau took 1.7676970958709717s
Availability | SPARQL endpoint availability check for Stone Tech Square took 4.100799560546875e-05s
Availability | VoID file availability check for Stone Tech Square took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.15781068801879883s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020153045654296875s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.2874603271484375e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.3113021850585938e-05s
INFO | --- Analysis for stone-tech-square-data took 1.822587013244629s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 8.440017700195312e-05s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.16480541229248047s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.02123856544494629s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00010538101196289062s
Believability | Calculation of trust value for STW Thesaurus for Economics took 7.152557373046875e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 1.777503252029419s
Availability | SPARQL endpoint availability check for SudershanTech took 8.296966552734375e-05s
Availability | VoID file availability check for SudershanTech took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.16381406784057617s
Reputation | Calculation of the PageRank for SudershanTech took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 2.9087066650390625e-05s
Believability | Calculation of trust value for SudershanTech took 1.1920928955078125e-05s
INFO | --- Analysis for SudershanTech took 1.714059591293335s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 8.106231689453125e-05s
Availability | VoID file availability check for Sudoc bibliographic data took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.16448426246643066s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.02115011215209961s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.792213439941406e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 9.775161743164062e-06s
INFO | --- Analysis for sudocfr took 1.7689940929412842s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 8.177757263183594e-05s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.15970611572265625s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.0209810733795166s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 7.2479248046875e-05s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.0251998901367188e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 1.7643699645996094s
Availability | SPARQL endpoint availability check for Surge Radio took 9.703636169433594e-05s
Availability | VoID file availability check for Surge Radio took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.1608579158782959s
Reputation | Calculation of the PageRank for Surge Radio took 0.02318739891052246s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.249282836914062e-05s
Believability | Calculation of trust value for Surge Radio took 7.62939453125e-06s
INFO | --- Analysis for surge-radio took 1.7748453617095947s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.1961669921875e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.15576815605163574s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.02106785774230957s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 2.9325485229492188e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.0013580322265625e-05s
INFO | --- Analysis for SWAT took 1.7537617683410645s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 8.249282836914062e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.16503691673278809s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.021167993545532227s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.128715515136719e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.2159347534179688e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 1.8343415260314941s
Availability | SPARQL endpoint availability check for SweFN-RDF took 8.511543273925781e-05s
Availability | VoID file availability check for SweFN-RDF took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.15615415573120117s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for SweFN-RDF took 6.9141387939453125e-06s
INFO | --- Analysis for swefn-rdf took 1.7607219219207764s
Availability | SPARQL endpoint availability check for SwetoDblp took 7.772445678710938e-05s
Availability | VoID file availability check for SwetoDblp took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.16438889503479004s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.647804260253906e-05s
Believability | Calculation of trust value for SwetoDblp took 1.1920928955078125e-05s
INFO | --- Analysis for sweto-dblp took 1.7729382514953613s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 7.748603820800781e-05s
Availability | VoID file availability check for Swift Vocabulary took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.17050504684448242s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 6.890296936035156e-05s
Believability | Calculation of trust value for Swift Vocabulary took 7.152557373046875e-06s
INFO | --- Analysis for Swift took 1.7701923847198486s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 8.177757263183594e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.15770244598388672s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.022288084030151367s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.266334533691406e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.1920928955078125e-05s
INFO | --- Analysis for symptoms-in-chinese took 1.7903342247009277s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.3347010612487793s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0004718303680419922s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4413878917694092s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.7836463451385498s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 34.654194831848145s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 19.789855241775513s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.15472030639648438s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.4914777278900146s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.09637761116027832s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.39194750785827637s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.22190546989440918s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.15807127952575684s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.28203487396240234s
License | HR license check for National Digital Data Archive of Hungary (partial) took 52.9498450756073s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.43355631828308105s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 36.11200261116028s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.32440829277038574s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.17991185188293457s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.15968847274780273s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.15880441665649414s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 10.996716260910034s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 6.914138793945312e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 0.19971895217895508s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 0.33039236068725586s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 0.18211936950683594s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 0.15667152404785156s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 0.16602206230163574s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 0.3173706531524658s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 0.31572437286376953s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 61.33319640159607s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.1577162742614746s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.17287707328796387s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.1560969352722168s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.20860862731933594s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0020422935485839844s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0014574527740478516s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.1572251319885254s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 44.202544927597046s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.23052573204040527s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.6019208431243896s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3571727275848389s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.67531967163086s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002276897430419922s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.517448902130127s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.19722962379455566s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 9.715487241744995s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.23310399055480957s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.022577524185180664s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.082389831542969e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-05s
INFO | --- Analysis for sztaki-lod took 467.1019060611725s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00010657310485839844s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.1596531867980957s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.054473876953125e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.3113021850585938e-05s
INFO | --- Analysis for t4gm-info took 1.7813541889190674s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.291534423828125e-05s
Availability | VoID file availability check for tags2con delicious took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.15093326568603516s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02160811424255371s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.458427429199219e-05s
Believability | Calculation of trust value for tags2con delicious took 1.239776611328125e-05s
INFO | --- Analysis for tags2con-delicious took 1.7673158645629883s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 8.392333984375e-05s
Availability | VoID file availability check for Taiwan geographic names took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.15805435180664062s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.02024054527282715s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 4.744529724121094e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.0728836059570312e-05s
INFO | --- Analysis for taiwan-geographic-names took 1.7653992176055908s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 8.821487426757812e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.16242480278015137s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.02163982391357422s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 8.630752563476562e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.1920928955078125e-05s
INFO | --- Analysis for talis-openlibrary took 3.0589544773101807s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 8.678436279296875e-05s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.15179729461669922s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.021027326583862305s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00011968612670898438s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.049041748046875e-05s
INFO | --- Analysis for taxonconcept took 1.7187609672546387s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.0531158447265625e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.15714097023010254s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 7.557868957519531e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.0967254638671875e-05s
INFO | --- Analysis for taxonconcept-assets took 1.7261989116668701s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.2438507080078125e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.16112542152404785s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 4.982948303222656e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.1205673217773438e-05s
INFO | --- Analysis for taxonconcept-occurences took 1.7399110794067383s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 3.886222839355469e-05s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.15977096557617188s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 4.839897155761719e-05s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.1205673217773438e-05s
INFO | --- Analysis for taxref-ld took 1.7334873676300049s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 6.866455078125e-05s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.1656501293182373s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 2.6702880859375e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.049041748046875e-05s
INFO | --- Analysis for tcga took 1.734189510345459s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 8.296966552734375e-05s
Availability | VoID file availability check for TCGA Roadmap took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.1663806438446045s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 6.699562072753906e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.0728836059570312e-05s
INFO | --- Analysis for tcga-roadmap took 1.764679193496704s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 8.296966552734375e-05s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.15494942665100098s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020249605178833008s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 9.489059448242188e-05s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.1444091796875e-05s
INFO | --- Analysis for tcmgenedit_dataset took 1.7379400730133057s
Availability | SPARQL endpoint availability check for TDS took 8.440017700195312e-05s
Availability | VoID file availability check for TDS took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for TDS took 0.1632251739501953s
Reputation | Calculation of the PageRank for TDS took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for TDS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TDS took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for TDS took 3.647804260253906e-05s
Believability | Calculation of trust value for TDS took 1.2636184692382812e-05s
INFO | --- Analysis for tds took 1.755122423171997s
Availability | SPARQL endpoint availability check for TEKORD took 8.225440979003906e-05s
Availability | VoID file availability check for TEKORD took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for TEKORD took 0.15952825546264648s
Reputation | Calculation of the PageRank for TEKORD took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.1961669921875e-05s
Believability | Calculation of trust value for TEKORD took 1.2636184692382812e-05s
INFO | --- Analysis for tekord took 1.797623634338379s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 4.1961669921875e-05s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.16310358047485352s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00010728836059570312s
Believability | Calculation of trust value for Telegraphis Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for telegraphis took 1.7364277839660645s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.100799560546875e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.16274452209472656s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.020314455032348633s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 6.461143493652344e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.1920928955078125e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 1.752851963043213s
Availability | SPARQL endpoint availability check for Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Ontology took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Ontology took 0.16682195663452148s
Reputation | Calculation of the PageRank for Ontology took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0009465217590332031s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Ontology took 1.33514404296875e-05s
INFO | --- Analysis for Terrorist_attack took 1.774078130722046s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.1961669921875e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.15326261520385742s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 2.7894973754882812e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.239776611328125e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 1.7441072463989258s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 8.58306884765625e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.1549079418182373s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.02208542823791504s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 2.7418136596679688e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.1682510375976562e-05s
INFO | --- Analysis for Tesla_Deaths took 1.7199573516845703s
Availability | SPARQL endpoint availability check for test took 8.440017700195312e-05s
Availability | VoID file availability check for test took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for test took 0.15552139282226562s
Reputation | Calculation of the PageRank for test took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for test took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for test took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for test took 2.8133392333984375e-05s
Believability | Calculation of trust value for test took 1.1920928955078125e-05s
INFO | --- Analysis for test took 1.715571641921997s
Availability | SPARQL endpoint availability check for Test took 8.320808410644531e-05s
Availability | VoID file availability check for Test took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Test took 0.15629816055297852s
Reputation | Calculation of the PageRank for Test took 0.02022576332092285s
Interlinking | Calculation of Degree of Connection for Test took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Test took 2.7894973754882812e-05s
Believability | Calculation of trust value for Test took 1.239776611328125e-05s
INFO | --- Analysis for Test took 1.7539165019989014s
Availability | SPARQL endpoint availability check for test-svu took 4.076957702636719e-05s
Availability | VoID file availability check for test-svu took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for test-svu took 0.1631450653076172s
Reputation | Calculation of the PageRank for test-svu took 0.020287513732910156s
Interlinking | Calculation of Degree of Connection for test-svu took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for test-svu took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for test-svu took 2.7418136596679688e-05s
Believability | Calculation of trust value for test-svu took 1.2159347534179688e-05s
INFO | --- Analysis for test-svu took 1.8550443649291992s
Availability | SPARQL endpoint availability check for Test took 8.487701416015625e-05s
Availability | VoID file availability check for Test took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Test took 0.1619586944580078s
Reputation | Calculation of the PageRank for Test took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for Test took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Test took 2.765655517578125e-05s
Believability | Calculation of trust value for Test took 1.2159347534179688e-05s
INFO | --- Analysis for Test_ took 1.7677912712097168s
Availability | SPARQL endpoint availability check for xxxxx took 8.463859558105469e-05s
Availability | VoID file availability check for xxxxx took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for xxxxx took 0.1522984504699707s
Reputation | Calculation of the PageRank for xxxxx took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for xxxxx took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for xxxxx took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.029273986816406e-05s
Believability | Calculation of trust value for xxxxx took 1.3113021850585938e-05s
INFO | --- Analysis for testee took 1.8123457431793213s
Availability | SPARQL endpoint availability check for tharawat magazine took 8.273124694824219e-05s
Availability | VoID file availability check for tharawat magazine took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.15260863304138184s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02024364471435547s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 9.918212890625e-05s
Believability | Calculation of trust value for tharawat magazine took 1.1205673217773438e-05s
INFO | --- Analysis for tharawat-magazine-com took 1.7095849514007568s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 4.0531158447265625e-05s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.15237116813659668s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020113468170166016s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 2.6464462280273438e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.0728836059570312e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 1.72855544090271s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 2.2613120079040527s
Availability | VoID file availability check for The European Library Open Dataset took 0.00048065185546875s
Extra | Recovery of all triples for The European Library Open Dataset took 6.924414396286011s
Performance | Total latancy measurement for The European Library Open Dataset took 15.974554777145386s
Amount of data | Number of triples check for The European Library Open Dataset took 64.0956621170044s
Interoperability | New terms check for The European Library Open Dataset took 60.2822527885437s
Versatility | Languages check for The European Library Open Dataset took 3.1728670597076416s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.2012898921966553s
Interpretability | RDF structures check for The European Library Open Dataset took 3.2030794620513916s
Versatility | Serialization formats check for The European Library Open Dataset took 3.196554660797119s
Availability | RDF dump link check for The European Library Open Dataset took 3.168236255645752s
License | MR license check for The European Library Open Dataset took 3.202672243118286s
License | HR license check for The European Library Open Dataset took 3.200751304626465s
Amount of data | Number of property check for The European Library Open Dataset took 3.202312707901001s
Understandability | Number of label check for The European Library Open Dataset took 3.731212854385376s
Understandability | URI regex check for The European Library Open Dataset took 6.3754730224609375s
Understandability | Vocabs check for The European Library Open Dataset took 3.202481985092163s
Verifiability | Authors check for The European Library Open Dataset took 3.1998631954193115s
Verifiability | Publishers check for The European Library Open Dataset took 3.1959688663482666s
Performance | Throughput check for The European Library Open Dataset took 31.9047749042511s
Amount of data | Check the number of entities for The European Library Open Dataset took 3.218650817871094e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.169569730758667s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.347712278366089s
Interlinking | skos check for The European Library Open Dataset took 3.228515863418579s
Interlinking | skos check for The European Library Open Dataset took 3.2286500930786133s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.1901252269744873s
Currency | Creation date check for The European Library Open Dataset took 6.365343809127808s
Currency | Modification date check for The European Library Open Dataset took 6.401464939117432s
Rep.Conc. | URIs length for The European Library Open Dataset took 123.00205755233765s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 3.1712470054626465s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.4809787273406982s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.02621150016784668s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.026918888092041016s
Consistency | Disjoint class check for The European Library Open Dataset took 3.186929941177368s
Consistency | Check Misplaced properties for The European Library Open Dataset took 67.41020131111145s
Consistency | Misplaced classes for The European Library Open Dataset took 3.2715039253234863s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.8301026821136475s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.3135430812835693s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 66.37198543548584s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.031074047088623047s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.170567035675049s
Security | Sign check for The European Library Open Dataset took 3.200989007949829s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 9.93712854385376s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.3002612590789795s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 9.775161743164062e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for the-european-library-open-dataset took 901.5934646129608s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 4.57763671875e-05s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.1646876335144043s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.021223783493041992s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010323524475097656s
Believability | Calculation of trust value for The Eurostat Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for the-eurostat-linked-data took 1.7584571838378906s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 8.416175842285156e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.15156149864196777s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.009506225585938e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 4.76837158203125e-06s
INFO | --- Analysis for the-living-lod-cloud took 1.747412919998169s
Availability | SPARQL endpoint availability check for The View From took 0.06467938423156738s
Availability | VoID file availability check for The View From took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for The View From took 0.1544938087463379s
Reputation | Calculation of the PageRank for The View From took 0.02178645133972168s
Interlinking | Calculation of Degree of Connection for The View From took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for The View From took 8.153915405273438e-05s
Believability | Calculation of trust value for The View From took 1.0251998901367188e-05s
INFO | --- Analysis for the-view-from took 1.8705077171325684s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 8.296966552734375e-05s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.15634942054748535s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.021215438842773438s
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.0007088184356689453s
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 1.0251998901367188e-05s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 1.7428979873657227s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 8.487701416015625e-05s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.1632850170135498s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.147125244140625e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.0967254638671875e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 1.7710776329040527s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.1961669921875e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.1641085147857666s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.02147531509399414s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010442733764648438s
Believability | Calculation of trust value for The Content Wrangler took 1.049041748046875e-05s
INFO | --- Analysis for thecontentwrangler-com took 1.749955177307129s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.220008850097656e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.15546226501464844s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.021384716033935547s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.1948089599609375e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 8.58306884765625e-06s
INFO | --- Analysis for thesaurus-datenwissen took 1.7629106044769287s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.5615987777709961s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.1641068458557129s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.021755218505859375s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.43865966796875e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.049041748046875e-05s
INFO | --- Analysis for thesaurus-w took 2.6318533420562744s
Availability | SPARQL endpoint availability check for theses.fr took 9.512901306152344e-05s
Availability | VoID file availability check for theses.fr took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for theses.fr took 0.16296958923339844s
Reputation | Calculation of the PageRank for theses.fr took 0.020723342895507812s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.792213439941406e-05s
Believability | Calculation of trust value for theses.fr took 5.9604644775390625e-06s
INFO | --- Analysis for thesesfr took 1.777141809463501s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.839897155761719e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.14935016632080078s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.023772716522216797s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0012497901916503906s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.5299530029296875e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 8.106231689453125e-06s
INFO | --- Analysis for Thinkphile took 1.7155992984771729s
Availability | SPARQL endpoint availability check for ThIST took 4.5299530029296875e-05s
Availability | VoID file availability check for ThIST took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for ThIST took 0.1633758544921875s
Reputation | Calculation of the PageRank for ThIST took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for ThIST took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for ThIST took 7.963180541992188e-05s
Believability | Calculation of trust value for ThIST took 1.1920928955078125e-05s
INFO | --- Analysis for thist took 1.7671349048614502s
Availability | SPARQL endpoint availability check for TIP took 40.03079605102539s
Availability | VoID file availability check for TIP took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for TIP took 0.15693902969360352s
Reputation | Calculation of the PageRank for TIP took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for TIP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010204315185546875s
Believability | Calculation of trust value for TIP took 1.1682510375976562e-05s
INFO | --- Analysis for tip took 101.9206235408783s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 8.320808410644531e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.15499186515808105s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 4.863739013671875e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.33514404296875e-05s
INFO | --- Analysis for TOPMODEL took 1.7442786693572998s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 8.273124694824219e-05s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.16461873054504395s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.02074408531188965s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.361701965332031e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 5.245208740234375e-06s
INFO | --- Analysis for TP-data took 1.7919237613677979s
Availability | SPARQL endpoint availability check for Trackloaded Artist Profiles took 4.291534423828125e-05s
Availability | VoID file availability check for Trackloaded Artist Profiles took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Trackloaded Artist Profiles took 0.15580320358276367s
Reputation | Calculation of the PageRank for Trackloaded Artist Profiles took 0.021608352661132812s
Interlinking | Calculation of Degree of Connection for Trackloaded Artist Profiles took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Trackloaded Artist Profiles took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Trackloaded Artist Profiles took 1.1920928955078125e-05s
Believability | Calculation of trust value for Trackloaded Artist Profiles took 9.775161743164062e-06s
INFO | --- Analysis for trackloaded took 1.7093737125396729s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.15738940238952637s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.482269287109375e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for traditional-korean-medicine took 1.7443089485168457s
Availability | SPARQL endpoint availability check for Traffic Scotland took 8.177757263183594e-05s
Availability | VoID file availability check for Traffic Scotland took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.15940618515014648s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.021260976791381836s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.647804260253906e-05s
Believability | Calculation of trust value for Traffic Scotland took 1.1205673217773438e-05s
INFO | --- Analysis for traffic-scotland took 1.8097279071807861s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 5.340576171875e-05s
Availability | VoID file availability check for Transparency International Linked Data took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.15677976608276367s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02031683921813965s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010538101196289062s
Believability | Calculation of trust value for Transparency International Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for transparency-linked-data took 1.767998456954956s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 4.00543212890625e-05s
Availability | VoID file availability check for transport.data.gov.uk took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.15567874908447266s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.059906005859375e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 1.0251998901367188e-05s
INFO | --- Analysis for transport-data-gov-uk took 1.7748510837554932s
Availability | SPARQL endpoint availability check for Trelios took 9.298324584960938e-05s
Availability | VoID file availability check for Trelios took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Trelios took 0.1623852252960205s
Reputation | Calculation of the PageRank for Trelios took 0.021737098693847656s
Interlinking | Calculation of Degree of Connection for Trelios took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.239776611328125e-05s
Believability | Calculation of trust value for Trelios took 1.0728836059570312e-05s
INFO | --- Analysis for Trelios took 1.7768433094024658s
Availability | SPARQL endpoint availability check for Twarql took 4.2438507080078125e-05s
Availability | VoID file availability check for Twarql took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Twarql took 0.16500568389892578s
Reputation | Calculation of the PageRank for Twarql took 0.02035069465637207s
Interlinking | Calculation of Degree of Connection for Twarql took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Twarql took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.318092346191406e-05s
Believability | Calculation of trust value for Twarql took 1.4543533325195312e-05s
INFO | --- Analysis for twarql took 1.7716879844665527s
Availability | SPARQL endpoint availability check for TWC Data-gov took 8.678436279296875e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.1525406837463379s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.023476362228393555s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.0279159545898438e-05s
Believability | Calculation of trust value for TWC Data-gov took 1.0251998901367188e-05s
INFO | --- Analysis for twc-data-gov took 1.7211339473724365s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 8.416175842285156e-05s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.16107177734375s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020381927490234375s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 2.7894973754882812e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 1.2636184692382812e-05s
INFO | --- Analysis for twc-healthdata took 1.727902889251709s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 8.368492126464844e-05s
Availability | VoID file availability check for Instance Hub (all) took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.15596938133239746s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.200241088867188e-05s
Believability | Calculation of trust value for Instance Hub (all) took 9.775161743164062e-06s
INFO | --- Analysis for twc-hub took 1.7794923782348633s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 4.124641418457031e-05s
Availability | VoID file availability check for IEEE VIS Source Data took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.15990948677062988s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.022526264190673828s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00010418891906738281s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.2874603271484375e-05s
INFO | --- Analysis for twc-ieeevis took 1.7324349880218506s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.7206878662109375e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.16484689712524414s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 8.726119995117188e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 1.3113021850585938e-05s
INFO | --- Analysis for twc-logd took 1.7438416481018066s
Availability | SPARQL endpoint availability check for twc-opendap took 4.3392181396484375e-05s
Availability | VoID file availability check for twc-opendap took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.16004133224487305s
Reputation | Calculation of the PageRank for twc-opendap took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0009837150573730469s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 8.511543273925781e-05s
Believability | Calculation of trust value for twc-opendap took 1.430511474609375e-05s
INFO | --- Analysis for twc-opendap took 1.7551429271697998s
Availability | SPARQL endpoint availability check for typepad took 4.291534423828125e-05s
Availability | VoID file availability check for typepad took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for typepad took 0.15292072296142578s
Reputation | Calculation of the PageRank for typepad took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for typepad took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for typepad took 4.935264587402344e-05s
Believability | Calculation of trust value for typepad took 9.775161743164062e-06s
INFO | --- Analysis for typepad took 1.7610394954681396s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.7917177677154541s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.16171646118164062s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.021712541580200195s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.1484832763671875e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.0967254638671875e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 3.187683343887329s
Availability | SPARQL endpoint availability check for Uberblic.org took 4.744529724121094e-05s
Availability | VoID file availability check for Uberblic.org took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.15523409843444824s
Reputation | Calculation of the PageRank for Uberblic.org took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010609626770019531s
Believability | Calculation of trust value for Uberblic.org took 1.0728836059570312e-05s
INFO | --- Analysis for uberblic took 1.7451822757720947s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.5637397766113281s
Availability | VoID file availability check for UDante in LiLa took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.15944266319274902s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for UDante took 2.6577792167663574s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.1600785255432129s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for ufo took 1.7427961826324463s
Availability | SPARQL endpoint availability check for Uganda Disasters took 9.059906005859375e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.15964221954345703s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0009388923645019531s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 5.340576171875e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.0728836059570312e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 1.810699462890625s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 8.106231689453125e-05s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.00020456314086914062s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.15190768241882324s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.02068161964416504s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 9.846687316894531e-05s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for uis-linked-data took 1.7252733707427979s
Availability | SPARQL endpoint availability check for UK Legislation took 4.172325134277344e-05s
Availability | VoID file availability check for UK Legislation took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.1621692180633545s
Reputation | Calculation of the PageRank for UK Legislation took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.7738037109375e-05s
Believability | Calculation of trust value for UK Legislation took 5.4836273193359375e-06s
INFO | --- Analysis for uk-legislation-api took 1.7470283508300781s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.00543212890625e-05s
Availability | VoID file availability check for UK Postcodes took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.15308833122253418s
Reputation | Calculation of the PageRank for UK Postcodes took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0031464099884033203s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 0.0001437664031982422s
Believability | Calculation of trust value for UK Postcodes took 1.1444091796875e-05s
INFO | --- Analysis for uk-postcodes took 1.7378346920013428s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 9.1552734375e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.15933609008789062s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.022499799728393555s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0010027885437011719s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0001571178436279297s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1205673217773438e-05s
INFO | --- Analysis for umbel took 1.7543540000915527s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 8.249282836914062e-05s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.1585996150970459s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.021882295608520508s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 4.124641418457031e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 1.1444091796875e-05s
INFO | --- Analysis for umthes took 1.7500345706939697s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 4.1484832763671875e-05s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0002067089080810547s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.15497112274169922s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.0040740966796875e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 1.049041748046875e-05s
INFO | --- Analysis for un-hazardous-numbers took 1.7358386516571045s
Availability | SPARQL endpoint availability check for UniProt took 8.106231689453125e-05s
Availability | VoID file availability check for UniProt took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for UniProt took 0.15909218788146973s
Reputation | Calculation of the PageRank for UniProt took 0.022452592849731445s
Interlinking | Calculation of Degree of Connection for UniProt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for UniProt took 3.719329833984375e-05s
Believability | Calculation of trust value for UniProt took 9.5367431640625e-06s
INFO | --- Analysis for UniProt took 1.749086618423462s
Availability | SPARQL endpoint availability check for UniProt took 4.506111145019531e-05s
Availability | VoID file availability check for UniProt took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for UniProt took 0.1649031639099121s
Reputation | Calculation of the PageRank for UniProt took 0.02083730697631836s
Interlinking | Calculation of Degree of Connection for UniProt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.887580871582031e-05s
Believability | Calculation of trust value for UniProt took 9.298324584960938e-06s
INFO | --- Analysis for uniprot took 1.7412426471710205s
Availability | SPARQL endpoint availability check for uniprot-metadata took 6.365776062011719e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.16012191772460938s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.021675825119018555s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.29425048828125e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.0013580322265625e-05s
INFO | --- Analysis for uniprot-metadata took 1.777709722518921s
Availability | SPARQL endpoint availability check for UniProtKB took 0.00010609626770019531s
Availability | VoID file availability check for UniProtKB took 0.0002110004425048828s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.15366697311401367s
Reputation | Calculation of the PageRank for UniProtKB took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 5.6743621826171875e-05s
Believability | Calculation of trust value for UniProtKB took 1.1205673217773438e-05s
INFO | --- Analysis for uniprotkb took 1.8128819465637207s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.16121697425842285s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.021952390670776367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 1.777721881866455s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.15967202186584473s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020750999450683594s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 1.7350823879241943s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 8.034706115722656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.16176509857177734s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 1.7420334815979004s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 8.058547973632812e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.15636801719665527s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.02265310287475586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 1.7268390655517578s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 8.177757263183594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.15117549896240234s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.021631956100463867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 5.245208740234375e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 1.7216360569000244s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 7.987022399902344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.16163945198059082s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.021981239318847656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007092952728271484s
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.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 1.7317769527435303s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 9.608268737792969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.16247868537902832s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.021723270416259766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007042884826660156s
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 1.801917552947998s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 8.368492126464844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.15923571586608887s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 1.7578141689300537s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 6.556510925292969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.1532137393951416s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.021544456481933594s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 1.7109205722808838s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.1633007526397705s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02069830894470215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 1.758723258972168s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 6.461143493652344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.16256070137023926s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 1.743530511856079s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 8.058547973632812e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.16503620147705078s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 1.765045404434204s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 8.678436279296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.15815997123718262s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.021843433380126953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 1.7622287273406982s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 9.965896606445312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.15471553802490234s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 1.750356912612915s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 9.250640869140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.151839017868042s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.02083301544189453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 5.0067901611328125e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 1.7392792701721191s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.1529695987701416s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.021733999252319336s
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.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 1.7388451099395752s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.00020432472229003906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.149489164352417s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.0228273868560791s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 1.7103488445281982s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 6.4849853515625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.1591320037841797s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.02156209945678711s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 1.7467310428619385s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 8.58306884765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.1541447639465332s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.022283077239990234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 1.718834638595581s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.15540862083435059s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 1.8199999332427979s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 5.030632019042969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.16089248657226562s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 1.8401589393615723s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 8.273124694824219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.15667462348937988s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020785808563232422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 1.7375528812408447s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.16040325164794922s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.021811246871948242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 1.7219951152801514s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.15627455711364746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.02193617820739746s
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.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 1.758145809173584s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 8.273124694824219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.15153050422668457s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02092576026916504s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 5.364418029785156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 1.7653965950012207s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 9.918212890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.15859031677246094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.0218355655670166s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 1.7794914245605469s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 8.273124694824219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.16510248184204102s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.022142887115478516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 1.7373411655426025s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 5.8650970458984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.1573638916015625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 1.8490116596221924s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 8.058547973632812e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.16547322273254395s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 1.7492735385894775s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.17750954627990723s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.021555423736572266s
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.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 1.7597911357879639s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 9.083747863769531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.16221261024475098s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 1.761439323425293s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.15734481811523438s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.021392345428466797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 1.7426838874816895s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 8.296966552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.16257953643798828s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.021736621856689453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 1.7802855968475342s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.2774045467376709s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020194053649902344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 1.8426790237426758s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 8.177757263183594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.1600031852722168s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.021066665649414062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 1.7707505226135254s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 5.364418029785156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.1650383472442627s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.02127385139465332s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 1.7529501914978027s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.15391898155212402s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.02196502685546875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 1.716538906097412s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 8.082389831542969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.15455961227416992s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02150726318359375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 1.7357134819030762s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 6.4849853515625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.15897369384765625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 1.7327396869659424s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.15921568870544434s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 1.754798412322998s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 9.989738464355469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.1582503318786621s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 1.735508918762207s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.744529724121094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.15715980529785156s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.02051520347595215s
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.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 1.7633404731750488s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.1528933048248291s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 1.7153451442718506s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 8.130073547363281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.16311907768249512s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 1.7695937156677246s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 5.364418029785156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0002110004425048828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.261019229888916s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 1.854515790939331s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 8.392333984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.15740585327148438s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.02065277099609375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 1.7480888366699219s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.15555500984191895s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 1.7914206981658936s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.320808410644531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0002079010009765625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.15249276161193848s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02198505401611328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 1.7537670135498047s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 5.0067901611328125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.16031956672668457s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 1.7293407917022705s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.1551976203918457s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.022071361541748047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 1.7784793376922607s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.15857362747192383s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 1.723374605178833s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.16518783569335938s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 1.7607841491699219s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.17212843894958496s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 1.8028440475463867s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 8.225440979003906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.1631019115447998s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020839452743530273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 1.7830569744110107s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 5.4836273193359375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0003662109375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.14831256866455078s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.031183958053588867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0010714530944824219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 5.2928924560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 1.7051258087158203s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 9.059906005859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.1638960838317871s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.5735626220703125e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 1.7398653030395508s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.15866541862487793s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.022699356079101562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 1.7481169700622559s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.15758419036865234s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 5.0067901611328125e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 1.7479491233825684s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.1628742218017578s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 1.7246222496032715s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.14975690841674805s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 1.7300002574920654s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 8.034706115722656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.150665283203125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 1.7338573932647705s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 7.915496826171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.1625227928161621s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 1.7272353172302246s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 5.1021575927734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.15411591529846191s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 1.70680570602417s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 6.747245788574219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.15259671211242676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.021880388259887695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 1.7400643825531006s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.124641418457031e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.1671907901763916s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.02127528190612793s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 7.104873657226562e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 9.775161743164062e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 1.7658798694610596s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.124641418457031e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.15960931777954102s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.02172255516052246s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.792213439941406e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.33514404296875e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 1.7509500980377197s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.1961669921875e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.15915679931640625s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020615816116333008s
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.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.528594970703125e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 9.5367431640625e-06s
INFO | --- Analysis for university-sussex-reading-lists took 1.7167980670928955s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 3.981590270996094e-05s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0002048015594482422s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.17367219924926758s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 6.866455078125e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.0967254638671875e-05s
INFO | --- Analysis for unodc took 1.7529687881469727s
Availability | SPARQL endpoint availability check for Super Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Super Ontology took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.1524217128753662s
Reputation | Calculation of the PageRank for Super Ontology took 0.020869970321655273s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 7.796287536621094e-05s
Believability | Calculation of trust value for Super Ontology took 1.239776611328125e-05s
INFO | --- Analysis for upper-ontology took 1.7464032173156738s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 7.915496826171875e-05s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.1527256965637207s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.02150750160217285s
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.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for Upper_Ontology took 1.755788803100586s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 7.987022399902344e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.1532297134399414s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.022663593292236328s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 2.8848648071289062e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 9.059906005859375e-06s
INFO | --- Analysis for Urban_Atlas_ took 1.79805588722229s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 4.172325134277344e-05s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.15138649940490723s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 2.9087066650390625e-05s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 9.775161743164062e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 1.7329587936401367s
Availability | SPARQL endpoint availability check for URIBurner took 8.177757263183594e-05s
Availability | VoID file availability check for URIBurner took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for URIBurner took 0.1582627296447754s
Reputation | Calculation of the PageRank for URIBurner took 0.021966218948364258s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for URIBurner took 9.059906005859375e-05s
Believability | Calculation of trust value for URIBurner took 6.67572021484375e-06s
INFO | --- Analysis for uriburner took 1.731724500656128s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.315376281738281e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.15759706497192383s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02089524269104004s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.0040740966796875e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.239776611328125e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 1.774655818939209s
Availability | SPARQL endpoint availability check for Legija Stranaca took 8.034706115722656e-05s
Availability | VoID file availability check for Legija Stranaca took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.15380454063415527s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.02196812629699707s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.075599670410156e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.4066696166992188e-05s
INFO | --- Analysis for Uros_Legija_Susa took 1.7504589557647705s
Availability | SPARQL endpoint availability check for Legija took 4.00543212890625e-05s
Availability | VoID file availability check for Legija took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for Legija took 0.15296530723571777s
Reputation | Calculation of the PageRank for Legija took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for Legija took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Legija took 3.075599670410156e-05s
Believability | Calculation of trust value for Legija took 9.5367431640625e-06s
INFO | --- Analysis for Uros_Susa took 1.750349998474121s
Availability | SPARQL endpoint availability check for USAGE review corpus took 6.604194641113281e-05s
Availability | VoID file availability check for USAGE review corpus took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.1687605381011963s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.022298574447631836s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.001027822494506836s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 4.172325134277344e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.3828277587890625e-05s
INFO | --- Analysis for usage-review-corpus took 1.7675526142120361s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 4.363059997558594e-05s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.15970635414123535s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007252693176269531s
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.049041748046875e-05s
INFO | --- Analysis for utpl-lod took 1.8653359413146973s
Availability | SPARQL endpoint availability check for terrorist attack took 4.076957702636719e-05s
Availability | VoID file availability check for terrorist attack took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.15905976295471191s
Reputation | Calculation of the PageRank for terrorist attack took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 2.9087066650390625e-05s
Believability | Calculation of trust value for terrorist attack took 9.775161743164062e-06s
INFO | --- Analysis for varsha took 1.743030309677124s
Availability | SPARQL endpoint availability check for VA took 8.726119995117188e-05s
Availability | VoID file availability check for VA took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for VA took 0.15983247756958008s
Reputation | Calculation of the PageRank for VA took 0.021587848663330078s
Interlinking | Calculation of Degree of Connection for VA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VA took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for VA took 3.170967102050781e-05s
Believability | Calculation of trust value for VA took 1.3113021850585938e-05s
INFO | --- Analysis for Vehicule_Autonome took 1.7631726264953613s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 8.296966552734375e-05s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.17182159423828125s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.02255868911743164s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 9.5367431640625e-06s
INFO | --- Analysis for VelezIndexTotiusArtis took 1.786045789718628s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 8.0108642578125e-05s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.16567111015319824s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02062368392944336s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.559226989746094e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.0728836059570312e-05s
INFO | --- Analysis for verrijktkoninkrijk took 1.7410228252410889s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 4.267692565917969e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.1536402702331543s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00017333030700683594s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 8.821487426757812e-06s
INFO | --- Analysis for viaf took 1.702967643737793s
Availability | SPARQL endpoint availability check for Vihar Exports took 9.560585021972656e-05s
Availability | VoID file availability check for Vihar Exports took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.15475058555603027s
Reputation | Calculation of the PageRank for Vihar Exports took 0.021762371063232422s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.123283386230469e-05s
Believability | Calculation of trust value for Vihar Exports took 1.1920928955078125e-05s
INFO | --- Analysis for Vihar_Exports took 1.7547199726104736s
Availability | SPARQL endpoint availability check for VIVO took 4.100799560546875e-05s
Availability | VoID file availability check for VIVO took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for VIVO took 0.15763449668884277s
Reputation | Calculation of the PageRank for VIVO took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.937980651855469e-05s
Believability | Calculation of trust value for VIVO took 1.1444091796875e-05s
INFO | --- Analysis for vivo took 1.7375781536102295s
Availability | SPARQL endpoint availability check for VIVO Cornell took 8.106231689453125e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.17677021026611328s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.02279186248779297s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.106231689453125e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.0013580322265625e-05s
INFO | --- Analysis for vivo-cornell-university took 1.7832081317901611s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.076957702636719e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.150465726852417s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 7.891654968261719e-05s
Believability | Calculation of trust value for VIVO Indiana took 9.775161743164062e-06s
INFO | --- Analysis for vivo-indiana-university took 1.8079290390014648s
Availability | SPARQL endpoint availability check for VIVO Ponce took 8.392333984375e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.15962457656860352s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.021465063095092773s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.552436828613281e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.3828277587890625e-05s
INFO | --- Analysis for vivo-ponce took 1.7414929866790771s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 6.437301635742188e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.15945076942443848s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.528594970703125e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 5.9604644775390625e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 1.7327039241790771s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 0.00010967254638671875s
Availability | VoID file availability check for VIVO University of Florida took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.15984082221984863s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.34600830078125e-05s
Believability | Calculation of trust value for VIVO University of Florida took 9.775161743164062e-06s
INFO | --- Analysis for vivo-university-of-florida took 1.76786470413208s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 8.249282836914062e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.16068768501281738s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.528594970703125e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 9.775161743164062e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 1.7423057556152344s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 7.843971252441406e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.16214990615844727s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.5762786865234375e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.4543533325195312e-05s
INFO | --- Analysis for vivo-wustl took 1.7388103008270264s
Availability | SPARQL endpoint availability check for vivo2doi took 9.965896606445312e-05s
Availability | VoID file availability check for vivo2doi took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.1537322998046875s
Reputation | Calculation of the PageRank for vivo2doi took 0.021864652633666992s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.100799560546875e-05s
Believability | Calculation of trust value for vivo2doi took 1.0967254638671875e-05s
INFO | --- Analysis for vivo2doi took 1.7780838012695312s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 8.130073547363281e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.15654969215393066s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.937980651855469e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 9.5367431640625e-06s
INFO | --- Analysis for vu-wordnet took 1.7637314796447754s
Availability | SPARQL endpoint availability check for vulnerapedia took 3.9577484130859375e-05s
Availability | VoID file availability check for vulnerapedia took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.14771032333374023s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.413459777832031e-05s
Believability | Calculation of trust value for vulnerapedia took 1.0251998901367188e-05s
INFO | --- Analysis for vulnerapedia took 1.7346160411834717s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 5.2928924560546875e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.00020313262939453125s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.15130901336669922s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.02069377899169922s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.52587890625e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1920928955078125e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.0251998901367188e-05s
INFO | --- Analysis for VVASIAK took 1.7208702564239502s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 7.915496826171875e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.16202878952026367s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 2.956390380859375e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 9.775161743164062e-06s
INFO | --- Analysis for Vyvasta took 1.7534470558166504s
Availability | SPARQL endpoint availability check for W3C took 8.130073547363281e-05s
Availability | VoID file availability check for W3C took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for W3C took 0.1530742645263672s
Reputation | Calculation of the PageRank for W3C took 0.02062368392944336s
Interlinking | Calculation of Degree of Connection for W3C took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001404285430908203s
Believability | Calculation of trust value for W3C took 1.4066696166992188e-05s
INFO | --- Analysis for w3c took 1.7362427711486816s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 6.556510925292969e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.17350363731384277s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00011038780212402344s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 8.106231689453125e-06s
INFO | --- Analysis for w3c-wordnet took 1.795163869857788s
Availability | SPARQL endpoint availability check for WarSampo took 0.316786527633667s
Availability | VoID file availability check for WarSampo took 0.00045752525329589844s
Extra | Recovery of all triples for WarSampo took 12.62733793258667s
Performance | Total latancy measurement for WarSampo took 0.7716987133026123s
Amount of data | Number of triples check for WarSampo took 0.20107507705688477s
Interoperability | New terms check for WarSampo took 1.498232364654541s
Versatility | Languages check for WarSampo took 0.17243719100952148s
Interpretability | Number of blank nodes check for WarSampo took 0.18323183059692383s
Security | Check HTTPS for WarSampo took 0.3781914710998535s
Interpretability | RDF structures check for WarSampo took 0.18138551712036133s
Versatility | Serialization formats check for WarSampo took 0.1725444793701172s
Availability | RDF dump link check for WarSampo took 0.7688205242156982s
License | MR license check for WarSampo took 0.17112302780151367s
License | HR license check for WarSampo took 0.1478738784790039s
Amount of data | Number of property check for WarSampo took 0.18374037742614746s
Understandability | Number of label check for WarSampo took 0.17174315452575684s
Understandability | URI regex check for WarSampo took 0.3630809783935547s
Understandability | Vocabs check for WarSampo took 0.15291619300842285s
Verifiability | Authors check for WarSampo took 0.17184162139892578s
Verifiability | Publishers check for WarSampo took 0.1716914176940918s
Performance | Throughput check for WarSampo took 10.421443223953247s
Amount of data | Check the number of entities for WarSampo took 15.323540687561035s
Verifiability | Contribs. check for WarSampo took 0.14854192733764648s
Interlinking | sameAs chians check for WarSampo took 0.1710653305053711s
Interlinking | skos check for WarSampo took 0.17186856269836426s
Interlinking | skos check for WarSampo took 0.1476151943206787s
Timeliness | dataset update frequency check for WarSampo took 0.1477494239807129s
Currency | Creation date check for WarSampo took 0.3241298198699951s
Currency | Modification date check for WarSampo took 0.3245983123779297s
Rep.Conc. | URIs length for WarSampo took 16.41651701927185s
Interoperability | New vocabularies check for WarSampo took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.17287564277648926s
Accuracy | Check Functional Property for WarSampo took 0.17171478271484375s
Accuracy | Check Inverse Functional Property for WarSampo took 0.14940166473388672s
Accuracy | Check Empty annotation labels for WarSampo took 8.476844310760498s
Accuracy | Check White space in annotation for WarSampo took 2.1557717323303223s
Accuracy | Check Datatype consistency for WarSampo took 5.2427520751953125s
Consistency | Disjoint class check for WarSampo took 0.17261838912963867s
Consistency | Check Misplaced properties for WarSampo took 0.42285847663879395s
Consistency | Check Ontology hijacking for WarSampo took 11.884950399398804s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.4066839218139648s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.6325287818908691s
Conciseness | Check Extensional conciseness for WarSampo took 2.7923288345336914s
Conciseness | Check Intensional conciseness for WarSampo took 0.24468278884887695s
Security | Sign check for WarSampo took 0.1479945182800293s
Availability | Check URIs Dereferenciability for WarSampo took 2.414217472076416s
Completeness | Calculation of interlinking completeness for WarSampo took 0.22181344032287598s
Reputation | Calculation of the PageRank for WarSampo took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.368492126464844e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for WarSampo took 8.106231689453125e-06s
INFO | --- Analysis for warsampo took 127.63429379463196s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.50542688369751s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.15353775024414062s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02087879180908203s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.939338684082031e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for wasabi took 52.37046408653259s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 4.38690185546875e-05s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.1556394100189209s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.022388935089111328s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 3.075599670410156e-05s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Water_Areas_Classification took 1.7555313110351562s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 8.296966552734375e-05s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.15033555030822754s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 3.0994415283203125e-05s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.3589859008789062e-05s
INFO | --- Analysis for Water_Buffer took 1.7000234127044678s
Availability | SPARQL endpoint availability check for WebIsALOD took 4.315376281738281e-05s
Availability | VoID file availability check for WebIsALOD took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.1577620506286621s
Reputation | Calculation of the PageRank for WebIsALOD took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 9.72747802734375e-05s
Believability | Calculation of trust value for WebIsALOD took 8.344650268554688e-06s
INFO | --- Analysis for webisalod took 1.798480749130249s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 0.0001456737518310547s
Availability | VoID file availability check for webnmasunotraveler took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.1547071933746338s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.790855407714844e-05s
Believability | Calculation of trust value for webnmasunotraveler took 5.9604644775390625e-06s
INFO | --- Analysis for webnmasunotraveler took 1.8119666576385498s
Availability | SPARQL endpoint availability check for Whisky Circle took 4.029273986816406e-05s
Availability | VoID file availability check for Whisky Circle took 0.00021409988403320312s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.15395641326904297s
Reputation | Calculation of the PageRank for Whisky Circle took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010395050048828125s
Believability | Calculation of trust value for Whisky Circle took 5.9604644775390625e-06s
INFO | --- Analysis for whisky-circle-info took 1.7240033149719238s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0002186298370361328s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.16254520416259766s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.62396240234375e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for WHOnto took 1.7816205024719238s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.14986681938171387s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.020724058151245117s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 2.956390380859375e-05s
INFO | --- Analysis for whonto took 1.700895071029663s
Availability | SPARQL endpoint availability check for Wikidata took 4.267692565917969e-05s
Availability | VoID file availability check for Wikidata took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Wikidata took 0.16503047943115234s
Reputation | Calculation of the PageRank for Wikidata took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0002887248992919922s
Believability | Calculation of trust value for Wikidata took 5.4836273193359375e-06s
INFO | --- Analysis for wikidata took 1.7110252380371094s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 8.630752563476562e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.16108918190002441s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.02127671241760254s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.343292236328125e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 4.76837158203125e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 1.7537055015563965s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 4.6253204345703125e-05s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.16547369956970215s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.021571874618530273s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007185935974121094s
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 1.743943691253662s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2210798263549805s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.17625689506530762s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.021168231964111328s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.0040740966796875e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 9.775161743164062e-06s
INFO | --- Analysis for wl-kg took 3.2919085025787354s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 4.1961669921875e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.160841703414917s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 6.961822509765625e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.0728836059570312e-05s
INFO | --- Analysis for wn-wiki-instances took 1.7281548976898193s
Availability | SPARQL endpoint availability check for World Loanword Database took 4.2438507080078125e-05s
Availability | VoID file availability check for World Loanword Database took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.15241217613220215s
Reputation | Calculation of the PageRank for World Loanword Database took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 6.914138793945312e-05s
Believability | Calculation of trust value for World Loanword Database took 1.0013580322265625e-05s
INFO | --- Analysis for wold took 1.7501740455627441s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 8.273124694824219e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.15293097496032715s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.0517578125e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.0728836059570312e-05s
INFO | --- Analysis for woodtrick took 1.7269964218139648s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 8.0108642578125e-05s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.15634775161743164s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.023449182510375977s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0010089874267578125s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 4.649162292480469e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 5.0067901611328125e-06s
INFO | --- Analysis for WordFormationLatin took 1.7061223983764648s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 4.100799560546875e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.15677237510681152s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010585784912109375s
Believability | Calculation of trust value for WordLift Blog EN took 9.775161743164062e-06s
INFO | --- Analysis for wordlift-io-blog-en took 1.8056399822235107s
Availability | SPARQL endpoint availability check for WordLift IT took 9.942054748535156e-05s
Availability | VoID file availability check for WordLift IT took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.1568613052368164s
Reputation | Calculation of the PageRank for WordLift IT took 0.022216796875s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00010561943054199219s
Believability | Calculation of trust value for WordLift IT took 1.0967254638671875e-05s
INFO | --- Analysis for wordlift-io-blog-it took 1.7274482250213623s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.00543212890625e-05s
Availability | VoID file availability check for WordNet-RDF took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.1564474105834961s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.894371032714844e-05s
Believability | Calculation of trust value for WordNet-RDF took 6.198883056640625e-06s
INFO | --- Analysis for wordnet-rdf took 1.6859228610992432s
Availability | SPARQL endpoint availability check for wordpress took 4.1484832763671875e-05s
Availability | VoID file availability check for wordpress took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for wordpress took 0.17255759239196777s
Reputation | Calculation of the PageRank for wordpress took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for wordpress took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.487701416015625e-05s
Believability | Calculation of trust value for wordpress took 5.4836273193359375e-06s
INFO | --- Analysis for wordpress took 1.6953213214874268s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 4.315376281738281e-05s
Availability | VoID file availability check for World Bank Linked Data took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.15058398246765137s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.0001239776611328125s
Believability | Calculation of trust value for World Bank Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for world-bank-linked-data took 1.8176517486572266s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 4.1484832763671875e-05s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0002186298370361328s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.15950727462768555s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.022785663604736328s
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.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.20159912109375e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 9.775161743164062e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 1.775986671447754s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.2438507080078125e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.15601587295532227s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.440017700195312e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 5.7220458984375e-06s
INFO | --- Analysis for world-wide-web-foundation took 1.7063078880310059s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.17224907875061035s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.00023412704467773438s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.1751465797424316s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.7616775035858154s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.17162632942199707s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.4946775436401367s
Versatility | Languages check for World War 1 as Linked Open Data took 0.17230916023254395s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.17118024826049805s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.22824549674987793s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.17115378379821777s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.17160749435424805s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.196949481964111s
License | MR license check for World War 1 as Linked Open Data took 0.171156644821167s
License | HR license check for World War 1 as Linked Open Data took 0.14748501777648926s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.17357921600341797s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.17319393157958984s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.319927453994751s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.18305301666259766s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.17137408256530762s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.17209982872009277s
Performance | Throughput check for World War 1 as Linked Open Data took 10.470768451690674s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.06922245025634766s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.17200303077697754s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.1713576316833496s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1721043586730957s
Interlinking | skos check for World War 1 as Linked Open Data took 0.14875173568725586s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.14888691902160645s
Currency | Creation date check for World War 1 as Linked Open Data took 0.34978199005126953s
Currency | Modification date check for World War 1 as Linked Open Data took 0.17282509803771973s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 1.4615046977996826s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 21.895480632781982s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.17142415046691895s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.17743611335754395s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.14836478233337402s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 0.9919865131378174s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.0496363639831543s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.31368565559387207s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.1711413860321045s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.46899986267089844s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 1.9994871616363525s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.3618977069854736s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5697274208068848s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.1903831958770752s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.47653937339782715s
Security | Sign check for World War 1 as Linked Open Data took 0.1543264389038086s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1481.3540782928467s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.5012946128845215s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.021106481552124023s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 9.942054748535156e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 17.43007230758667s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for ww1lod took 1578.6610600948334s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.0001068115234375s
Availability | VoID file availability check for xLiD-Lexica took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.16537189483642578s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020413875579833984s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.009506225585938e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.0728836059570312e-05s
INFO | --- Analysis for xlid-lexica took 1.794386863708496s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.172325134277344e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.15516352653503418s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.7670135498046875e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.0967254638671875e-05s
INFO | --- Analysis for xwn took 1.7658731937408447s
Availability | SPARQL endpoint availability check for xxx took 4.363059997558594e-05s
Availability | VoID file availability check for xxx took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for xxx took 0.16086769104003906s
Reputation | Calculation of the PageRank for xxx took 0.020862340927124023s
Interlinking | Calculation of Degree of Connection for xxx took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for xxx took 3.1948089599609375e-05s
Believability | Calculation of trust value for xxx took 7.62939453125e-06s
INFO | --- Analysis for xx took 1.7998936176300049s
Availability | SPARQL endpoint availability check for YAGO took 4.172325134277344e-05s
Availability | VoID file availability check for YAGO took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for YAGO took 0.1530611515045166s
Reputation | Calculation of the PageRank for YAGO took 0.021029233932495117s
Interlinking | Calculation of Degree of Connection for YAGO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for YAGO took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00013446807861328125s
Believability | Calculation of trust value for YAGO took 6.437301635742188e-05s
INFO | --- Analysis for yago took 1.731886863708496s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 8.0108642578125e-05s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.00020456314086914062s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.15425419807434082s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.82012939453125e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.0728836059570312e-05s
INFO | --- Analysis for yahoo_geoplanet took 1.7319002151489258s
Availability | SPARQL endpoint availability check for Yale Senselab took 7.43865966796875e-05s
Availability | VoID file availability check for Yale Senselab took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.16046857833862305s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 2.9802322387695312e-05s
Believability | Calculation of trust value for Yale Senselab took 1.049041748046875e-05s
INFO | --- Analysis for yale_senselab took 1.7477517127990723s
Availability | SPARQL endpoint availability check for test-dapp-2 took 6.270408630371094e-05s
Availability | VoID file availability check for test-dapp-2 took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.1629180908203125s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.0517578125e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.0967254638671875e-05s
INFO | --- Analysis for yordhis took 1.750201940536499s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 8.392333984375e-05s
Availability | VoID file availability check for Yovisto - academic video search took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.15511393547058105s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.021748065948486328s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.818771362304688e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 1.0013580322265625e-05s
INFO | --- Analysis for yovisto took 1.7370648384094238s
Availability | SPARQL endpoint availability check for YSA - General Finnish Thesaurus took 6.318092346191406e-05s
Availability | VoID file availability check for YSA - General Finnish Thesaurus took 0.0003218650817871094s
Completeness | Calculation of interlinking completeness for YSA - General Finnish Thesaurus took 0.15727448463439941s
Reputation | Calculation of the PageRank for YSA - General Finnish Thesaurus took 0.020750761032104492s
Interlinking | Calculation of Degree of Connection for YSA - General Finnish Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for YSA - General Finnish Thesaurus took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for YSA - General Finnish Thesaurus took 3.4809112548828125e-05s
Believability | Calculation of trust value for YSA - General Finnish Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for ysa took 1.7531845569610596s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.15468883514404297s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.364418029785156e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 9.5367431640625e-06s
INFO | --- Analysis for yso took 1.746748685836792s
Availability | SPARQL endpoint availability check for yso-fi-allars took 9.894371032714844e-05s
Availability | VoID file availability check for yso-fi-allars took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.15440011024475098s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.337860107421875e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.0251998901367188e-05s
INFO | --- Analysis for yso-fi-allars took 1.7606744766235352s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 8.296966552734375e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.15549898147583008s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.022117137908935547s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.266334533691406e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.0251998901367188e-05s
INFO | --- Analysis for yso-fi-ysa took 1.7367823123931885s
Availability | SPARQL endpoint availability check for YSO places took 4.553794860839844e-05s
Availability | VoID file availability check for YSO places took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for YSO places took 0.15290355682373047s
Reputation | Calculation of the PageRank for YSO places took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for YSO places took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.0994415283203125e-05s
Believability | Calculation of trust value for YSO places took 1.1444091796875e-05s
INFO | --- Analysis for yso-paikat took 1.8962230682373047s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 8.368492126464844e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.15257978439331055s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.552436828613281e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 1.3113021850585938e-05s
INFO | --- Analysis for zaragoza-datosabiertos took 1.7714571952819824s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 5.459785461425781e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.16089487075805664s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.02026677131652832s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.218650817871094e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.0967254638671875e-05s
INFO | --- Analysis for zaragoza_turruta took 1.7390284538269043s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.124641418457031e-05s
Availability | VoID file availability check for ZBW Labs took 0.00021576881408691406s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.15617632865905762s
Reputation | Calculation of the PageRank for ZBW Labs took 0.02079153060913086s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.818771362304688e-05s
Believability | Calculation of trust value for ZBW Labs took 1.1682510375976562e-05s
INFO | --- Analysis for zbw-labs took 1.7542214393615723s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.3775317668914795s
Availability | VoID file availability check for 20th Century Press Archives took 0.0004744529724121094s
Extra | Recovery of all triples for 20th Century Press Archives took 40.89129137992859s
Performance | Total latancy measurement for 20th Century Press Archives took 0.6687099933624268s
Amount of data | Number of triples check for 20th Century Press Archives took 2.4448797702789307s
Interoperability | New terms check for 20th Century Press Archives took 1.9777581691741943s
Versatility | Languages check for 20th Century Press Archives took 7.286458492279053s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 1.4110167026519775s
Interpretability | RDF structures check for 20th Century Press Archives took 0.14353370666503906s
Versatility | Serialization formats check for 20th Century Press Archives took 0.14350247383117676s
Availability | RDF dump link check for 20th Century Press Archives took 0.16071534156799316s
License | MR license check for 20th Century Press Archives took 0.14965057373046875s
License | HR license check for 20th Century Press Archives took 7.29921817779541s
Amount of data | Number of property check for 20th Century Press Archives took 0.12828421592712402s
Understandability | Number of label check for 20th Century Press Archives took 0.5426895618438721s
Understandability | URI regex check for 20th Century Press Archives took 0.27747488021850586s
Understandability | Vocabs check for 20th Century Press Archives took 0.1283860206604004s
Verifiability | Authors check for 20th Century Press Archives took 0.14436888694763184s
Verifiability | Publishers check for 20th Century Press Archives took 0.14926433563232422s
Performance | Throughput check for 20th Century Press Archives took 10.574261903762817s
Amount of data | Check the number of entities for 20th Century Press Archives took 0.00010347366333007812s
Verifiability | Contribs. check for 20th Century Press Archives took 0.13019156455993652s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.14485430717468262s
Interlinking | skos check for 20th Century Press Archives took 0.17517495155334473s
Interlinking | skos check for 20th Century Press Archives took 0.16998052597045898s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.1271193027496338s
Currency | Creation date check for 20th Century Press Archives took 0.2535529136657715s
Currency | Modification date check for 20th Century Press Archives took 0.25765538215637207s
Rep.Conc. | URIs length for 20th Century Press Archives took 15.0772123336792s
Interoperability | New vocabularies check for 20th Century Press Archives took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.14867544174194336s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.12946295738220215s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.1397242546081543s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 4.703855037689209s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8704342842102051s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.059191942214966s
Consistency | Disjoint class check for 20th Century Press Archives took 1.7308464050292969s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.3866915702819824s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.460883378982544s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 6.943236589431763s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 4.416900157928467s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7367453575134277s
Security | Sign check for 20th Century Press Archives took 0.13293743133544922s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 998.1016430854797s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.24406862258911133s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021759033203125s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00010323524475097656s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 2.1457672119140625e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.2874603271484375e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1135.8970963954926s
Availability | SPARQL endpoint availability check for zhishi.lemon took 8.392333984375e-05s
Availability | VoID file availability check for zhishi.lemon took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.16411519050598145s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.022368907928466797s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.506111145019531e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.2874603271484375e-05s
INFO | --- Analysis for zhishi-lemon took 1.7695331573486328s
Availability | SPARQL endpoint availability check for Zhishi.me took 9.107589721679688e-05s
Availability | VoID file availability check for Zhishi.me took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.1563701629638672s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 6.961822509765625e-05s
Believability | Calculation of trust value for Zhishi.me took 1.2636184692382812e-05s
INFO | --- Analysis for zhishi-me took 1.805112600326538s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.291534423828125e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.16345930099487305s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 6.079673767089844e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.1920928955078125e-05s
INFO | --- Analysis for zitgist-musicbrainz took 1.7685275077819824s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 8.392333984375e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.1552259922027588s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.02037668228149414s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 2.8848648071289062e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.0728836059570312e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 1.788374662399292s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.2948944568634033s
Availability | VoID file availability check for performing-arts.ch took 0.0005056858062744141s
Extra | Recovery of all triples for performing-arts.ch took 16.702812671661377s
Performance | Total latancy measurement for performing-arts.ch took 0.693244457244873s
Amount of data | Number of triples check for performing-arts.ch took 51.61612153053284s
Interoperability | New terms check for performing-arts.ch took 1.5183253288269043s
Versatility | Languages check for performing-arts.ch took 60.12036728858948s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.11718535423279s
Interpretability | RDF structures check for performing-arts.ch took 0.3708059787750244s
Versatility | Serialization formats check for performing-arts.ch took 0.15421819686889648s
Availability | RDF dump link check for performing-arts.ch took 0.1378767490386963s
License | MR license check for performing-arts.ch took 0.13686156272888184s
License | HR license check for performing-arts.ch took 60.11633348464966s
Amount of data | Number of property check for performing-arts.ch took 0.15825510025024414s
Understandability | Number of label check for performing-arts.ch took 3.840602159500122s
Understandability | URI regex check for performing-arts.ch took 0.2853572368621826s
Understandability | Vocabs check for performing-arts.ch took 0.1396176815032959s
Verifiability | Authors check for performing-arts.ch took 0.14904379844665527s
Verifiability | Publishers check for performing-arts.ch took 0.14380097389221191s
Performance | Throughput check for performing-arts.ch took 11.113424301147461s
Amount of data | Check the number of entities for performing-arts.ch took 0.0001068115234375s
Verifiability | Contribs. check for performing-arts.ch took 0.142958402633667s
Interlinking | sameAs chians check for performing-arts.ch took 1.1119725704193115s
Interlinking | skos check for performing-arts.ch took 0.1544187068939209s
Interlinking | skos check for performing-arts.ch took 0.15354108810424805s
Timeliness | dataset update frequency check for performing-arts.ch took 0.1467757225036621s
Currency | Creation date check for performing-arts.ch took 0.29679250717163086s
Currency | Modification date check for performing-arts.ch took 0.30143284797668457s
Rep.Conc. | URIs length for performing-arts.ch took 23.685661554336548s
Interoperability | New vocabularies check for performing-arts.ch took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.14392495155334473s
Accuracy | Check Functional Property for performing-arts.ch took 0.1389615535736084s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.1494448184967041s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.078826665878296s
Accuracy | Check White space in annotation for performing-arts.ch took 2.500551700592041s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.732391834259033s
Consistency | Disjoint class check for performing-arts.ch took 0.14524173736572266s
Consistency | Check Misplaced properties for performing-arts.ch took 0.37845826148986816s
Consistency | Misplaced classes for performing-arts.ch took 8.438666820526123s
Consistency | Check Ontology hijacking for performing-arts.ch took 43.43752837181091s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 16490.49017047882s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.800619125366211s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.8544514179229736s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.28270697593688965s
Security | Sign check for performing-arts.ch took 0.14319944381713867s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.23138689994812s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.42764759063720703s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.020981311798095703s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 2.384185791015625e-06s
Believability | Calculation of trust value for performing-arts.ch took 4.76837158203125e-06s
INFO | --- Analysis for performing-arts.ch took 17251.78801894188s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.4170830249786377s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.1605393886566162s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.1682510375976562e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for The-AA-Thesaurus took 7.392552614212036s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.3022279739379883s
Availability | VoID file availability check for MiMoTextBase took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.15546083450317383s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.026386499404907227s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 3.409385681152344e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0021970272064208984s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 2.9087066650390625e-05s
Believability | Calculation of trust value for MiMoTextBase took 9.059906005859375e-06s
INFO | --- Analysis for MiMoTextBase took 4.333169460296631s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.4700338840484619s
Availability | VoID file availability check for National Library of Sweden took 0.0005183219909667969s
Extra | Recovery of all triples for National Library of Sweden took 5.759291887283325s
Performance | Total latancy measurement for National Library of Sweden took 0.989142656326294s
Amount of data | Number of triples check for National Library of Sweden took 18.75975513458252s
Interoperability | New terms check for National Library of Sweden took 16.740995407104492s
Versatility | Languages check for National Library of Sweden took 0.19736695289611816s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.21851420402527s
Interpretability | RDF structures check for National Library of Sweden took 0.32665300369262695s
Versatility | Serialization formats check for National Library of Sweden took 0.22887015342712402s
Availability | RDF dump link check for National Library of Sweden took 0.1957850456237793s
License | MR license check for National Library of Sweden took 0.20328092575073242s
License | HR license check for National Library of Sweden took 0.1996173858642578s
Amount of data | Number of property check for National Library of Sweden took 0.20088553428649902s
Understandability | Number of label check for National Library of Sweden took 0.21329641342163086s
Understandability | URI regex check for National Library of Sweden took 0.4087386131286621s
Understandability | Vocabs check for National Library of Sweden took 0.19707822799682617s
Verifiability | Authors check for National Library of Sweden took 0.20962095260620117s
Verifiability | Publishers check for National Library of Sweden took 0.20268702507019043s
Performance | Throughput check for National Library of Sweden took 11.603878021240234s
Amount of data | Check the number of entities for National Library of Sweden took 4.315376281738281e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.19118142127990723s
Interlinking | sameAs chians check for National Library of Sweden took 0.19955968856811523s
Interlinking | skos check for National Library of Sweden took 0.19430041313171387s
Interlinking | skos check for National Library of Sweden took 0.19180846214294434s
Timeliness | dataset update frequency check for National Library of Sweden took 0.1916666030883789s
Currency | Creation date check for National Library of Sweden took 0.3839421272277832s
Currency | Modification date check for National Library of Sweden took 0.41672396659851074s
Rep.Conc. | URIs length for National Library of Sweden took 81.58704829216003s
Interoperability | New vocabularies check for National Library of Sweden took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.2224886417388916s
Accuracy | Check Functional Property for National Library of Sweden took 0.19985294342041016s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.21635890007019043s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2725379467010498s
Consistency | Disjoint class check for National Library of Sweden took 0.20189523696899414s
Consistency | Check Misplaced properties for National Library of Sweden took 60.94956111907959s
Consistency | Misplaced classes for National Library of Sweden took 1.0993189811706543s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.6076717376708984s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.3021180629730225s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 61.81851315498352s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.2730214595794678s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.3423161506652832s
Security | Sign check for National Library of Sweden took 0.22794818878173828s
Availability | Check URIs Dereferenciability for National Library of Sweden took 12.904460191726685s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.33977365493774414s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020282268524169922s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.3589859008789062e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 3.5762786865234375e-06s
Believability | Calculation of trust value for National Library of Sweden took 7.3909759521484375e-06s
INFO | --- Analysis for NLS took 1395.4563612937927s
Availability | SPARQL endpoint availability check for Japan Search took 1.1524558067321777s
Availability | VoID file availability check for Japan Search took 0.0003998279571533203s
Extra | Recovery of all triples for Japan Search took 3.463562250137329s
Performance | Total latancy measurement for Japan Search took 2.131643533706665s
Amount of data | Number of triples check for Japan Search took 5.0526745319366455s
Interoperability | New terms check for Japan Search took 3.736524820327759s
Versatility | Languages check for Japan Search took 0.7234370708465576s
Interpretability | Number of blank nodes check for Japan Search took 12.279507875442505s
Interpretability | RDF structures check for Japan Search took 0.9188377857208252s
Versatility | Serialization formats check for Japan Search took 0.8426151275634766s
Availability | RDF dump link check for Japan Search took 0.3059074878692627s
License | MR license check for Japan Search took 0.49106860160827637s
License | HR license check for Japan Search took 10.276625394821167s
Amount of data | Number of property check for Japan Search took 0.7309455871582031s
Understandability | Number of label check for Japan Search took 2.510679006576538s
Understandability | URI regex check for Japan Search took 1.0066039562225342s
Understandability | Vocabs check for Japan Search took 0.2690279483795166s
Verifiability | Authors check for Japan Search took 0.29798245429992676s
Verifiability | Publishers check for Japan Search took 0.26042795181274414s
Performance | Throughput check for Japan Search took 10.528594970703125s
Amount of data | Check the number of entities for Japan Search took 6.031990051269531e-05s
Verifiability | Contribs. check for Japan Search took 0.2618684768676758s
Interlinking | sameAs chians check for Japan Search took 0.2621450424194336s
Interlinking | skos check for Japan Search took 0.28589892387390137s
Interlinking | skos check for Japan Search took 0.26565980911254883s
Timeliness | dataset update frequency check for Japan Search took 0.3331010341644287s
Currency | Creation date check for Japan Search took 0.5322885513305664s
Currency | Modification date check for Japan Search took 0.5223574638366699s
Rep.Conc. | URIs length for Japan Search took 13.677724599838257s
Interoperability | New vocabularies check for Japan Search took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.7168686389923096s
Accuracy | Check Empty annotation labels for Japan Search took 0.6400182247161865s
Accuracy | Check White space in annotation for Japan Search took 0.029125452041625977s
Accuracy | Check Datatype consistency for Japan Search took 0.02973151206970215s
Consistency | Disjoint class check for Japan Search took 0.2639436721801758s
Consistency | Check Misplaced properties for Japan Search took 10.76471471786499s
Consistency | Misplaced classes for Japan Search took 1.0396578311920166s
Consistency | Check Ontology hijacking for Japan Search took 3.5100290775299072s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.355536937713623s
Consistency | Check Invalid usage of undefined properties for Japan Search took 12.310076236724854s
Conciseness | Check Extensional conciseness for Japan Search took 0.03741955757141113s
Conciseness | Check Intensional conciseness for Japan Search took 0.9515976905822754s
Security | Sign check for Japan Search took 0.2685225009918213s
Availability | Check URIs Dereferenciability for Japan Search took 13.795413255691528s
Completeness | Calculation of interlinking completeness for Japan Search took 0.1580219268798828s
Reputation | Calculation of the PageRank for Japan Search took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.6689300537109375e-06s
Believability | Calculation of trust value for Japan Search took 9.5367431640625e-06s
INFO | --- Analysis for Japan-Search took 380.45046639442444s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.078798532485962s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.1691761016845703s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.1682510375976562e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 9.298324584960938e-06s
INFO | --- Analysis for Rijksmuseum took 3.4186830520629883s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.3458590507507324s
Availability | VoID file availability check for Finnish Public Libraries took 0.0007040500640869141s
Extra | Recovery of all triples for Finnish Public Libraries took 14.100148916244507s
Performance | Total latancy measurement for Finnish Public Libraries took 1.383673906326294s
Amount of data | Number of triples check for Finnish Public Libraries took 51.76697564125061s
Interoperability | New terms check for Finnish Public Libraries took 12.952104091644287s
Versatility | Languages check for Finnish Public Libraries took 60.652143716812134s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 54.218886375427246s
Interpretability | RDF structures check for Finnish Public Libraries took 0.32001519203186035s
Versatility | Serialization formats check for Finnish Public Libraries took 0.26408910751342773s
Availability | RDF dump link check for Finnish Public Libraries took 0.24489164352416992s
License | MR license check for Finnish Public Libraries took 0.350588321685791s
License | HR license check for Finnish Public Libraries took 33.39290475845337s
Amount of data | Number of property check for Finnish Public Libraries took 0.11426854133605957s
Understandability | Number of label check for Finnish Public Libraries took 11.485468626022339s
Understandability | URI regex check for Finnish Public Libraries took 0.7971389293670654s
Understandability | Vocabs check for Finnish Public Libraries took 0.10907173156738281s
Verifiability | Authors check for Finnish Public Libraries took 0.9770722389221191s
Verifiability | Publishers check for Finnish Public Libraries took 0.11547541618347168s
Performance | Throughput check for Finnish Public Libraries took 11.888123512268066s
Amount of data | Check the number of entities for Finnish Public Libraries took 6.937980651855469e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.2647426128387451s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.4394559860229492s
Interlinking | skos check for Finnish Public Libraries took 0.11453056335449219s
Interlinking | skos check for Finnish Public Libraries took 0.26276540756225586s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.26937007904052734s
Currency | Creation date check for Finnish Public Libraries took 0.538813591003418s
Currency | Modification date check for Finnish Public Libraries took 0.38136982917785645s
Rep.Conc. | URIs length for Finnish Public Libraries took 75.00410676002502s
Interoperability | New vocabularies check for Finnish Public Libraries took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.46694469451904297s
Accuracy | Check Functional Property for Finnish Public Libraries took 0.3625645637512207s
Accuracy | Check Inverse Functional Property for Finnish Public Libraries took 0.2967383861541748s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 7.9463512897491455s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.1494781970977783s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.354503631591797s
Consistency | Disjoint class check for Finnish Public Libraries took 0.2621612548828125s
Consistency | Check Misplaced properties for Finnish Public Libraries took 53.544121742248535s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 13.806407928466797s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.566504716873169s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 56.35531258583069s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.7061049938201904s
Security | Sign check for Finnish Public Libraries took 0.7946460247039795s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.4098374843597412s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.3579890727996826s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.021079301834106445s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.7881393432617188e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 2.384185791015625e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 1.0251998901367188e-05s
INFO | --- Analysis for FI-Library took 663.3319251537323s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 63.79121804237366s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.16077280044555664s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.021136999130249023s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.2636184692382812e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.0013580322265625e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 77.42547297477722s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.4327130317687988s
Availability | VoID file availability check for National Library Netherlands took 0.0005698204040527344s
Extra | Recovery of all triples for National Library Netherlands took 0.6597123146057129s
Performance | Total latancy measurement for National Library Netherlands took 0.7698338031768799s
Amount of data | Number of triples check for National Library Netherlands took 0.14250493049621582s
Interoperability | New terms check for National Library Netherlands took 1.4356162548065186s
Versatility | Languages check for National Library Netherlands took 58.12693643569946s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.14883875846862793s
Interpretability | RDF structures check for National Library Netherlands took 0.14594125747680664s
Versatility | Serialization formats check for National Library Netherlands took 0.15420269966125488s
Availability | RDF dump link check for National Library Netherlands took 0.14935040473937988s
License | MR license check for National Library Netherlands took 0.1410369873046875s
License | HR license check for National Library Netherlands took 0.18189311027526855s
Amount of data | Number of property check for National Library Netherlands took 0.14019322395324707s
Understandability | Number of label check for National Library Netherlands took 0.1678152084350586s
Understandability | URI regex check for National Library Netherlands took 0.30266666412353516s
Understandability | Vocabs check for National Library Netherlands took 0.16816306114196777s
Verifiability | Authors check for National Library Netherlands took 0.15461373329162598s
Verifiability | Publishers check for National Library Netherlands took 0.1435222625732422s
Performance | Throughput check for National Library Netherlands took 10.238647937774658s
Amount of data | Check the number of entities for National Library Netherlands took 7.200241088867188e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.15155768394470215s
Interlinking | sameAs chians check for National Library Netherlands took 0.14203572273254395s
Interlinking | skos check for National Library Netherlands took 0.1514599323272705s
Interlinking | skos check for National Library Netherlands took 0.1744251251220703s
Timeliness | dataset update frequency check for National Library Netherlands took 0.1560382843017578s
Currency | Creation date check for National Library Netherlands took 0.28095078468322754s
Currency | Modification date check for National Library Netherlands took 0.28079771995544434s
Rep.Conc. | URIs length for National Library Netherlands took 0.6124012470245361s
Interoperability | New vocabularies check for National Library Netherlands took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.14193511009216309s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.41590023040771484s
Accuracy | Check White space in annotation for National Library Netherlands took 0.0267789363861084s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.0274655818939209s
Consistency | Disjoint class check for National Library Netherlands took 0.1344912052154541s
Consistency | Check Misplaced properties for National Library Netherlands took 0.29341864585876465s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.7227907180786133s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.3129627704620361s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.4961493015289307s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.031688690185546875s
Security | Sign check for National Library Netherlands took 0.14818382263183594s
Availability | Check URIs Dereferenciability for National Library Netherlands took 5.5737080574035645s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.2061316967010498s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.021668672561645508s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.0013580322265625e-05s
INFO | --- Analysis for National-Library-Netherlands took 165.9431347846985s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.4293556213378906s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.15780305862426758s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0009512901306152344s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.811981201171875e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.1682510375976562e-05s
INFO | --- Analysis for Antique-Renaissance took 4.200865030288696s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 6.828532934188843s
Availability | VoID file availability check for ARTSDATA.CA took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.15582489967346191s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.021083831787109375s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.049041748046875e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.1920928955078125e-05s
INFO | --- Analysis for ARTSDATA-CA took 10.840494871139526s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.1436786651611328s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.1533660888671875s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.0967254638671875e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 1.1682510375976562e-05s
INFO | --- Analysis for ArCo took 2.125199317932129s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3104383945465088s
Availability | VoID file availability check for ConfermentSampo took 0.0004999637603759766s
Extra | Recovery of all triples for ConfermentSampo took 6.65575098991394s
Performance | Total latancy measurement for ConfermentSampo took 0.7666499614715576s
Amount of data | Number of triples check for ConfermentSampo took 0.1717972755432129s
Interoperability | New terms check for ConfermentSampo took 1.5297915935516357s
Versatility | Languages check for ConfermentSampo took 0.17275500297546387s
Interpretability | Number of blank nodes check for ConfermentSampo took 0.17194795608520508s
Security | Check HTTPS for ConfermentSampo took 0.3801693916320801s
Interpretability | RDF structures check for ConfermentSampo took 0.17346906661987305s
Versatility | Serialization formats check for ConfermentSampo took 0.1727440357208252s
Availability | RDF dump link check for ConfermentSampo took 2.8771369457244873s
License | MR license check for ConfermentSampo took 0.17252111434936523s
License | HR license check for ConfermentSampo took 0.14910316467285156s
Amount of data | Number of property check for ConfermentSampo took 0.17574334144592285s
Understandability | Number of label check for ConfermentSampo took 0.17309975624084473s
Understandability | URI regex check for ConfermentSampo took 0.3207285404205322s
Understandability | Vocabs check for ConfermentSampo took 0.14862465858459473s
Verifiability | Authors check for ConfermentSampo took 0.1729729175567627s
Verifiability | Publishers check for ConfermentSampo took 0.17234277725219727s
Performance | Throughput check for ConfermentSampo took 10.4457528591156s
Amount of data | Check the number of entities for ConfermentSampo took 0.00018930435180664062s
Verifiability | Contribs. check for ConfermentSampo took 0.14861798286437988s
Interlinking | sameAs chians check for ConfermentSampo took 0.17278718948364258s
Interlinking | skos check for ConfermentSampo took 0.1491713523864746s
Interlinking | skos check for ConfermentSampo took 0.14911890029907227s
Timeliness | dataset update frequency check for ConfermentSampo took 0.14974665641784668s
Currency | Creation date check for ConfermentSampo took 0.326617956161499s
Currency | Modification date check for ConfermentSampo took 0.3208944797515869s
Rep.Conc. | URIs length for ConfermentSampo took 11.186782121658325s
Interoperability | New vocabularies check for ConfermentSampo took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.17899441719055176s
Accuracy | Check Functional Property for ConfermentSampo took 0.1755049228668213s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.14813661575317383s
Accuracy | Check Empty annotation labels for ConfermentSampo took 8.345626831054688s
Accuracy | Check White space in annotation for ConfermentSampo took 2.991952419281006s
Consistency | Disjoint class check for ConfermentSampo took 0.14837121963500977s
Consistency | Check Misplaced properties for ConfermentSampo took 0.39562225341796875s
Consistency | Check Ontology hijacking for ConfermentSampo took 17.381470441818237s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.5167748928070068s
Conciseness | Check Extensional conciseness for ConfermentSampo took 0.00013327598571777344s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.17221713066101074s
Security | Sign check for ConfermentSampo took 0.14900565147399902s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1212.4772832393646s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.44919776916503906s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.022124052047729492s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.5020370483398438e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 5.4836273193359375e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.1205673217773438e-05s
INFO | --- Analysis for ConfermentSampo took 1334.3410468101501s
Availability | SPARQL endpoint availability check for Museum Finland took 0.17334699630737305s
Availability | VoID file availability check for Museum Finland took 0.00046563148498535156s
Extra | Recovery of all triples for Museum Finland took 3.689028739929199s
Performance | Total latancy measurement for Museum Finland took 0.7671184539794922s
Amount of data | Number of triples check for Museum Finland took 0.1719048023223877s
Interoperability | New terms check for Museum Finland took 1.533630609512329s
Versatility | Languages check for Museum Finland took 0.1722562313079834s
Interpretability | Number of blank nodes check for Museum Finland took 0.1721174716949463s
Security | Check HTTPS for Museum Finland took 0.22936081886291504s
Interpretability | RDF structures check for Museum Finland took 0.17161226272583008s
Versatility | Serialization formats check for Museum Finland took 0.1752767562866211s
Availability | RDF dump link check for Museum Finland took 0.1475963592529297s
License | MR license check for Museum Finland took 0.14783453941345215s
License | HR license check for Museum Finland took 0.16399931907653809s
Amount of data | Number of property check for Museum Finland took 0.17328691482543945s
Understandability | Number of label check for Museum Finland took 0.17146897315979004s
Understandability | URI regex check for Museum Finland took 0.2947721481323242s
Understandability | Vocabs check for Museum Finland took 0.14736723899841309s
Verifiability | Authors check for Museum Finland took 0.14775395393371582s
Verifiability | Publishers check for Museum Finland took 0.14831233024597168s
Performance | Throughput check for Museum Finland took 10.474879264831543s
Amount of data | Check the number of entities for Museum Finland took 0.00012230873107910156s
Verifiability | Contribs. check for Museum Finland took 0.1485903263092041s
Interlinking | sameAs chians check for Museum Finland took 0.15014910697937012s
Interlinking | skos check for Museum Finland took 0.14848709106445312s
Interlinking | skos check for Museum Finland took 0.1486530303955078s
Timeliness | dataset update frequency check for Museum Finland took 0.14870882034301758s
Currency | Creation date check for Museum Finland took 0.32341980934143066s
Currency | Modification date check for Museum Finland took 0.3210642337799072s
Rep.Conc. | URIs length for Museum Finland took 2.5428225994110107s
Interoperability | New vocabularies check for Museum Finland took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.1719822883605957s
Accuracy | Check Functional Property for Museum Finland took 0.14843130111694336s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.1488175392150879s
Accuracy | Check Empty annotation labels for Museum Finland took 0.8258652687072754s
Accuracy | Check White space in annotation for Museum Finland took 0.06097126007080078s
Accuracy | Check Datatype consistency for Museum Finland took 0.9609065055847168s
Consistency | Disjoint class check for Museum Finland took 0.14894628524780273s
Consistency | Check Misplaced properties for Museum Finland took 0.29650306701660156s
Consistency | Check Ontology hijacking for Museum Finland took 2.0015225410461426s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.3471078872680664s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.50606369972229s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6445167064666748s
Conciseness | Check Intensional conciseness for Museum Finland took 0.17203712463378906s
Security | Sign check for Museum Finland took 0.14832758903503418s
Availability | Check URIs Dereferenciability for Museum Finland took 2940.1099667549133s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.24921059608459473s
Reputation | Calculation of the PageRank for Museum Finland took 0.021395444869995117s
Interlinking | Calculation of Degree of Connection for Museum Finland took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.8596649169921875e-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 2.0742416381835938e-05s
INFO | --- Analysis for FI-Museum took 2986.275341272354s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.17742109298706055s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0005297660827636719s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 12.177079200744629s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.7642874717712402s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 0.17078280448913574s
Interoperability | New terms check for Mapping Manuscript Migrations took 1.4892215728759766s
Versatility | Languages check for Mapping Manuscript Migrations took 0.17148160934448242s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 0.18630266189575195s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.3771970272064209s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.17276740074157715s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.17277288436889648s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.14858746528625488s
License | MR license check for Mapping Manuscript Migrations took 0.1716928482055664s
License | HR license check for Mapping Manuscript Migrations took 0.17299890518188477s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.17616653442382812s
Understandability | Number of label check for Mapping Manuscript Migrations took 0.17244887351989746s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3194601535797119s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.1485884189605713s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.17219066619873047s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.17209410667419434s
Performance | Throughput check for Mapping Manuscript Migrations took 10.461637020111084s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 0.9573869705200195s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.148468017578125s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.17397236824035645s
Interlinking | skos check for Mapping Manuscript Migrations took 0.1475236415863037s
Interlinking | skos check for Mapping Manuscript Migrations took 0.1486058235168457s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.14855241775512695s
Currency | Creation date check for Mapping Manuscript Migrations took 0.32594895362854004s
Currency | Modification date check for Mapping Manuscript Migrations took 0.1719193458557129s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 13.722333192825317s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.148057222366333s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.1490309238433838s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.1485438346862793s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 8.049922943115234s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.44551682472229s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.674858331680298s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.1721174716949463s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 0.3986043930053711s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 8.09248399734497s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.5919101238250732s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.5948455333709717s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.7827203273773193s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.1721818447113037s
Security | Sign check for Mapping Manuscript Migrations took 0.14767074584960938s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1252.2852926254272s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.9762027263641357s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.049041748046875e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 1.9073486328125e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.1920928955078125e-05s
INFO | --- Analysis for MMM took 1348.890858411789s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.17181801795959473s
Availability | VoID file availability check for Semantic Kalevala took 0.0004992485046386719s
Extra | Recovery of all triples for Semantic Kalevala took 4.5823118686676025s
Performance | Total latancy measurement for Semantic Kalevala took 0.7637181282043457s
Amount of data | Number of triples check for Semantic Kalevala took 0.17148900032043457s
Interoperability | New terms check for Semantic Kalevala took 1.4318361282348633s
Versatility | Languages check for Semantic Kalevala took 0.1715373992919922s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.17117762565612793s
Security | Check HTTPS for Semantic Kalevala took 0.22701644897460938s
Interpretability | RDF structures check for Semantic Kalevala took 0.17592525482177734s
Versatility | Serialization formats check for Semantic Kalevala took 0.18400049209594727s
Availability | RDF dump link check for Semantic Kalevala took 0.14980673789978027s
License | MR license check for Semantic Kalevala took 0.14926886558532715s
License | HR license check for Semantic Kalevala took 0.14850640296936035s
Amount of data | Number of property check for Semantic Kalevala took 0.1736922264099121s
Understandability | Number of label check for Semantic Kalevala took 0.17243027687072754s
Understandability | URI regex check for Semantic Kalevala took 0.29573607444763184s
Understandability | Vocabs check for Semantic Kalevala took 0.14887094497680664s
Verifiability | Authors check for Semantic Kalevala took 0.14841556549072266s
Verifiability | Publishers check for Semantic Kalevala took 0.1481156349182129s
Performance | Throughput check for Semantic Kalevala took 10.436248540878296s
Amount of data | Check the number of entities for Semantic Kalevala took 0.00011420249938964844s
Verifiability | Contribs. check for Semantic Kalevala took 0.14835596084594727s
Interlinking | sameAs chians check for Semantic Kalevala took 0.17139554023742676s
Interlinking | skos check for Semantic Kalevala took 0.17178821563720703s
Interlinking | skos check for Semantic Kalevala took 0.14847278594970703s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.14914727210998535s
Currency | Creation date check for Semantic Kalevala took 0.3246898651123047s
Currency | Modification date check for Semantic Kalevala took 0.32198572158813477s
Rep.Conc. | URIs length for Semantic Kalevala took 3.5931501388549805s
Interoperability | New vocabularies check for Semantic Kalevala took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.17142081260681152s
Accuracy | Check Functional Property for Semantic Kalevala took 0.17506074905395508s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.14821243286132812s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.449418544769287s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.2921149730682373s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.3799896240234375s
Consistency | Disjoint class check for Semantic Kalevala took 0.15015673637390137s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.32144784927368164s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.071042060852051s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.368682861328125s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.5373528003692627s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8840529918670654s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.17189455032348633s
Security | Sign check for Semantic Kalevala took 0.14800238609313965s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 3208.9959387779236s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.2833733558654785s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.596581220626831s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.33514404296875e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 2.1457672119140625e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.0728836059570312e-05s
INFO | --- Analysis for Semantic-Kalevala took 3259.6379232406616s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.851710319519043s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0007827281951904297s
Extra | Recovery of all triples for Smithsonian American Art Museum took 272.1875789165497s
Performance | Total latancy measurement for Smithsonian American Art Museum took 2.9168639183044434s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5903363227844238s
Interoperability | New terms check for Smithsonian American Art Museum took 3.488877773284912s
Versatility | Languages check for Smithsonian American Art Museum took 28.2089741230011s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5622665882110596s
Security | Check HTTPS for Smithsonian American Art Museum took 0.35961103439331055s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.5847432613372803s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.5716066360473633s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.5957455635070801s
License | MR license check for Smithsonian American Art Museum took 0.5710771083831787s
License | HR license check for Smithsonian American Art Museum took 17.638065338134766s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5641119480133057s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5639979839324951s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1425635814666748s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.570631742477417s
Verifiability | Authors check for Smithsonian American Art Museum took 0.5699126720428467s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5815777778625488s
Performance | Throughput check for Smithsonian American Art Museum took 11.390818357467651s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.224082946777344e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.569582462310791s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5657224655151367s
Interlinking | skos check for Smithsonian American Art Museum took 0.5631206035614014s
Interlinking | skos check for Smithsonian American Art Museum took 0.5625536441802979s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5700867176055908s
Currency | Creation date check for Smithsonian American Art Museum took 1.1411418914794922s
Currency | Modification date check for Smithsonian American Art Museum took 1.1519172191619873s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 101.42627573013306s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5675716400146484s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 18.93584156036377s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.49253296852111816s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.214239835739136s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5623860359191895s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 3.978611707687378s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 96.53592276573181s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.6462945938110352s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.797767162322998s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.8564536571502686s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.5681362152099609s
Security | Sign check for Smithsonian American Art Museum took 0.568878173828125s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.158245086669922s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.4678359031677246s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.1920928955078125e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.1457672119140625e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 7.867813110351562e-06s
INFO | --- Analysis for Smithsonian took 631.6241693496704s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.19454193115234375s
Availability | VoID file availability check for Zeri Photo Archive took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.16036105155944824s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.021474123001098633s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.1205673217773438e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.1205673217773438e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 8.66236400604248s
Availability | SPARQL endpoint availability check for Archives Hub took 21.39704179763794s
Availability | VoID file availability check for Archives Hub took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.15395736694335938s
Reputation | Calculation of the PageRank for Archives Hub took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for Archives Hub took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.811981201171875e-05s
Believability | Calculation of trust value for Archives Hub took 9.775161743164062e-06s
INFO | --- Analysis for Archives-Hub took 53.218013048172s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 0.9730415344238281s
Availability | VoID file availability check for Yale centre of British Art took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.16243886947631836s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.021346569061279297s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0008788108825683594s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.1205673217773438e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.0013580322265625e-05s
INFO | --- Analysis for Yale took 2.7306182384490967s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.6484327316284s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.1672813892364502s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.0208127498626709s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.0967254638671875e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.049041748046875e-05s
INFO | --- Analysis for ADL took 535.3440401554108s
Availability | SPARQL endpoint availability check for MusicKG took 0.7680850028991699s
Availability | VoID file availability check for MusicKG took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for MusicKG took 0.15644502639770508s
Reputation | Calculation of the PageRank for MusicKG took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.1682510375976562e-05s
Believability | Calculation of trust value for MusicKG took 4.76837158203125e-06s
INFO | --- Analysis for MusicKG took 2.8403050899505615s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.7857298851013184s
Availability | VoID file availability check for CIDOC-CRM took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.16355204582214355s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.2636184692382812e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.0251998901367188e-05s
INFO | --- Analysis for CIDOC-CRM took 2.7658302783966064s
Availability | SPARQL endpoint availability check for Mondis took 0.2791905403137207s
Availability | VoID file availability check for Mondis took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Mondis took 0.15903854370117188s
Reputation | Calculation of the PageRank for Mondis took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Mondis took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.1682510375976562e-05s
Believability | Calculation of trust value for Mondis took 1.1920928955078125e-05s
INFO | --- Analysis for Mondis took 2.017409563064575s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.486647129058838s
Availability | VoID file availability check for DigitalNZ took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.1555769443511963s
Reputation | Calculation of the PageRank for DigitalNZ took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.0967254638671875e-05s
Believability | Calculation of trust value for DigitalNZ took 1.1682510375976562e-05s
INFO | --- Analysis for DigitalNZ took 6.166469573974609s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.16886138916015625s
Availability | VoID file availability check for Fondazione Zeri took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.1524033546447754s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.0203096866607666s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.1682510375976562e-05s
Believability | Calculation of trust value for Fondazione Zeri took 9.5367431640625e-06s
INFO | --- Analysis for Fondazione-Zeri took 2.0200600624084473s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.17687463760375977s
Availability | VoID file availability check for Digital Public Library of America took 0.0003180503845214844s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.153717041015625s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.1444091796875e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.0251998901367188e-05s
INFO | --- Analysis for Library-of-America took 2.6877307891845703s
Availability | SPARQL endpoint availability check for Auckland Museum took 2.0378313064575195s
Availability | VoID file availability check for Auckland Museum took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.16027450561523438s
Reputation | Calculation of the PageRank for Auckland Museum took 0.02216196060180664s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.1444091796875e-05s
Believability | Calculation of trust value for Auckland Museum took 1.0728836059570312e-05s
INFO | --- Analysis for Auckland-Museum took 5.457594394683838s
Availability | SPARQL endpoint availability check for National Library of Spain took 3.810457706451416s
Availability | VoID file availability check for National Library of Spain took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.1621236801147461s
Reputation | Calculation of the PageRank for National Library of Spain took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.0013580322265625e-05s
Believability | Calculation of trust value for National Library of Spain took 1.0967254638671875e-05s
INFO | --- Analysis for BNE took 5.645846843719482s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.2641828060150146s
Availability | VoID file availability check for National Library of Korea took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.1508471965789795s
Reputation | Calculation of the PageRank for National Library of Korea took 0.023135900497436523s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.0728836059570312e-05s
Believability | Calculation of trust value for National Library of Korea took 1.0967254638671875e-05s
INFO | --- Analysis for Korea-Library took 2.992053985595703s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.230994462966919s
Availability | VoID file availability check for The State Russian Museum took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.1539151668548584s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020998239517211914s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.0967254638671875e-05s
Believability | Calculation of trust value for The State Russian Museum took 8.821487426757812e-06s
INFO | --- Analysis for Russian-Museum took 2.961235284805298s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.655250072479248s
Availability | VoID file availability check for National Library of Scotland took 0.0003275871276855469s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.1509249210357666s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.33514404296875e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.1920928955078125e-05s
INFO | --- Analysis for National-Library-of-Scotland took 5.754268169403076s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.29207396507263184s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.15784907341003418s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.02192831039428711s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.1682510375976562e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 4.76837158203125e-06s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 2.134241819381714s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.19336771965026855s
Availability | VoID file availability check for OntoComedySources took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.15329217910766602s
Reputation | Calculation of the PageRank for OntoComedySources took 0.020394563674926758s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.049041748046875e-05s
Believability | Calculation of trust value for OntoComedySources took 5.9604644775390625e-06s
INFO | --- Analysis for OntoComedySources took 3.5140063762664795s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.1942753791809082s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.15852856636047363s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.020212173461914062s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.0967254638671875e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.049041748046875e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 3.233586072921753s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.32721853256225586s
Availability | VoID file availability check for SaintGall Ontology took 0.00021004676818847656s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.15819001197814941s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.020319223403930664s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.1920928955078125e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for SaintGall-Ontology took 2.176894187927246s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.8442974090576172s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.1634688377380371s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.1682510375976562e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 2.7857589721679688s
Availability | SPARQL endpoint availability check for ICON took 0.2249152660369873s
Availability | VoID file availability check for ICON took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for ICON took 0.15906143188476562s
Reputation | Calculation of the PageRank for ICON took 0.02295064926147461s
Interlinking | Calculation of Degree of Connection for ICON took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for ICON took 1.0967254638671875e-05s
Believability | Calculation of trust value for ICON took 1.1682510375976562e-05s
INFO | --- Analysis for ICON took 2.8510138988494873s
Availability | SPARQL endpoint availability check for Polifonia took 0.25810766220092773s
Availability | VoID file availability check for Polifonia took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Polifonia took 0.16243934631347656s
Reputation | Calculation of the PageRank for Polifonia took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.1205673217773438e-05s
Believability | Calculation of trust value for Polifonia took 1.049041748046875e-05s
INFO | --- Analysis for Polifonia took 3.157726526260376s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.24840140342712402s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.173020601272583s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020334243774414062s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.1444091796875e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 9.775161743164062e-06s
INFO | --- Analysis for Atlas-of-Paths took 2.57943058013916s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.1904315948486328s
Availability | VoID file availability check for Music Note Ontology took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.16142678260803223s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.1682510375976562e-05s
Believability | Calculation of trust value for Music Note Ontology took 1.1444091796875e-05s
INFO | --- Analysis for Music-Note-Ontology took 7.563578844070435s
Availability | SPARQL endpoint availability check for HaMSE took 0.19274568557739258s
Availability | VoID file availability check for HaMSE took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for HaMSE took 0.1631145477294922s
Reputation | Calculation of the PageRank for HaMSE took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.239776611328125e-05s
Believability | Calculation of trust value for HaMSE took 1.1920928955078125e-05s
INFO | --- Analysis for HaMSE took 7.167407035827637s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.09630012512207031s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.15589380264282227s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.021514892578125s
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.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.1920928955078125e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.239776611328125e-05s
INFO | --- Analysis for FOod took 3.542368173599243s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 1.033552646636963s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.16585350036621094s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.3113021850585938e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.0967254638671875e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 3.957106113433838s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.5543088912963867s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.15840768814086914s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.020786046981811523s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.1920928955078125e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 9.775161743164062e-06s
INFO | --- Analysis for ARIADNE took 4.497874021530151s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.3076801300048828s
Availability | VoID file availability check for Odeuropa Ontology took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.1534268856048584s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.020806550979614258s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.2636184692382812e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for Odeuropa took 2.153513193130493s

--- Total time for analysis:67983.58488082886s ---
--- Total time for analysis:18.884329133563572 hours ---